ERCOT · Grid

Resource outage capacity

Capacity on outage by forecast zone, hour by hour for the coming week — total, intermittent and not-yet-commercial. Collected from ERCOT MIS (NP3-233).

ercot-outage-capacityhourly, week out · 1h rows4 entities
HOUSTON
1,469MW
2026-09-25 03:00 UTC
NORTH
2,755MW
2026-09-25 03:00 UTC
SOUTH
1,910MW
2026-09-25 03:00 UTC
Read from the Dryos API and cached for an hour; the stream itself updates hourly, week out.

What is in it

Updates
hourly, week out · 1h rows
Entities
4 entities — HOUSTON, NORTH, SOUTH…
Source timezone
US Central — every timestamp Dryos serves is UTC
Coverage
29 August 2026 to now
Rows held
347,136
Primary key
iso, zone, interval_start_utc, source_published_at_utc

What it measures

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

  • Capacity on outageMW

    Total resource capacity on outage in the zone.

    total_resource_mw
  • Intermittent on outageMW

    Intermittent renewable capacity on outage.

    total_irr_mw

Columns

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

ColumnTypeDescription
interval_start_utcrequiredtimestampStart of the interval, UTC. Always UTC — ERCOT publishes wall-clock Central with a repeated-hour flag, which is resolved on ingest.e.g. 2026-08-29T14:15:00Z
isorequiredstringPublishing ISO.e.g. ERCOT
zonerequiredstringERCOT forecast zone: SOUTH, NORTH, WEST or HOUSTON.e.g. SOUTH
total_resource_mwrequirednumberTotal resource capacity on outage, MW.e.g. 1997
total_irr_mwrequirednumberIntermittent renewable capacity on outage, MW.e.g. 998
total_new_equip_mwrequirednumberNew-equipment capacity not yet commercial, MW.e.g. 850
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-outage-capacity/query?node=HOUSTON&limit=12"

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

shell
curl "https://api.dryos.ai/v1/datasets/ercot-outage-capacity"

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 Capacity on outage been at HOUSTON over the last 24 hours, and when did it peak?

Setup for every client is on the MCP server page.

How this stream is checked

  • Pulled straight from ERCOT MIS · NP3-233-CD — 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 hourly, week out; 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