We started checking Calendly on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Calendly reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Calendly's own status page declared. Below it, any public chatter we saw about Calendly and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Calendly's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Calendly in the last 24 hours, which is not evidence that nothing is wrong.
Calendly's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Calendly's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Calendly next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
449
US-West
100.00%
351
Europe
100.00%
318
Asia-Pacific
100.00%
194
Their declared record
Calendly's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Users Unable to Log In to Calendly due to blank Login PageMinor incident
Jul 23, 2026, 9:21 PM UTC to Jul 23, 2026, 9:47 PM UTC (27 min)resolved
their latest update (Jul 23, 2026, 9:47 PM UTC): We have resolved the issue that prevented users from logging into Calendly.
Degraded performance on Calendly.comMinor incident
Jul 8, 2026, 5:25 PM UTC to Jul 9, 2026, 4:37 PM UTC (23h 11m)resolved
their latest update (Jul 9, 2026, 4:37 PM UTC): We are continuing to monitor the system to ensure everything remains stable.
Error on Meetings pageMinor incident
May 22, 2026, 5:01 PM UTC to May 22, 2026, 5:55 PM UTC (54 min)resolved
their latest update (May 22, 2026, 5:55 PM UTC): The issue has been resolved, and we are closely monitoring the situation to ensure continued stability.
Stripe unavailableMajor outage
Jul 10, 2019, 9:37 PM UTC to Jul 11, 2019, 1:41 PM UTC (16h 5m)resolved
their latest update (Jul 11, 2019, 1:41 PM UTC): Stripe billing and account upgrade/downgrade functionality have been fully restored.
On 2019-07-10, the Stripe API was unavailable from 16:36–17:02 UTC, and again from 21:14–22:47 UTC. Stripe has confirmed that systems are restored and fully operational.
Stripe billing unavailableMajor outage
Jul 10, 2019, 5:03 PM UTC to Jul 10, 2019, 5:12 PM UTC (8 min)resolved
their latest update (Jul 10, 2019, 5:12 PM UTC): Stripe has resolved the issue and their billing functionality has been restored within the Calendly system.
https://status.stripe.com/
Calendly downMajor outage
Jul 2, 2019, 1:52 PM UTC to Jul 2, 2019, 2:14 PM UTC (21 min)resolved
their latest update (Jul 2, 2019, 2:14 PM UTC): Cloudflare systems have recovered and access to Calendly and Zendesk has been restored. Our developers will continue to monitor going forward.
Unable to connect to Google Calendar serviceMajor outage
Jun 18, 2019, 2:14 PM UTC to Jun 18, 2019, 5:33 PM UTC (3h 19m)resolved
their latest update (Jun 18, 2019, 5:33 PM UTC): Google reports that its services have been fully restored and the issues are now resolved.
More information on the status of the Google Calendar service can be found at https://www.google.com/appsstatus#hl=en&v=issue&sid=2&iid=cc21ebe3962430b2e4ae2b52e3dde98f
Google Cloud Service DisruptionPartial outage
Jun 2, 2019, 7:39 PM UTC to Jun 3, 2019, 12:16 AM UTC (4h 37m)resolved
their latest update (Jun 3, 2019, 12:16 AM UTC): Google reports that its services have been fully restored and the issues are now resolved.
Calendly OutagePartial outage
May 31, 2019, 6:17 PM UTC to May 31, 2019, 8:20 PM UTC (2h 2m)resolved
their latest update (May 31, 2019, 8:20 PM UTC): The issue has been resolved and we are continuing to monitor performance.
Calendar events are not being saved when users select GTM or Zoom as their locationMinor incident
May 22, 2019, 9:23 PM UTC to May 22, 2019, 9:43 PM UTC (20 min)resolved
their latest update (May 22, 2019, 9:43 PM UTC): Issue has been resolved. All calendar events and correspondence should be fully operational.
Showing the 10 most recent of 25 incidents Calendly has declared in the history we hold.
These entries are Calendly's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Calendly's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.