Running now

158 collectors, maintained and running

Every stream on Dryos has a collector behind it: a program that reads the operator's own feed on its schedule and lands each interval as it is posted. These are the ones running right now — what each reads, how often, when it last collected, and every change made to it.

Collectors running
158
Grid operators
7
Every five minutes or faster
60
Last collection

1,926,477 rows landed across their latest runs.

Energy · 150 collectors

Weather · 4 collectors

Property · 4 collectors

Recent changes

A change in a collector is a change in the data, so each one is dated and kept with the collector it was made to.

  1. 2026-11-16

    Freshness budget widened from two hours to three.

    NYISO · Pricing · Real-time hourly

  2. 2026-11-15

    Collected for the first time, with the 31 days the listing held.

    ERCOT · Grid · Outages

  3. 2026-11-15

    A watermark older than PJM keeps the feed restarts inside what PJM still has.

    PJM · Pricing · Real-time

  4. 2026-11-15

    A watermark older than PJM keeps the feed restarts inside what PJM still has.

    PJM · Pricing · RT bus LMP

  5. 2026-11-15

    A watermark older than PJM keeps the feed restarts inside what PJM still has.

    PJM · Pricing · Real-time hourly

  6. 2026-11-15

    A watermark older than PJM keeps the feed restarts inside what PJM still has.

    PJM · Load · Load by area

  7. 2026-11-15

    A watermark older than PJM keeps the feed restarts inside what PJM still has.

    PJM · Grid · Tie flows

  8. 2026-11-15

    A watermark older than PJM keeps the feed restarts inside what PJM still has.

    PJM · Ancillary · Regulation

