Lago incident

Service outage on EU region

Resolved after 3 hours 36 minutes, affecting Current Usage API and API and 1 more, on May 19, 2026.

resolved May 19, 2026, 08:43 AM UTC

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.

Started
May 19, 2026, 05:06 AM UTC
Resolved
May 19, 2026, 08:43 AM UTC
Duration
3h 36m
Detected by Pingoru
May 19, 2026, 05:06 AM UTC

Affected components

Current Usage APIAPIAPIEvent Ingestion APICurrent Usage API

Update timeline

  1. investigating May 19, 2026, 05:06 AM UTC

    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.

  2. resolved May 19, 2026, 05:11 AM UTC

    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

    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.

Your product runs on more than Lago

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →