Utilities: Monitoring Outage Maps and Service Status Pages

A utility's outage map exists for exactly one high-pressure moment: a widespread outage, when traffic to that page spikes far beyond a normal day and a rendering failure is both more likely and more visible than at any other time. The map that works fine every other day of the year is precisely the page worth checking closely during a storm, not the one to assume is fine because it usually is.

Where This Comes Up

• Load-driven rendering failures. A map widget or status table that degrades under the traffic surge a real outage event brings.
• Data staleness. An outage map that stops updating due to a backend sync issue looks, to a customer, exactly like the utility doesn't know about their outage at all.
• Third-party map or widget dependencies. Many outage maps embed a third-party mapping service — confirming that dependency renders correctly is as important as the utility's own page.
• Multi-service consistency. Utilities serving electricity, gas, and water separately often run separate status pages per service, each worth its own check.

Capturing the Outage Map

curl --request POST \
  --url https://api.prod.ss.snapshot-site.com/api/v1/screenshot \
  --header 'Content-Type: application/json' \
  --header 'x-snapshotsiteapi-key: YOUR_API_KEY' \
  --data '{
    "url": "https://example-utility.com/outage-map",
    "format": "png",
    "width": 1440,
    "fullSize": true,
    "hideCookie": true,
    "delay": 2
  }'

delay matters here — map widgets and live status tables frequently render after the initial page shell, and a capture taken instantly can miss them entirely.

A Tight Cadence During Active Events

Similar to a ticketing on-sale window, an outage map benefits from a much tighter capture interval during an active, widespread outage than routine daily monitoring would provide — every few minutes for the duration of the event. Compare each capture against a known-good baseline to flag a rendering failure immediately, during the exact window when the most people are relying on the page:

curl --request POST \
  --url https://api.prod.ss.snapshot-site.com/api/v3/compare \
  --header 'Content-Type: application/json' \
  --header 'x-snapshotsiteapi-key: YOUR_API_KEY' \
  --data '{
    "before": {"imageUrl": "https://cdn.example.com/baselines/outage-map-good.png"},
    "after": {"url": "https://example-utility.com/outage-map", "width": 1440, "fullSize": true, "hideCookie": true},
    "threshold": 0.2
  }'

Building the Monitor Around Weather and Event Triggers

The practical setup ties the tight-interval monitoring window to known risk periods — severe weather forecasts, planned maintenance windows — rather than running at high frequency year-round. Route alerts to whoever is on call for communications or customer support during an active event, since a broken outage map during a real outage is an immediate operational problem, not something to triage the next morning.

For utilities, the outage map matters most in exactly the moments it's most likely to fail — Snapshot Site watches that specific window automatically.