PricingEnergy · 47 running

  • Every transmission constraint CAISO's day-ahead market bound on, hour by hour, with the contingency and its shadow price, posted for the whole of tomorrow each afternoon.

    1 change ›
    1. 2026-09-14

      First collected, from CAISO OASIS.

      The binding constraints PJM already had. Reconciled against a live response on 2026-09-14.

    Last collected
    Schedule
    hourly
  • Hourly day-ahead prices at the ~1,900 CAISO aggregated pricing nodes cleared in the day-ahead market — trading hubs, load aggregation points, resources and PacifiCorp's Extended Day-Ahead Market hubs — with energy, congestion, loss and greenhouse-gas components, posted for the whole of tomorrow each afternoon.

    1 change ›
    1. 2026-09-14

      First collected, from CAISO OASIS.

      Every other operator here had a day-ahead price and CAISO did not. Reconciled against a live response on 2026-09-14: schema, nulls, primary key, value bands and row counts passed, every node typed, and the four components summed to the LMP on every row. The 445 Western EIM nodes the file lists at zero in every component are not stored.

    Last collected
    Schedule
    hourly
  • Prices from CAISO's fifteen-minute market at its ~2,700 priced nodes — trading hubs, load aggregation points, resources and every Western EIM area — with energy, congestion, loss and greenhouse-gas components, posted about 25 minutes ahead of each interval.

    2 changes ›
    1. 2026-11-15

      Node types come from CAISO's reference for the day being read, not today's.

      CAISO's APnode reference is dated, and 620 nodes listed on 2026-10-01 were retired by 2026-11-15. A run reading an older window typed it with today's reference, so the retired nodes came out untyped, the 2% null budget refused the batch, and the watermark stayed on 2026-10-01 from then until this fix.

    2. 2026-09-14

      First collected, from CAISO OASIS.

      The third of CAISO's energy markets, beside the day-ahead and the five-minute. Reconciled against a live response on 2026-09-14.

    Last collected
    Schedule
    every 15 min
  • Every transmission constraint CAISO's hour-ahead scheduling run bound on, with the contingency and its shadow price, posted about an hour before each hour.

    1 change ›
    1. 2026-11-15

      First collected, from CAISO OASIS.

      The hour-ahead run between the day-ahead and real-time constraint streams.

    Last collected
    Schedule
    every 15 min
  • The interties CAISO's hour-ahead run scheduled up against — Palo Verde, IPP, the Wyoming exports — by direction, with the contingency and the shadow price, about an hour before each hour.

    1 change ›
    1. 2026-11-15

      First collected, from CAISO OASIS.

      Where imports and exports are scheduled against a limit, beside the transmission constraints.

    Last collected
    Schedule
    every 15 min
  • Every transmission constraint CAISO's real-time dispatch was up against, five minutes at a time, with the contingency and its shadow price. Empty when nothing binds, which is a fact and not a gap.

    1 change ›
    1. 2026-09-14

      First collected, from CAISO OASIS.

      The binding constraints PJM already had. Reconciled against a live response on 2026-09-14.

    Last collected
    Schedule
    every 5 min
  • The interties CAISO's fifteen-minute market scheduled up against, by direction, with the contingency and the shadow price, posted ahead of each interval.

    1 change ›
    1. 2026-11-15

      First collected, from CAISO OASIS.

      Where imports and exports are scheduled against a limit in real time.

    Last collected
    Schedule
    every 5 min
  • Real-time dispatch prices at all ~2,750 CAISO aggregated pricing nodes — trading hubs, load aggregation points, resources and every Western EIM area — with energy, congestion, loss and greenhouse-gas components, every five minutes.

    2 changes ›
    1. 2026-11-15

      Node types come from CAISO's reference for the day being read, not today's.

      CAISO's APnode reference is dated, and 620 nodes listed on 2026-10-01 were retired by 2026-11-15. A run reading an older window typed it with today's reference, so the retired nodes came out untyped, the 2% null budget refused the batch, and the watermark stayed on 2026-10-01 from then until this fix. Today's prices were fully typed by today's reference throughout.

    2. 2026-09-14

      Nodes listed at zero in every component are no longer stored.

      Forty-six Western EIM transfer points and flexible-ramp zones read exactly zero in all five components in every interval: listed by OASIS, not priced. They were stored as $0 prices from 2026-09-12 until this change, and those rows remain in the table.

    Last collected
    Schedule
    every 5 min
  • Day-ahead hourly LMPs for all ~19,000 ERCOT electrical buses, published once daily after the DAM run (~463k rows per file).

    Last collected
    Schedule
    hourly
  • Day-ahead market settlement point prices for all ~1,100 ERCOT settlement points, hourly, published once daily after the DAM run.

    Last collected
    Schedule
    hourly
  • Every binding transmission constraint in the day-ahead market, with its limit, cleared flow and shadow price — why nodal prices diverge from the system lambda.

    Last collected
    Schedule
    hourly
  • The day-ahead hourly system-wide marginal energy price, published once daily after the DAM run.

    Last collected
    Schedule
    hourly
  • Cleared day-ahead purchase volumes per settlement point and hour — the quantity side of the DAM, published daily.

    Last collected
    Schedule
    hourly
  • Cleared day-ahead sale volumes per settlement point and hour — the supply side of the DAM, published daily.

    Last collected
    Schedule
    hourly
  • RTD's look-ahead: indicative LMPs for every settlement point, several intervals forward, republished every five minutes — where real-time prices are about to go.

    Last collected
    Schedule
    every 5 min
  • Locational marginal prices for all ~19,000 ERCOT electrical buses from every SCED run, roughly every five minutes. The heaviest feed ERCOT publishes.

    Last collected
    Schedule
    every 5 min
  • Locational marginal prices for all ~1,100 ERCOT settlement points — resource nodes, load zones, trading hubs and DC ties — from the latest SCED run, roughly every five minutes.

    1 change ›
    1. 2026-09-08

      Collects within the minute again; the record had read five to six minutes late on every interval.

      The delivery record showed every interval collected five to six minutes after ERCOT posted it. Two causes. Each run re-fetched the previous SCED file — the document filter compared publish times against the interval watermark, which the newest file always passes — and the upsert overwrote collected_at with the second fetch, so the record kept the later time. And an off-grid SCED run shifted the predicted window by half a cycle, so the two regular files after it were each found two minutes late. The collector sits on the shared MIS base now, filtering on the publish watermark; the window is predicted from the median phase of recent publications; a 30-second heartbeat outside the window catches anything the prediction misses; and the window polls every 4s from 15s before the stamp, since the listing shows a file about 40s after the time it carries.

    Last collected
    Schedule
    every 5 min
  • The scarcity-pricing feed: reliability deployment price adders, deployments and online reserve limits from every SCED run.

    Last collected
    Schedule
    every 5 min
  • The 15-minute settlement point price for all ~1,100 ERCOT settlement points — the price settlement actually uses, computed from the SCED LMPs plus price adders.

    Last collected
    Schedule
    every 15 min
  • The system-wide marginal energy price from every SCED run, roughly every five minutes — one number for what energy is worth in ERCOT right now.

    Last collected
    Schedule
    every 5 min
  • Hourly day-ahead prices at all ~1,200 ISO New England pricing locations — the Hub, the eight load zones, the external nodes and every network node — with energy, congestion and loss components, posted for the whole of tomorrow each afternoon.

    1 change ›
    1. 2026-11-15

      First collected, from ISO Express.

      ISO-NE was the one operator with a real-time price here and no day-ahead one beside it, though its day-ahead file was already read daily for location names. Reconciled against the live file on 2026-11-15: market days 2026-11-15 and 11-16, every check passing; the hour-ending convention was checked against ISO-NE's hourly real-time file and the five-minute prices.

    Last collected
    Schedule
    hourly
  • Preliminary real-time prices at all ~1,200 ISO New England pricing locations — the Hub, the eight load zones, the external nodes and every network node — with energy, congestion and loss components, every five minutes.

    Last collected
    Schedule
    every 5 min
  • Hourly day-ahead ex-post prices for all ~2,600 MISO commercial pricing nodes — hubs, load zones, generator nodes and interfaces — with energy, congestion and loss components, posted for the whole of tomorrow each afternoon.

    1 change ›
    1. 2026-09-14

      First collected, from MISO's Data Exchange.

      MISO was the one operator on the price map with a real-time price and no day-ahead one beside it, so its nodes sat out the DA and DA/RT views. Reconciled against a live response on 2026-09-14: market days 2026-09-14 and 2026-09-15, schema, nulls, primary key, value bands and row counts passed, and the three components summed to the LMP on every row.

    Last collected
    Schedule
    hourly
  • The forward-looking five-minute price at MISO's eight trading hubs and the SPP interface — what the dispatch is about to clear at, published just before each interval, from a feed that keeps only the current one.

    Last collected
    Schedule
    every 5 min
  • Preliminary ex-post locational marginal prices for all ~2,600 MISO commercial pricing nodes — hubs, load zones, generator nodes and interfaces — with congestion and loss components, every five minutes.

    Last collected
    Schedule
    every 5 min
  • Every transmission facility that bound in NYISO's day-ahead market, hour by hour, with the contingency it bound for and its constraint cost, posted for tomorrow each morning.

    1 change ›
    1. 2026-09-14

      First collected, from NYISO's MIS.

      CAISO's and SPP's day-ahead constraints were here and NYISO's were not. Reconciled against the live files on 2026-09-14: every check passed.

    Last collected
    Schedule
    hourly
  • Hourly day-ahead prices at NYISO's eleven load zones, its four external proxies and all ~750 generator buses, with loss and congestion components, posted for the whole of tomorrow each morning.

    1 change ›
    1. 2026-09-14

      First collected, from NYISO's MIS.

      NYISO's real-time price was its only stream here, and every other operator with one had a day-ahead price beside it. Reconciled against the live files on 2026-09-14: schema, nulls, primary key, value bands and row counts passed, and the derived energy was one number across the state each hour.

    Last collected
    Schedule
    daily
  • NYISO's hourly real-time price at its eleven load zones and four external proxies — the five-minute prices weighted by interval length — with loss and congestion components.

    2 changes ›
    1. 2026-11-16

      Freshness budget widened from two hours to three.

      A row is stamped at its hour's start and kept once the hour closes, so it is an hour old on arrival; one late posting failed the run at two.

    2. 2026-11-15

      First collected, from NYISO's MIS.

      NYISO's hourly real-time price is weighted by interval length, so it is not the mean of the five-minute prices whenever an extra dispatch run lands: the plain mean missed by up to $1.52 in those hours, and the time-weighted one matched to the cent in all 1,800 zone-hours of 2026-11-10 to 11-14.

    Last collected
    Schedule
    every 15 min
  • Every transmission facility NYISO's real-time dispatch was up against, five minutes at a time, with the contingency it bound for and its constraint cost.

    1 change ›
    1. 2026-09-14

      First collected, from NYISO's MIS.

      CAISO's, PJM's and SPP's binding constraints were here and NYISO's were not. Reconciled against the live files on 2026-09-14: every check passed.

    Last collected
    Schedule
    every 5 min
  • Real-time dispatch prices at NYISO's eleven load zones, its four external proxies and all ~750 generator buses, with energy, congestion and loss components, every five minutes.

    1 change ›
    1. 2026-09-17

      The price band widened to [-15,000, 15,000] $/MWh, and the intervals it had been refusing landed.

      Four buses in the Linden pocket cleared at -$5,938.85 between 12:00 and 12:20 EDT — NYISO's $6,000 constraint penalty against a $57 energy price, exactly as NYISO published it. The band was ERCOT's, and refusing the batch stopped the whole stream for nine hours, because a batch that is never promoted never moves the watermark.

    Last collected
    Schedule
    every 5 min
  • Every transmission constraint the real-time dispatch was up against, five minutes at a time, with the contingency it bound for and its shadow price. Empty when the grid is unconstrained, which is a fact and not a gap.

    3 changes ›
    1. 2026-11-15

      The row-count check counts rows per interval, not per run.

      A run reads from the watermark to now, so after the 2026-11-12 outage the first batch was two days long: 1,622 rows, 2.9 an interval, which is the grid's usual. Against a per-run median of four it failed every run and the watermark could not move.

    2. 2026-11-15

      A watermark older than PJM keeps the feed restarts inside what PJM still has.

      A run asks PJM for the window after the newest row held. Once that window is older than PJM's retention it answers empty, the run is recorded as skipped and the watermark never moves, so the stream stopped while reading as running: the real-time LMPs from early October, the fifteen-second feeds from mid-October. Runs now start a day inside the retention, trusting no more than fifteen days (PJM lists thirty for several feeds and kept fifteen on 2026-11-15). The stretch before is gone at the source and is a hole in the stream.

    3. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 5 min
  • Every transmission constraint that binds in PJM's day-ahead market, hour by hour, with the contingency and its shadow price, posted with tomorrow's prices.

    1 change ›
    1. 2026-09-13

      First collected, from PJM Data Miner 2.

      PJM's settled shadow prices, kept by PJM indefinitely. Reconciled against live responses on 2026-09-13.

    Last collected
    Schedule
    hourly
  • Hourly day-ahead locational marginal prices at every one of PJM's 13,967 electrical buses, with the energy, congestion and loss components as PJM publishes them. A third of a million rows a day.

    1 change ›
    1. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    hourly
  • Hourly day-ahead locational marginal prices at PJM's 482 aggregate pricing nodes — hubs, zones, interfaces, EHV and residual aggregates — with the energy, congestion and loss components as PJM publishes them, posted for the whole of tomorrow around 12:30 EPT.

    1 change ›
    1. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    hourly
  • The dispatch signal PJM sends each of its 20 transmission zones, in $/MWh, every fifteen seconds — the price the control room is steering generators to at the instant. PJM keeps fifteen days.

    2 changes ›
    1. 2026-11-15

      A watermark older than PJM keeps the feed restarts inside what PJM still has.

      A run asks PJM for the window after the newest row held. Once that window is older than PJM's retention it answers empty, the run is recorded as skipped and the watermark never moves, so the stream stopped while reading as running: the real-time LMPs from early October, the fifteen-second feeds from mid-October. Runs now start a day inside the retention, trusting no more than fifteen days (PJM lists thirty for several feeds and kept fifteen on 2026-11-15). The stretch before is gone at the source and is a hole in the stream.

    2. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 5 min
  • What PJM's intermediate-term dispatch expects the next four five-minute intervals to cost at its ties with New York and MISO, re-run every few minutes and kept case by case — the forward-looking price at the seams.

    1 change ›
    1. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 5 min
  • PJM's settled record of every transmission constraint that bound in the real-time market, five minutes at a time: the contingency, the shadow price, the penalty factor and the limit control percentage. Posted about three days late, on business days.

    1 change ›
    1. 2026-09-13

      First collected, from PJM Data Miner 2.

      PJM's settled shadow prices, kept by PJM indefinitely. Reconciled against live responses on 2026-09-13.

    Last collected
    Schedule
    every 3 h
  • PJM's own hourly integration of its unverified real-time prices at the 12 trading hubs, 22 transmission zones, 7 interfaces and every other aggregate — 482 in all — with the congestion and loss components, posted for the previous hour. PJM keeps it thirty days.

    2 changes ›
    1. 2026-11-15

      A watermark older than PJM keeps the feed restarts inside what PJM still has.

      A run asks PJM for the window after the newest row held. Once that window is older than PJM's retention it answers empty, the run is recorded as skipped and the watermark never moves, so the stream stopped while reading as running: the real-time LMPs from early October, the fifteen-second feeds from mid-October. Runs now start a day inside the retention, trusting no more than fifteen days (PJM lists thirty for several feeds and kept fifteen on 2026-11-15). The stretch before is gone at the source and is a hole in the stream.

    2. 2026-09-13

      First collected, from PJM Data Miner 2.

      One of PJM's thirty-day feeds, taken first for that reason. Reconciled against live responses on 2026-09-13.

    Last collected
    Schedule
    hourly
  • Unverified five-minute locational marginal prices at every one of PJM's 13,967 electrical buses — generator, load and external — with the congestion and loss components. Four million rows a day.

    3 changes ›
    1. 2026-11-15

      A watermark older than PJM keeps the feed restarts inside what PJM still has.

      A run asks PJM for the window after the newest row held. Once that window is older than PJM's retention it answers empty, the run is recorded as skipped and the watermark never moves, so the stream stopped while reading as running: the real-time LMPs from early October, the fifteen-second feeds from mid-October. Runs now start a day inside the retention, trusting no more than fifteen days (PJM lists thirty for several feeds and kept fifteen on 2026-11-15). The stretch before is gone at the source and is a hole in the stream.

    2. 2026-09-17

      The price band widened to [-15,000, 15,000] $/MWh, and the intervals it had been refusing landed.

      On 2026-09-16 six 69 kV buses around Conneaut and two solar buses cleared between $6,187 and $6,870.31 — PJM's $3,700 scarcity energy price with $1,088.95 of congestion and up to $2,081.36 of losses on top, exactly as PJM published it. The band was ERCOT's, and refusing the batch stopped the whole stream for a day, because a batch that is never promoted never moves the watermark.

    3. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 5 min
  • Unverified five-minute locational marginal prices at PJM's 12 trading hubs, 22 transmission zones, 7 interfaces and every other aggregate pricing node — 482 in all — with the congestion and loss components, about four minutes after the interval starts.

    2 changes ›
    1. 2026-11-15

      A watermark older than PJM keeps the feed restarts inside what PJM still has.

      A run asks PJM for the window after the newest row held. Once that window is older than PJM's retention it answers empty, the run is recorded as skipped and the watermark never moves, so the stream stopped while reading as running: the real-time LMPs from early October, the fifteen-second feeds from mid-October. Runs now start a day inside the retention, trusting no more than fifteen days (PJM lists thirty for several feeds and kept fifteen on 2026-11-15). The stretch before is gone at the source and is a hole in the stream.

    2. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 5 min
  • The five-minute real-time prices PJM settles on, at 340 hubs, zones, interfaces, EHV and residual aggregates, with the energy, congestion and loss components. The zone and residual prices are the recomputed settlement figures, not the estimates the dispatch posted. About four days late, on business days.

    1 change ›
    1. 2026-11-15

      First collected, from PJM Data Miner 2.

      PJM's settlement prices at the aggregates, kept indefinitely. Checked against the verified five-minute feed on 2026-11-09: equal at every hub, interface and EHV node, and different at the zones and residual aggregates, whose prices settlement recomputes.

    Last collected
    Schedule
    hourly
  • PJM's verified hourly real-time prices at its 484 aggregate pricing nodes — hubs, zones, interfaces, EHV and residual aggregates — with the energy, congestion and loss components as PJM publishes them. Posted the next business day and kept indefinitely.

    1 change ›
    1. 2026-11-15

      First collected, from PJM Data Miner 2.

      The verified copy of the real-time hourly prices, kept by PJM indefinitely where the unverified feed keeps thirty days. Reconciled against a live response on 2026-11-15.

    Last collected
    Schedule
    hourly
  • Every transmission constraint that bound in SPP's day-ahead market, hour by hour, with the contingency it bound for and its shadow price, posted for the whole of tomorrow each afternoon.

    2 changes ›
    1. 2026-11-15

      The NERC flowgate id may be blank on up to 90% of rows, from 40%.

      SPP leaves the id blank on constraints that have none: 149 of 714 rows on market day 2026-09-14, 205 of 439 on 2026-11-16. The blanks are SPP's and move with which constraints bind; a renamed column would blank every row, which the budget still refuses.

    2. 2026-09-14

      First collected, from SPP's marketplace portal.

      CAISO's and PJM's day-ahead constraints were here and SPP's were not. Reconciled against the live files on 2026-09-14: every check passed.

    Last collected
    Schedule
    hourly
  • Hourly day-ahead prices at all ~9,250 SPP electrical buses, the western market included, with energy, congestion and loss components, posted for the whole of tomorrow each afternoon.

    1 change ›
    1. 2026-09-14

      First collected, from SPP's marketplace portal.

      ERCOT's and PJM's bus-level prices were here and SPP's were not. Reconciled against the live files on 2026-09-14: schema, nulls, primary key, value bands and row counts passed.

    Last collected
    Schedule
    hourly
  • Hourly day-ahead prices at all ~1,600 SPP settlement locations — hubs, load areas, resources and the interfaces with its neighbours, the western market included — with energy, congestion and loss components, posted for the whole of tomorrow each afternoon.

    1 change ›
    1. 2026-09-14

      First collected, from SPP's marketplace portal.

      The real-time price was SPP's only one here, and every other operator with a real-time price had a day-ahead one beside it. Reconciled against a live response on 2026-09-14: schema, nulls, primary key, value bands and row counts passed, every location typed, and the three components summed to the LMP on every row.

    Last collected
    Schedule
    hourly
  • Every transmission constraint in SPP's real-time dispatch, five minutes at a time — binding, breached or activated — with the contingency it is monitored for, its limits and its shadow price.

    2 changes ›
    1. 2026-11-15

      A file SPP never posted is passed over even when a whole run's worth are missing.

      Each run read a fixed slice of the dated files after the watermark. SPP never posted two hours on the evening of 2026-09-22, every file in the slice was a 404, nothing was read, so the watermark could not move and every later run asked for the same slice: the real-time streams stopped there for 54 days. Runs now read on until they find a run's worth, up to a day of missing files. The hole stays a hole.

    2. 2026-09-14

      First collected, from SPP's marketplace portal.

      CAISO's and PJM's binding constraints were here and SPP's were not. Reconciled against the live files on 2026-09-14: every check passed; activated constraints are kept beside the binding ones.

    Last collected
    Schedule
    every 5 min
  • Real-time balancing market prices at all ~1,600 SPP settlement locations — hubs, load areas, resources and the interfaces with its neighbours, the western market included — with energy, congestion and loss components, every five minutes.

    1 change ›
    1. 2026-11-15

      A file SPP never posted is passed over even when a whole run's worth are missing.

      Each run read a fixed slice of the dated files after the watermark. SPP never posted two hours on the evening of 2026-09-22, every file in the slice was a 404, nothing was read, so the watermark could not move and every later run asked for the same slice: the real-time streams stopped there for 54 days. Runs now read on until they find a run's worth, up to a day of missing files. The hole stays a hole.

    Last collected
    Schedule
    every 5 min

