Labrador CMS incident

Degraded API performance

Major Resolved View vendor source →

Labrador CMS experienced a major incident on October 20, 2026 affecting Labrador Frontend, lasting 1h 21m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2026, 11:51 AM UTC
Resolved
Oct 20, 2026, 01:13 PM UTC
Duration
1h 21m
Detected by Pingoru
Oct 20, 2026, 11:51 AM UTC

Affected components

Labrador Frontend

Update timeline

  1. investigating Oct 20, 2026, 11:51 AM UTC

    We are experiencing an increased level of 503s on our APIs and are currently investigating. This may affect internal API-requests for automatic fronts and similar.

  2. identified Oct 20, 2026, 12:32 PM UTC

    We have identified the issue and are currently working on a fix.

  3. monitoring Oct 20, 2026, 01:06 PM UTC

    The fix has been deployed and we are monitoring the situation. Services should be going back to normal again.

  4. resolved Oct 20, 2026, 01:13 PM UTC

    The incident has been resolved. "Most read"-lists may take some time to come back due to cache, but everything will be back to normal shortly.