Status badges and feeds

Badge. An SVG image, 20 pixels high, with the service name and one of six states: operational, minor incident, major incident, critical outage, maintenance or no data. It can be cached for up to 60 seconds.

RSS. One item per declared incident, updated when the provider posts an update. Each item links to the provider's own incident report. There is one feed per service and one for all services together.

JSON snapshot. /api/status.json lists every service with level, the provider's own description, the time of the last successful reading (checkedAt), the count of consecutive failed reads (failures), open incidents and a 90-character string with one code per day (0 no incident, 1 minor, 2 major, 3 critical, - no record).

JSON detail. /api/service/<id>.json adds the components, the incident record with the text of each official update, and the date from which that record is held (coverageSince).

If you display these states, keep the meaning of nodata: it is the absence of a valid answer. Treating it as operational would defeat the purpose. The method is described on the how it works page.