Skip to main content
SavvyCal logo

Is SavvyCal Down?

No — SavvyCal is up
SavvyCal's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 569 ms

Right now

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

SavvyCal's status page

savvycal.instatus.com · read · checked every 3 minutes

Operational
SavvyCal's components, as its status page reports them
ComponentStatus
AppOperational
Calendar ConnectionsOperational
IntegrationsOperational
Microsoft 365Operational
Google CalendarOperational
SquadCastOperational

FlareWarden checks

savvycal.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
569 ms
Checked

By region

  • Amsterdam reachable, 740 ms
  • Ashburn reachable, 43 ms
  • Dallas reachable, 314 ms
  • Frankfurt reachable, 714 ms
  • Newark reachable, 114 ms
  • Paris reachable, 843 ms
  • Stockholm reachable, 787 ms
  • São Paulo reachable, 1002 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam61 ms94 ms96 ms456 ms
Ashburn9 ms2 ms5 ms36 ms
Dallas76 ms31 ms33 ms219 ms
Frankfurt36 ms95 ms96 ms430 ms
Newark42 ms8 ms9 ms89 ms
Paris39 ms112 ms114 ms505 ms
Stockholm91 ms96 ms98 ms495 ms
São Paulo145 ms120 ms121 ms640 ms
We check that savvycal.com loads, not every feature behind it. Test it yourself

History

Incidents SavvyCal reported

Since Oct 27, 10 days · from savvycal.instatus.com

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

SavvyCal website availability

Measured by FlareWarden · savvycal.com

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

Last 30 days

72-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, 29 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, 30 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 savvycal.com from multiple regions every 6 hours. SavvyCal's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 72 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 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. 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 SavvyCal 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 SavvyCal 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 SavvyCal goes down

We check SavvyCal 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