Companies / Coralogix / changes

Coralogix change history

5Major incident
When (UTC)ChangeKind
Major incident: RUM data is unavailable for specific users
Coralogix reported a major RUM outage affecting some customers’ ability to view RUM data or access RUM-related features. It began at 2026-08-06 09:37 UTC and was resolved at 2026-08-06 10:15 UTC; the computed duration was 37 min. A fix was implemented, but no cause was stated.
Major incident
Major incident: Log Query failures across EU1 region
Coralogix reported a major incident causing log query failures in Explore → Logs (v2 and Legacy), including errors accessing archived log data. It started at 2026-08-05 08:46 UTC and was resolved at 2026-08-05 09:01 UTC, lasting 15 min. Although initially reporting EU1 and US1 impact, Coralogix confirmed only EU1 was affected; all services were restored.
Major incident
Major incident: RUM (Real User Monitoring) Data Ingestion Unavailable in EU2
Coralogix reported a major outage affecting RUM data ingestion in EU2, starting at 2026-05-29 10:14 UTC and resolved at 2026-05-29 11:02 UTC (48 min). A fix was implemented, and all previously affected RUM data was available within the system after resolution.
Major incident
Major incident: Real User Monitoring (RUM) feature is currently unavailable in the UI across the EU1, EU2, US1, US2, AP1, and AP3 regions.
Coralogix reported a major RUM UI outage across EU1, EU2, US1, US2, AP1, and AP3, leaving users with a blank page when accessing RUM. It started at 2026-04-20 14:47 UTC and lasted 34 min, resolving at 2026-04-20 15:21 UTC after a fix was implemented.
Major incident
Critical incident: We are currently investigating an issue affecting the alerting pipeline in the EU2 environment.
Coralogix reported a critical EU2 alerting pipeline degradation that could cause missing or delayed alerts. It started at 2026-04-14 06:21 UTC and was resolved at 2026-04-14 06:58 UTC, lasting 37 min. A fix was implemented, but no cause was disclosed.
Major incident