Lago incident

Degraded performance on our API

Minor Resolved View vendor source →

Lago experienced a minor incident on January 27, 2026 affecting API, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jan 27, 2026, 01:47 PM UTC
Resolved
Jan 27, 2026, 01:47 PM UTC
Duration
—
Detected by Pingoru
Jan 27, 2026, 01:47 PM UTC

Affected components

API

Update timeline

  1. investigating Jan 27, 2026, 01:00 PM UTC

    Status: Investigating We are experiencing elevated latency on our API endpoints. Some API requests may take longer than usual. Our team is investigating and working to resolve this. We will provide updates as we learn more.

  2. investigating Jan 27, 2026, 01:01 PM UTC

    Status: Investigating We are seeing a lot of 500 errors on multiple API endpoints. Investigating Affected components API (Partial outage) API (Partial outage)

  3. monitoring Jan 27, 2026, 01:06 PM UTC

    Status: Monitoring We are deploying fixes and monitoring our endpoints. The situation is stabilized and we are cleaning up the inconsistent states. Affected components API (Operational) API (Operational)

  4. resolved Jan 27, 2026, 01:47 PM UTC

    Status: Resolved All systems are back to normal. This incident is now resolved. A post-mortem will follow. Affected components API (Operational) API (Operational)