GenerationEnergy · 31 running

  • CAISO's batteries every five minutes, charging and discharging, split into stand-alone and hybrid as caiso.com's Today's Outlook draws them.

    1 change ›
    1. 2026-11-15

      First collected, from caiso.com's Today's Outlook files.

      The stand-alone and hybrid split of CAISO's battery output; the total is already the fuel mix's BATTERIES.

    Last collected
    Schedule
    every 5 min
  • CAISO's CO2 emission rate every five minutes by source — gas, imports, biogas, biomass, geothermal, coal — in metric tons an hour, from caiso.com's Today's Outlook.

    1 change ›
    1. 2026-11-15

      First collected, from caiso.com's Today's Outlook files.

      CAISO's emission rate by source, beside the fuel mix it is computed from.

    Last collected
    Schedule
    every 5 min
  • CAISO's hourly day-ahead wind and solar forecast for NP15, SP15 and ZP26, two days out. Kept as snapshots: every value it has held, stamped when Dryos first saw it.

    1 change ›
    1. 2026-09-14

      First collected, from CAISO OASIS.

      OASIS overwrites these forecasts in place with no issue time, so they are kept as snapshots stamped with Dryos's first sight of each value.

    Last collected
    Schedule
    every 15 min
  • The wind and solar forecast behind CAISO's fifteen-minute market, posted about 25 minutes ahead, for NP15, SP15, ZP26 and every Western EIM authority.

    1 change ›
    1. 2026-09-14

      First collected, from CAISO OASIS.

      Wind and solar by hub at every grain CAISO publishes them.

    Last collected
    Schedule
    every 15 min
  • The wind and solar forecast CAISO's real-time dispatch runs on, every five minutes, for NP15, SP15, ZP26 and every Western EIM authority.

    1 change ›
    1. 2026-09-14

      First collected, from CAISO OASIS.

      Wind and solar by hub at every grain CAISO publishes them.

    Last collected
    Schedule
    every 5 min
  • What is generating across CAISO: five-minute generation by source — solar, wind, geothermal, hydro, gas, nuclear, batteries and net imports — from the files behind caiso.com's Today's Outlook.

    1 change ›
    1. 2026-09-14

      First collected, from caiso.com's Today's Outlook files.

      The fuel mix every other operator here already had. CAISO's posted readings flicker by a few MW from one publication to the next; a row holds what CAISO said within the hour.

    Last collected
    Schedule
    every 5 min
  • CAISO's hourly hour-ahead wind and solar forecast for NP15, SP15 and ZP26. Kept as snapshots: every value it has held, stamped when Dryos first saw it.

    1 change ›
    1. 2026-09-14

      First collected, from CAISO OASIS.

      OASIS overwrites these forecasts in place with no issue time, so they are kept as snapshots stamped with Dryos's first sight of each value.

    Last collected
    Schedule
    every 15 min
  • Hourly actual wind and solar generation at NP15, SP15 and ZP26, posted about an hour after the hour.

    1 change ›
    1. 2026-09-14

      First collected, from CAISO OASIS.

      Wind and solar by hub at every grain CAISO publishes them.

    Last collected
    Schedule
    every 30 min
  • What is generating right now: 5-minute generation by fuel type from ERCOT's own dashboard feed — which retains two days, so the history exists because this collector was running.

    Last collected
    Schedule
    every 5 min
  • Hourly averaged actual solar generation and forecasts by geographical region — CenterWest through FarEast — refreshed hourly.

    Last collected
    Schedule
    hourly
  • Hourly averaged actual solar generation and ERCOT's own forecasts (STPPF, PVGRPP), system-wide, refreshed hourly with a rolling week of horizon.

    Last collected
    Schedule
    hourly
  • Hourly averaged actual wind generation and forecasts by geographical region — Panhandle, Coastal, South, West, North — refreshed hourly.

    Last collected
    Schedule
    hourly
  • Hourly averaged actual wind generation and ERCOT's own forecasts (STWPF, WGRPP), system-wide and by load zone, refreshed hourly with a rolling week of horizon.

    Last collected
    Schedule
    hourly
  • What is generating across New England at every dispatch run — gas, nuclear, hydro, wind, solar, wood, refuse, batteries and the rest — with the fuel ISO-NE marks as marginal.

    1 change ›
    1. 2026-11-15

      First collected, from ISO Express.

      Every other operator's fuel mix was here and ISO-NE's was not. Reconciled against the live files on 2026-11-15: every check passed.

    Last collected
    Schedule
    every 5 min
  • What is generating right now across MISO: 5-minute generation by fuel category from MISO's own dashboard feed, which keeps two days.

    Last collected
    Schedule
    every 5 min
  • Hourly wind and solar output against MISO's own forecast for today and tomorrow, republished every hour — each publication is kept as a vintage, so a forecast can be scored against what it said at the time.

    Last collected
    Schedule
    every 5 min
  • What is generating across New York every five minutes — gas, dual-fuel, nuclear, hydro, wind, other renewables and other fossil fuels.

    1 change ›
    1. 2026-09-14

      First collected, from NYISO's MIS.

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

    Last collected
    Schedule
    every 5 min
  • The generation offered into PJM each hour at its economic and emergency maximum, beside the capacity committed through the RPM market.

    1 change ›
    1. 2026-11-15

      First collected, from PJM Data Miner 2.

      Kept by PJM indefinitely. Reconciled against live responses on 2026-11-15.

    Last collected
    Schedule
    every 4 h
  • PJM's wind and solar forecasts for the next six hours in five-minute steps — solar utility-scale and behind-the-meter separately — re-issued every ten minutes and kept as vintages. PJM keeps them thirty days.

    1 change ›
    1. 2026-09-13

      First collected, from PJM Data Miner 2.

      Taken first of PJM's uncollected feeds because PJM keeps it thirty days. Reconciled against live responses on 2026-09-13.

    Last collected
    Schedule
    every 10 min
  • What generated across PJM each hour, by fuel: coal, gas, nuclear, hydro, wind, solar, storage, oil and the rest, with each one's share of the total. Posted fifteen minutes past the hour.

    1 change ›
    1. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    hourly
  • Estimated CO2, SO2 and NOx emitted across PJM each hour by each of its eleven fuel categories, in pounds, with each one's share of the total. PJM publishes it for the whole RTO only.

    1 change ›
    1. 2026-11-15

      First collected, from PJM Data Miner 2.

      PJM's hourly emissions by fuel, kept seven years. Reconciled against a live response on 2026-11-15.

    Last collected
    Schedule
    hourly
  • PJM's marginal CO2, SO2 and NOx emission rates at up to 12,600 pricing nodes — the RTO, its zones and the load buses — every hour, in pounds per MWh: what one more MWh at the node would emit. Informational, as PJM says; it supports no claim of clean energy.

    1 change ›
    1. 2026-11-15

      First collected, from PJM Data Miner 2.

      The emissions counterpart of the nodal price, kept seven years by PJM. Reconciled against a live response on 2026-11-15.

    Last collected
    Schedule
    hourly
  • Metered utility-scale solar output across the whole of PJM every five minutes, from a feed that holds thirty days. Behind-the-meter solar is not in it — PJM sees that as missing load.

    2 changes ›
    1. 2026-11-15

      A watermark older than PJM keeps the feed restarts inside what PJM still has.

      A run asks PJM for the window after the newest row held. Once that window is older than PJM's retention it answers empty, the run is recorded as skipped and the watermark never moves, so the stream stopped while reading as running: the real-time LMPs from early October, the fifteen-second feeds from mid-October. Runs now start a day inside the retention, trusting no more than fifteen days (PJM lists thirty for several feeds and kept fifteen on 2026-11-15). The stretch before is gone at the source and is a hole in the stream.

    2. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 5 min
  • PJM Settlements' hourly wind and solar generation for each region and the RTO, kept indefinitely and revised for ninety days — the settled record behind the real-time readings.

    1 change ›
    1. 2026-11-15

      First collected, from PJM Data Miner 2.

      Kept by PJM indefinitely. Reconciled against live responses on 2026-11-15.

    Last collected
    Schedule
    daily
  • PJM's hourly wind forecast for the next 46 hours, re-issued every ten minutes, and its hourly solar forecast for the next four days — utility-scale and behind-the-meter separately — re-issued hourly. Every issue is kept as a vintage.

    1 change ›
    1. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 10 min
  • Wind output across the whole of PJM, a SCADA reading every fifteen seconds, kept at that grain from a feed that holds thirty days.

    2 changes ›
    1. 2026-11-15

      A watermark older than PJM keeps the feed restarts inside what PJM still has.

      A run asks PJM for the window after the newest row held. Once that window is older than PJM's retention it answers empty, the run is recorded as skipped and the watermark never moves, so the stream stopped while reading as running: the real-time LMPs from early October, the fifteen-second feeds from mid-October. Runs now start a day inside the retention, trusting no more than fifteen days (PJM lists thirty for several feeds and kept fifteen on 2026-11-15). The stretch before is gone at the source and is a hole in the stream.

    2. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 5 min
  • What is generating across SPP's RTO every five minutes — wind, gas, coal, nuclear, hydro, solar, storage and the rest — each split into market-dispatched and self-scheduled output.

    1 change ›
    1. 2026-09-14

      First collected, from SPP's marketplace portal.

      Every other operator here had a fuel mix and SPP did not. This is the RTO, balancing authority SPP. Reconciled against a live response on 2026-09-14: schema, nulls, primary key, value bands and freshness passed, eleven fuels an interval, and market plus self equal to SPP's own chart figure.

    Last collected
    Schedule
    every 5 min
  • What is generating in SPP's western market, RTO West, every five minutes — hydro, coal, gas, wind, solar and storage — each split into market-dispatched and self-scheduled output.

    1 change ›
    1. 2026-09-14

      First collected, from SPP's marketplace portal.

      Every other operator here had a fuel mix and SPP did not. This is RTO West, balancing authority SWPW, live since 2026-04-01. Reconciled against a live response on 2026-09-14: schema, nulls, primary key, value bands and freshness passed, eleven fuels an interval, and market plus self equal to SPP's own chart figure.

    Last collected
    Schedule
    every 5 min
  • SPP's hourly wind and solar forecast seven days ahead for the RTO and RTO West, every hourly publication kept.

    3 changes ›
    1. 2026-11-15

      A file SPP never posted is passed over even when a whole run's worth are missing.

      Each run read a fixed slice of the dated files after the watermark. SPP never posted two hours on the evening of 2026-09-22, every file in the slice was a 404, nothing was read, so the watermark could not move and every later run asked for the same slice: the real-time streams stopped there for 54 days. Runs now read on until they find a run's worth, up to a day of missing files. The hole stays a hole.

    2. 2026-09-17

      The three-day gap from 2026-09-14 to 2026-09-17 is a collector fault, not a source one. SPP's dated files still hold it, and the runs after this read it back in oldest first.

      Every run since the first raised `TypeError: Start and end cannot both be tz-aware with different timezones` while planning which files to read. Postgres hands a stored timestamp back under `Etc/UTC`, which is the same zone as pandas' `UTC` and not the same object, and a range built between the two is refused — a break that could not happen on the SQLite these were written against. SPP had published normally throughout.

    3. 2026-09-14

      First collected, from SPP's marketplace portal.

      PJM's and CAISO's wind and solar forecasts were here and SPP's was not. Reconciled against the live files on 2026-09-14: schema, nulls, primary key, value bands and row counts passed.

    Last collected
    Schedule
    every 15 min
  • Wind and solar curtailed every five minutes in SPP's RTO and RTO West — by redispatch, manually, and for energy — a day behind.

    2 changes ›
    1. 2026-09-17

      Intervals SPP files under no balancing authority are dropped rather than stored as zero curtailment. Ten of them are missing from 2026-09-15, 21:10 to 21:55 Central.

      SPP writes the row anyway when an authority reports nothing for an interval — its two stamps and every other cell empty, the authority included. The authority is in the primary key, so the row could not be stored, and stored it would have claimed no curtailment in those intervals, which SPP did not say. The six value columns came back 0.88% null against a zero budget and the collector refused every batch for three days.

    2. 2026-09-14

      First collected, from SPP's marketplace portal.

      Curtailment is the story of SPP's wind, and it was not here. Reconciled against the live files on 2026-09-14: schema, nulls, primary key, value bands and row counts passed.

    Last collected
    Schedule
    hourly
  • Wind and solar output every five minutes in SPP's RTO and in RTO West, from the actuals SPP publishes beside its short-term resource forecast.

    3 changes ›
    1. 2026-11-15

      A file SPP never posted is passed over even when a whole run's worth are missing.

      Each run read a fixed slice of the dated files after the watermark. SPP never posted two hours on the evening of 2026-09-22, every file in the slice was a 404, nothing was read, so the watermark could not move and every later run asked for the same slice: the real-time streams stopped there for 54 days. Runs now read on until they find a run's worth, up to a day of missing files. The hole stays a hole.

    2. 2026-09-17

      The three-day gap from 2026-09-14 to 2026-09-17 is a collector fault, not a source one. SPP's dated files still hold it, and the runs after this read it back in oldest first.

      Every run since the first raised `TypeError: Start and end cannot both be tz-aware with different timezones` while planning which files to read. Postgres hands a stored timestamp back under `Etc/UTC`, which is the same zone as pandas' `UTC` and not the same object, and a range built between the two is refused — a break that could not happen on the SQLite these were written against. SPP had published normally throughout.

    3. 2026-09-14

      First collected, from SPP's marketplace portal.

      Every other operator's wind and solar output was here and SPP's was not. Reconciled against the live files on 2026-09-14: schema, nulls, primary key, value bands and row counts passed.

    Last collected
    Schedule
    every 5 min

