Lago experienced a minor incident on May 11, 2026 affecting Current Usage API and API and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 11, 2026, 07:11 AM 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.
- investigating May 11, 2026, 07:58 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.
- identified May 11, 2026, 08:05 AM UTC
Status: Identified We've identified the root cause and are working on a fix. Customers may notice delays in billing processing in the meantime. We'll post another update as soon as the fix is rolled out. Affected components Dashboard (Lago UI) (Degraded performance) Current Usage API (Degraded performance) API (Degraded performance) Event Ingestion API (Degraded performance)
- monitoring May 11, 2026, 09:06 AM UTC
Status: Monitoring The system is stable and the immediate impact has been resolved. We're now processing a significant backlog of billing events that built up during the incident. This may take a while to fully clear. During this window, customers may notice delays in billing processing. All events and invoices will be processed once the backlog is cleared. We're monitoring progress closely and will update this page as the system fully catches up. Affected components Dashboard (Lago UI) (Operational) Current Usage API (Operational) API (Operational) Event Ingestion API (Degraded performance)
- identified May 11, 2026, 09:59 AM UTC
Status: Identified We're investigating an elevated rate of API errors. The root cause has been identified and we're deploying a fix. Customers may experience failed requests or degraded performance in the meantime. We'll update this page as the fix rolls out. Affected components Current Usage API (Partial outage) API (Partial outage) Event Ingestion API (Partial outage) Dashboard (Lago UI) (Partial outage)
- identified May 11, 2026, 10:48 AM UTC
Status: Identified The root cause has been identified as an autovacuum running on a large table in our EU database. Cancelling it is not safe at this stage, so we are letting it complete. The system remains operational, though some EU customers may experience increased latency on API calls and delays on background jobs. Next update in 30 minutes or as soon as the vacuum completes. Affected components Dashboard (Lago UI) (Partial outage) Current Usage API (Partial outage) API (Partial outage) Event Ingestion API (Partial outage)
- monitoring May 11, 2026, 11:36 AM UTC
Status: Monitoring The autovacuum has completed and database performance has returned to normal levels on the EU cluster. We're monitoring the system to confirm full recovery. We'll post a final update shortly. Affected components Dashboard (Lago UI) (Partial outage) Current Usage API (Partial outage) API (Partial outage) Event Ingestion API (Partial outage)
- monitoring May 11, 2026, 12:18 PM UTC
Status: Monitoring The system is stable again and the immediate impact has been resolved. We're now processing again a significant backlog of billing events that built up during the incident. This may take a while to fully clear. During this window, customers may notice delays in billing processing. All events and invoices will be processed once the backlog is cleared. We're monitoring progress closely and will update this page as the system fully catches up. Affected components Dashboard (Lago UI) (Degraded performance) Current Usage API (Degraded performance) API (Degraded performance) Event Ingestion API (Degraded performance)
- resolved May 11, 2026, 02:11 PM UTC
Status: Resolved The incident is resolved. Earlier today, a long-running autovacuum on our EU database caused elevated latency on some API calls and delays on background jobs. The vacuum has completed, performance has returned to baseline, and monitoring confirms full recovery. We'll follow up internally to reduce the impact of similar operations in the future. Thanks for your patience. Affected components API (Operational) Event Ingestion API (Operational) Dashboard (Lago UI) (Operational) Current Usage API (Operational)