Ask the Grid
Create free workspace

Outages & Grid Events

Generation and transmission outages, customer outage counts, and the alerts, advisories, and operating messages grid operators publish as conditions change.

44 datasetspublished by ATG DataUS reference14NYISO8ERCOT5SPP5ISONE4CAISO3MISO3PJM2

Outages & Grid Events datasets
DatasetRows
ISO-NEAlertsATG Data·ISONE·ISO-NE's published Alerts source feed. This catalog page exposes the physical schema, coverage, and latest source rows without inventing a normalized grain for publisher-shaped snapshot fields. Use the documented key and event time when comparing revisions or vintages.01970
BPA Planned Transmission OutagesATG Data·US reference·BPA's posted transmission outage plans (rolling year, monthly initial and final), every revision kept, one row per outage request.2.6K2023
BPA Transmission OutagesATG Data·US reference·Every outage in BPA's calendar-year outage reports (1999 onward) and Daily Interruptions Reports: customer service points, transmission lines and transformers.195.1K1988
SPPCompleted-year outage archiveATG Data·SPP·SPP's Completed-year outage archive. Each row preserves a publisher record, workbook row, or report document with its source member and row index. Source timestamps, units, geographic scope, and revision qualifiers are retained in record_json; event_time is collection time; completed_at is when the entire document became available.0—
CAISOCurtailed Non-Operational GeneratorsATG Data·CAISO·CAISO's prior-trade-date report of planned and forced generator curtailments. publish_time is the report vintage; curtailment start and end are the operating interval.519.4K2024
Customer Outages by CountyATG Data·US reference·Live county-level customer outage snapshots from ORNL/DOE's ODIN public county map API. Ask the Grid queries the nationwide grid='us' archive and derives each live product map from its exact state-FIPS scope, so every supported grid uses the same accumulated history. Each row is an active county outage at that snapshot with county FIPS, state FIPS, affected meters, contributing utility rows, and the ODIN county polygon. Missing county rows at a snapshot mean zero or cleared public ODIN outage, not stale carry-forward. This is distribution/customer outage data, not ISO generation or resource outage data.2.5M2026
SPPDaily generation-outage capacityATG Data·SPP·SPP's Daily generation-outage capacity. Each row preserves a publisher record, workbook row, or report document with its source member and row index. Source timestamps, units, geographic scope, and revision qualifiers are retained in record_json; event_time is collection time; completed_at is when the entire document became available.5.0K2026
Distribution Reliability (SAIDI/SAIFI)ATG Data·US reference·EIA-861 reliability: SAIDI, SAIFI and CAIDI with and without major event days, under IEEE 1366 and other standards, by utility. Reliability, 2013 on. EIA relabelled the index columns in 2021, so earlier years fill the *_with_med / *_without_med columns and later years the *_major_event_days columns. event_time is 1 January of the report year. release is final or early_release: EIA posts an early release of a year in August and replaces it with the final file in the autumn, and the mirror keeps the newest row per key. A key cell EIA leaves blank is '' or 0, and duplicate_index numbers rows that still share a key, in workbook order.14.0K2013
Distribution Reliability by StateATG Data·US reference·EIA-861 reliability state totals, 2023 on. The State Totals sheet of Reliability. event_time is 1 January of the report year. release is final or early_release: EIA posts an early release of a year in August and replaces it with the final file in the autumn, and the mirror keeps the newest row per key. A key cell EIA leaves blank is '' or 0, and duplicate_index numbers rows that still share a key, in workbook order.2012023
ERCOTERCOT Outage CapacityATG Data·ERCOT·How much ERCOT generation capacity is expected to be unavailable, one row per target hour and region. 268,745 rows, 2017-01 out to roughly eight days ahead. Regions are system, north, south, west and houston. ERCOT publishes this as a rolling forward view with an hourly vintage for every target hour — 15.17M raw rows across 83,875 vintages. This table collapses that to the latest published view of each target hour, which is what almost every question about expected outages actually wants, and removes the vintage-selection step where those questions usually go wrong. ERCOT reported this system-wide until 2021 and regionally afterwards; system rows are ERCOT's own total where it published one and the sum of the four regions after. No hour carries both. The forced-versus-planned split and the separate IRR and new-equipment categories are NOT here — they remain in ercot.hourly_resource_outage_capacity and ercot.reported_outages.275.2K2017
NYISOGeneration Maintenance ForecastATG Data·NYISO·NYISO rolling forecast of total generator maintenance outage MW by future date. This is a forward outage/availability context feed and currently has no full historical archive writer.1.4K2026
PJMGeneration Outages by TypeATG Data·PJM·PJM's daily generator-outage outlook by report date, target forecast date, and region. Each row separates total, planned, maintenance, and forced outage capacity in MW for PJM RTO, Western, or Mid Atlantic - Dominion. This is generation availability evidence from PJM Market Data, not distribution-customer outage data. Source: PJM Market Data.87.6K2015
SPPGeneration-Outage Outlook by FuelATG Data·SPP·Published outage-MW outlook by fuel and BAA. SPP, SWPW and Total are distinct source scopes; never add Total to its components. Target Market Hour remains an unqualified calendar label; event_time is file publication, not the target hour. Select one source file/vintage before comparing target labels. Complete views require a matching receipt and mirrored row count; empty results are unknown coverage. Raw sources retain publication history internally.6.0K2026
NYISOGenerator & Transmission Outage ScheduleATG Data·NYISO·NYISO scheduled generator and transmission outage records by PTID and equipment name, including scheduled out and scheduled in timestamps.839.1K2001
ERCOTHourly Resource Outage CapacityATG Data·ERCOT·ERCOT's Hourly Resource Outage Capacity report — the amount of generation capacity out of service across the Texas grid, projected hour by hour over a rolling seven-day horizon. Each posting from the Outage Scheduler breaks the outaged megawatts out by weather zone (South, North, West, Houston) and by category: Total Resource (a proxy for thermal outages), Total IRR (intermittent wind and solar), and Total New Equipment Resource (units still in commissioning). It is bitemporal — every row carries both the projected delivery hour (event_time) and the publishing vintage (source_time), and because ERCOT revises the projection every hour, successive vintages accumulate as distinct rows rather than overwriting. This is the core dataset for seeing how much capacity is unavailable at any moment, how outage expectations shift as an operating hour approaches, and how planned and forced outages concentrate by region — a direct input to scarcity, reserve adequacy, and reliability-unit-commitment analysis. The official source is ERCOT report NP3-233-CD, Hourly Resource Outage Capacity.15.5M2017
Hydro-Québec Peak Demand EventsATG Data·US reference·Every winter peak event Hydro-Québec called under its demand-response offers (Flex D, Hilo, business offers): the offer, customer sector, start and end.——
MISOLive Generation-Outage OutlookATG Data·MISO·MISO's rolling eleven-day generation-outage outlook in MW, separated into planned, unplanned, forced, and derated categories. The four values sum to each day's reported total; that total must not be added to its components. These are capacity totals, not counts of units or causes.1.7K2026
CAISOOASIS `AGGR_OUTAGE_SCH_GRP`ATG Data·CAISO·CAISO's OASIS `AGGR_OUTAGE_SCH_GRP`. Each row preserves a publisher record, workbook row, or report document with its source member and row index. Source timestamps, units, geographic scope, and revision qualifiers are retained in record_json; event_time is collection time; completed_at is when the entire document became available.336.8K2026
NYISOOperator MessagesATG Data·NYISO·NYISO operational announcements and dispatcher-issued messages, including interface scheduling changes, manual reductions, and market notices.362.2K2000
NYISOOperator-Initiated CommitmentsATG Data·NYISO·NYISO out-of-merit operator-initiated commitment records by resource PTID and event start time, including requester, commitment type, load zone, reason, ARR, UOL, and committed MW fields.64.3K2019
SPPOperator-Initiated CommitmentsATG Data·SPP·Weekly operator commitment report with location, size, reason and source start-time label. Exact duplicate source rows keep separate ordinals because no unique unit/commitment key is published. event_time is report publication; start-time timezone and size units are unqualified. Choose a single weekly report before counting entries. Complete views require a matching receipt and mirrored row count; empty results are unknown coverage. Raw sources retain publication history internally.5342026
NYISOP-14B Transmission Outage ScheduleATG Data·NYISO·NYISO's public P-14B transmission outage schedule, kept as one row per outage per published version of the list, with equipment PTID, name and type, scheduled out and in times, and status with its status time. event_time is the scheduled out time; source_time is the version's publication time, so every revision NYISO posts is retained. The current schedule is the rows at the latest source_time; counting one outage_id across versions double-counts it. Status values include UPDATED, EXTENDED, EXT FORCED, FORCED, DENIED, and CANCELLED, so a DENIED or CANCELLED row is not an outage that took place. Distinct from nyiso.outage_schedule, the date-stamped operational feed of generator and transmission outages.4.4M2014
PG&E Outage AreasATG Data·US reference·The polygons PG&E draws for larger outages on its outage map, per build, as GeoJSON, with the same customers, cause and restoration fields as `pge_outages.outages`, joined on `outage_id` and `event_time`. Read with FINAL.582.5K2026
PG&E Outage MapATG Data·US reference·Every outage on PG&E's public outage map, one row per outage per map build (every 10-15 minutes): estimated customers out, cause, crew status, outage start, the estimated time of restoration (`current_etor`), circuit, city, county and a point. `kind` is `outage` or `psps` (a Public Safety Power Shutoff). An outage's episode is its rows across builds grouped by `outage_id`; the newest build is `event_time = (SELECT max(event_time) FROM pge_outages.outages)`. Read with FINAL.407.6K2026
PG&E PSPS FootprintsATG Data·US reference·The footprint of each Public Safety Power Shutoff on PG&E's outage map, per build: the event, its stage, customers and Medical Baseline customers affected, the de-energization window and estimated restoration, as GeoJSON. Empty between shutoffs. Read with FINAL.119.2K2026

About outages & grid events data

These datasets bring together planned and unplanned equipment outages, public customer-impact counts, and event-driven operator communications. Use the numeric feeds to track capacity or customer impact over time and the message feeds to establish what an operator reported, when it was issued, and which area or condition it addressed.