Cronofy incident

Elevated API 500 errors in our AU data center

Minor Resolved View vendor source →
Started
Feb 13, 2026, 01:44 PM UTC
Resolved
Feb 13, 2026, 01:44 PM UTC
Duration
Detected by Pingoru
Feb 13, 2026, 01:44 PM UTC

Update timeline

  1. resolved Feb 13, 2026, 01:44 PM UTC

    Between 12:52 and 12:55 we saw that calls to our API encountered a higher level of 500 Server Error responses than usual We have investigated this and it appears to relate to a period where we saw a large spike in traffic, a rapid drop and another spike in quick succession resulting in some temporary 500 errors. This is now resolved but we will continue monitoring for any further issues.

Looking to track Cronofy downtime and outages?

Pingoru polls Cronofy's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Cronofy reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Cronofy alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Cronofy for free

5 free monitors · No credit card required