Checked every 60 seconds
Our monitoring node requests each endpoint in turn and records the response code and round-trip time. The page then refreshes itself on the same 60-second cycle.
Checking services…
Every service we run, checked live from our own monitoring node. If we cannot confirm that something is up, this page says so. It never fills the gap with a green tick.
Service by service
How this page works
Nothing on this page is typed in by us. Each service is probed over the public internet and the result is published exactly as it came back.
Our monitoring node requests each endpoint in turn and records the response code and round-trip time. The page then refreshes itself on the same 60-second cycle.
Response time is the full round trip from our monitoring node, so it includes network latency as well as the service itself. A slower figure is not the same as an outage.
A failed check means we could not reach the service from outside. If this page cannot reach the monitoring node at all, it tells you that plainly instead of reporting everything as fine.
Checks run from our monitoring node every 60 seconds. What you see above is the most recent check only. It is a live snapshot, not a monthly uptime report.
Our written uptime commitment is 99.9%, backed by service credits. The measurement window, the exclusions and how to claim are all set out in the service level agreement.
If a service is misbehaving and this page still says it is fine, tell us. A real person reads every ticket, and we would rather hear it twice than not at all.
Support cover: 09:00–22:00 UK, every day