| Site | Status | Uptime (24h) | Avg response | Last checked | Recent |
|---|---|---|---|---|---|
| Google https://www.google.com |
Up (200) | 100% | 55 ms | 2026-10-18 01:21:05 | |
| GitHub https://github.com |
Up (200) | 100% | 55 ms | 2026-10-18 01:21:05 | |
| Cloudflare https://www.cloudflare.com |
Up (200) | 99.4% | 84 ms | 2026-10-18 01:21:05 | |
| Wikipedia https://www.wikipedia.org |
Up (200) | 100% | 29 ms | 2026-10-18 01:21:05 | |
| Microsoft https://www.microsoft.com |
Up (200) | 100% | 159 ms | 2026-10-18 01:21:05 | |
| Amazon Web Services https://aws.amazon.com |
Up (200) | 100% | 76 ms | 2026-10-18 01:21:05 | |
| Apple https://www.apple.com |
Up (200) | 99.9% | 54 ms | 2026-10-18 01:21:05 |
Checks run in the background roughly every minute. History shows the last 20 checks (oldest to newest).
This dashboard shows the current status and recent history of the sites being monitored. Each one is checked on a regular interval, and the result recorded so you can see not just whether it is up now but how it has behaved.
Each check makes an HTTP request and records whether it succeeded and how long it took. A site counts as up when it answers with a success status within the timeout, and down when it returns an error status, refuses the connection or fails to answer in time.
Response time is measured from the monitoring server, so it reflects the path between that server and the site. It is a useful relative measure — a sudden jump means something changed — rather than a statement about what any particular visitor experiences.
Availability figures compress badly. Over a 30-day month, 99.9% allows around 43 minutes of downtime, 99.5% allows about three and a half hours, and 99% allows just over seven hours. The gap between numbers that look almost identical is substantial.
The other thing a percentage hides is distribution. Forty minutes of downtime spread across brief blips is a different experience from forty minutes in one outage during business hours, and both produce the same monthly figure.
Work from the outside in. Most outages turn out to be one of a handful of causes, and checking them in this order finds them fastest:
A monitor running on the same server as the site goes down with it, so it can never report the outage that matters most. Useful monitoring checks from a different machine, ideally a different network, and alerts through a channel that does not depend on the thing being monitored.
Each monitor runs on a fixed interval and records the result. The history shown on this page is built from those checks, so the resolution of the timeline matches the check interval.
A check fails when the site returns an error status, refuses the connection, or does not respond within the timeout. Consecutive failed checks are what constitute an outage.
Over a 30-day month it permits roughly 43 minutes of downtime. For comparison, 99.5% allows about three and a half hours and 99% just over seven hours, so small-looking differences in the percentage matter a great deal.