Cronofy incident

Increased API errors in our US data center

Resolved after 2 minutes, affecting Scheduler and API, on May 14, 2026.

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.

Started
May 14, 2026, 03:08 AM UTC
Resolved
May 14, 2026, 03:10 AM UTC
Duration
2m
Detected by Pingoru
May 14, 2026, 03:08 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.

Your product runs on more than Cronofy

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →