Delayed Message Sends

What to do

• Check whether you use Iterable Global System Webhooks, Global Campaign Sends, Global Proof Sends, Global Journey Processing. 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 52m it lasted.

  Anything that failed between 2025-11-18 14:46 UTC and 2025-11-18 16:38 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 4

1. identifiedNov 18, 2025, 2:46 PM UTC

   We are currently experiencing delays in processing certain message sends and exit-trigger workflows. This is due to an upstream outage affecting some of our backend components that handle message publishing.

   provider

2. monitoringNov 18, 2025, 2:57 PM UTC

   Upstream issue has been resolved. we will continue monitoring.

   provider

3. monitoringNov 18, 2025, 3:36 PM UTC

   All processing is back to normal. We continue to monitor.

   provider

4. resolvedNov 18, 2025, 4:38 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

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