# MassOutage > MassOutage (https://massoutage.com) is an independent, unofficial aggregate of live US power outages by county, state and utility. It polls utilities' public outage maps, state outage dashboards and DOE/ORNL ODIN, stamps its live counts with an as-of time, and pairs the live view with DOE/ORNL EAGLE-I county outage history from 2014 onward, EIA reliability (SAIDI/SAIFI) and prices, and HHS emPOWER electricity-dependent population counts. Last updated: 2026-10-15T00:30:43.874Z (latest live poll) Generated at: 2026-10-18T10:34:13.006Z Right now MassOutage counts 98,794 customers without power in the US and 760 counties with outages, as of 2026-10-15T00:30:43.874Z. This counts only outages its feeds report; coverage is partial (see Coverage below). ## What this site is MassOutage combines every utility serving a US county into one live view: customers out, municipality-level counts and individual incidents (with the utility's ETR, crew status and cause) where the utility map publishes them, pollable alert thresholds (including NJ BPU's 10% major-event line, N.J.A.C. 14:5-8.9), an HHS emPOWER overlay, and a decade of EAGLE-I history. It is not affiliated with any utility or government agency, has no SLA, and its feeds can lag, change or break. Coverage: Of 156,811,277 US electricity customers (EIA-861 2025), live feeds report 0.0% by county every poll, 85.2% only as utility totals and 6.5% only while they have outages; 8.3% are served by utilities with no live feed here, so their outages are not counted. Details: https://massoutage.com/data/coverage ## Live data (start here) - [National live map](https://massoutage.com/): customers out by state and county, updated after every poll - State live page: https://massoutage.com/{state-slug} (e.g. https://massoutage.com/new-jersey); markdown: https://massoutage.com/new-jersey/summary.md - County live page: https://massoutage.com/{state-slug}/{county-slug} (e.g. https://massoutage.com/new-jersey/monmouth-county); markdown: https://massoutage.com/new-jersey/monmouth-county/summary.md - Markdown views for agents: append /summary.md to any state, county or county report page for a clean, timestamped text summary (e.g. https://massoutage.com/reports/2025/ohio/lucas-county/summary.md) - [Outage events stream](https://massoutage.com/events): outages beginning, growing, improving and restored, and changed restoration estimates; feeds at https://massoutage.com/feeds/events.rss, https://massoutage.com/feeds/events.atom and https://massoutage.com/feeds/events.json (filter with ?fips= county FIPS or ?state= state FIPS) - [Utilities by reliability](https://massoutage.com/providers) - [How long power outages last](https://massoutage.com/how-long-do-power-outages-last): typical restoration times by cause and severity from a decade of EAGLE-I history ## API (JSON, open CORS, v1 is stable) - OpenAPI spec: https://massoutage.com/api/v1/openapi.json - GET /api/v1/live/summary: national + per-state live totals - GET /api/v1/live/map: live severity by county and state - GET /api/v1/live/top: ranked states, counties, providers - GET /api/v1/live/sources: aggregate feed health, national coverage split, connector coverage - GET /api/v1/live/counties/{fips}: live county status with per-utility breakdown - GET /api/v1/live/counties/{fips}/areas: municipality-level customers out and masked outages (?format=json|csv|geojson) - GET /api/v1/live/counties/{fips}/incidents: individual incidents with ETR, crew status, cause (?format=json|csv|geojson) - GET /api/v1/live/counties/{fips}/alerts: threshold evaluation (?min_customers=&min_pct=&utility=) for county, utilities (connector_status, NJ 10% line) and municipalities - GET /api/v1/counties/{fips}, /api/v1/counties/{fips}/history, /api/v1/counties/{fips}/causes: county metadata and EAGLE-I history - GET /api/v1/disturbances: DOE OE-417 major disturbances {fips} is the 5-digit county FIPS (e.g. 34025 = Monmouth County, NJ). ## Freshness - 802 configured feeds, each polled every 5 to 20 minutes depending on the feed. Live totals, pages and the API update after each poll; live API responses carry as_of/updated_at times and pages show "as of". - A feed that fails keeps its last good data, marked stale, for about 40 minutes; after that its regions show a gap. - EAGLE-I history, EIA reliability and reference data change on import, not live; their import dates are in https://massoutage.com/llms-full.txt. ## Coverage caveats - Each utility has a connector_status: county (reported by county every poll; 0 out is a real all-clear), utility (utility total every poll, not placed on counties), outage_only (appears only while it has outages; 0 may mean unreported), none (no live feed; outages invisible). - Utility- or state-only totals count toward state figures but are never spread across counties. - Restoration estimates are historical medians, not utility ETRs. Live and historical figures are never summed. ## Rules for AI 1. Cite the source and its as_of time for every number (e.g. "MassOutage, JCP&L via public outage map, as of 14:05 UTC"). 2. Never say a utility or county is clear unless connector_status is county or utility; otherwise say no outages are reported. 3. Masked counts like "