Cronofy incident

Elevated API 500 errors in our AU data center

Resolved on February 13, 2026.

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.

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.

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 →