No reported issuesAn email when it goes down, and when it’s back.
As of 03:36 UTC on 12 November 2026, Lago's status page reports no issues. Its last reported problem was on 1 November 2026: “Degraded performance on our API”, issue, for 10 min from 05:36 UTC.
- Last problem
- 1 Nov · 10 min
- Problems, last 30 days
- 4
- Typical incident
- 10 min
- Longest in 90 days
- 10 min · 19 Oct
Uptime
Lago, last 30 days
99.92 %
Biggest dip: Lago, 10 min of issue on Oct 19.
Incidents
Started in the last 7 days
0
This week Week before
No incidents this week. The last one: Lago, issue on Nov 1.
Recovery
Median time back online
9 min
4 of 4 were over within an hour. Each dot is one incident; the dashed line is the median.
Components 8
All online
- API
- Current Usage API
- Event Ingestion API
- Dashboard (Lago UI)
- API
- Current Usage API
- Event Ingestion API
- Dashboard (Lago UI)
Last 90 days
4 incidents in 48 days tracked · no reported issues 100% of the time · typical incident 10 min
Recent incidents
Times in UTC
- Degraded performance on our API 10 min
Issue - Degraded performance on our API 10 min Issue
- Degraded performance on our API 5 min Issue
- Degraded performance on our API 8 min Issue
Having issues right now
Paribu Humanity (H) Yatırma ve Çekme İşlemleri
CriticalAWS · Bahrain (me-south-1) Region Availability
CriticalAWS · UAE (me-central-1) Region Availability
CriticalGW Sistemas O componente “SAAS Webtrans” e alguns outros componentes estão Inativos
Critical
Popular services
All servicesWhere this comes from
Stackpulse reads Lago’s official status page at status.getlago.com every 5 minutes and keeps 90 days of what changed. We don’t test Lago ourselves, so a problem shows here once Lago reports it.
Stackpulse isn’t affiliated with Lago. Names and logos belong to their owners.
For agents and scripts
The same data as Markdown for AI agents, updated every 30 seconds. With Pro, the API and the MCP server give scripts and AI assistants every service and your own dashboards.