PJM · Grid
PJM generation outage forecast, ninety days
PJM's forecast of generation out of service for each of the next ninety days, for the RTO, the west and the rest — issued daily and kept as vintages.
pjm-gen-outage-forecastdaily, ninety days ahead · 1d rows3 entitiesWhat is in it
- Updates
- daily, ninety days ahead · 1d rows
- Entities
- 3 entities — PJM RTO, Western, Other…
- Source timezone
- US Eastern — every timestamp Dryos serves is UTC
- Coverage
- 7 September 2026 to now
- Rows held
- 3,276
- Primary key
- iso, region, interval_start_utc, source_published_at_utc
What it measures
Every value, its unit, and what the source means by it.
- Forecast outMW
Generation forecast out that day.
outage_mw
Columns
Exactly what a request answers with, read from the API rather than written here.
| Column | Type | Description |
|---|---|---|
| interval_start_utcrequired | timestamp | Start of the interval, UTC, read from PJM's own UTC column.e.g. 2026-09-09T12:30:00Z |
| isorequired | string | Publishing ISO.e.g. PJM |
| regionrequired | string | PJM's region: PJM RTO, Western, and Mid Atlantic - Dominion (week ahead) or Other, the RTO less the west (ninety days).e.g. PJM RTO |
| outage_mwrequired | number | Generation forecast out that day, MW.e.g. 17464 |
| source_published_at_utcrequired | timestamp | When PJM evaluated this forecast, UTC — the vintage. Every publication is kept, so one interval carries a row per vintage that covered it.e.g. 2026-09-10T02:15:00Z |
| collected_at_utcrequired | timestamp | When Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-09-09T12:35:12Z |
Read it
Public, read-only, no key and no sign-up. Relative times stay relative, so a URL keeps working.
The newest rows
curl "https://api.dryos.ai/v1/datasets/pjm-gen-outage-forecast/query?node=PJM%20RTO&limit=12"The catalogue entry — every column, its type and the source
curl "https://api.dryos.ai/v1/datasets/pjm-gen-outage-forecast"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.
claude mcp add --transport http dryos https://api.dryos.ai/mcpThen ask:
What has Forecast out been at PJM RTO 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.
- 2026-09-13
First collected, from PJM Data Miner 2.
PJM's daily generation outage forecasts, kept by PJM indefinitely. Reconciled against live responses on 2026-09-13.
How this stream is checked
- Pulled straight from PJM Data Miner 2 · frcstd_gen_outages — 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, ninety days ahead; the interval timestamp is the start of the interval, in UTC.
- PJM's Eastern Prevailing Time observes daylight saving; its rows carry UTC as well. Every timestamp Dryos serves is UTC.
Related streams
- PJM tie flowsPJM
Actual against scheduled flow every five minutes on each of PJM's ties with its neighbours — New York, the MISO seams, TVA, Duke and the rest — plus the MISO net and the RTO net.
every 5 min · 5m rows21 entitiespjm-tie-flows - PJM area control errorPJM
How far PJM is from its interchange schedule and frequency obligation at the instant, in megawatts, every fifteen seconds — the number the control room regulates to zero.
every 15 s · 15s rows1 entitypjm-ace - PJM hourly interchange by tiePJM
Actual, scheduled and inadvertent flow over each of PJM's ties with its neighbours, hour by hour — the record PJM keeps indefinitely behind the five-minute tie flows it keeps thirty days.
every 2 h, hours behind · 1h rows20 entitiespjm-interchange-hourly - PJM generation outages, week aheadPJM
PJM's generation outages for today and the next six days, for the RTO and its two regions, split into planned, maintenance and forced — issued daily and kept as vintages.
daily, a week ahead · 1d rows3 entitiespjm-gen-outages - PJM performance assessment intervalsPJM
Which five-minute intervals PJM flags as Performance Assessment Intervals — the emergencies in which capacity resources are scored on whether they delivered — for the RTO and the active subzone, as PJM first flags them.
every 10 min, one row per interval · 5m rows1 entitypjm-pai-intervals - PJM transfer interfacesPJM
Actual flow against the transfer limit on the eleven interfaces PJM watches for stability — the eastern, central and western reactive interfaces, AP South, Bedington–Black Oak and the seams — every five minutes.
every 5 min · 5m rows11 entitiespjm-transfer-interfaces