LoadEnergy · 28 running

  • CAISO's hourly day-ahead load forecast for each area and every Western EIM authority. Kept as snapshots: every value it has held, stamped when Dryos first saw it.

    1 change ›
    1. 2026-09-14

      First collected, from CAISO OASIS.

      OASIS overwrites these forecasts in place with no issue time, so they are kept as snapshots stamped with Dryos's first sight of each value.

    Last collected
    Schedule
    every 15 min
  • The load forecast behind CAISO's fifteen-minute market, posted about 25 minutes ahead, for each of its areas and every Western EIM authority.

    1 change ›
    1. 2026-09-14

      First collected, from CAISO OASIS.

      Load by area at every grain CAISO publishes it.

    Last collected
    Schedule
    every 15 min
  • The load forecast CAISO's real-time dispatch runs on, every five minutes, for each of its areas and every Western EIM balancing authority.

    1 change ›
    1. 2026-09-14

      First collected, from CAISO OASIS.

      Load by area at every grain CAISO publishes it.

    Last collected
    Schedule
    every 5 min
  • Hourly integrated actual load for each CAISO area and every Western EIM authority, posted about an hour after the hour.

    1 change ›
    1. 2026-09-14

      First collected, from CAISO OASIS.

      Load by area at every grain CAISO publishes it.

    Last collected
    Schedule
    every 30 min
  • CAISO's net demand every five minutes — demand less wind and solar, the duck curve — as CAISO computes it for caiso.com's Today's Outlook.

    1 change ›
    1. 2026-11-15

      First collected, from caiso.com's Today's Outlook files.

      CAISO's own net demand — the duck curve — which the fuel mix and demand streams cannot reproduce: demand less their solar and wind misses it by up to 1.6 GW.

    Last collected
    Schedule
    every 5 min
  • CAISO's hourly load forecast for the next seven days for each area and every Western EIM authority. Kept as snapshots: every value it has held, stamped when Dryos first saw it.

    1 change ›
    1. 2026-09-14

      First collected, from CAISO OASIS.

      OASIS overwrites these forecasts in place with no issue time, so they are kept as snapshots stamped with Dryos's first sight of each value.

    Last collected
    Schedule
    every 15 min
  • CAISO-wide demand every five minutes — the Current demand line on caiso.com's Today's Outlook — flagged on the evenings CAISO calls on demand response.

    1 change ›
    1. 2026-09-14

      First collected, from caiso.com's Today's Outlook files.

      The five-minute system demand every other operator here already had. The file's forecast columns are not stored; OASIS publishes those by area.

    Last collected
    Schedule
    every 5 min
  • CAISO's hourly load forecast two days ahead for each area and every Western EIM authority. Kept as snapshots: every value it has held, stamped when Dryos first saw it.

    1 change ›
    1. 2026-09-14

      First collected, from CAISO OASIS.

      OASIS overwrites these forecasts in place with no issue time, so they are kept as snapshots stamped with Dryos's first sight of each value.

    Last collected
    Schedule
    every 15 min
  • Hourly average actual load for the four ERCOT forecast zones and the system total, published each morning for the prior day.

    Last collected
    Schedule
    hourly
  • Hourly average actual load for the eight ERCOT weather zones and the system total, published each morning for the prior day.

    Last collected
    Schedule
    hourly
  • ERCOT's hourly-refreshed load forecast for the four forecast zones and the system, seven days out — every revision kept.

    Last collected
    Schedule
    hourly
  • ERCOT's hourly-refreshed load forecast for the eight weather zones and the system, seven days out — every revision kept.

    Last collected
    Schedule
    hourly
  • The grid-conditions headline: 5-minute system demand against available capacity, from ERCOT's own dashboard feed.

    Last collected
    Schedule
    every 5 min
  • System-wide actual demand at 15-minute resolution, published hourly — the one-line answer to how much Texas is using.

    Last collected
    Schedule
    hourly
  • New England's load every five minutes — total, native and storage charging, with and without ISO-NE's estimate of behind-the-meter solar.

    1 change ›
    1. 2026-11-15

      First collected, from ISO Express.

      ISO-NE had prices here and no load. Reconciled against the live files on 2026-11-15: every check passed.

    Last collected
    Schedule
    every 5 min
  • MISO-wide real-time demand every five minutes, from the dashboard feed behind the Current Demand number — which keeps only today.

    Last collected
    Schedule
    every 5 min
  • Actual load every five minutes in each of NYISO's eleven zones — New York City, Long Island and the rest.

    1 change ›
    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.

    Last collected
    Schedule
    every 5 min
  • NYISO's hourly load forecast six days ahead for each of its eleven zones and the state, every daily issue kept.

    1 change ›
    1. 2026-09-14

      First collected, from NYISO's MIS.

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

    Last collected
    Schedule
    hourly
  • The load bias PJM's operators applied to every approved real-time SCED, intermediate-term SCED and pricing calculator case — their adjustment to the load forecast each case solved against, in MW — about every five minutes, posted every fifteen.

    1 change ›
    1. 2026-11-15

      First collected, from PJM Data Miner 2.

      Three small feeds PJM keeps seven years, one number per approved case each, taken as one stream. Reconciled against live responses on 2026-11-15.

    Last collected
    Schedule
    every 15 min
  • PJM's load forecast for the next two hours in five-minute steps, for 25 areas — the zones, the three regions and the RTO — re-issued every five minutes and kept as vintages, so a forecast can be scored against what it said at the time.

    1 change ›
    1. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 5 min
  • Real-time load every five minutes for each of PJM's 21 transmission zones, its three regions and the RTO total, from telemetry — the number on PJM's own load dashboard, not the metered load that settles.

    2 changes ›
    1. 2026-11-15

      A watermark older than PJM keeps the feed restarts inside what PJM still has.

      A run asks PJM for the window after the newest row held. Once that window is older than PJM's retention it answers empty, the run is recorded as skipped and the watermark never moves, so the stream stopped while reading as running: the real-time LMPs from early October, the fifteen-second feeds from mid-October. Runs now start a day inside the retention, trusting no more than fifteen days (PJM lists thirty for several feeds and kept fifteen on 2026-11-15). The stretch before is gone at the source and is a hole in the stream.

    2. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 5 min
  • Every load forecast PJM issued, kept by the moment it was made, for each forecast area — PJM's own archive of what it expected, to hold against what came.

    1 change ›
    1. 2026-11-15

      First collected, from PJM Data Miner 2.

      Kept by PJM indefinitely. Reconciled against live responses on 2026-11-15.

    Last collected
    Schedule
    every 4 h
  • PJM's settlement-quality hourly load for 30 load areas and the RTO, from the distribution companies' own meters, filled in company by company over the days after — so every run re-reads ten days and keeps each revision.

    1 change ›
    1. 2026-09-13

      First collected, from PJM Data Miner 2.

      PJM's hourly load, kept by PJM indefinitely. Reconciled against live responses on 2026-09-13.

    Last collected
    Schedule
    every 3 h
  • PJM's preliminary hourly load for ten areas, integrated from telemetry the day after — the figure between the five-minute reading and the metered settlement load.

    1 change ›
    1. 2026-09-13

      First collected, from PJM Data Miner 2.

      PJM's hourly load, kept by PJM indefinitely. Reconciled against live responses on 2026-09-13.

    Last collected
    Schedule
    every 3 h
  • PJM's hourly load forecast for the next seven days, for 25 areas — the zones, the three regions and the RTO — re-issued twice an hour and replaced in place at the source, so the vintages kept here are the only record of what it said.

    1 change ›
    1. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 30 min
  • Hourly load in each of SPP's 20 control zones across the RTO and RTO West, split as SPP files it into CF and NC load, about two days behind.

    1 change ›
    1. 2026-09-14

      First collected, from SPP's marketplace portal.

      SPP's load by zone was not here. Reconciled against the live files on 2026-09-14: schema, nulls, primary key, value bands and row counts passed.

    Last collected
    Schedule
    hourly
  • SPP's hourly load forecast seven days ahead for the RTO and RTO West, every hourly publication kept.

    3 changes ›
    1. 2026-11-15

      A file SPP never posted is passed over even when a whole run's worth are missing.

      Each run read a fixed slice of the dated files after the watermark. SPP never posted two hours on the evening of 2026-09-22, every file in the slice was a 404, nothing was read, so the watermark could not move and every later run asked for the same slice: the real-time streams stopped there for 54 days. Runs now read on until they find a run's worth, up to a day of missing files. The hole stays a hole.

    2. 2026-09-17

      The three-day gap from 2026-09-14 to 2026-09-17 is a collector fault, not a source one. SPP's dated files still hold it, and the runs after this read it back in oldest first.

      Every run since the first raised `TypeError: Start and end cannot both be tz-aware with different timezones` while planning which files to read. Postgres hands a stored timestamp back under `Etc/UTC`, which is the same zone as pandas' `UTC` and not the same object, and a range built between the two is refused — a break that could not happen on the SQLite these were written against. SPP had published normally throughout.

    3. 2026-09-14

      First collected, from SPP's marketplace portal.

      Every other operator's load forecast was here and SPP's was not. Reconciled against the live files on 2026-09-14: schema, nulls, primary key, value bands and row counts passed.

    Last collected
    Schedule
    every 15 min
  • Load every five minutes in SPP's RTO and in RTO West, with SPP's own short-term forecast for each interval beside it.

    4 changes ›
    1. 2026-11-15

      Rows that name no authority are dropped instead of refusing the file.

      The load file posted at 13:50 Central on 2026-09-15 carried its last three intervals with no authority and an actual of 0, and the one at 21:30 carried every row that way. Refusing them held the stream from then until 2026-11-15. Those intervals are a hole; a file that names nobody now reads as empty, so an SPP that stopped naming authorities would show as a stale stream.

    2. 2026-11-15

      A file SPP never posted is passed over even when a whole run's worth are missing.

      Each run read a fixed slice of the dated files after the watermark. SPP never posted two hours on the evening of 2026-09-22, every file in the slice was a 404, nothing was read, so the watermark could not move and every later run asked for the same slice: the real-time streams stopped there for 54 days. Runs now read on until they find a run's worth, up to a day of missing files. The hole stays a hole.

    3. 2026-09-17

      The three-day gap from 2026-09-14 to 2026-09-17 is a collector fault, not a source one. SPP's dated files still hold it, and the runs after this read it back in oldest first.

      Every run since the first raised `TypeError: Start and end cannot both be tz-aware with different timezones` while planning which files to read. Postgres hands a stored timestamp back under `Etc/UTC`, which is the same zone as pandas' `UTC` and not the same object, and a range built between the two is refused — a break that could not happen on the SQLite these were written against. SPP had published normally throughout.

    4. 2026-09-14

      First collected, from SPP's marketplace portal.

      Every other operator's system load was here and SPP's was not. Reconciled against the live files on 2026-09-14: schema, nulls, primary key, value bands and row counts passed.

    Last collected
    Schedule
    every 5 min

