ToolsStatus page uptime report
What does your status page's history add up to?
Enter a public status page to see the uptime its own incidents add up to over the last 30 and 90 days, overall or for one component.
Report
We read the page’s public incident feed once. We do not store or log the address you enter; we keep only daily totals of how many reports ran.
Enter a status page to see the uptime its own incident history adds up to over the last 30 and 90 days.
Method
How the report is built.
Source
The page's public incident feed
One request for /api/v2/incidents.json, which every page hosted on Atlassian Statuspage publishes without a login. It lists the 50 most recent incidents; when they do not reach back to the start of a window, the report says which span it covers.
Outage
Major and critical incidents
Counted from the time the incident started (or was posted) to the time it was resolved; an incident still open counts until now. Overlapping incidents are merged, so no minute counts twice.
Degraded
Minor incidents
Shown separately and left out of the uptime figure, minus any time already counted as outage. Incidents with no impact and scheduled maintenance count as neither.
Uptime
Minutes without an outage
One minus outage time over the covered span, truncated (never rounded up) to two decimals. With a component chosen, only incidents that list that component count.
Limits
What the page said, not what happened
Incidents are posted by people, often after customers noticed, and closed when the team is confident. The figure is only as good as the page's discipline. It is an estimate, not a measurement.
Privacy
The address is not kept
The address you enter is used for one request and then discarded. It is not logged or stored. A report is reused for 5 minutes, held in memory under a one-way hash of the address. Observer keeps only daily totals of how many reports ran.