Logz.io change history
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Data Ingestions Delays for Specific Regions Logz.io reported major log-delivery delays affecting some customers in AWS Canada (ca-central-1) and AWS London (eu-west-2). The incident started at 2026-02-18 18:59 UTC and was resolved at 2026-02-18 20:50 UTC, lasting 1 h 50 min; a fix was implemented at 02-18 20:22 UTC. | Major incident | |
| Critical incident: US-EAST: Some customers are experiencing an issue when accessing Grafana UI Some Logz.io customers had trouble accessing Grafana UI in US-EAST during a critical incident from 2025-09-30 22:01 UTC to 2025-10-01 00:05 UTC, lasting 2 h 4 min. Listed components included AWS N. Virginia (us-east-1) Metrics Ingestion and Metrics Visualizations and Dashboards. A fix was implemented at 09-30 22:47 UTC; the incident was subsequently resolved. | Major incident | |
| Major incident: us-east-1 - Metrics Ingestion - Inconsistent Ingestion Logz.io reported a major incident causing inconsistent Metrics Ingestion in AWS N. Virginia (us-east-1), affecting ingestion reliability. It started at 2025-09-16 01:14 UTC and was resolved at 2025-09-16 02:08 UTC, lasting 53 min; Logz.io implemented a fix but did not state a cause. | Major incident | |
| Critical incident: Some Log Shippers are no longer sending log data for a portion of Accounts | Major incident |