Factbird incident

Degraded application experience resulting in 504 errors

Major Resolved View vendor source →

Factbird experienced a major incident on March 12, 2025 affecting User Interface and API Service, lasting –. The incident has been resolved; the full update timeline is below.

Started
Mar 12, 2025, 10:39 AM UTC
Resolved
Mar 12, 2025, 10:39 AM UTC
Duration
–
Detected by Pingoru
Mar 12, 2025, 10:39 AM UTC

Affected components

User InterfaceAPI Service

Update timeline

  1. resolved Mar 12, 2025, 10:39 AM UTC

    This morning (CET), our backend encountered service timeouts due to a specific service/application usage pattern, resulting in a ripple effect that impacted a large number of Factbird users. The issue stemmed from a change implemented on March 11th, intended to enhance overall performance. For now, we have disabled the change and are actively assessing solutions to mitigate the ripple effect it caused.