GridEnergy · 27 running

  • Energy moving between the Western Energy Imbalance Market's balancing authorities, tie by tie, every fifteen minutes, with the limit each transfer ran against and the time CAISO posted it.

    2 changes ›
    1. 2026-11-15

      A post time in the autumn's repeated hour is read from the interval it is for.

      UPD_DATE is Pacific wall-clock, and 01:00-02:00 on 2026-11-01 happened twice. Read as unknown, every flow posted in it failed the 2% null budget on source_published_at_utc, and the watermark stayed at 2026-11-01 04:35 until this fix. A post lands minutes before its interval, so the repeated hour now takes whichever of its two instants is closer to the interval.

    2. 2026-09-14

      First collected, from CAISO OASIS.

      The Western EIM transfers and their limits, the cause behind the WEIM areas' energy prices parting. Reconciled against a live response on 2026-09-14.

    Last collected
    Schedule
    every 15 min
  • Energy moving between the Western Energy Imbalance Market's balancing authorities, tie by tie, every five minutes, with the limit each transfer ran against and the time CAISO posted it.

    2 changes ›
    1. 2026-11-15

      A post time in the autumn's repeated hour is read from the interval it is for.

      UPD_DATE is Pacific wall-clock, and 01:00-02:00 on 2026-11-01 happened twice. Read as unknown, every flow posted in it failed the 2% null budget on source_published_at_utc, and the watermark stayed at 2026-11-01 04:35 until this fix. A post lands minutes before its interval, so the repeated hour now takes whichever of its two instants is closer to the interval.

    2. 2026-09-14

      First collected, from CAISO OASIS.

      The Western EIM transfers and their limits, the cause behind the WEIM areas' energy prices parting. Reconciled against a live response on 2026-09-14.

    Last collected
    Schedule
    every 5 min
  • Capacity on outage by forecast zone, hour by hour for the coming week — total, intermittent and not-yet-commercial — refreshed hourly.

    Last collected
    Schedule
    hourly
  • ERCOT's own hour-by-hour view of whether it has enough capacity: generation, load resources and offline-available MW per zone, 168 hours out, refreshed hourly.

    Last collected
    Schedule
    hourly
  • The hourly temperature forecast ERCOT plans against, per weather zone, published daily — every revision kept.

    Last collected
    Schedule
    hourly
  • Every forced and maintenance outage or derate at an ERCOT generator or battery — unit, fuel, MW out, start and end — posted daily for the third day back.

    1 change ›
    1. 2026-11-15

      Collected for the first time, with the 31 days the listing held.

      NP1-346 is the one per-unit outage record ERCOT publishes without a key. It had been skipped because the MIS base read only CSV; it now takes a reader per report, and this one reads the workbook. The listing keeps about a month and is the only free archive, so the first run took all 32 postings it held.

    Last collected
    Schedule
    hourly
  • MISO's net actual interchange with its neighbours every five minutes, over a rolling day.

    Last collected
    Schedule
    every 5 min
  • Scheduled interchange with each neighbouring balancing authority every five minutes, plus the MISO total, over a rolling day and a half.

    Last collected
    Schedule
    every 5 min
  • Flow every five minutes across each of NYISO's transfer interfaces — Total East, Central East, UPNY-ConEd and the ties with PJM, New England, Ontario and Quebec — against the limits it is held to.

    1 change ›
    1. 2026-09-14

      First collected, from NYISO's MIS.

      PJM's transfer interfaces were here and NYISO's were not. Reconciled against the live files on 2026-09-14: every check passed.

    Last collected
    Schedule
    every 5 min
  • 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. PJM keeps thirty days.

    2 changes ›
    1. 2026-11-15

      A watermark older than PJM keeps the feed restarts inside what PJM still has.

      A run asks PJM for the window after the newest row held. Once that window is older than PJM's retention it answers empty, the run is recorded as skipped and the watermark never moves, so the stream stopped while reading as running: the real-time LMPs from early October, the fifteen-second feeds from mid-October. Runs now start a day inside the retention, trusting no more than fifteen days (PJM lists thirty for several feeds and kept fifteen on 2026-11-15). The stretch before is gone at the source and is a hole in the stream.

    2. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 5 min
  • The flow the day-ahead market cleared over each of PJM's interface limits, hour by hour, beside the limit it was held to.

    1 change ›
    1. 2026-11-15

      First collected, from PJM Data Miner 2.

      Kept by PJM indefinitely. Reconciled against live responses on 2026-11-15.

    Last collected
    Schedule
    every 2 h
  • 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.

    1 change ›
    1. 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.

    Last collected
    Schedule
    every 4 h
  • 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, so a forecast can be held against what happened.

    1 change ›
    1. 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.

    Last collected
    Schedule
    every 4 h
  • 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.

    1 change ›
    1. 2026-09-13

      First collected, from PJM Data Miner 2.

      PJM's hourly record of its ties, kept indefinitely. Reconciled against live responses on 2026-09-13; replaces rt_scheduled_interchange, whose schedule equalled this feed's on every tie-hour compared.

    Last collected
    Schedule
    daily
  • Hour by hour, how much more each state in PJM generated than it used — positive exports, negative imports — PJM's netting of generation and load by jurisdiction.

    1 change ›
    1. 2026-11-15

      First collected, from PJM Data Miner 2.

      Kept by PJM indefinitely. Reconciled against live responses on 2026-11-15.

    Last collected
    Schedule
    every 3 h
  • Yesterday hour by hour for PJM's zones and the Mid-Atlantic, from the morning Operations Summary: the load each area saw and its dispatch rate.

    1 change ›
    1. 2026-11-15

      First collected, from PJM Data Miner 2.

      PJM's morning Operations Summary, kept by PJM indefinitely. Reconciled against live responses on 2026-11-15.

    Last collected
    Schedule
    every 2 h
  • PJM's forecast limit on each of its transfer interfaces at the day's projected peak, from the morning summary. Each projection is kept as a vintage stamped with the moment PJM wrote it, so a forecast can be held against what happened.

    1 change ›
    1. 2026-11-15

      First collected, from PJM Data Miner 2.

      PJM's morning Operations Summary, kept by PJM indefinitely. Reconciled against live responses on 2026-11-15.

    Last collected
    Schedule
    every 2 h
  • PJM's morning projection for each region and zone at the day's RTO peak: load forecast, scheduled capacity and unscheduled steam. Each projection is kept as a vintage stamped with the moment PJM wrote it, so a forecast can be held against what happened.

    1 change ›
    1. 2026-11-15

      First collected, from PJM Data Miner 2.

      PJM's morning Operations Summary, kept by PJM indefinitely. Reconciled against live responses on 2026-11-15.

    Last collected
    Schedule
    every 2 h
  • PJM's morning projection of the day's peak for the whole RTO: the load forecast, the capacity scheduled against it, net interchange and the operating reserve left over. Each projection is kept as a vintage stamped with the moment PJM wrote it, so a forecast can be held against what happened.

    1 change ›
    1. 2026-11-15

      First collected, from PJM Data Miner 2.

      PJM's morning Operations Summary, kept by PJM indefinitely. Reconciled against live responses on 2026-11-15.

    Last collected
    Schedule
    every 2 h
  • The flow PJM has scheduled over each tie with its neighbours at the day's projected peak, from the morning summary. Each projection is kept as a vintage stamped with the moment PJM wrote it, so a forecast can be held against what happened.

    1 change ›
    1. 2026-11-15

      First collected, from PJM Data Miner 2.

      PJM's morning Operations Summary, kept by PJM indefinitely. Reconciled against live responses on 2026-11-15.

    Last collected
    Schedule
    every 2 h
  • Which five-minute intervals PJM flags as Performance Assessment Intervals — the emergencies in which capacity resources are scored on delivery — for the RTO and the active subzone, as PJM first flags them. PJM keeps sixty days.

    1 change ›
    1. 2026-09-13

      First collected, from PJM Data Miner 2.

      PJM keeps sixty days of it. Reconciled against live responses on 2026-09-13, when every interval read No PAI.

    Last collected
    Schedule
    every 10 min
  • Actual against scheduled flow every five minutes on each of PJM's ties with its neighbours — New York, MISO, TVA, Duke and the rest — plus the MISO net and the RTO net. Positive is into PJM.

    2 changes ›
    1. 2026-11-15

      A watermark older than PJM keeps the feed restarts inside what PJM still has.

      A run asks PJM for the window after the newest row held. Once that window is older than PJM's retention it answers empty, the run is recorded as skipped and the watermark never moves, so the stream stopped while reading as running: the real-time LMPs from early October, the fifteen-second feeds from mid-October. Runs now start a day inside the retention, trusting no more than fifteen days (PJM lists thirty for several feeds and kept fifteen on 2026-11-15). The stretch before is gone at the source and is a hole in the stream.

    2. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 5 min
  • 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. How close the grid is to its edges.

    3 changes ›
    1. 2026-11-15

      A watermark older than PJM keeps the feed restarts inside what PJM still has.

      A run asks PJM for the window after the newest row held. Once that window is older than PJM's retention it answers empty, the run is recorded as skipped and the watermark never moves, so the stream stopped while reading as running: the real-time LMPs from early October, the fifteen-second feeds from mid-October. Runs now start a day inside the retention, trusting no more than fifteen days (PJM lists thirty for several feeds and kept fifteen on 2026-11-15). The stretch before is gone at the source and is a hole in the stream.

    2. 2026-09-17

      The transfer-limit band accepts a negative limit, and the intervals it had been refusing landed.

      PJM signs a limit the way it signs the flow it bounds. On 2026-09-15 CENTRAL ran to -4,040.83 MW and COMED sat pinned at -200 for hours, with the flow tracking each. A floor of zero read that as a parse error and stopped the stream for three days.

    3. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 5 min
  • Generating capacity forecast out of service, hour by hour a week ahead, by fuel, for the RTO and RTO West — every daily report kept.

    1 change ›
    1. 2026-09-14

      First collected, from SPP's marketplace portal.

      PJM's outage forecasts were here and SPP's was not. Reconciled against the live files on 2026-09-14: schema, nulls, primary key, value bands and row counts passed.

    Last collected
    Schedule
    hourly
  • The day-ahead market's hourly summary for the RTO and RTO West — generation, demand and virtual bids cleared, interchange, the system marginal price and reserves — posted for tomorrow each afternoon.

    1 change ›
    1. 2026-09-14

      First collected, from SPP's marketplace portal.

      SPP's day-ahead market summary was not here. Reconciled against the live files on 2026-09-14: schema, nulls, primary key, value bands and row counts passed.

    Last collected
    Schedule
    hourly
  • Actual flow every minute on each of SPP's ties with its neighbours, in the RTO and RTO West, with each authority's net actual and net scheduled interchange.

    1 change ›
    1. 2026-09-14

      First collected, from SPP's interchange trend charts.

      PJM's and MISO's interchange were here and SPP's was not, and SPP keeps a day of it. Reconciled against the live files on 2026-09-14: every check passed.

    Last collected
    Schedule
    every 5 min
  • The real-time market's five-minute summary for the RTO and RTO West — generation, demand response, interchange, the system marginal price, the price range and reserves — a day behind.

    1 change ›
    1. 2026-09-14

      First collected, from SPP's marketplace portal.

      SPP's market summary was not here. Reconciled against the live files on 2026-09-14: schema, nulls, primary key, value bands and row counts passed.

    Last collected
    Schedule
    hourly

