NYISO · Load

NYISO load by zone

Actual load every five minutes in each of NYISO's eleven zones — New York City, Long Island, the Hudson Valley and the rest of the state.

nyiso-system-loadevery 5 min · 5m rows11 entities
N.Y.C.
6,251MW
2026-09-18 04:50 UTC
LONGIL
2,494MW
2026-09-18 04:50 UTC
WEST
1,561MW
2026-09-18 04:50 UTC
Read from the Dryos API and cached for an hour; the stream itself updates every 5 min.

What is in it

Updates
every 5 min · 5m rows
Entities
11 entities — N.Y.C., LONGIL, WEST…
Source timezone
US Eastern — every timestamp Dryos serves is UTC
Coverage
14 September 2026 to now
Rows held
12,672
Primary key
iso, zone, interval_start_utc

What it measures

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

  • LoadMW

    Actual load in the zone for the interval.

    load_mw

Columns

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

ColumnTypeDescription
interval_start_utcrequiredtimestampStart of the five-minute interval, UTC. NYISO's stamps run 00:00 to 23:55 through a day, so the stamp is read as the start.e.g. 2026-09-14T22:20:00Z
isorequiredstringPublishing ISO.e.g. NYISO
zonerequiredstringLoad zone as NYISO names it: CAPITL, CENTRL, DUNWOD, GENESE, HUD VL, LONGIL, MHK VL, MILLWD, N.Y.C., NORTH, WEST — and, in the forecast, NYISO, their sum.e.g. N.Y.C.
load_mwnumberActual load in the zone for the interval, MW.e.g. 9841.2
source_published_at_utctimestampWhen NYISO published the row.
collected_at_utcrequiredtimestampWhen Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-09-14T22:35:00Z

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/nyiso-system-load/query?node=N.Y.C.&limit=12"

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

shell
curl "https://api.dryos.ai/v1/datasets/nyiso-system-load"

Hourly averages for the last day

shell
curl "https://api.dryos.ai/v1/datasets/nyiso-system-load/query?node=N.Y.C.&start=-24h&interval=1h&agg=avg"

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 Load been at N.Y.C. 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-09-14

    First collected, from NYISO's MIS.

    Every other operator's load was here and NYISO's was not. Reconciled against the live files on 2026-09-14: every check passed.

How this stream is checked

  • Pulled straight from NYISO MIS · Real-Time Actual Load (P-58B) — 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 every 5 min; the interval timestamp is the start of the interval, in UTC.
  • NYISO stamps its files in Eastern prevailing time with no zone column. Every timestamp Dryos serves is UTC.

Related streams