Lago had 3 outages in the last 2 years totaling 24m of downtime — averaging 0.1 incidents per month.
There were 3 Lago outages since January 27, 2026 totaling 24m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
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. Affected components Current Usage API (Full outage) API (Full outage) Event Ingestion API (Full outage)
Status: Resolved We had a spike of usage on EU API that caused temporary degradation in response times. The API is now operating normally. No action is needed on your end. Apologies for any inconvenience. Affected components Event Ingestion API (Operational) Current Usage API (Operational) API (Operational)
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. Affected components Current Usage API (Full outage) API (Full outage) Event Ingestion API (Full outage)
Status: Resolved The service has been restored and is operating normally. We apologize for any inconvenience this may have caused. Thank you for your patience.
Status: 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. Affected components Current Usage API (Operational) API (Operational) Event Ingestion API (Operational)