Skip to main content
Cal.com logo

Is Cal.com Down?

No — Cal.com is up

Reachable from all 8 checked regions

Average response time: 191ms

Last checked · checks run every 6 hours

Official status page: https://status.cal.com

Cal.com uptime

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

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

30-day history

28-day clean streak
Sep 7: no data
Sep 8: no data
Sep 9: 100.00% uptime, 16 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 30 checks
Sep 13: 100.00% uptime, 31 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 56 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 39 checks
Sep 18: 100.00% uptime, 31 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 31 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 30 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 24 checks
Sep 7 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.

gru
124ms
DNS 16ms TCP 1ms TLS 9ms TTFB 99ms
iad
220ms
DNS 117ms TCP 1ms TLS 10ms TTFB 174ms
jnb
167ms
DNS 0ms TCP 0ms TLS 7ms TTFB 119ms
lax
193ms
DNS 23ms TCP 1ms TLS 8ms TTFB 143ms
lhr
206ms
DNS 86ms TCP 2ms TLS 10ms TTFB 157ms
nrt
197ms
DNS 119ms TCP 1ms TLS 5ms TTFB 175ms
ord
202ms
DNS 60ms TCP 1ms TLS 9ms TTFB 158ms
sin
219ms
DNS 93ms TCP 1ms TLS 8ms TTFB 192ms

What Cal.com does

Cal.com is open-source scheduling infrastructure. It hosts booking pages that let people pick a time from your live calendar availability, and it exposes the same scheduling as an API that other products embed. Teams use it for sales calls, interviews and support sessions, so an outage stops new bookings arriving rather than breaking an internal tool.

What an outage looks like

Booking pages fail to load or show no available times, so invitees see an empty calendar rather than an error and quietly give up. Confirmation emails and calendar invitations stop arriving after someone books. Embedded booking widgets on your own site render blank. API calls from products built on Cal.com time out or return errors.

What to do about it

Read status.cal.com, which reports App, Website and API as three separate components. If only API is affected, hosted booking pages may still work while embeds and integrations fail. Tell anyone waiting on a meeting link to arrange it by email for now, and re-check your calendar before assuming a missing invitation was never sent.

Is it down for everyone, or just you?

If this page says Cal.com 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

Cal.com outage FAQ

My booking page shows no available times. Is Cal.com down?
That is a common outage symptom, but it is not the only cause. Cal.com reads availability from your connected calendar, so an expired Google or Microsoft connection produces the same empty page for your link alone while everyone else's works normally. Check status.cal.com first. If App is operational there, reconnect the calendar in your Cal.com settings.
Does a Cal.com outage affect bookings that are already confirmed?
Confirmed bookings live in your own calendar once created, so a meeting already on your calendar stays there and its video link still works. What stops is new bookings, reschedules and cancellations made through Cal.com. Tell attendees to join the invitation they already have rather than looking for a fresh link during the incident.
Is it Cal.com or my embedded widget?
Compare where it fails. If the hosted page on cal.com works but the embed on your own site is blank, that points at the API component or at your page loading the embed script, not at the whole service. status.cal.com separates App, Website and API precisely so those cases can be told apart.
Will I lose bookings made during an outage?
A booking exists once Cal.com has recorded it and sent a confirmation, so treat the confirmation email as the signal that it landed. An attempt that never reached that point will usually need to be made again. Check the calendar event itself rather than relying on what the booking page displayed at the time.
Does a Cal.com outage affect my Google Calendar?
No. Cal.com writes into your calendar, so the calendar keeps working and events already created stay in place. The dependency also runs the other way: if Google Calendar or Microsoft 365 has an incident, Cal.com cannot read availability or create events, and the booking page looks identical to a Cal.com outage from the invitee's side.

How we measure this

  • We request Cal.com's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • 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 Cal.com 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 Cal.com goes down

This page refreshes every 6 hours. 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