Plainwork / Catalogue / Status Endpoint Atlas
246 status pages with a JSON endpoint, tested live
Every row was fetched on 2026-10-09 and returned a valid Statuspage-style summary.json, with component counts, RSS and Atom availability and CORS for developers building status panels, bots and dependency checks.
- 246 developer and business services in 12 categories, as CSV and JSON
- The summary.json URL, status page URL, platform, component count and group count on every row
- Whether /history.rss and /history.atom actually work, whether status.json and components.json answer, and the CORS header
- status-check.mjs: prints which of the 246 services are degraded right now (--exit-code to gate a deploy)
- probe.mjs: the probe used, to re-verify any host list or the whole Atlas
- An offline searchable viewer and a README with the inclusion rule
| Service | Category | Platform | Components | RSS | Atom |
|---|---|---|---|---|---|
| GitHub | Developer tools, CI/CD and code | Atlassian Statuspage | 12 | yes | yes |
| OpenAI | AI and ML platforms | incident.io (Statuspage-compatible) | 25 | yes | yes |
| Twilio (incl. SendGrid) | Messaging and email | Atlassian Statuspage | 192 | yes | yes |
| Cloudflare | Cloud, hosting and DNS | Statuspage-compatible (host not identified) | 480 | yes | yes |
| Vercel | Cloud, hosting and DNS | Atlassian Statuspage | 67 | yes | yes |
| Sentry | Observability and error tracking | Atlassian Statuspage | 47 | yes | yes |
| Supabase | Databases and data infrastructure | incident.io (Statuspage-compatible) | 1 | yes | yes |
The full file adds the status page, the exact summary.json URL, groups, CORS header, status.json and components.json availability, the indicator at fetch time and the fetch date for all 246 rows.
Made for
Who it's for
Fetched, not collected
A host is a row only if its summary.json returned HTTP 200 with a valid body on 2026-10-09. A second check of 41 rows with curl found no differences.
The decisions are columns
11 of 246 services have no working RSS or Atom feed, and 42 run on incident.io's compatible route. The file says which, and the README notes that incident.io rows omit empty incidents keys, so you do not find out in production.
Re-check it yourself
probe.mjs and status-check.mjs are included, so you can re-verify any row or add your own vendors with the same rule.
What's inside
Everything you get
How it works
From checkout to done
Buy
Pay securely with Stripe.
Open
Your download page opens straight away.
Use
Download everything and start using it. Bookmark the page to come back.
Questions
Good to know
Will these endpoints keep working?
They all worked on 2026-10-09. Vendors change status providers, so re-run probe.mjs on the ones you depend on. The README says what was and was not tested.
Does it rank services by reliability?
No. It is a map of where to read each service's status from. indicator_at_fetch is a one-time snapshot, and the README says so.
Which services are included?
246 developer and business services in 12 categories, from cloud and databases to payments and AI platforms. Consumer-only services were removed and each status page appears once.
Can I call these from a browser?
The summary.json responses all carried Access-Control-Allow-Origin: * on a plain GET (246 of 246). Preflighted requests were not tested.
What if it doesn't work for me?
If it doesn't work as described or you can't access it, email us within 14 days and we'll fix it or refund you. See the refund policy for details.
Status Endpoint Atlas
246 vendor status pages with a working summary.json, feeds and CORS noted, each fetched live and dated.
More from the catalogue
Other small tools
One Oven Dinner
Offline holiday dinner planner: backwards schedule, shared oven, thaw start day, printable.
Change Order Desk
Priced change orders with a no-login client approval link and a timestamped record. Free for 3.
Birder's First Binoculars
Decode binocular specs and choose a sensible first pair for birdwatching, free.