Skip to content
Council Discourse

NYC Council meetings, chaptered and linked by time.

Independent project. Not affiliated with the New York City Council.

Created by Uzair Qadir

Inspired by Vikram Oberoi's City Meetings

Q&A

Won questions firmware update frequency and post-update testing

New York City Council · Sep 9, 2026 · starts 1:31:56 · 2 min 8 sec

Council Member Won asks how often firmware updates happen and whether the city tests them. Barbera confirms hundreds of updates happen per year, with test protocols before, during, and after changes. Won presses that testing failed to catch the issue. Barbera explains the issue surfaced an hour after the change completed, during a period when validation showed successful calls.

Phil Wong

This is not the first time that Motorola updates the firmware to the firewalls or the routers.

Phil Wong

It happens many times in a year.

Phil Wong

Or whenever there are urgent security fixes, they will do it right away.

Phil Wong

Is that right?

Lisa Gelobter

They require approval, but it does.

Lisa Gelobter

These kinds of firmware upgrades do happen throughout the course of the year.

Phil Wong

Many times, right?

Robert Barbera

Hundreds of times.

Phil Wong

Hundreds, okay, yeah.

Phil Wong

So these updates, after they get updated, it is the city's responsibility to test the updates, whether they're working or whether they fail.

Phil Wong

Is that right?

Phil Wong

Or you just rely on Motorola.

Phil Wong

Motorola says, okay, I'm done, and then you don't do anything to verify whether everything works.

Robert Barbera

So based on the type of change that's happening, there are test protocols and test plans that are implemented before the change actually begins to validate that everything was working correctly before it started.

Robert Barbera

There's test procedures that happen throughout the change, and then there's...

Robert Barbera

Validation steps that happen once the change is complete.

Phil Wong

Okay, so was that done?

Phil Wong

Because it seemed to me that after the updates were in store,

Phil Wong

the testings or whatever testings you were doing failed to catch the issues.

Robert Barbera

So the testing was performed.

Robert Barbera

The issue didn't occur until an hour after the change was complete.

Robert Barbera

So that validation period actually had successful calls and successful monitoring.

Robert Barbera

And then the issue started after the change was over.

Phil Wong

Okay, go ahead.

Lisa Gelobter

I agree with everything my colleague said.

Lisa Gelobter

I will also say.

Lisa Gelobter

That not learning about the issue until 6 a.m.

Lisa Gelobter

Is something that we need to figure out how to get in front of.

Lisa Gelobter

So yes, it went through the testing protocols that had been written for this deemed low risk change.

Lisa Gelobter

And so that did happen.

Lisa Gelobter

It did not identify and catch these issues, which means that it needs to be improved.