Live / Coralogix / Incident
Coralogix: AP1 - increased latency in Metrics/Logs Ingestion
Coralogix · coralogix.comResolved2026-10-06 20:52 UTC
Public — what happened
Summary
Coralogix reported delays in processing incoming metrics and logs in its AP1 region starting at 19:12 UTC on October 6, 2026, and said alerts tied to that data were also affected. The company said it had found the problem within a few minutes, though it did not describe what the cause was. By 19:35 UTC it reported that most of the trouble was eased, with some remaining delay in log alerts, and a fix was in place and being watched from 19:40 UTC. The incident was marked resolved at 20:52 UTC.
Affected
Alerts - Logs
Timeline
- Started — 2026-10-06 19:12 UTC
- Investigating — 2026-10-06 19:12 UTC
- Identified — 2026-10-06 19:16 UTC (4 updates)
- Monitoring — 2026-10-06 19:40 UTC
- Resolved — 2026-10-06 20:52 UTC · 1h 40m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Coralogix against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Coralogix: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Coralogix report →
More from Coralogix
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.