User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Microsoft 365 elevated error rates | Increase in failures to join Google Meet calls
Source: the vendor's status page · We are not affiliated with Cronofy.
Estimated fix: Not enough Cronofy history yet; similar Productivity outages lasted 41 min (median, typically 11 min–5 h; 26 outages).
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 233 ms.
Minor incident
Microsoft 365 elevated error rates | Increase in failures to join Google Meet calls Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 10:45 | 0 | 0.0 | 122 ms | 0 |
| 12:45 | 0 | 0.0 | 191 ms | 0 |
| 15:00 | 0 | 0.0 | 334 ms | 0 |
| 17:00 | 0 | 0.0 | 191 ms | 0 |
| 19:00 | 0 | 0.0 | 118 ms | 0 |
| 21:15 | 0 | 0.0 | 294 ms | 0 |
| 23:15 | 0 | 0.0 | 177 ms | 0 |
| 01:15 | 0 | 0.0 | 188 ms | 0 |
| 03:15 | 0 | 0.0 | 207 ms | 0 |
| 05:15 | 0 | 0.0 | 201 ms | 0 |
| 07:30 | 0 | 0.0 | 233 ms | 0 |
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.
No outages on record for Cronofy yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
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.
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: 205 ms average, 118–334 ms range across 11 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Microsoft 365 elevated error rates | Increase in failures to join Google Meet calls
We have not recorded a public Cronofy incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
205 ms on average over the last 24 hours (118–334 ms).
Yes, at https://status.cronofy.com.
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.