Outage Sphere
Last checked

Data

Everything this site shows is also plain JSON: the live status of 90 vendors, a twin of every vendor page and of each of 150 outage pages, and a feed of what changed last.

The live file was last written at .

A twin for every pageThe same answer, as JSON, at a guessable address

/data/status/<vendor>.json (for example /data/status/cloudflare.json) and /data/outages/<slug>.json, where the slug is the last part of the outage page's address. Fields: url, title, answer (the page's first line), asOf, status, factsChangedAt, sources[] (title, url, publisher, at).

/data/feed.json and /feed.xmlThe 50 most recently changed pages

JSON Feed 1.1 and Atom. Each item has the page's title, address, first line with its time, when it was first seen and when its facts last changed.

/data/status.jsonThe live file, every minute

generatedAt; summary (monitored, operational, degraded, outage, word); vendors[] (slug, name, category, state, officialUrl, lastChecked); incidents[] (id, vendor, title, impact, state, startedAt, updatedAt, regions, components, updates, officialUrl), covering what is open now and what ended in the last two days.

/data/vendors.jsonOne row a vendor

slug, name, category, state, statusText (the vendor's own wording), officialUrl, lastChecked, and the address of the vendor's page here.

/data/outages.jsonOutages with a page here, newest first

id, vendor, title, impact, state, startedAt, resolvedAt, updatedAt, regions, officialUrl, and the address of the outage page here.

Using it

Times are ISO 8601 in UTC. A state of unknown means the vendor's page could not be read; treat it as no information, not as up. Please ask no more than once a minute, and name the source as Outage Sphere with a link to the page you used.