StatusDetector

Status intelligence

Internet Pulse

A live snapshot of the internet from StatusDetector's vantage point. Built from the same probes, official feeds, and community reports the rest of the site uses — rolled up so you can read the whole catalogue at a glance.

Updated just nowRefreshes every 2 min

Catalogue coverage

Catalogue coverage is temporarily limited

External infrastructure feeds are still available. Service-level snapshots are refreshing — we don't publish an aggregate percentage until enough services report fresh data.

Fresh service snapshots

Services with fresh data in the last 24 h

0
Services without recent data

Out of 424 catalogue entries

424
External watchlist

AWS · Cloudflare

Available
Last refresh attempt

Refreshes every 2 min

just now
How we decide
Source details — per-pipeline health

Data source health

Where the numbers above come from — and whether each pipeline is currently healthy.

1/4

Official status feeds

Unavailable

No fresh snapshots ingested in the last 24 h.

Probe pipeline

Unavailable

No probes recorded in the last hour.

Community reports

Unavailable

Reports table did not respond.

External watchlist

Available

2 of 2 cloud providers responding.

External infrastructure watchlist

The internet runs on a handful of providers we surface separately because they affect many tracked services at once. Not counted in catalogue health above.

AWS via the public Service Health RSS feed; Cloudflare via its public Statuspage. GCP and Azure don’t expose conforming feeds and are intentionally omitted rather than surfaced with mock data.

Most affected (last 24 h)

No services tracked any incidents in the last 24 hours.

Trending in user reports (last hour)

No community reports submitted in the last hour.

Community report volume by category (last hour)

No reports submitted in the last hour.

How this is computed. Catalogue health counts services whose latest official-status snapshot is “none” or “maintenance” within the last 24 hours, divided by services that have any data in the window. Services with no recent data are counted separately rather than assumed healthy. Affected services are sorted by combined active + last-24h incident count. Trending services and category report volume come from the user-reports table over the last hour. Cloud-provider rows pull live from public AWS / Cloudflare feeds and are listed as a watchlist, not part of the catalogue rollup. Refreshed every 2 min via Next ISR. Full methodology