Factbird incident
Several pages reporting "lambda function error: Unhandled"
Factbird experienced a major incident on March 10, 2026 affecting User Interface and API Service and 1 more component, lasting 1h 23m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Mar 10, 2026, 12:02 PM UTC
We have received reports that many customers are seeing "lambda function error: Unhandled" errors when trying to access the Faccbird system. We are investigating
- monitoring Mar 10, 2026, 12:33 PM UTC
We identified an issue in connecting to one of our databases. We have made a quick update to circumvent it, and are monitoring error rates
- resolved Mar 10, 2026, 01:26 PM UTC
Services are back to normal
- postmortem Mar 13, 2026, 02:59 PM UTC
On March 10th, around 8AM CET, we started seeing sporadic connectivity failures towards a database that couldn’t be reached, resulting in some compute resources failing to start up and serve user requests. This particular database connection was not at all required and was made optional to address the failing API requests during this incident. The root cause was an optional, and under-provisioned database, that started seeing an unexpected load from an internal service which it failed to recover from on its own requiring manual intervention at the time of the incident.