Skip to main content
Coralogix

Log Query failures across EU1 region

Partial outage Lasted 15m · started · Coralogix's page

Level
confirmed
Worst impact
Partial outage
Components
Processing - Logs, Processing - Logs, UI - Explore, UI - Explore

What to do

  • Check whether you use Coralogix Processing - Logs, Processing - Logs, UI - Explore, UI - Explore. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 15m it lasted.

    Anything that failed between 2026-08-05 08:46 UTC and 2026-08-05 09:01 UTC may need a replay.
  • Subscribe to Coralogix's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=coralogix works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Coralogix 3

  1. monitoring

    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.

    provider

  2. monitoring

    We are continuing to monitor for any further issues.

    provider

  3. resolved

    All services are currently up and running. We can confirm that the issue was affecting only EU1 region.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-9574cd2d53

Is Coralogix still down?

No, this incident was resolved 2026-08-05 09:01 UTC. For Coralogix's live state, see https://down.guide/coralogix.

How long did it last?

15m, from 2026-08-05 08:46 UTC to 2026-08-05 09:01 UTC, by the times Coralogix posted.

What was affected?

Coralogix named Processing - Logs, Processing - Logs, UI - Explore, UI - Explore.

What caused it?

Coralogix hasn't published a root cause. If it does, it shows here.

Where does this come from?

Coralogix's official status page, https://status.coralogix.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.