Cronofy incident

Increased API errors in our US data center

Notice Resolved View vendor source →

Cronofy experienced a notice incident on May 14, 2026 affecting Scheduler and API, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 14, 2026, 10:37 AM UTC
Resolved
May 14, 2026, 10:37 AM UTC
Duration
—
Detected by Pingoru
May 14, 2026, 10:37 AM UTC

Affected components

SchedulerAPI

Update timeline

  1. resolved May 14, 2026, 10:37 AM UTC

    Between 03:08 UTC and 03:10 UTC we observed increased API error rates in our US data center. During this time, customers may have received 500 Internal Server Error responses. Since that time, error rates have returned to normal levels. These errors were caused by a read-only database server going through an automated recovery process.