Coralogix incident

Delayed ingestion for Logs, Metrics, Traces in US2 cluster

Minor Resolved View vendor source →

Coralogix experienced a minor incident on January 21, 2026 affecting Ingestion - Logs (Frequent Search) and Ingestion - Logs (Archive) and 1 more component, lasting 1h 42m. The incident has been resolved; the full update timeline is below.

Started
Jan 21, 2026, 01:30 PM UTC
Resolved
Jan 21, 2026, 03:13 PM UTC
Duration
1h 42m
Detected by Pingoru
Jan 21, 2026, 01:30 PM UTC

Affected components

Ingestion - Logs (Frequent Search)Ingestion - Logs (Archive)Ingestion - MetricsIngestion - Traces (Frequent Search)Ingestion - Traces (Archive)

Update timeline

  1. investigating Jan 21, 2026, 01:30 PM UTC

    Starting today 21st of January at 13:15 UTC some customers may be affected due to a delayed ingestion of logs, metrics and traces on US2 cluster. Our teams are currently actively working to isolate this issue. Updates will follow as soon as available.

  2. identified Jan 21, 2026, 01:37 PM UTC

    Issue has been identified and a fix is being implemented. Updates about the status will follow shortly.

  3. monitoring Jan 21, 2026, 02:21 PM UTC

    Fix has been implemented and LAG is decreasing. Data can be queried for more than 10 minutes time window. Recovering is ongoing and we'll update with the confirmation as soon as available.

  4. monitoring Jan 21, 2026, 02:53 PM UTC

    At this time, the majority of systems are operational; however, recovery efforts are still in progress for a small number of isolated systems. The situation remains under close observation, and status updates will be communicated promptly as they become available.

  5. resolved Jan 21, 2026, 03:13 PM UTC

    All the systems are up and stable for the moment. Incident has been resolved.