MISO Hourly Actual Load

Actual hourly electricity demand in MISO, one row per hour with a system total and one column per market region.

Load data MISO market

Query with the agent

Native record

one row per operating hour, wide by sub-area

hourly publication cadence

Evidence

Observed market data

Published observations from the named source

Time basis

Interval-start records

UTC · event_time

Overview

27,371 hours, 2023-08 to now. Columns: system_mw plus central_mw, north_mw, south_mw. system_mw is DERIVED as the sum of MISO's three market regions, which is how MISO itself reports system load, so a region share is region_mw / system_mw. Wide rather than long, so "load right now" and "the 3 market region shares of it" are one row, not 4. Every market's load table in this catalog shares the system_mw column and the same hourly grain, so a cross-market demand comparison needs no reshaping.

Query contract

One row is the canonical hourly value; the refresh already collapsed the source's restatements. Read the hour you want and use its columns together.

Analysis rules

Take every value for one hour from that hour's single row. Never combine a system total from one hour with area values from another.
An area's share of demand is <area>_mw / system_mw within the same row. Do not sum the 3 area columns and system_mw together — that double-counts the whole market.

Interpretation

Hourly actuals. For MISO demand in the last few minutes use miso_live_load series='actual_five_minute'. The seven LSE-zone series in miso_demand_load_state_estimator are opaque zone ids that do not map to these regions.
system_mw is derived by summing the area columns, so the identity system_mw = sum(areas) proves nothing about either. Do not present it as an independent cross-check.

Access

Query from your own tools

Use the guarded HTTP endpoint directly, or connect an MCP client and load the dataset contract with describe_data before calling query_data.

MISO MCP API reference

HTTP endpoint

POST /api/v1/datasets/miso_load/query

Need the full history of this dataset in Snowflake, Databricks or your own storage? Data services delivers it on a schedule.

Schema5

Column

Type

event_timeDateTime64(6, 'UTC')

system_mwNullable(Float64)

central_mwNullable(Float64)

north_mwNullable(Float64)

south_mwNullable(Float64)

Sample data

event_time	system_mw	central_mw	north_mw	south_mw
2026-10-16 04:00:00.000000	71561.2	33959.4	16613	20988.8
2026-10-16 03:00:00.000000	75271.5	35757.4	17239.5	22274.6
2026-10-16 02:00:00.000000	78990.7	37611.7	17808.5	23570.5
2026-10-16 01:00:00.000000	82290.29999999999	39279.9	18424.8	24585.6
2026-10-16 00:00:00.000000	85017.20000000001	40508.9	18840.9	25667.4
2026-10-15 23:00:00.000000	86688.4	41164.6	18974.2	26549.6
2026-10-15 22:00:00.000000	87225.4	40808.9	18793	27623.5
2026-10-15 21:00:00.000000	87592.20000000001	40650	18797.3	28144.9
2026-10-15 20:00:00.000000	87422.1	40425.8	18830.4	28165.9
2026-10-15 19:00:00.000000	86610.8	40181.3	18845	27584.5
2026-10-15 18:00:00.000000	86138.20000000001	40297.3	19197	26643.9
2026-10-15 17:00:00.000000	85081.8	39909.8	19245.2	25926.8
2026-10-15 16:00:00.000000	82770.90000000001	39388.9	19085.2	24296.8
2026-10-15 15:00:00.000000	80813.8	39106.1	18751.2	22956.5
2026-10-15 14:00:00.000000	78768.20000000001	38804.4	18601.2	21362.6
2026-10-15 13:00:00.000000	76911.3	38340	18248.9	20322.4
2026-10-15 12:00:00.000000	75486.7	37709.2	17919.3	19858.2
2026-10-15 11:00:00.000000	73548.29999999999	36531	17139.7	19877.6
2026-10-15 10:00:00.000000	69343.3	34197.5	16020.6	19125.2
2026-10-15 09:00:00.000000	66024.8	32087.8	15263.7	18673.3
2026-10-15 08:00:00.000000	64660.1	31111.9	14949.1	18599.1
2026-10-15 07:00:00.000000	64854.5	30934.9	14966.3	18953.3
2026-10-15 06:00:00.000000	65914	31265.9	15262.4	19385.7
2026-10-15 05:00:00.000000	67684.5	32185.3	15583	19916.2
2026-10-15 04:00:00.000000	70446.4	33358.8	16112.5	20975.1

Coverage

No time-indexed data — coverage isn’t applicable to this dataset.

Related load data

Related load data
Dataset	Description
Actual Demand by RegionMISO · hourly	Observed hourly MISO demand in MW for the Central, North, and South sub-regions. Region labels are normalized to uppercase; this is regional operational load, not a local-resource-zone series.
Completed-year `12_dfal_HIST_xls.zip`MISO · year publication	MISO's Completed-year `12_dfal_HIST_xls.zip`. Each row preserves a publisher record, workbook row, or report document with its source member and row index. Source timestamps, units, geographic scope, and revision qualifiers are retained in record_json; event_time is collection time; completed_at is when the entire document became available.
Daily `df_al.xls`, including zonal actual loadMISO · day publication	MISO's Daily `df_al.xls`, including zonal actual load. Each row preserves a publisher record, workbook row, or report document with its source member and row index. Source timestamps, units, geographic scope, and revision qualifiers are retained in record_json; event_time is collection time; completed_at is when the entire document became available.
Day-Ahead Cleared DemandMISO · hourly (Day-Ahead)	Hourly day-ahead cleared MISO demand by sub-region, separated into fixed, price-sensitive, and virtual demand. Virtual demand is a financial market position and must not be reported as physical electricity consumption.