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

As listed on Coralogix’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Coralogix status & history page.

Related: Coralogix status & history. SquidGrid is not affiliated with Coralogix.