Skip to main content
Iterable

Sends Outage/Delays Across all Mediums

Degraded Lasted 0m · started · Iterable's page

Level
confirmed
Worst impact
Degraded
Regions
us
Down Index
12of 100

What to do

  • Check whether you use Iterable 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 0m it lasted.

    Anything that failed between 2025-06-06 04:15 UTC and 2025-06-06 04:15 UTC may need a replay.
  • Subscribe to Iterable's feed to hear about the next one first. RSS feed

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

Updates from Iterable 1

  1. resolved

    US Data Center Sends Cluster Outage Summary: Between 12:14 AM and 12:55 AM EDT, our US Data Center's sends cluster experienced a critical outage, effectively preventing message delivery. All publishes during this period were safely backed up to our secondary queues. Resolution: We initiated recovery efforts at 12:55 AM EDT, working through the accumulated backlog of unsent messages. During this time, sends were delayed but actively processing. By approximately 1:48 AM EDT, the backlog was cleared, and the sends cluster in the US Data Center was fully recovered. Current Status: We are fully recovered and do not anticipate any further issues related to this incident. All messages are now being sent without delay.

    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-ed20ac5a0b

Is Iterable still down?

No, this incident was resolved 2025-06-06 04:15 UTC. For Iterable's live state, see https://down.guide/iterable.

How long did it last?

0m, from 2025-06-06 04:15 UTC to 2025-06-06 04:15 UTC, by the times Iterable posted.

What was affected?

Iterable named in us.

What caused it?

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

Where does this come from?

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