Skip to main content
Calendly logo

Is Calendly Down?

No — Calendly is up

Reachable from all 8 checked regions

Average response time: 347ms

Last checked · checks run every 6 hours

Official status page: https://www.calendlystatus.com

Calendly uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
303ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

21-day clean streak
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 29 checks
Jul 29: 100.00% uptime, 32 checks
Jul 30: 100.00% uptime, 32 checks
Jul 31: 100.00% uptime, 32 checks
Aug 1: 100.00% uptime, 40 checks
Aug 2: 100.00% uptime, 32 checks
Aug 3: 100.00% uptime, 32 checks
Aug 4: 100.00% uptime, 32 checks
Aug 5: 100.00% uptime, 32 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 40 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 24 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 24 checks
Jul 19 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
141ms
DNS 0ms TCP 1ms TLS 10ms TTFB 123ms
lax
72ms
DNS 0ms TCP 1ms TLS 10ms TTFB 47ms
lhr
310ms
DNS 0ms TCP 1ms TLS 6ms TTFB 292ms
nrt
535ms
DNS 0ms TCP 1ms TLS 10ms TTFB 514ms
ord
79ms
DNS 0ms TCP 5ms TLS 7ms TTFB 60ms
sin
594ms
DNS 0ms TCP 2ms TLS 16ms TTFB 481ms
sjc
277ms
DNS 0ms TCP 1ms TLS 5ms TTFB 263ms
syd
705ms
DNS 1ms TCP 1ms TLS 6ms TTFB 690ms
yyz
138ms
DNS 0ms TCP 1ms TLS 6ms TTFB 89ms

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 all 18 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 — 8 of them answered the most recent check.
  • 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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Calendly goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required