User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Health
cronometer.com · Health
Is Cronometer down?
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → cronometer.com—
Your browser → us—
Our checksReaching it
Official · ReportsNo status feed · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
What's broken
Our checks
Reaching it
Last check reached it in 146 ms · 7 min ago.
Official status
No status feed
Cronometer does not publish a status feed we can read.
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 12:30 | 0 | 0.0 | 300 ms | 0 |
| 12:45 | 0 | 0.0 | 290 ms | 0 |
| 13:00 | 0 | 0.0 | 308 ms | 0 |
| 13:15 | 0 | 0.0 | 116 ms | 0 |
| 13:30 | 0 | 0.0 | 194 ms | 0 |
| 13:45 | 0 | 0.0 | 484 ms | 0 |
| 14:00 | 0 | 0.0 | 956 ms | 0 |
| 14:15 | 0 | 0.0 | 129 ms | 0 |
| 14:30 | 0 | 0.0 | 347 ms | 0 |
| 14:45 | 0 | 0.0 | 356 ms | 0 |
| 15:00 | 0 | 0.0 | 609 ms | 0 |
| 15:15 | 0 | 0.0 | 216 ms | 0 |
| 15:30 | 0 | 0.0 | 999 ms | 0 |
| 15:45 | 0 | 0.0 | 356 ms | 0 |
| 16:00 | 0 | 0.0 | 598 ms | 0 |
| 16:15 | 0 | 0.0 | 398 ms | 0 |
| 16:30 | 0 | 0.0 | 196 ms | 0 |
| 16:45 | 0 | 0.0 | 1467 ms | 0 |
| 17:00 | 0 | 0.0 | 253 ms | 0 |
| 17:15 | 0 | 0.0 | 406 ms | 0 |
| 17:30 | 0 | 0.0 | 954 ms | 0 |
| 17:45 | 0 | 0.0 | 234 ms | 0 |
| 18:00 | 0 | 0.0 | 239 ms | 1 |
| 18:15 | 0 | 0.0 | 424 ms | 0 |
| 18:30 | 0 | 0.0 | 350 ms | 0 |
| 18:45 | 0 | 0.0 | 175 ms | 0 |
| 19:00 | 0 | 0.0 | 305 ms | 0 |
| 19:15 | 0 | 0.0 | 645 ms | 0 |
| 19:30 | 0 | 0.0 | 836 ms | 0 |
| 19:45 | 0 | 0.0 | 197 ms | 0 |
| 20:00 | 0 | 0.0 | 291 ms | 0 |
| 20:15 | 0 | 0.0 | 304 ms | 0 |
| 20:30 | 0 | 0.0 | 211 ms | 0 |
Reliability
98.28%Uptime · 30 days
98.28%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Cronometer badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Cronometer yet. Outages of 10 minutes or more get their own page here.
Having trouble with Cronometer?
One report per service every 10 minutes from this network. No account.
Follow Cronometer
Get an email when Cronometer goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Cronometer alerts to Slack, Discord or a webhook — free.
About Cronometer
Cronometer is listed in our Health category and checked at cronometer.com. Live checks and user reports.
Cronometer has no official status feed we can read, so this page relies on our own checks and user reports.
What usually goes wrong with health services: patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors.
Measured uptime from our checks: 98.28% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 412 ms average, 79–2286 ms range across 60 successful checks.
Questions
Is Cronometer down right now?
Checks are succeeding and user reports are near the baseline.
When was Cronometer last down?
We have not recorded a public Cronometer incident since monitoring began 1 day ago.
What is Cronometer's uptime?
From our own checks: 98.28% over 1 day of checks.
How fast does Cronometer respond?
412 ms on average over the last 24 hours (79–2286 ms).
Does Cronometer have an official status page?
Not one we can read. This page uses independent checks of cronometer.com and user reports.
Cronometer not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For health services, watch for patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors. If many people report Cronometer here at once, the problem is on Cronometer's side.