Lago Outage History

Lago had 3 outages in the last 2 years — averaging 0.1 incidents per month.

There were 3 Lago outages since January 27, 2026. Each is summarised below — incident details, duration, and resolution information.

Minor September 17, 2026

Degraded performance on our API

Timeline · 2 updates

investigating Sep 17, 2026, 05:11 PM UTC

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. Affected components API (Degraded performance)
resolved Sep 17, 2026, 05:21 PM UTC

Status: Resolved Latency has returned to normal levels. All services are operating as expected. Thank you for your patience.

Minor May 29, 2026

Affected: APIAPIEvent Ingestion APICurrent Usage API

Timeline · 2 updates

investigating May 29, 2026, 02:42 PM UTC

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)
resolved May 29, 2026, 02:45 PM UTC

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)

Minor May 19, 2026

Affected: Current Usage APIAPIAPIEvent Ingestion APICurrent Usage API

Timeline · 3 updates

investigating May 19, 2026, 05:06 AM UTC

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)
resolved May 19, 2026, 05:11 AM UTC

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.
resolved May 19, 2026, 08:43 AM UTC

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)