Balancing Authority Hourly Demand

4.5M rows, 71 BAs, 2019-01 to now. The latest EIA submission for each hour. Every region reads the same columns, so comparing two areas is a filter on ba rather than a second table.

Query contract

One row per (ba, event_time) is already the latest EIA submission; read it plainly.

Analysis rules

Filter ba to your scope's code with a direct WHERE; search_data returns the allowed value. One ba per query keeps a region's rows from mixing with another's.demand_mw is an hourly average in MW; a daily energy total is sum(demand_mw) in MWh.

Interpretation

event_time is EIA-930's HOUR-ENDING stamp: the row at 18:00 UTC is the 17:00-18:00 hour. To compare with an ISO's interval-start table, match this row at t with the ISO row at t - 1 hour.EIA-930 is submitted by each balancing authority and trails real time by about a day; for the last hours use the region's own operator feed where one exists.

Related analysis

day-ahead forecast error · join on (ba, event_time)

Download

Query it in SQL, download it, or read it with an API key. Download data

MCP

Connect an MCP client and load the contract with describe_data before calling query_data.ERCOT MCPCAISO MCPNYISO MCPPJM MCPSPP MCPMISO MCPISO-NE MCPBPA MCPAPI reference

HTTP endpoint

POST /api/v1/datasets/ba_load/query

Full history

Delivered to Snowflake, Databricks or your own storage on a schedule by Data services.

More coverage

Request data coverage

Complete

100.0%

Gap days

0

Days with data

2,864