StatusDetector

Live · independent status intelligence

Detect what’s down across the internet.

Check websites, apps, AI tools, delivery systems, banks, and infrastructure signals in one place.

Services tracked
424
Official feeds wired
37
Signals · last hour
1

Live activity

Recent signals across the catalogue

Probe pipeline delayed

Pinned vendor feeds

Direct from Statuspage · refreshes every 1 min

Active incident console

1 incident · scan 02:47 PM UTC

Open Shutdown Radar for the full live feed and recent shutdowns.

How we know

Vendor status feeds
37 services with an official Statuspage or vendor JSON feed. We read it directly — no scraping.
Live HTTP / SSL probes
424 services probed from our infrastructure. 401 / 403 / 429 responses are flagged as probe-blocked, not down.
Anonymous community reports
30-minute rolling window. Weighted low individually; escalate only with volume.

Full methodology · last refresh: 02:47 PM UTC · catalogue: 424 services across 13 categories.

Frequently asked

The questions readers most often have on their first visit.

What makes StatusDetector different from other status checkers?

We combine three independent signals — the vendor's own status feed, our own HTTP/SSL probes from a fixed location, and anonymous community reports — into a single confidence-scored verdict. Single-source checkers miss the situations that matter most: vendor pages that lag a real incident by 30 minutes, account-specific bugs that never trip global alarms, and regional CDN failures that look healthy in aggregate.

Is StatusDetector free? Do I need an account?

The homepage, all category and service pages, the tools, the radar, and every blog post are free. No signup, no paywall, no email gate. We run modest Google AdSense to cover hosting and infrastructure — ads never load on the embed routes and never load before you accept the cookie banner.

How often is the data refreshed?

Different surfaces refresh at different cadences depending on cost and stability. The homepage live strip refreshes every 1 min; service pages every 1 min; the radar and pulse rollups every 2 min. The underlying probes write to our pipeline every 5 minutes for featured services and every 30 minutes for the long tail.

A vendor says "operational" but their service is broken for me. Who is right?

Both of you, often. Vendor status pages lag real incidents by 5–60 minutes because their alarms fire on aggregate metrics — a regional CDN failure or an account-specific bug can be very real while the global metric stays green. The cross-reference is the useful signal: when our probe disagrees with the vendor page, that disagreement itself is information you can take to support.