Methodology and data sources
History begins November 5, 2026. Every number on the site comes from the snapshots described here.
The question
When fire weather hits California, how many customers lose power, and how long do they stay out? Utilities publish live outage maps. Cal OES pulls them into one statewide feed. That feed shows only the present, so a wind event disappears from it the moment power comes back. Gridwatch saves the feed every 15 minutes and lays Red Flag Warnings and fire perimeters on top, which makes past events replayable and measurable.
Data sources
Cal OES Statewide Power Outages
A public ArcGIS feature service (service directory) with three layers. Layer 0 holds outage incident points for every utility. Layer 1 holds outage area polygons that some utilities publish, PG&E most of all. Layer 2 totals outages by county. The service refreshes from utility outage maps about every 15 minutes. It keeps no history, and small municipal utilities report unevenly. A customer is one electric meter, which can be a whole household or a business. A utility's map can also trail conditions in the field.
National Weather Service alerts
Active alerts for California from api.weather.gov, filtered to Red Flag Warning, Fire Weather Watch, High Wind Warning, and Wind Advisory. Many alerts list fire weather zones and carry no polygon, so Gridwatch fetches each zone's outline and caches it. NWS Sacramento redrew its public and fire weather zones on April 16, 2026, so zones are refetched whenever an unfamiliar id appears. Alerts update as forecasters issue them.
NIFC WFIGS current perimeters
Current interagency wildfire perimeters from the NIFC open data site, filtered to fires whose point of origin is in California. Perimeters update as incident teams map them, often once or twice a day, and small fires may have only a placeholder.
Map layers
Basemap from OpenFreeMap with OpenStreetMap data. Terrain from the AWS Terrain Tiles open dataset. Address search uses Photon and OpenStreetMap Nominatim at no more than one request per second, and searches are not stored.
Snapshots
- Every 15 minutes a scheduled job in the database calls the snapshot function. A GitHub Actions workflow on the same cycle takes over when the newest snapshot is more than 30 minutes old.
- The function pages through every Cal OES layer 0 and layer 1 record. It then reads the NWS alerts and fills in zone outlines from the cache.
- All rows for one snapshot are written in a single transaction. When Cal OES fails to answer, the snapshot is marked failed and no outage is counted as ended.
- Detail rows for each snapshot are kept 90 days. Statewide counts stay indefinitely, as do the outage and event tables.
How each number is calculated
Customers out
The sum of impacted customers across all incident points in a snapshot, grouped by utility and by county, with planned and unplanned outages split apart.
customers_out = Σ ImpactedCustomers over incident points in the snapshotOutage duration
Each utility and incident id pair becomes one outage. It stays open while it appears in snapshots and closes after it is missing from two snapshots in a row. Duration starts at the utility's own start time when one is given and falls before Gridwatch first saw the outage. Otherwise it starts at the first snapshot that saw it. County pages report the median and the longest duration over 7 and 30 days.
duration = last_seen − (start_time if start_time ≤ first_seen, else first_seen)Fire-weather overlap
At each snapshot Gridwatch tests every outage point against the active Red Flag Warning polygons. The baseline uses the same zone outlines on snapshots from the past 30 days when no Red Flag Warning was active anywhere in the state. PSPS shutoffs and unplanned outages are reported separately, because utilities schedule shutoffs in response to the warnings themselves.
overlap = customers out inside Red Flag polygons / all customers out baseline = customers out inside the same zones / all customers out, on no-warning snapshots ratio = overlap / baselineThis is a correlation. A high ratio says outages cluster where the warning is. It does not say the weather caused them.
Events
An event opens when statewide customers out reaches 50,000. It closes once customers out has stayed under 10,000 for six hours. Both thresholds and the six-hour window live in a configuration table and can be tuned. The event slug combines the start date in Pacific time with the region carrying the most customers out at that moment.
Restoration curve
Statewide customers out from the event peak onward. Time to 50% restored is the first snapshot after the peak at or below half the peak. Time to 90% restored is the first at or below a tenth of it.
t50 = first t after peak where customers_out(t) ≤ 0.5 × peak t90 = first t after peak where customers_out(t) ≤ 0.1 × peakWhat the tool cannot tell you
Gridwatch cannot confirm that your own power is out or say when it will return. It also cannot confirm a planned shutoff for a specific address. Utility estimates for restoration appear as published and are often revised. Outage points mark an incident and can sit some distance from the homes it affects. A 15-minute snapshot can miss an outage that starts and ends between two snapshots.
Questions
Why does Gridwatch keep its own history?
The Cal OES outage service shows only the current state. Gridwatch saves a copy every 15 minutes so past wind events can be replayed and measured. History begins at the first saved snapshot.
Does a Red Flag Warning cause the outages shown inside it?
The overlap number is a correlation. Wind, dry fuel, planned shutoffs, and ordinary equipment failures all show up in the same data, and the tool has no way to separate their causes.
How is a PSPS shutoff told apart from other planned outages?
Cal OES marks each outage Planned or Not Planned. Gridwatch counts a planned outage as a PSPS shutoff when its cause text mentions a power shutoff or fire risk. Planned maintenance stays in its own group.
How current is the map?
Cal OES refreshes from utility outage maps about every 15 minutes, and Gridwatch snapshots on the same cycle. Utilities can lag their own field crews by 30 minutes or more.
Safety
For situational awareness only. Follow official alerts and evacuation orders. Official sources: PG&E outages, PG&E PSPS updates, SCE PSPS, SDG&E outage map, NWS Sacramento fire weather.
Changelog
- November 5, 2026. First release with the live map, a 48-hour replay, event and county pages, and the overlap readout.