Is Calendly Down?

No — Calendly is up

Calendly's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 431 ms

Right now

The verdict is the worse of these two. How we decide

Calendly's status page

calendlystatus.com · read 4 minutes ago · checked every 3 minutes

Operational

Calendly's components, as its status page reports them
Component	Status
calendly.com the service itself	Operational
Notifications	Operational
Google	Operational
Outlook.com & Office 365	Operational
Outlook Desktop	Operational
iCloud	Operational
Exchange	Operational
Zoom	Operational
Intercom	Operational
GoToMeeting	Operational
Salesforce	Operational
Stripe	Operational

5 more, all operational · show all 17

All of Calendly's components
Component	Status
calendly.com	Operational
Notifications	Operational
Google	Operational
Outlook.com & Office 365	Operational
Outlook Desktop	Operational
iCloud	Operational
Exchange	Operational
Zoom	Operational
Intercom	Operational
GoToMeeting	Operational
Salesforce	Operational
Stripe	Operational
PayPal	Operational
Google Analytics	Operational
Calendly for Chrome	Operational
Calendly API	Operational
Webhooks	Operational

Open their status page

FlareWarden checks

calendly.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 431 ms
Checked: 3 hours ago

By region

Amsterdam reachable, 282 ms
Chicago reachable, 236 ms
San Jose reachable, 373 ms
Singapore reachable, 804 ms
Stockholm reachable, 85 ms
Sydney reachable, 797 ms
Tokyo reachable, 651 ms
Toronto reachable, 221 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	31 ms	6 ms	12 ms	260 ms
Chicago	107 ms	2 ms	8 ms	225 ms
San Jose	76 ms	2 ms	15 ms	353 ms
Singapore	76 ms	2 ms	9 ms	793 ms
Stockholm	37 ms	2 ms	11 ms	70 ms
Sydney	99 ms	1 ms	10 ms	776 ms
Tokyo	113 ms	1 ms	11 ms	641 ms
Toronto	34 ms	1 ms	15 ms	164 ms

We check that calendly.com loads, not every feature behind it. Test it yourself

History

Incidents Calendly reported

Since Oct 22, 15 days · from calendlystatus.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Calendly website availability

Measured by FlareWarden · calendly.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 341ms

Last 30 days

91-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of calendly.com from multiple regions every 6 hours. Calendly's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Calendly does

Calendly turns a shared link into a booking page, reading availability from a connected calendar and writing meetings back to it. Sales teams, recruiters and support staff put the link in email signatures and on websites, so an outage silently removes a booking path that people rely on without ever visiting Calendly themselves.

What an outage looks like

Booking pages fail to load for invitees, who see an error instead of your availability and usually give up rather than report it. Slots may display but fail on confirmation. Calendar integrations stop syncing, so meetings booked do not appear in the underlying calendar, or booked slots keep showing as free. Confirmation emails and webhooks arrive late or not at all.

What to do about it

Check calendlystatus.com, which reports calendly.com, the Chrome extension, calendar integrations, third-party integrations, and API and webhooks as separate components, so a broken calendar sync does not always mean the booking page is down. Post a direct alternative for anyone trying to book, since an invitee who hits a broken page has no way to tell you.

Is it down for everyone, or just you?

If this page says Calendly is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Calendly outage FAQ

Is Calendly down or has my calendar disconnected?

Calendar integrations are reported separately from calendly.com, and a disconnected calendar is the more common problem. It usually shows as availability that looks wrong rather than a page that fails to load, and it is fixed by reconnecting the calendar in settings. Check the status page first, then the integration, before assuming an outage.

Do bookings made during an outage still reach my calendar?

A booking Calendly confirmed is recorded and syncs to your calendar once the integration recovers, sometimes with a delay. A booking that failed at the confirmation step was never created and no one is notified, including you. After an incident, comparing Calendly's scheduled events against your calendar is worth the few minutes it takes.

Will invitees know my booking page is broken?

No, and this is the real cost of a Calendly outage. An invitee sees an error page, assumes the link is stale, and often does not tell you. Nothing is queued and nothing is recovered. During a longer incident, offering a direct reply as an alternative recovers meetings that would otherwise silently disappear.

Does a Calendly outage stop existing meetings from happening?

No. Meetings already booked live in your calendar and in the conferencing tool attached to them, both of which run independently of Calendly. The meeting link still works and both parties still get their reminders from the calendar. What breaks is new bookings, rescheduling and cancellations routed through Calendly.

Why do my confirmation emails and webhooks arrive late?

API and webhooks are tracked as their own component, so notification delivery can degrade while booking itself works. During recovery, queued messages often arrive together, which can look like duplicate bookings when it is only duplicate notifications. Check the scheduled event itself rather than counting emails before assuming something was double booked.

How we measure this

We request Calendly's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Calendly publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Calendly itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Calendly goes down

We check Calendly every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required