Lago Outage History
Lago is up right nowPingoru has recorded 93 incidents for Lago: 93 in the last 12 months and 9 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 6 | 3 of 720 (0%) |
| May 2026 | 5 | 11 of 744 (1%) |
| June 2026 | 8 | 4 of 720 (1%) |
| July 2026 | 7 | 2 of 744 (0%) |
| August 2026 | 3 | 1 of 744 (0%) |
| September 2026 | 2 | 4 of 720 (1%) |
| October 2026 | 3 | 0 of 569 (0%) |
Incidents, newest first
Minor October 19, 2026 Degraded performance on our API 6m
Started Oct 19, 2026, 09:11 PM UTC· resolved Oct 19, 2026, 09:17 PM UTC
- investigating Oct 19, 2026, 09:11 PM UTC
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.
- resolved Oct 19, 2026, 09:17 PM UTC
Latency has returned to normal levels. All services are operating as expected. Thank you for your patience.
Minor May 29, 2026 Service degradation on EU region 3m API, API, Event Ingestion API, Current Usage API
Started May 29, 2026, 02:42 PM UTC· resolved May 29, 2026, 02:45 PM UTC
- investigating May 29, 2026, 02:42 PM UTC
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.
- resolved May 29, 2026, 02:45 PM UTC
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.
Minor May 19, 2026 Service outage on EU region 3h 36m Current Usage API, API, API, Event Ingestion API and 1 more
Started May 19, 2026, 05:06 AM UTC· resolved May 19, 2026, 08:43 AM UTC
- investigating May 19, 2026, 05:06 AM UTC
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.
- resolved May 19, 2026, 05:11 AM UTC
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
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.