IT staff at Foster City, California, discovered ransomware spreading across the city’s networks in early March 2026. By morning nearly every non-emergency municipal service was offline: building permits, business licences, park reservations, public records requests and utility billing. Emergency services, including 911 and police dispatch, continued operating.
The Separation Held, And It Was Not Luck
Emergency dispatch surviving while permit systems did not is the single most important fact in this file. It indicates that the systems carrying life-safety functions sit on infrastructure that ransomware moving through the corporate network did not reach.
That separation is expensive to maintain and produces daily friction — separate credentials, separate support, duplicated work. It is exactly the kind of arrangement that gets questioned in budget reviews on the grounds that nothing has ever happened.
The Services That Failed Are Not Trivial
It is tempting to file a permit system outage as an inconvenience. For a construction firm with crews booked, a permit delay is payroll. For a household, a utility billing failure can mean a missed payment on a bill they cannot pay online — the pattern this desk filed at BridgePay in 26-0209.
Public records requests stopping also has a specific civic consequence: the mechanism by which residents and journalists scrutinise the city was unavailable, and there is no alternative provider.
Cities Cannot Route Around Themselves
A retailer taken offline loses customers to competitors. A city has no competitor. Residents who need a business licence cannot get one anywhere else, and the demand does not disappear during the outage — it queues and arrives all at once on restoration.
That is why municipal recovery timelines are longer than the technical restoration suggests, and why the visible impact continues well after systems come back.
Compiled from public reporting, listed below. No attribution has been established and we offer none. The scope of any data exfiltration has not been disclosed. Corrections: corrections@forensicpost.com.