- Service Status
- /
- SavvyCal

Is SavvyCal Down?
- 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
| Component | Status |
|---|---|
| App | Operational |
| Calendar Connections | Operational |
| Integrations | Operational |
| Microsoft 365 | Operational |
| Google Calendar | Operational |
| SquadCast | Operational |
FlareWarden checks
savvycal.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- 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
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 61 ms | 94 ms | 96 ms | 456 ms |
| Ashburn | 9 ms | 2 ms | 5 ms | 36 ms |
| Dallas | 76 ms | 31 ms | 33 ms | 219 ms |
| Frankfurt | 36 ms | 95 ms | 96 ms | 430 ms |
| Newark | 42 ms | 8 ms | 9 ms | 89 ms |
| Paris | 39 ms | 112 ms | 114 ms | 505 ms |
| Stockholm | 91 ms | 96 ms | 98 ms | 495 ms |
| São Paulo | 145 ms | 120 ms | 121 ms | 640 ms |
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 streakMeasured 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.
Related services
SavvyCal outage FAQ
Someone booked but nothing is in my calendar. What happened?
Is a Google Calendar outage the same as SavvyCal being down?
Will my booking page show wrong times during an incident?
Do my existing meetings disappear?
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
403or429means 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


