Skip to main content
SavvyCal logo

Is SavvyCal Down?

No — SavvyCal is up

Reachable from all 8 checked regions

Average response time: 547ms

Last checked · checks run every 6 hours

Official status page: https://savvycal.instatus.com

SavvyCal uptime

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

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

30-day history

26-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: 100.00% uptime, 16 checks
Aug 27: 100.00% uptime, 32 checks
Aug 28: 100.00% uptime, 32 checks
Aug 29: 100.00% uptime, 32 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 31 checks
Sep 2: 100.00% uptime, 24 checks
Sep 3: 100.00% uptime, 24 checks
Sep 4: 100.00% uptime, 14 checks
Sep 5: 100.00% uptime, 21 checks
Sep 6: 100.00% uptime, 31 checks
Sep 7: 100.00% uptime, 32 checks
Sep 8: 100.00% uptime, 40 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 47 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 checks
Aug 22 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
620ms
DNS 67ms TCP 0ms TLS 75ms TTFB 423ms
arn
706ms
DNS 140ms TCP 0ms TLS 32ms TTFB 387ms
bom
1340ms
DNS 122ms TCP 0ms TLS 38ms TTFB 651ms
cdg
472ms
DNS 30ms TCP 0ms TLS 52ms TTFB 249ms
dfw
251ms
DNS 46ms TCP 0ms TLS 32ms TTFB 156ms
ewr
112ms
DNS 38ms TCP 0ms TLS 31ms TTFB 95ms
fra
592ms
DNS 72ms TCP 0ms TLS 60ms TTFB 317ms
yyz
283ms
DNS 97ms TCP 0ms TLS 77ms TTFB 227ms

What SavvyCal does

SavvyCal shares availability as a link and books meetings straight into a connected calendar. It reads free and busy times from Google Calendar or Microsoft 365 and writes the resulting event back. Recipients pick a time without creating an account, so the booking page is customer-facing for whoever shared the link.

What an outage looks like

Booking links fail to load or show no available times, so the person you sent it to cannot schedule and usually will not tell you. Bookings may be accepted without the event appearing in your calendar. Availability can also be wrong rather than absent, offering slots you are not actually free for.

What to do about it

Check SavvyCal's status page, which reports the App separately from Calendar Connections, with Microsoft 365 and Google Calendar as their own rows under that group. A calendar provider outage breaks availability while SavvyCal itself is fine. If links are failing, propose a specific time by email rather than leaving prospects on a broken booking page.

Is it down for everyone, or just you?

If this page says SavvyCal 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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

SavvyCal outage FAQ

Someone booked but nothing is in my calendar. What happened?
That is the shape of a calendar connection fault rather than a SavvyCal outage. The booking was recorded, but writing the event to Google Calendar or Microsoft 365 failed. Both are separate components on SavvyCal's status page. Check your SavvyCal bookings list directly, since it holds the record your calendar is missing.
Is a Google Calendar outage the same as SavvyCal being down?
No, though it looks identical to the person trying to book. SavvyCal reads availability from the connected calendar, so a Google or Microsoft incident produces empty or wrong availability while SavvyCal's own App component stays operational. The status page lists both providers for exactly this reason.
Will my booking page show wrong times during an incident?
It can, and that is worse than an outright failure. If SavvyCal cannot read current free and busy data it may offer slots you are already booked for, producing double bookings you discover later. Treat degraded calendar connections as a reason to pause sharing links, not merely a slow page.
Do my existing meetings disappear?
No. Events already written to your calendar live in Google Calendar or Microsoft 365 and are unaffected by a SavvyCal incident. What stops is new scheduling. Meetings already on the books proceed normally, including any video conferencing links attached to them when they were created.

How we measure this

  • We request SavvyCal'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 SavvyCal 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 SavvyCal goes down

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

Start Free Monitoring
Free plan available No credit card required