- Level
- confirmed
- Worst impact
- Major outage
- Regions
- eu
- Down Index
- 38of 100
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 5m it lasted.
Anything that failed between 2026-05-19 05:06 UTC and 2026-05-19 05: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 3
- 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.
provider
- resolved
The service has been restored and is operating normally. We apologize for any inconvenience this may have caused. Thank you for your patience.
provider
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-8440371654
Is Lago still down?
No, this incident was resolved 2026-05-19 05:11 UTC. For Lago's live state, see https://down.guide/lago.
How long did it last?
5m, from 2026-05-19 05:06 UTC to 2026-05-19 05:11 UTC, by the times Lago posted.
What was affected?
Lago named in eu.
What caused it?
Lago hasn't published a root cause. If it does, it shows here.
Where does this come from?
Lago's official status page, https://status.getlago.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.