Can I check a specific store?

You pull the outage feed nationally or filtered to the states, counties, or utilities you care about, then match your own store coordinates against the outage geometry we return. That tells you whether a location sits inside an active outage the utility has reported. What we report is what the utility publishes about the surrounding area, not a meter reading for one building.

Do you provide estimated restoration times?

Yes, when the utility publishes one. ETR and reported cause come through exactly as the utility reports them. Not every utility publishes either field, so coverage varies by provider.

How current is the data?

We refresh every 10 minutes, from statewide totals down to individual utilities. Every record comes from the reporting utility, so nothing is modeled or crowdsourced.

Can we get historical data for claims and analysis?

Yes. Our historical outage data goes back to 2017 and is available down to city level, which covers insurance claims, post-event review, and site selection work. Tell us your footprint and we can scope a dataset for it.

Who we serve

Retail & Multi-Location Brands

See which stores lost power, and when they're getting it back.

A dark store costs you a day of sales, and if it holds perishable stock, a lot more than that. PowerOutage.com shows you which locations sit inside a confirmed outage across every utility in your footprint, without a single call to the field.

Request Integration

Why retail teams use PowerOutage.com

Confirmed grid status across a national footprint, for the teams protecting sales, inventory, and store operations.

Hundreds of stores, dozens of utilities, one endpoint. A national footprint sits under a long list of electric providers. No power outage API covers more of them than we do, and it takes one integration instead of a per-utility scramble every time weather moves through.
Skip the call to the store. Confirming a store lost power usually means reaching a manager who is already standing in a dark building. Check the grid first and start from an answer.
Protect perishable inventory. In grocery, convenience, and food service, the clock on refrigerated stock starts the second power drops. Triage depends on knowing which sites are hit and for how long.
Restoration times and cause from the utility. When the utility publishes an ETR and a cause, we pass both through. A two-hour outage and an all-day outage call for very different decisions about generators, staff, and stock.
A record that holds up after the storm. Every outage we return came from the utility itself, which gives loss prevention and insurance teams a time-stamped account of which sites went down and when.

We handle external verification and context. There's no predictive modeling here, and you never have to send us customer PII.

Services available today

Aggregated Power Status API

The most comprehensive coverage of any power outage API, in one normalized feed.

Look up outages by GPS coordinate, county, utility service territory, or polygon.

One schema across every utility we cover, so you build the integration once.

Outage counts, restoration times, and cause, exactly as the utility reports them.

Refreshed every 10 minutes, from statewide totals down to individual utilities.

Common workflows

Give store support, facilities, and loss prevention the same view of which sites are dark.

Store-down triage

Screen POS and network alarms against confirmed outages before the support queue starts working tickets nobody can close.

Cold chain response

Surface the affected sites holding perishable stock first, then use published restoration times to decide what gets moved.

Generator prioritization

Rank which locations get portable power based on how wide the event is and when the utility expects it back.

Custom dashboard development

Need more than an API? We build dashboards around the way your team already works. Tell us what you're tracking and we'll scope it with you.

Security & reliability

You never send us customer PII. You pull in a national snapshot and query it with your locations.
Scoped API keys, limited to the endpoints and regions you actually need.
Redundant ingestion, monitoring, and alerting built for teams running around the clock.

FAQ

Here are some commonly asked questions