De La Rosa questions timing disparity between 3:13 a.m. and 4:13 a.m.
De La Rosa presses Gelobter on the gap between the issue starting at 3:13 a.m. and the upgrade completing at 4:13 a.m. Gelobter explains the issue wasn't caught until 9:30 a.m. and acknowledges it should have been caught earlier, with a deep dive underway to understand why and what alerts can be added.
I know our colleagues have a lot of questions.
I want to walk back through your testimony and just talk a little bit about the timing of what occurred on August 18th.
So you testified that...
The change process began at 9.45 p.m.
On August 17 and completed at 4.13 a.m.
On August 18.
Later in the testimony, you revealed that callers were not able to hear 911 call takers and that the issue had started at 3.13 a.m.
So can you talk about the disparity between 3.13 a.m.
And 4.13 a.m.?
I can.
The issue was not caught until, we didn't understand that it was affecting 911 calls until about 9.30 in the morning.
9.30 in the morning.
So, yes, so even after the rollout was completed, the issue wasn't surfaced.
Eventually, call takers on the floor surfaced, again, issues around alarm calls.
But the answer was it wasn't caught, and obviously it should have been, and that's one of the things that we are doing a very thoughtful deep dive on to understand
not just what happened, how it is possible that the error was not caught, and then also what kind of alarms and alerts that we can put into place going forward so that
these things are caught and actioned much earlier.
Is it safe to say that the calls from the alarm companies to the NYPD at 7.30 is really what rang the alarm that something was critically wrong?