Lago incident

Service outage on EU region

Minor Resolved View vendor source →

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

Started
May 19, 2026, 08:43 AM UTC
Resolved
May 19, 2026, 08:43 AM UTC
Duration
Detected by Pingoru
May 19, 2026, 08:43 AM UTC

Affected components

Current Usage APIAPIEvent Ingestion API

Update timeline

  1. investigating May 19, 2026, 05:06 AM 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 19, 2026, 05:11 AM UTC

    Status: Resolved The service has been restored and is operating normally. We apologize for any inconvenience this may have caused. Thank you for your patience.

  3. resolved May 19, 2026, 08:43 AM UTC

    Status: Resolved We experienced a brief service disruption caused by a configuration change that was rolled back within minutes of detection. We apologize for the inconvenience and will share a full post-incident summary shortly. Affected components Current Usage API (Operational) API (Operational) Event Ingestion API (Operational)