Overview

PJM metered load sampled every five minutes by area, where 'PJM RTO' is the whole-RTO system total and the remaining areas are the transmission-zone operating regions (AEP, COMED, DOM, PSEG, and so on). Because it posts within minutes, this is the live demand signal for PJM — system load, zonal load, and the shape of the daily peak — unlike the hourly metered-load tables that settle on a delay. Source: PJM Data Miner 2.

PJM market Ask the agent about this dataset

Use with MCP

This table is readable two ways, over the same guarded boundary. Over HTTP: POST /api/v1/datasets/pjm_inst_load/query, described in the API reference. Or from an MCP client: connect a market below, then use search_data or describe_data to load its query contract before calling query_data.

PJM MCP Server

Schema4

Column

Type

event_timeDateTime64(6, 'UTC')

areaLowCardinality(String)

instantaneous_loadNullable(Float64)

ingested_atDateTime64(6, 'UTC')

Sample rows

event_time	area	instantaneous_load	ingested_at
2026-08-28 02:20:01.000000	UG	123.673988	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	RECO	190.108521	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	PS	5440.43	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	PN	2005.49377	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	PL	5127.104	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	PJM WESTERN REGION	54882.4453	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	PJM SOUTHERN REGION	19078.6016	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	PJM RTO	109913.609	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	PJM MID ATLANTIC REGION	34147.4961	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	PEP	3910.43652	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	PE	4335.30127	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	ME	1938.28662	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	JC	2885.25952	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	EKPC	1806.168	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	DUQ	1769.54663	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	DPL	2413.39355	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	DOM	19078.6016	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	DEOK	3588.1377	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	DAYTON	2326.55273	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	COMED	13647.4395	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	BC	4195.83838	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	ATSI	8797.978	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	APS	6045.821	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	AEP	18705.8711	2026-08-28 02:23:34.533354
2026-08-28 02:20:01.000000	AE	1549.00781	2026-08-28 02:23:34.533354

Coverage

100.0% complete0 gap days54 days with data

Show coverage history ▾

Coverage: 100.0%Days with data: 54Gaps: 0

2026

gaplessmore

More data from PJM

7-Day Load ForecastPJM's seven-day-ahead hourly load forecast by forecast area, refreshed through the day. Rows are keyed by target time (event_time) with the issue time in evaluated_at_utc; take the latest vintage per target hour via an argMax over evaluated_at_utc. Forecast areas match the very-short-term feed (utility names, RTO_COMBINED for the system total). This is the table for tomorrow's peak and the week-ahead demand outlook. Source: PJM Data Miner 2.Day-Ahead Hourly LMPCleared day-ahead locational marginal prices for each PJM pricing node by delivery hour, with total LMP and its system-energy, congestion, and marginal-loss components in dollars per MWh. The table supports the posted next-day hourly curve, day-ahead-to-real-time basis, and node-level component attribution. A congestion component does not by itself identify which facility is expected to bind or establish a node-to-constraint relationship. Source: PJM Data Miner 2.Day-Ahead Transmission ConstraintsThe transmission constraints that bound in PJM's day-ahead market: the monitored facility, the contingency facility, the duration, and the congestion event. It names which elements are expected to limit flows for the next operating day. Note that PJM does not publish a real-time binding-constraint/shadow-price feed, so real-time congestion is read from the congestion component of the LMP tables rather than from a constraints table. Source: PJM Data Miner 2.Generation by Fuel TypePJM system generation broken out by fuel type every five minutes — gas, nuclear, coal, solar, wind, hydro, storage, and others — with each fuel's output in MW, its share of the total, and a renewable flag. This is the live fuel-mix signal for the PJM footprint: read it for current renewable output, the marginal fuel, and how the mix shifts across the day. Source: PJM Data Miner 2.