This page shows what our own probe observed: whether each service answered, how fast, and the share of checks that passed over the last 24 hours, 7, 30 and 90 days. Nothing here is estimated or typed by hand; incidents are added by a person only when confirmed.
How it is measured
- A small script on our web server requests each endpoint every 10 minutes and records the HTTP status and the time to first byte.
- A check passes when the endpoint answers with the status we expect for it; for example the intake endpoint is expected to refuse a plain GET, and the verification endpoint is expected to answer 404 without a key.
- Availability is the share of passed checks in each window. Bars show one UTC day each: green above 99.9%, yellow above 95%, red below.
- One probe location means a network problem between our server and the service shows as a failure even when the service is fine for you. We say so rather than hide it.
What this page does not do
- It does not predict or promise future availability, response time, delivery time or recovery time.
- It does not monitor the stores themselves; each store publishes its own status.
- It does not count delivery of releases to stores; that is tracked per release inside the app.