- Level
- confirmed
- Worst impact
- Operational
- Components
- Ingestion - Logs (Archive)
- Regions
- us
What to do
Check whether you use Coralogix Ingestion - Logs (Archive) in us. 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-06-22 17:26 UTC and 2026-06-22 17:41 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
- identified
Our team is currently investigating an issue with logs ingestion in the EU2 region. We are working actively to resolve this matter. Should you require further assistance or have any questions, please reach out via chat or email us at support@coralogix.com.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
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-a4ded13b6b
Is Coralogix still down?
No, this incident was resolved 2026-06-22 17:41 UTC. For Coralogix's live state, see https://down.guide/coralogix.
How long did it last?
15m, from 2026-06-22 17:26 UTC to 2026-06-22 17:41 UTC, by the times Coralogix posted.
What was affected?
Coralogix named Ingestion - Logs (Archive) in us.
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.