Coralogix Outage History

Coralogix experienced lag issues with their LiveTail feature in the US2 region, causing a processing backlog that affected real-time log streaming capabilities. The engineering team actively investigated and resolved the issue within 8 minutes.

Coralogix's Real User Monitoring (RUM) feature experienced a UI issue across all major regions (EU1, EU2, US1, US2, AP1, AP3), causing users to encounter blank pages when accessing the RUM section. The engineering team identified and implemented a fix, restoring functionality first to EU1, EU2, AP1, and AP3 regions, followed by the remaining US1 and US2 regions. The incident was fully resolved after 36 minutes of downtime.

Coralogix experienced login issues affecting customers in the EU1, EU2, and US2 regions where users would see the login page when refreshing despite being logged in. The incident impacted a subset of customers across these three regions for 20 minutes. The issue was resolved after implementing a fix and monitoring the results.

Coralogix experienced a major issue affecting the alerting pipeline in the EU2 environment, causing customers to experience missing or delayed alerts. The engineering team identified the root cause and implemented a fix within 41 minutes, restoring normal alert delivery.

Coralogix experienced an issue with querying All Logs in the AP2 region, while Frequent Search functionality remained operational. The engineering team identified and implemented a fix within 18 minutes, fully resolving the incident.

Coralogix experienced an 18-minute service interruption affecting metrics ingestion from Azure integrations across all environments. The issue impacted some customers' ability to receive Azure metrics data into the Coralogix platform. The problem was identified and resolved with a fix implementation, and any affected data is expected to be backfilled.

A frontend error in Coralogix's Cases page caused users to encounter blank pages when trying to open events across all regions for 1.1 hours. The issue was limited to the user interface and did not impact underlying data or system functionality. The engineering team identified and implemented a fix, resolving the incident after monitoring the results.