status
Watch the addresses that matter to you, and hand one link to the people who need to know when they stop answering. Each page belongs to one account; the monitors, the measurements and the history are that account's.
| Monitors | HTTP or HTTPS by method, or a TCP port. An expected status code, or any 2xx. An optional phrase the answer must contain. |
| History | 12 hours of measured latency, 90 days of incidents, and a 90-day availability bar per monitor. |
| The address | One link, with a JSON form of the same numbers at <address>/data. |
Checks run from Cloudflare's network, so this page reports what Cloudflare can see. An outage that only one region or one network sees is not detected here.
A page served from the same place as the thing it watches shares that thing's
fate. That is why the hosting model reserves the name status.zpe.vc for this app:
so the page can answer when the apex is broken.