// tool/outage-detector
ISP Outage Detector
Compare reachability signals to identify regional provider, backbone, or SaaS trouble.
What this is
Most reported outages are partial — one region, one carrier, one peering point. This tool checks reachability across multiple signals so you can tell 'the internet is down' (it isn't) from 'this provider's east-coast peering is down' (often the real story).
What it covers
- ›Multi-signal checks
- ›Provider context
- ›Reachability notes
- ›Escalation-friendly summary
Operator notes
- $Correlate user reports with route and status signals.
- $Avoid assuming global outage from one path.
- $Capture timing and impact while the issue is active.
status: Aggregated outage checks will run through Cloud functions.
Quick start
Search location
Override ISP
Units
Last
—
Status & summary
Pending checks
Click “Run checks” to probe major networks from your browser and our edge.
Targets
6
Reach
0/6
Slow
0
Fail
0
Browser vs Edge
Browser0/— · —
Edge0/— · —
Detected ISP
IP—
ISP—
ASN—
Loc—
Weather
Set a location to see conditions.
Region map
Click the map to drop a pin where you've confirmed issues.
Network target checks
Each target is probed from your browser and from our edge server. Browser failures with edge success suggest a local/ISP problem.
TargetBrowserEdge
Cloudflare www.cloudflare.com——
Google www.google.com——
Akamai www.akamai.com——
Apple www.apple.com——
Amazon www.amazon.com——
Microsoft www.microsoft.com——
Frequently asked
- How can I tell if it's my ISP or the destination?
- Test the destination from a second network (mobile hotspot, cloud shell). If it works there but not on your ISP, it's a path or peering issue between them.
- What's a backbone vs an edge outage?
- Edge = your last-mile to the ISP. Backbone = the carrier's internal long-haul. Edge problems affect one neighborhood; backbone problems affect entire regions.