About
About StatusDetector
StatusDetector is a universal status search engine. We aggregate three independent signals — official status feeds, our own HTTP/SSL probes, and anonymous community reports — into a single confidence-scored view of service health.
The terms we use
Used consistently across the homepage, press kit, pulse, and category pages so the same number always means the same thing.
Catalogue services
Every service we know about. 424 services across 13 categories today.
Live feeds wired
Services with an official Statuspage / vendor JSON / RSS feed integrated. 37 services qualify.
Probe monitored
Services we check via HTTP/SSL probes from our infrastructure. 424 services qualify.
Fresh data
Data we've ingested in the last 24 h. Stale data is shown separately rather than treated as healthy.
Tools
Standalone utilities — 13 of them, all free, no signup.
How confidence scoring works
Every service page shows an issue score from 0 to 100. Higher = more evidence of a problem.
The score is the sum of weighted impact from four independent inputs. Inputs that fail (e.g. our probe is blocked) contribute zero rather than a fake signal.
Official status feed
When a service publishes a machine-readable status page (Statuspage.io or compatible JSON), we read it directly. A "major outage" indicator adds +75; "partial outage" adds +60; "degraded performance" adds +45; "all systems operational" subtracts −10. Maintenance adds +25 and surfaces a dedicated badge.
Live HTTP/SSL probe
We probe each service's primary URL from our infrastructure. Two or more failed probes in the recent batch adds +45; one failure adds +25. Slow responses (>3s) add +10. Probe-blocked responses (HTTP 401/403/429) are flagged as "Probe inconclusive" — they do not add to the score.
Community reports
Anonymous reports within a 30-minute rolling window. 5+ reports add +15; 10+ add +25; 20+ add +35. Reports are weighted low individually and escalate only with volume.
Open incidents
If our cron-driven probe pipeline has recorded an unresolved incident for this service, +30 is added.
Final label bands
- Operationalscore 0–19, ≥ 1 fresh signal
- Degradedscore 20–39 ("Possible issue")
- Major Issuescore 40–69
- Confirmed Outagescore 70–100
- Maintenancescore-independent — surfaced when the vendor’s feed reports it
- Probe inconclusiveour probe was blocked (401/403/429) and no other signal confirms an issue
- No datafewer than the minimum signals required for a verdict
Data confidence is a separate 0–100 % rating that reflects how much agreement there is among inputs. A 70/100 score with 90 % data confidence means “multiple independent inputs all agree something is wrong.”
Refresh cadence
Each surface revalidates on its own schedule. Cadence in copy always matches the underlying ISR window.
- Homepage live strip — every 1 min
- Service detail page — every 1 min
- Category pages — every 2 min
- Internet Pulse — every 2 min
- Shutdown Radar — every 1 min
- Crypto Pulse — every 1 min
- Logistics Hub — every 1 min
Cron-driven probes write to our pipeline on their own schedule (typically every 5–15 min for featured services, longer for the long tail). The cadence above is when a given page re-reads from that pipeline.
Data sources
- Official Statuspage.io APIs published by each service (where available)
- Our own HTTP / SSL probes from our infrastructure (Cloudflare DNS-over-HTTPS for resolution)
- Anonymous community reports submitted through service status pages
- Public infrastructure feeds — AWS RSS, Cloudflare Statuspage, USGS, NWS, FMCSA, CBP, FAA, OpenSky, CoinGecko, mempool.space, Beaconcha.in
- Curated status-meaning definitions for shipping, payments, government, HTTP, and network errors
What we don't do
Inversions of the standard 'what we do' so the scope of the operation is unambiguous.
- No per-user tracking. We don’t have user accounts, we don’t profile visitors, and Vercel Analytics — the only analytics layer running on the site — is cookieless.
- No SLA. The verdicts and uptime numbers are estimates, not promises. Treat them as a second opinion, not the system of record.
- No vendor affiliation. We are not partnered with, endorsed by, or sponsored by any of the services we track. Brand names are descriptive use only.
- No support-ticket integration. A user report submitted here does not open a ticket with the vendor. We collect the report to improve our confidence score, not to forward to support teams.
- No paid placement. Services don’t pay to appear in the catalogue, to rank higher, or to have their feed wired up. The catalogue is curated, not sponsored.
Privacy
We do not collect Social Security numbers, passport numbers, government case numbers, bank credentials, immigration IDs, or any other private identifiers. IP addresses used for rate-limiting are hashed server-side with SHA-256 and never stored in plain text. Full privacy policy →
The operator
Who runs this, and how to reach us.
StatusDetector is an independent operation. It is not part of any larger company and is not affiliated with any of the services it tracks. There is no outside investor, no advertising network shaping the editorial line, and no vendor relationship to disclose.
The fastest way to reach us is support@statusdetector.com. Bug reports, takedown requests, press inquiries, and partnership questions all land in the same inbox. We aim to reply within 24–48 hours on business days.
Frequently asked
The handful of questions readers most often have after they reach this page.
How often do you refresh the data?
Refresh windows vary by surface — the homepage live strip every 1 min, service pages every 1 min, the Pulse and Radar rollups every 2 min. Cron-driven probes write to the underlying pipeline on their own schedule (typically every 5 minutes for featured services, every 30 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 threshold-based alerting fires on aggregate metrics. A regional outage or a per-user bug can be very real while the global aggregate stays green. That gap is exactly what we surface — when our probe and community reports both flag a service that the vendor still calls operational, the cross-reference is the useful signal.
Do you have a public API?
Not as a documented product. The site's internal JSON endpoints can be called: /api/status/[slug] and /api/search are GET; /api/check-url and /api/decode-status are POST (sending GET to either returns a short usage document describing the request body). We don't commit to keeping their shapes stable across deploys. RSS feeds at /incidents/feed.xml, /status/[slug]/feed.xml, and /category/[slug]/feed.xml are stable and recommended for programmatic use.
How do I add a service to the catalogue?
Email support@statusdetector.com with the service name, primary URL, and any official status feed URL (Statuspage.io, RSS, or vendor JSON). We add services when (a) they have measurable consumer or developer impact, (b) we can verify them via at least one independent signal, and (c) they fit our scope of tech-infrastructure status. Consumer logistics, immigration, and travel statuses are explicitly out of scope.
Is the site monetised?
Yes — modestly. We run Google AdSense to cover hosting costs. Ads do not load on the embeddable badge routes, never load before a visitor accepts the cookie banner, and are not allowed to influence editorial content or scoring weights. See /privacy for the full disclosure.
Disclaimer
StatusDetector is an independent monitoring aggregator. We are not affiliated with, endorsed by, or sponsored by any of the services, brands, government agencies, carriers, airlines, banks, or companies referenced on this site. Status information may be delayed or inaccurate. Do not rely on StatusDetector for life-safety or mission-critical decisions. Always consult the official service provider for authoritative status information.