Home / Answers / How up to date is the status shown here?
How up to date is the status shown here?
Each vendor feed is read about every 20 minutes, measured from our own stored readings. On our last update the freshest reading was 1 min ago and the oldest 16 min ago.
How the schedule works
A scheduled task runs every 5 minutes and reads a batch of feeds each time, so every feed comes round in turn. Each service page shows when its feed was last read.
We keep the last 24 readings for each service. The longest gap between two stored readings was about 18 hours, when our scheduled task did not run. A page that is not refreshing says so with its "last read" time rather than showing an old result as current.
What this means in an outage
Vendors usually post an incident some time after problems start, and our reading follows the feed. In the first minutes of an outage, your own test is often faster than any status page. Use the checker on this page, or follow is it down or just me?.
How a label is chosen: how we decide status.
FAQ
- Does opening a page check the vendor again?
- No. Pages use the last saved reading. That keeps the site fast and avoids hammering vendor feeds.
- Why might the official status page show something newer?
- Because we read each feed in turn. If the vendor has just posted, their own page can be ahead of ours until our next reading. The service page links to it.
More answers
- Is anything down right now?
- Is there planned maintenance this week?
- Can I see a service's past outages?
- If AWS, Azure or Google Cloud goes down, which tools are affected?
Figures on this page are worked out from our latest saved reading of each vendor's public feed (24 Oct, 17:35 UTC).