AncillaryEnergy · 17 running

  • Hourly day-ahead clearing prices for regulation up and down, spinning and non-spinning reserve and regulation mileage, in CAISO's six ancillary service regions, posted for the whole of tomorrow each afternoon.

    1 change ›
    1. 2026-09-14

      First collected, from CAISO OASIS.

      The ancillary prices ERCOT, MISO and PJM already had. Reconciled against a live response on 2026-09-14.

    Last collected
    Schedule
    hourly
  • Fifteen-minute real-time clearing prices for regulation up and down, spinning and non-spinning reserve and regulation mileage, in CAISO's six ancillary service regions.

    2 changes ›
    1. 2026-09-14

      A request always reaches the next hour.

      OASIS refuses a PRC_INTVL_AS window that opens and closes inside one clock hour (error 1001), which is what a run a quarter past or half past asked for, so most runs failed and only the one on the hour collected. Nothing was lost: that run healed the gap each time.

    2. 2026-09-14

      First collected, from CAISO OASIS.

      The ancillary prices ERCOT, MISO and PJM already had. Reconciled against a live response on 2026-09-14.

    Last collected
    Schedule
    every 15 min
  • How much of each ancillary service ERCOT plans to procure, per hour, seven days out — republished daily, with every revision kept.

    Last collected
    Schedule
    daily
  • Day-ahead hourly clearing prices for each ancillary service product, published once daily after the DAM run.

    Last collected
    Schedule
    hourly
  • The 15-minute settlement clearing price for each ancillary service product — what real-time capacity settlement actually uses.

    Last collected
    Schedule
    every 15 min
  • Real-time capacity clearing prices per ancillary service from every SCED run, roughly every five minutes — the RTC-era companion to the energy LMP.

    Last collected
    Schedule
    every 5 min
  • Market clearing prices for regulation, spinning, supplemental, short-term and ramp reserves in each of MISO's eight reserve zones: the real-time price every five minutes and the day-ahead price for the hour, from a feed that holds only the current interval.

    Last collected
    Schedule
    every 5 min
  • Hourly day-ahead clearing prices for NYISO's reserves and regulation capacity in each of its eleven zones, posted for tomorrow each morning.

    1 change ›
    1. 2026-09-14

      First collected, from NYISO's MIS.

      Every other operator's day-ahead reserve prices were here and NYISO's were not. Reconciled against the live files on 2026-09-14: every check passed.

    Last collected
    Schedule
    hourly
  • Five-minute clearing prices for NYISO's reserves and regulation — ten-minute spinning and non-synchronous, thirty-minute operating, regulation capacity and movement — in each of its eleven zones.

    1 change ›
    1. 2026-09-14

      First collected, from NYISO's MIS.

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

    Last collected
    Schedule
    every 5 min
  • PJM's day-ahead results for synchronized, primary and thirty-minute reserve, hourly, for the RTO and the Mid-Atlantic/Dominion subzone: clearing prices, requirements and the megawatts behind them, posted with tomorrow's market.

    1 change ›
    1. 2026-09-13

      First collected, from PJM Data Miner 2.

      PJM's ancillary market results, kept by PJM indefinitely. Reconciled against live responses on 2026-09-13, and checked price for price against PJM's two ancillary price feeds, which are copies of it and are not collected.

    Last collected
    Schedule
    hourly
  • Synchronized, primary and thirty-minute reserve every five minutes in the RTO and the Mid-Atlantic/Dominion sub-zone: the megawatts the dispatch held against each requirement, the clearing price, and whether PJM called the interval short. Preliminary, from the operating day.

    2 changes ›
    1. 2026-11-15

      A watermark older than PJM keeps the feed restarts inside what PJM still has.

      A run asks PJM for the window after the newest row held. Once that window is older than PJM's retention it answers empty, the run is recorded as skipped and the watermark never moves, so the stream stopped while reading as running: the real-time LMPs from early October, the fifteen-second feeds from mid-October. Runs now start a day inside the retention, trusting no more than fifteen days (PJM lists thirty for several feeds and kept fifteen on 2026-11-15). The stretch before is gone at the source and is a hole in the stream.

    2. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 5 min
  • The megawatts of synchronized, primary and thirty-minute reserve PJM is holding against each requirement, as the control room sees them every fifteen seconds, in the RTO and the Mid-Atlantic/Dominion sub-zone. Thirteen series; PJM keeps fifteen days.

    2 changes ›
    1. 2026-11-15

      A watermark older than PJM keeps the feed restarts inside what PJM still has.

      A run asks PJM for the window after the newest row held. Once that window is older than PJM's retention it answers empty, the run is recorded as skipped and the watermark never moves, so the stream stopped while reading as running: the real-time LMPs from early October, the fifteen-second feeds from mid-October. Runs now start a day inside the retention, trusting no more than fifteen days (PJM lists thirty for several feeds and kept fifteen on 2026-11-15). The stretch before is gone at the source and is a hole in the stream.

    2. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 5 min
  • PJM's settled real-time results for regulation, synchronized, primary and thirty-minute reserve, every five minutes, for the RTO and the Mid-Atlantic/Dominion subzone: clearing prices, regulation's capability and performance prices, requirements and the megawatts behind them. Posted about three days late, on business days.

    1 change ›
    1. 2026-09-13

      First collected, from PJM Data Miner 2.

      PJM's ancillary market results, kept by PJM indefinitely. Reconciled against live responses on 2026-09-13, and checked price for price against PJM's two ancillary price feeds, which are copies of it and are not collected.

    Last collected
    Schedule
    every 3 h
  • The five-minute regulation market clearing price for the PJM RTO — its capability and performance components, the capped price, and the megawatts cleared against the requirement. Preliminary, from the operating day; the verified price settles later.

    2 changes ›
    1. 2026-11-15

      A watermark older than PJM keeps the feed restarts inside what PJM still has.

      A run asks PJM for the window after the newest row held. Once that window is older than PJM's retention it answers empty, the run is recorded as skipped and the watermark never moves, so the stream stopped while reading as running: the real-time LMPs from early October, the fifteen-second feeds from mid-October. Runs now start a day inside the retention, trusting no more than fifteen days (PJM lists thirty for several feeds and kept fifteen on 2026-11-15). The stretch before is gone at the source and is a hole in the stream.

    2. 2026-09-09

      First collected, from PJM Data Miner 2.

      Non-member API access was granted on 2026-09-09. Reconciled against live responses the same day: schema, nulls, primary key, value bands and row counts all passed, and the energy identity and the node naming rule were checked row-for-row against the day-ahead feed and the pricing-node master.

    Last collected
    Schedule
    every 5 min
  • Hourly day-ahead clearing prices for SPP's reserve products — regulation, spinning, supplemental, ramp and uncertainty reserve — in every reserve zone, posted for the whole of tomorrow each afternoon.

    1 change ›
    1. 2026-09-14

      First collected, from SPP's marketplace portal.

      Every other operator's day-ahead reserve prices were here and SPP's were not. Reconciled against the live files on 2026-09-14: every check passed, eight zones an hour, seven products each.

    Last collected
    Schedule
    hourly
  • Five-minute clearing prices for SPP's reserve products — regulation and its mileage, spinning, supplemental, ramp and uncertainty reserve — in every reserve zone of the RTO and RTO West.

    2 changes ›
    1. 2026-11-15

      A file SPP never posted is passed over even when a whole run's worth are missing.

      Each run read a fixed slice of the dated files after the watermark. SPP never posted two hours on the evening of 2026-09-22, every file in the slice was a 404, nothing was read, so the watermark could not move and every later run asked for the same slice: the real-time streams stopped there for 54 days. Runs now read on until they find a run's worth, up to a day of missing files. The hole stays a hole.

    2. 2026-09-14

      First collected, from SPP's marketplace portal.

      Every other operator's reserve prices were here and SPP's were not. Reconciled against the live files on 2026-09-14: every check passed, eight zones an interval, nine products each.

    Last collected
    Schedule
    every 5 min
  • The megawatts of each reserve product SPP's real-time market cleared, every five minutes, by reserve zone in the RTO and RTO West.

    2 changes ›
    1. 2026-11-15

      A file SPP never posted is passed over even when a whole run's worth are missing.

      Each run read a fixed slice of the dated files after the watermark. SPP never posted two hours on the evening of 2026-09-22, every file in the slice was a 404, nothing was read, so the watermark could not move and every later run asked for the same slice: the real-time streams stopped there for 54 days. Runs now read on until they find a run's worth, up to a day of missing files. The hole stays a hole.

    2. 2026-09-14

      First collected, from SPP's marketplace portal.

      SPP's reserve prices were here without the quantities they cleared. Reconciled against the live files on 2026-09-14: every check passed.

    Last collected
    Schedule
    every 5 min

