Skip to main content
Coralogix

Cases creation delay US1

Degraded Lasted 1h 16m · started · Coralogix's page

Level
confirmed
Worst impact
Degraded
Regions
us

What to do

  • Check whether you use Coralogix 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 1h 16m it lasted.

    Anything that failed between 2026-05-07 21:47 UTC and 2026-05-07 23:03 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 4

  1. investigating

    Our team is investigating a delay in case creation in the us1 region (team.coralogix.us). For assistance or more questions, please contact us via chat or email support@coralogix.com.

    provider

  2. identified

    The issue has been identified and a fix is being implemented.

    provider

  3. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  4. 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-67b172634a

Is Coralogix still down?

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

How long did it last?

1h 16m, from 2026-05-07 21:47 UTC to 2026-05-07 23:03 UTC, by the times Coralogix posted.

What was affected?

Coralogix named 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.