- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 12of 100
What to do
Check whether your product depends on Lago. 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 6m it lasted.
Anything that failed between 2026-08-17 14:08 UTC and 2026-08-17 14:14 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 2
- 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.
provider
- resolved
Latency has returned to normal levels. All services are operating as expected. Thank you for your patience.
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-280bfc64c3
Is Lago still down?
No, this incident was resolved 2026-08-17 14:14 UTC. For Lago's live state, see https://down.guide/lago.
How long did it last?
6m, from 2026-08-17 14:08 UTC to 2026-08-17 14:14 UTC, by the times Lago posted.
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.