ForecastWeather · 3 running

AnalysisWeather · 1 running

PermitsProperty · 4 running

  • Every building, trade and driveway permit the City of Austin issues, by the day, with the work, the value, the contractor and the place.

    1 change ›
    1. 2026-09-13

      Permits carry a subject and an action (rules version 1), kept in a table of their own so the city's rows are untouched.

      Austin has no roofing type and no column that says what a permit is for; a re-roof is a building permit whose description says so, and a new house's description rides on every trade permit it pulls. The subject (Roof, HVAC, Home, …) and action (New, Replace, Repair, …) are read off the permit type, the work class and the description by versioned rules in reference/permit_classes.py, after every run, and served beside the city's columns. They are a maintainer's reading, not the city's: stored apart, joined on at serve time, and a permit not yet labelled reads Unspecified.

    Last collected
    Schedule
    daily
  • Building permits from every city in Collin County — Plano, Frisco, McKinney, Allen and thirty more — as the appraisal district records them.

    Last collected
    Schedule
    daily
  • Every building and trade permit filed with the City of Fort Worth, by the day, with its status, the work, the value and the place.

    Last collected
    Schedule
    daily
  • Every building and trade permit the City of San Antonio issues, by the day, with its own re-roof type, the work, the company and the place.

    1 change ›
    1. 2026-09-13

      Permits carry a subject and an action (rules version 1), kept in a table of their own so the city's rows are untouched.

      San Antonio's sixty-odd permit types nearly say what a permit is for (RE_ROOF is a roof being replaced), but its trade types name only the trade and its descriptions are addresses and names. The subject (Roof, HVAC, Home, …) and action (New, Replace, Repair, …) are read off the type, the work type and, for trade permits only, the words, by versioned rules in reference/permit_classes.py, after every run, and served beside the city's columns. About half the permits are trade permits whose action the city does not state; those read Unspecified rather than a guess.

    Last collected
    Schedule
    daily

Read any of it

Every collector here fills a stream you can read over the REST API, through your AI agent on the MCP server, or on a live dashboard.