Where the numbers come from
Every chart and map on this site reads public files or public feeds. We do not have a hidden database.
| File | What it provides | Count | As of |
|---|---|---|---|
| Loading… | |||
Live status feeds
We keep a catalog of public status pages and feeds, checked from this project.
The live map reads a shorter working set through /api/status. That proxy caches results for about 60 seconds. The map itself checks again every 3 minutes.
Country outage signals come from IODA at Georgia Tech, through /api/ioda. That proxy asks for the last 24 hours and caches the result for about 2 minutes. Those signals are labeled REPORTED. A signal is not a confirmed outage.
Cloudflare Radar has a public outage center. Its live outage API needs a private token, so this site links out instead of calling it.
| Firm | Feed | HTTP at check | Checked | Note |
|---|---|---|---|---|
| Loading… | ||||
Link check
Source URLs in the datasets were fetched from this project and recorded in link_audit.csv.
Report lists
The Report page compares early-access firms with a comparison group.
How the data moves through the site
- Public status pages and AWS Health A Cloudflare worker reads them at /api/status, caches the result for about 60 seconds, and the live map and infrastructure page use it. Data center status uses /api/infra. Hub operator feeds use /api/hubs. Both of those cache for about 2 minutes.
- IODA country signals The same worker reads IODA at /api/ioda, caches the result for about 2 minutes, and the live map draws country rings.
- The live wire Public posts on X are searched, then each hit is checked against official statements or credible press. Accepted items are written to wire.json with a CONFIRMED, REPORTED, or CLAIM label.
- Most reported A catalog in services.json is scored from official feeds at /api/reported and from public X post counts in crowd.json. The ranked list is on Reported. Crowd counts are CLAIM. They are never a confirmation by themselves.
- Sourced history files Outages, hacks, breaches, and cascade links live in JSON files on the site. The Report, History, and Connections pages all read those files.
- Publish The site is static files plus API routes, served on Cloudflare. Custom domains point at that same site. This page does not name internal project IDs.
The live wire scanner
The wire file records how each scan was done. Counts and run times are filled from wire.json when this page loads.
New items are meant to go through a small checker script so duplicates and empty sources cannot sneak in. If a run is still in progress, this page shows the latest file we can read.
API health
We fetch every local API route on both live domains, every URL in status_feeds.csv, and the data JSON files the site reads. Results are recorded in api_health.csv.
The table fills from the latest check file.
| Name | Kind | HTTP | Latency | Freshness | Schema | Note |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Pages and the files they read
- Live map reads map-data.json, cable files, hubs.json, infra.json, /api/status, /api/ioda, /api/infra, and /api/hubs.
- Reported reads services.json, crowd.json, history.json, wire.json, /api/reported, and /api/ioda.
- History (list, map, and globe) reads history.json, and can draw official cloud sites from infra.json.
- Report reads data.json, which is built from the early-access and comparison lists. The point-cloud view also reads pointcloud.json.
- Connections pages read history.json, links.json, and sometimes wire.json and infra.json.
- AI and apps reads ai_saas_outages.json.
- Cluster reads cluster.json, which is built from history, the 2026 lists, and verified wire extras.
How the map and globe place a point
Libraries and base map
- The live map uses MapLibre GL version 5.24.1. The projection is Web Mercator.
- The base map comes from OpenFreeMap and OpenMapTiles, with data from OpenStreetMap contributors.
- The history globe uses deck.gl version 9.1.14. Globe view is a 3D globe. Map view is a pitched flat map, also in Web Mercator.
- Land dots on the globe come from a Natural Earth derived file, geo/landdots.json.
Cables
Submarine cables and landing points come from TeleGeography's Submarine Cable Map, used under CC BY-SA 4.0, and were fetched on Nov 17, 2026.
Open the TeleGeography Submarine Cable Map.
Firm dots on the live map
- A firm dot sits at the company's head office city, not at a data center.
- Color is the firm's public status feed: green is up, gold is degraded, red is down, gray is unknown.
- Down means the feed reports a major or critical issue somewhere. It does not mean the whole firm is offline.
- Degraded includes planned maintenance when a feed reports it.
- Unknown means we could not read a public feed. It is not the same as up.
- Hub arcs are illustrative links between major exchange and cloud hub cities. They do not show measured traffic.
- Country rings are IODA signals for the last 24 hours, labeled REPORTED.
Events on the history map and globe
Each event in history.json has a latitude, a longitude, and a placement note that says why it sits there.
- Color shows the event type: outage, hack, breach, DDoS, or ransomware.
- Column height uses a log scale of people, records, or devices when we have that number.
- A short stub with a white cap means the size is unknown, or it was given in money or bandwidth instead.
- A ring marks a firm on the public Glasswing early-access list.
- An arc runs from the country an official source blamed to the target. Faded arcs are disputed. No arc means no official attribution.
Cloud regions and points of presence
Locations come from each provider's own public list. Airport codes are placed with OurAirports coordinates (public domain). City names are placed with GeoNames cities15000 (CC BY 4.0).
| Provider | Sites on our map | Location list |
|---|---|---|
| Loading… | ||
Limits of the maps
- Most historical events sit at a head office or an approximate home region, not at the room where something broke.
- Some events share a city, so the globe nudges overlapping columns a little so you can see them.
- Akamai does not publish a per-location list, so it has no dots.
- The cable layer is a snapshot from Nov 17, 2026. It is not a live cut cable feed.
- The history is broad, but it is not complete. Many incidents never got a public write-up we could check.
What the labels mean
- CONFIRMED means the firm, a government agency, or the named investigating firm said it, in a status page, postmortem, or official statement.
- REPORTED means credible press or a well-sourced encyclopedia entry only.
- CLAIM is used on the live wire when a public post alleges an incident that we have not backed with an official source or credible press. The same label applies to crowd post counts on the Reported list. A count of posts is not a confirmation.
- A field reads unknown when no checked source gave it. Unknown is not a guess.
- We keep a number only if it appeared in a source we fetched.
The Report page also has a strict and a loose rule for what counts as a major 2026 incident. Those rules are explained on the Report page.
How we grade a consumer service
The Reported list uses three public levels: No problems, Possible problems, and Problems. The rule is meant to be stricter than a raw complaint count.
- When we can read an official status feed, that feed is the first source.
- A crowd spike on X can raise a service only to Possible problems.
- A spike is never enough to mark Problems. Problems requires a major (or equivalent) official feed, or a CONFIRMED or press-backed REPORTED incident from the last 24 hours that is still open. If the official feed is now clear, a same-day confirmed item is shown on the service card and can keep the level at Possible problems, not Problems.
- If there is no official feed we can read, and there is no spike and no recent sourced incident, the level is No problems, with a note that we lack a live official feed.
Crowd counts
Each service has a public X search such as "Steam down" or "Steam outage", excluding retweets. We count posts by the hour for the last 24 hours, and by the day for the last seven days. The last two hours are compared with that service's own typical hour over the prior six days. A two-hour spike needs at least eight posts, at least three times the typical two-hour baseline, and at least ten posts above that baseline. A day-level spike, which also stays a CLAIM, needs at least 20 posts in 24 hours, at least three times the median prior day, and at least 25 posts above that median.
This is a CLAIM signal. Queries can overcount jokes, ads, and short or ambiguous names such as X, EA, Teams, Google, or A1. The count is not a unique-user report, and it is not a Downdetector figure.
Downdetector
We do not scrape Downdetector report counts. Those figures are proprietary. Each service card links out to the matching public Downdetector page so you can read their view. A 403 from an automated fetch is treated as a bot block, not as proof that a page is missing.
Country filter
The country selector shows services we catalog for that country, plus global services. The connectivity signal for a selected country comes from IODA, the Internet Outage Detection and Analysis project at Georgia Tech. An IODA signal is labeled REPORTED. It is not a confirmation, and it is not a grade for one consumer app.
What this does not claim
- Downwatch does not claim that Mythos or Glasswing caused any outage, hack, or breach.
- A green dot is only what a public status feed said at the last check. It is not a guarantee that every product works.
- An IODA country signal is not a confirmed national outage.
- Events that happen in the same week are not, by themselves, a chain. A link is drawn only when a source said one event spread to another.
- Official attribution of an attack is often disputed. Some entries name convicted individuals, not governments.
- This site is not a substitute for a firm's own status page or for emergency notices.
- A rank on Most reported is a rank of matching public posts, not a rank of proven outages.
Plain English
- You can see where each number came from, and how often the live pieces refresh.
- The map is honest about what it cannot see.
- If a source is missing, the label says so.
Action steps to review
- Skim the feed catalog for a firm you care about and open its official status page.
- Compare a history event's placement note with where you would have put it.
- Tell us if a source link has moved.