Lago incident

Service degradation on EU region

Minor Resolved View vendor source →

Lago experienced a minor incident on May 29, 2026 affecting API and Event Ingestion API and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 29, 2026, 02:45 PM UTC
Resolved
May 29, 2026, 02:45 PM UTC
Duration
Detected by Pingoru
May 29, 2026, 02:45 PM UTC

Affected components

APIEvent Ingestion APICurrent Usage API

Update timeline

  1. investigating May 29, 2026, 02:42 PM UTC

    Status: Investigating We are currently experiencing a service outage. Our systems are not responding as expected. Our engineering team has been alerted and is actively investigating the issue. We will provide updates as soon as we have more information. Affected components Current Usage API (Full outage) API (Full outage) Event Ingestion API (Full outage)

  2. resolved May 29, 2026, 02:45 PM UTC

    Status: Resolved We had a spike of usage on EU API that caused temporary degradation in response times. The API is now operating normally. No action is needed on your end. Apologies for any inconvenience. Affected components Event Ingestion API (Operational) Current Usage API (Operational) API (Operational)