Live  /  Coralogix  /  Incident

Coralogix: Ingestion Delays Across All Pipelines in the US3 Region

Coralogix · coralogix.comMinor incidentResolved2026-10-14 11:32 UTC
Public — what happened

Summary

Coralogix reported slowdowns in how quickly incoming data was processed in its US3 region beginning at 10:27 UTC on 2026-10-14, affecting logs, metrics and traces, and said some related platform features could also be affected. The company said at 10:53 UTC that it had found the problem, though it did not describe a cause, and it put a fix in place by 11:05 UTC. Coralogix said alerting features were working again at 11:11 UTC while it kept watching for further delays, and the incident was marked resolved at 11:32.

Affected

Fleet, Processing – Logs, Processing – Metrics, Processing – Event2Metric, Processing – Traces, Processing – RUM, Ingestion – Logs (Frequent Search), Ingestion – Logs (Archive), Ingestion – Metrics, Ingestion – Traces (Frequent Search), Ingestion – Traces (Archive), Alerts – Logs, Alerts – Metrics, Alerts – Traces, Alerts – Flow, Alerts - SLO, Alerts – Notifications, Notification Center, Cases/Incidents

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 43, 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.