Calendly Outage History

Calendly is up right now

Calendly had 4 outages in the last 2 years — averaging 0.2 incidents per month.

There were 4 Calendly outages since April 13, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.calendlystatus.com

Minor July 23, 2026

Users Unable to Log In to Calendly due to blank Login Page

Detected by Pingoru
Jul 23, 2026, 09:47 PM UTC
Resolved
Jul 23, 2026, 09:47 PM UTC
Duration
Affected: calendly.com
Timeline · 3 updates
  1. investigating Jul 23, 2026, 09:21 PM UTC

    Status: Investigating We are currently investigating an issue with the calendly login page Affected components calendly.com (Degraded performance)

  2. identified Jul 23, 2026, 09:39 PM UTC

    Status: Identified We have identified an issue that prevents users from logging into Calendly. The team is currently making an update to fix this. Affected components calendly.com (Degraded performance)

  3. resolved Jul 23, 2026, 09:47 PM UTC

    Status: Resolved We have resolved the issue that prevented users from logging into Calendly. Affected components calendly.com (Operational)

Read the full incident report →

Minor July 9, 2026

Degraded performance on Calendly.com

Detected by Pingoru
Jul 09, 2026, 04:37 PM UTC
Resolved
Jul 09, 2026, 04:37 PM UTC
Duration
Affected: ExchangeiCloudGoogleNotificationsOutlook.com & Office 365calendly.comOutlook Desktop
Timeline · 4 updates
  1. investigating Jul 08, 2026, 05:25 PM UTC

    Status: Investigating We are currently investigating an issue with Calendly Affected components calendly.com (Degraded performance) Outlook Desktop (Degraded performance) Notifications (Degraded performance) iCloud (Degraded performance) Exchange (Degraded performance) Google (Degraded performance) Outlook.com & Office 365 (Degraded performance)

  2. identified Jul 08, 2026, 06:06 PM UTC

    Status: Identified We are currently investigating an issue with calendly Affected components calendly.com (Degraded performance) Outlook Desktop (Degraded performance) Notifications (Degraded performance) iCloud (Degraded performance) Exchange (Degraded performance) Google (Degraded performance) Outlook.com & Office 365 (Degraded performance)

  3. monitoring Jul 09, 2026, 03:10 PM UTC

    Status: Monitoring We are continuing to monitor the fix that has been put in place. Calendly is fully operational, and we will provide additional updates if needed. Affected components Exchange (Operational) Google (Operational) Outlook.com & Office 365 (Operational) calendly.com (Operational) Outlook Desktop (Operational) Notifications (Operational) iCloud (Operational)

  4. resolved Jul 09, 2026, 04:37 PM UTC

    Status: Resolved We are continuing to monitor the system to ensure everything remains stable. Affected components iCloud (Operational) Exchange (Operational) Google (Operational) Outlook.com & Office 365 (Operational) calendly.com (Operational) Outlook Desktop (Operational) Notifications (Operational)

Read the full incident report →

Minor May 22, 2026

Error on Meetings page

Detected by Pingoru
May 22, 2026, 05:55 PM UTC
Resolved
May 22, 2026, 05:55 PM UTC
Duration
Affected: calendly.com
Timeline · 3 updates
  1. investigating May 22, 2026, 04:45 PM UTC

    Status: Investigating Users may experience error messages on the Meetings page. Affected components calendly.com (Degraded performance)

  2. monitoring May 22, 2026, 05:08 PM UTC

    Status: Monitoring Users are now able to view the Meetings page. Affected components calendly.com (Operational)

  3. resolved May 22, 2026, 05:55 PM UTC

    Status: Resolved The issue has been resolved, and we are closely monitoring the situation to ensure continued stability. Affected components calendly.com (Operational)

Read the full incident report →

Minor April 13, 2026

Calendly Site Unavailable

Detected by Pingoru
Apr 13, 2026, 01:00 PM UTC
Resolved
Apr 13, 2026, 01:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 13, 2026, 01:00 PM UTC

    Status: Resolved Calendly was down from ~9:09am EDT (13:09 UTC) to ~9:18am EDT (13:18 UTC).

Read the full incident report →