Skip to main content
Iterable

Journeys are having issues fetching, creating and saving journeys.

Partial outage Lasted 8h 38m · started · Iterable's page

Level
confirmed
Worst impact
Partial outage
Components
Global Web Application
Down Index
32of 100

What to do

  • Check whether you use Iterable Global Web Application. 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 8h 38m it lasted.

    Anything that failed between 2025-03-07 09:57 UTC and 2025-03-07 18:35 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 3

  1. investigating

    We are currently investigating an issue affecting Journeys where fetching, creation and saving of journeys is not working correctly. Customers may experience delays or unexpected behavior when using Journeys. Our Engineering team is actively working to identify the root cause. We will provide the next update in 60 minutes or sooner if more information becomes available.

    provider

  2. monitoring

    A fix has been deployed and journey function is operating normally. Moving to monitoring state.

    provider

  3. resolved

    We do not see any more errors in journey edits.

    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-9a862ed6e8

Is Iterable still down?

No, this incident was resolved 2025-03-07 18:35 UTC. For Iterable's live state, see https://down.guide/iterable.

How long did it last?

8h 38m, from 2025-03-07 09:57 UTC to 2025-03-07 18:35 UTC, by the times Iterable posted.

What was affected?

Iterable named Global Web Application.

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.