User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is Cronofy down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → cronofy.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · 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. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 42 min ago. Last stored result reached it in 217 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 225 ms | 0 |
| Tue 02 | 0 | 0.0 | 190 ms | 0 |
| Tue 04 | 0 | 0.0 | 178 ms | 0 |
| Tue 06 | 0 | 0.0 | 213 ms | 0 |
| Tue 08 | 0 | 0.0 | 135 ms | 0 |
| Tue 11 | 0 | 0.0 | 183 ms | 0 |
| Tue 13 | 0 | 0.0 | 102 ms | 0 |
| Tue 15 | 0 | 0.0 | 194 ms | 0 |
| Tue 17 | 0 | 0.0 | 87 ms | 0 |
| Tue 20 | 0 | 0.0 | 331 ms | 0 |
| Tue 22 | 0 | 0.0 | 158 ms | 0 |
| Wed 00 | 0 | 0.0 | 142 ms | 0 |
| Wed 02 | 0 | 0.0 | 157 ms | 0 |
| Wed 05 | 0 | 0.0 | 111 ms | 0 |
| Wed 07 | 0 | 0.0 | 187 ms | 0 |
| Wed 09 | 0 | 0.0 | 187 ms | 0 |
| Wed 11 | 0 | 0.0 | 202 ms | 0 |
| Wed 13 | 0 | 0.0 | 193 ms | 0 |
| Wed 15 | 0 | 0.0 | 184 ms | 0 |
| Wed 17 | 0 | 0.0 | 243 ms | 0 |
| Wed 20 | 0 | 0.0 | 325 ms | 0 |
| Wed 22 | 0 | 0.0 | 200 ms | 0 |
| Thu 00 | 0 | 0.0 | 302 ms | 0 |
| Thu 02 | 0 | 0.0 | 190 ms | 0 |
| Thu 04 | 0 | 0.0 | 158 ms | 0 |
| Thu 06 | 0 | 0.0 | 115 ms | 0 |
| Thu 08 | 0 | 0.0 | 335 ms | 0 |
| Thu 10 | 0 | 0.0 | 122 ms | 0 |
| Thu 12 | 0 | 0.0 | 191 ms | 0 |
| Thu 15 | 0 | 0.0 | 334 ms | 0 |
| Thu 17 | 0 | 0.0 | 191 ms | 0 |
| Thu 19 | 0 | 0.0 | 118 ms | 0 |
| Thu 21 | 0 | 0.0 | 294 ms | 0 |
| Thu 23 | 0 | 0.0 | 177 ms | 0 |
| Fri 01 | 0 | 0.0 | 188 ms | 0 |
| Fri 03 | 0 | 0.0 | 207 ms | 0 |
| Fri 05 | 0 | 0.0 | 201 ms | 0 |
| Fri 07 | 0 | 0.0 | 233 ms | 0 |
| Fri 09 | 0 | 0.0 | 213 ms | 0 |
| Fri 11 | 0 | 0.0 | 108 ms | 0 |
| Fri 12 | 0 | 0.0 | 112 ms | 0 |
| Fri 14 | 0 | 0.0 | 127 ms | 0 |
| Fri 16 | 0 | 0.0 | 99 ms | 0 |
| Fri 17 | 0 | 0.0 | 179 ms | 0 |
| Fri 18 | 0 | 0.0 | 212 ms | 0 |
| Fri 19 | 0 | 0.0 | 206 ms | 0 |
| Fri 21 | 0 | 0.0 | 139 ms | 0 |
| Fri 23 | 0 | 0.0 | 217 ms | 0 |
Reliability
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Cronofy 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 Cronofy yet. Outages of 10 minutes or more get their own page here.
Having trouble with Cronofy?
One report per service every 10 minutes from this network. No account.
Follow Cronofy
Get an email when Cronofy goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Cronofy alerts to Slack, Discord or a webhook — free.
About Cronofy
We track Cronofy (cronofy.com) as part of the Productivity group. Add native calendar sync, scheduling and meeting transcription to your product on one integration. The infrastructure behind 450+ SaaS products.
Cronofy publishes an official status page at status.cronofy.com; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 175 ms average, 99–233 ms range across 15 successful checks.
Questions
Is Cronofy down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Cronofy last down?
We have not recorded a public Cronofy incident since monitoring began 8 days ago.
What is Cronofy's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Cronofy respond?
175 ms on average over the last 24 hours (99–233 ms).
Does Cronofy have an official status page?
Yes, at https://status.cronofy.com.
Cronofy 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 productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Cronofy here at once, the problem is on Cronofy's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Cronofy. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.