Skip to main content
Cal.com logo

Is Cal.com Down?

No — Cal.com is up
Cal.com's status page
Not available · we could not read it
FlareWarden checks
Website reachable · 8 of 8 regions · 182 ms

Right now

We could not read Cal.com's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

cal.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
182 ms
Checked

By region

  • Chicago reachable, 187 ms
  • Johannesburg reachable, 142 ms
  • London reachable, 218 ms
  • Los Angeles reachable, 146 ms
  • San Jose reachable, 176 ms
  • Singapore reachable, 273 ms
  • Sydney reachable, 98 ms
  • Tokyo reachable, 216 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Chicago24 ms1 ms13 ms173 ms
Johannesburg18 ms1 ms7 ms130 ms
London58 ms3 ms12 ms200 ms
Los Angeles37 ms2 ms15 ms133 ms
San Jose72 ms3 ms16 ms161 ms
Singapore97 ms2 ms8 ms249 ms
Sydney0 ms1 ms7 ms88 ms
Tokyo107 ms1 ms7 ms203 ms
We check that cal.com loads, not every feature behind it. Test it yourself

History

Cal.com website availability

Measured by FlareWarden · cal.com

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

Last 30 days

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

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

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. 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 Cal.com 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 Cal.com 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. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Cal.com goes down

We check Cal.com 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