User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
cronitor.io · Cloud & developer
Is Cronitor 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 → cronitor.io—
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 630 ms · 3 min ago.
Official status
No status feed
Cronitor does not publish a status feed we can read.
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 13:45 | 0 | 0.0 | 633 ms | 0 |
| 14:00 | 0 | 0.0 | 427 ms | 0 |
| 14:15 | 0 | 0.0 | 216 ms | 0 |
| 14:30 | 0 | 0.0 | 625 ms | 0 |
| 14:45 | 0 | 0.0 | 630 ms | 0 |
| 15:00 | 0 | 0.0 | 385 ms | 0 |
| 15:15 | 0 | 0.0 | 529 ms | 0 |
| 15:30 | 0 | 0.0 | 385 ms | 0 |
| 15:45 | 0 | 0.0 | 544 ms | 0 |
| 16:00 | 0 | 0.0 | 761 ms | 0 |
| 16:15 | 0 | 0.0 | 726 ms | 0 |
| 16:30 | 0 | 0.0 | 632 ms | 0 |
| 16:45 | 0 | 0.0 | 630 ms | 0 |
| 17:00 | 0 | 0.0 | 461 ms | 0 |
| 17:15 | 0 | 0.0 | 408 ms | 0 |
| 17:30 | 0 | 0.0 | 668 ms | 0 |
| 17:45 | 0 | 0.0 | 453 ms | 0 |
| 18:00 | 0 | 0.0 | 706 ms | 0 |
| 18:15 | 0 | 0.0 | 659 ms | 0 |
| 18:30 | 0 | 0.0 | 331 ms | 0 |
| 18:45 | 0 | 0.0 | 776 ms | 0 |
| 19:00 | 0 | 0.0 | 400 ms | 0 |
| 19:15 | 0 | 0.0 | 298 ms | 0 |
| 19:30 | 0 | 0.0 | 611 ms | 0 |
| 19:45 | 0 | 0.0 | 541 ms | 0 |
| 20:00 | 0 | 0.0 | 630 ms | 0 |
Reliability
100%Uptime · 30 days
100%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 a live Cronitor status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for Cronitor yet. Outages of 10 minutes or more get their own page here.
Having trouble with Cronitor?
One report per service every 10 minutes from this network. No account.
Follow Cronitor
Get an email when Cronitor goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Cronitor alerts to Slack, Discord or a webhook — free.
About Cronitor
We track Cronitor (cronitor.io) as part of the Cloud & developer group. Live checks and user reports.
Cronitor has no official status feed we can read, so this page relies on our own checks and user reports.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 552 ms average, 166–907 ms range across 44 successful checks.
Questions
Is Cronitor down right now?
Checks are succeeding and user reports are near the baseline.
When was Cronitor last down?
We have not recorded a public Cronitor incident since monitoring began 1 day ago.
What is Cronitor's uptime?
From our own checks: 100% over 1 day of checks.
How fast does Cronitor respond?
552 ms on average over the last 24 hours (166–907 ms).
Does Cronitor have an official status page?
Not one we can read. This page uses independent checks of cronitor.io and user reports.
Cronitor 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 cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Cronitor here at once, the problem is on Cronitor's side.