ERCOT · Grid

ERCOT unplanned resource outages

Every forced and maintenance outage or derate at an ERCOT generator or battery, one row per unit per day it was active: fuel, outage type, MW out of MW available, when it began and when it was planned to end and did. Posted daily for the third day back.

ercot-unplanned-outagesdaily, three days back · 1d rows906 entities
ETCCS_UNIT1
31.0MW
2026-11-19 06:00 UTC
WCPP_CT1
42.0MW
2026-11-19 06:00 UTC
FRNYPP_ST10
418MW
2026-11-19 06:00 UTC
Read from the Dryos API and cached for an hour; the stream itself updates daily, three days back.

What is in it

Updates
daily, three days back · 1d rows
Entities
906 entities — ETCCS_UNIT1, WCPP_CT1, FRNYPP_ST10…
Source timezone
US Central — every timestamp Dryos serves is UTC
Coverage
13 October 2026 to now
Rows held
15,294
Primary key
iso, resource, interval_start_utc, outage_start_utc, entry

What it measures

Every value, its unit, and what the source means by it.

  • MW outMW

    The unit's effective reduction due to the outage: its maximum less what stayed available.

    mw_reduction
  • MW still availableMW

    What the unit could still produce during the outage; 0 is a full outage.

    mw_available

Columns

Exactly what a request answers with, read from the API rather than written here.

ColumnTypeDescription
interval_start_utcrequiredtimestampStart of the Central day the outage was active on, UTC: the day the posting covers, the third before it was posted.e.g. 2026-11-12T06:00:00Z
isorequiredstringPublishing ISO.e.g. ERCOT
resourcerequiredstringERCOT's Resource Unit Code: the generating unit or storage resource on outage, as the Outage Scheduler names it.e.g. NUECES_B_NUECESG7
resource_namerequiredstringERCOT's Resource Name: the site the unit belongs to.e.g. NUECES_B
fuel_typerequiredstringFuel as ERCOT files it: Natural Gas, Wind, Solar, BATT, Lignite, Nuclear and so on.e.g. Natural Gas
outage_typerequiredstringForced, Forced Extension, Unavoidable Extension, or Maintenance Level 1-3 (equipment to come out within 24 hours, 7 days or 30 days). Can change between postings as an outage is extended.e.g. Forced
nature_of_workrequiredstringThe operator's reason from ERCOT's fixed list; Other on most rows.e.g. Turbine/Generator Vibration/Repair
outage_start_utcrequiredtimestampWhen the outage actually began, UTC.e.g. 2026-10-20T05:00:00Z
entryrequiredinteger1 on nearly every row. ERCOT exposes no outage id, and now and then files two or three entries for one unit under one start (successive derates, a resubmitted extension); they are numbered within the day in the order they ended, the open one last.e.g. 1
mw_reductionrequirednumberEffective reduction due to the outage, MW: the maximum less what stays available.e.g. 115
mw_availablerequirednumberMW still available from the unit during the outage. 0 is a full outage.e.g. 0
mw_maxrequirednumberThe unit's maximum in the Outage Scheduler when the report ran, MW — which may differ from its maximum when the outage began.e.g. 115
planned_end_utcrequiredtimestampWhen the outage is projected to end, UTC; the end of record until an actual end is entered.e.g. 2026-11-30T23:59:00Z
actual_end_utctimestampWhen the outage actually ended, UTC.e.g. 2026-11-13T23:00:00Z
source_published_at_utcrequiredtimestampWhen ERCOT posted the document this row came from, UTC. For reports republished on a rolling window this is the vintage: the same interval appears once per publication, and the newest is the current view.e.g. 2026-08-29T14:17:01Z
collected_at_utcrequiredtimestampWhen Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-08-29T14:18:02Z

Read it

Public, read-only, no key and no sign-up. Relative times stay relative, so a URL keeps working.

The newest rows

shell
curl "https://api.dryos.ai/v1/datasets/ercot-unplanned-outages/query?node=ETCCS_UNIT1&limit=12"

The catalogue entry — every column, its type and the source

shell
curl "https://api.dryos.ai/v1/datasets/ercot-unplanned-outages"

Full parameters — bucketing, aggregation, filters and search — are on the API reference.

Ask an agent

The same stream through the Model Context Protocol, so Claude, ChatGPT, Cursor or any MCP client can query it directly.

shell
claude mcp add --transport http dryos https://api.dryos.ai/mcp

Then ask:

What has MW out been at ETCCS_UNIT1 over the last 24 hours, and when did it peak?

Setup for every client is on the MCP server page.

Changes to this collector

A change in the collector is a change in the data. Anyone reading a step in a series is owed the day it moved under them.

  1. 2026-11-15

    Collected for the first time, with the 31 days the listing held.

    NP1-346 is the one per-unit outage record ERCOT publishes without a key. It had been skipped because the MIS base read only CSV; it now takes a reader per report, and this one reads the workbook. The listing keeps about a month and is the only free archive, so the first run took all 32 postings it held.

How this stream is checked

  • Pulled straight from ERCOT MIS · NP1-346-ER — no reseller in between — and compared against that file before it is served.
  • Null means the source did not report it — never zero.
  • A reading lands daily, three days back; the interval timestamp is the start of the interval, in UTC.
  • ERCOT settles and publishes on US Central time. Every timestamp Dryos serves is UTC.

Related streams