Coverage, honestly
804 of 1,127 mapped vendors (71%) publish a status feed we can read. On the last poll 761 of 804 answered; the rest are shown as unknown. 121 seed entries were dead links — that is the rot the daily map exists to catch.
| Platform | Vendors | Polled | How / why not |
|---|---|---|---|
| Atlassian Statuspage | 692 | yes | GET /api/v2/summary.json + /api/v2/incidents.json (history back-filled) |
| bespoke HTML page | 179 | no | bespoke page (Apple, Microsoft 365, Okta, Auth0…) — needs a hand-written parser each; the ones buyers ask for most are done (row above) |
| unreachable | 121 | no | unreachable at probe time (DNS gone, TLS broken, or 4xx/5xx) |
| Status.io | 37 | yes | page id resolved once, then api.status.io/1.0/status/<id> — open incidents only |
| Instatus | 34 | yes | GET /summary.json — open incidents only |
| Better Stack | 28 | yes | GET /index.json — open incidents only |
| UptimeRobot | 11 | no | public status pages are HTML only |
| vendor's own feed (hand-written parser) | 9 | yes | the vendor's own public feed, one hand-written parser each: Slack JSON API, Stripe /current, Google incidents.json (Cloud, Firebase, Workspace, Play), AWS Health currentevents, Azure status RSS, Heroku api/v4 |
| Hund | 7 | no | API answers 401 without a key; no public feed |
| incident.io | 5 | yes | custom host is a JS app; the canonical host's /feed.rss carries a Status: line per incident (Notion, Hasura…) |
| Cachet | 3 | no | /api/v1/* returns 404 on every instance seen |
| Sorry™ | 1 | yes | GET /api/v1/status + /api/v1/notices (Postmark) |
Seed list: metoro-io/statusphere (MIT), de-duplicated from 1,425 rows to 1,127 unique status URLs, then every URL probed live and re-probed daily. Missing a vendor? Open an issue.
