Current
Every watched rate sheet matches the version the encoded rates were taken from.
No plan is waiting on a filing we have already seen.
Every time a watched rate sheet stops matching the version the served rates were taken from. The monitor compares bytes, so it cannot tell a re-filed rate from a re-rendered PDF - both are real changes to the document and only one needs the rates re-derived. The outcome column says which, and a row that changed no rate is kept rather than hidden.
| Detected | Affects | Change | Outcome |
|---|---|---|---|
| 2026-08-20 | sce-toud-4-9-2026-06-01, sce-toud-5-8-2026-06-01, sce-toud-prime-2026-06-01 | content changed (1722304 -> 1508586 bytes) | no rate change SCE re-rendered the TOU-D book 2026-08-19, 22 pages to 19. Every energy charge, baseline credit and period rate identical. Removed figures were the CARE surcharge and DWR bond charge, in CARE eligibility prose, not in any TOU-D rate table. |
Whether the monitor ran each day. A gap is a day when staleness could not be ruled out. This is not an uptime chart - uptime is the wrong question for a data product. A day counts as checked whether or not anything changed, because a quiet day and a broken monitor must not look alike.
3 of 90 days had at least one check. Hover a cell for the date and how many of the 81 watched sources were checked that day. · The service is new, so most of this window predates it.
Time from detecting that a utility filed a change to the served rates being updated. This bounds how out-of-date any figure here can be, and it is computed from the record rather than promised.
Measured over every filing since launch, not the window above. Rate changes arrive roughly quarterly, so a 90-day window would usually contain too few to mean anything - and a median over one sample would look like precision it does not have.
Time from detecting a filing to the encoded rates being updated. Pending means detected and not yet encoded.
Every rate API claims to be current, and from the outside that claim cannot be checked. This one can: the source documents are polled daily, every version is kept, and when a utility files something we have not encoded yet this page says so by name. A status page that can only report good news is marketing.
Browse rates ·
GET /health returns this page's summary as JSON, without a key.
GET /changes returns the change log as JSON, and needs one.