Loading status…
Loading status…
Calendly status · SaaS · checked (1m ago)
No — Calendly is not down. All Calendly systems are reported operational.
According to Calendly's official status page, Calendly was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Calendly's feed reported no outage in 100.00% of our checks.
Everything above is read from Calendly's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Calendly in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Calendly handles meeting scheduling: a booking page that reads your calendar's availability and writes the meeting back to it. It sits between your calendar provider and the person booking, which shapes what its outages look like.
The status page separates the booking pages from the app and from the calendar integrations and API. Integrations are the component to read: a Google Calendar or Outlook sync problem means availability is wrong or bookings do not appear, while Calendly's own pages load perfectly — and the root cause is frequently the calendar provider rather than Calendly.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Calendly's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Calendly was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 1m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Calendly's status endpoint.
Calendly has published 25 incidents in the last 12 months, the 20 most recent shown here. Only what Calendly posted itself — not every problem users hit.
resolved · Jul 23, 09:21 PM (58d ago)
resolved · Jul 8, 05:25 PM (73d ago)
resolved · May 22, 05:01 PM (120d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
resolved · Apr 15, 03:21 PM (157d ago)
Availability that looks wrong is usually the event type's rules — buffers, minimum notice, date ranges — or a timezone mismatch between you and the invitee. A revoked calendar connection stops sync silently. Bookings not appearing in your calendar after a Google or Microsoft password change is a broken OAuth grant, not an outage.