Patternode status
The status of every service Patternode offers customers, served by status.patternode.com.
It is static files, published apart from the services it reports on, so it answers when
they do not. No key: anyone may read it, and nothing in it is about your account. For
your account's view (your jurisdiction, your plan, this month's availability against its
target) call GET /v1/status on the API, and for a push when an incident opens, subscribe
to the status.* events on your webhook endpoint.
The shapes follow the Atlassian Statuspage /api/v2/ format, the one most status tools
read, so a monitor, chat app or agent that reads that format reads this one. The one
addition is the component status not_in_service, for a service listed before it is
offered; a client that does not know it should treat it as unknown, never as operational.
How it is measured: probes from outside Patternode call each service every 5 minutes (a
run may be late by several minutes), and a component is marked down after two failures in
a row. An open incident overrides the probes. Each file is cached for up to 5 minutes;
page.updated_at says when the probes last ran, and a page more than 30 minutes old says
so instead of showing green.
Also served, not described here: the page itself (/), each incident (/incidents/\{id\}/),
an Atom feed (/feed.atom) and RSS (/feed.rss) of incidents and maintenance, a badge per
component (/badge/{component}.svg) and /llms.txt.
Contact Patternode partner support: partners@patternode.com
License Apache 2.0