Service outage on EU region

What to do

• Check whether you use Lago in eu. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 7h it lasted.

  Anything that failed between 2026-05-11 07:11 UTC and 2026-05-11 14:11 UTC may need a replay.

• Subscribe to Lago's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=lago works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Lago 9

1. investigatingMay 11, 2026, 7:11 AM UTC

   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.

   provider

2. investigatingMay 11, 2026, 7:58 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.

   provider

3. identifiedMay 11, 2026, 8:05 AM UTC

   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.

   provider

4. monitoringMay 11, 2026, 9:06 AM UTC

   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.

   provider

5. identifiedMay 11, 2026, 9:59 AM UTC

   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.

   provider

6. identifiedMay 11, 2026, 10:48 AM UTC

   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.

   provider

7. monitoringMay 11, 2026, 11:36 AM UTC

   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.

   provider

8. monitoringMay 11, 2026, 12:18 PM UTC

   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.

   provider

9. resolvedMay 11, 2026, 2:11 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.