Check the status of any service.

An answer in seconds: we read the vendor’s status feed, probe it ourselves, and count user reports — then tell you which one to believe.

Or decode an error: 503 · ERR_CONNECTION_REFUSED

Know before your users do

Pick your services and get an email when we confirm a real outage — and another when it recovers.

Alerts fire only when the combined evidence crosses our confirmed threshold, and 401/403/429 anti-bot responses are flagged as probe-blocked, not down. One click to unsubscribe.

How we know

We track 305 services. 37 of them publish an official status feed, and we read it directly — no scraping. 305 are probed from our own infrastructure, independently of what the vendor says.

When a service blocks our probe with a 401, 403, or 429, we say “probe blocked” — we don’t count it as down. A single user report means little; twenty in half an hour means something. That’s when we escalate.

Every verdict shows its evidence: which signals we read, what each one said, and how they were weighted. Full methodology →

Straight answers

What is StatusDetector?

An independent second opinion on service health. We read official status feeds, probe services ourselves, and count user reports — then show you a verdict with the evidence behind it.

Is it free?

Checking any status and per-service email alerts are free. A Pro plan for teams that need faster probes and richer alerting is described on the pricing page.

The vendor says "operational" but it's broken for me. Who is right?

Often both. Vendor status pages can lag real incidents by 5–60 minutes because their alarms fire on aggregate metrics. When our independent probe disagrees with the vendor's green dot, that disagreement is the signal — take it to support.

How fresh is this data?

This page refreshes every 1 min. Featured services are probed every 5–15 minutes; the rest of the list rotates through the pipeline continuously.

Also on StatusDetector: Shutdown Radar · Outage Map · Internet Pulse · Internet Graveyard · Sunset Watch · Blog