Changes / Coralogix / Log Query failures across EU1 region
Coralogix: Major incident: Log Query failures across EU1 region
Summary
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.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
Incident page: full timeline of updates →
What changed
Before: not present
After: Log Query failures across EU1 region
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-08-05 08:46 UTC
Before: not present
After: 2026-08-05 09:01 UTC
Before: not present
After: EU1 - Processing - Logs, EU1 - UI - Explore, Processing - Logs, UI - Explore, US1 - Processing - Logs, US1 - UI - Explore
Before: not present
After: We experienced a brief period of log query failures affecting Explore → Logs (both v2 and Legacy) in the EU1 and US1 regions.
During this time, some customers may have encountered errors when running log queries or accessing archived log data.
Our engineering team was actively engaged and at this time, the platform is operating normally.
We will continue to monitor the situation to ensure stability. We apologize for the inconvenience and appreciate your patience.
Before: not present
After: We are continuing to monitor for any further issues.
Before: not present
After: All services are currently up and running. We can confirm that the issue was affecting only EU1 region.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When | Change | Kind |
|---|---|---|
| Major incident: Log Query failures across EU1 region (this change) 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 |
All Coralogix changes → · Coralogix profile · Markdown · JSON