Factbird incident

Sporadic application error code 413

Critical Resolved View vendor source →

Factbird experienced a critical incident on February 13, 2025, lasting –. The incident has been resolved; the full update timeline is below.

Started
Feb 13, 2025, 02:30 PM UTC
Resolved
Feb 13, 2025, 02:30 PM UTC
Duration
–
Detected by Pingoru
Feb 13, 2025, 02:30 PM UTC

Update timeline

  1. resolved Feb 14, 2025, 10:51 AM UTC

    Some users experience API error 413 when navigating Factbird. The issue is isolated to users that have access to a large quantity of sensors and lines.

  2. postmortem Feb 14, 2025, 10:51 AM UTC

    The root cause of the incident was an internal authentication payload exceeding a limit, which caused the API layer to error. # Actions taken * Deploy a change to the authentication layer that reduces the authentication payload size