Skip to main content
Iterable

Mailgun has Degraded Performance

Degraded Lasted 46m · started · Iterable's page

Level
confirmed
Worst impact
Degraded
Down Index
17of 100

What to do

  • Check whether your product depends on Iterable. 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 46m it lasted.

    Anything that failed between 2025-05-19 21:42 UTC and 2025-05-19 22:28 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. investigating

    Mailgun is reporting degraded performance across their application https://status.mailgun.com/. We are monitoring mailgun and their performance.

    provider

  2. monitoring

    We are monitoring the affect of the mailgun degradation

    provider

  3. monitoring

    Mailgun has implemented a fix and is in Monitoring status

    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-99abfd7e41

Is Iterable still down?

No, this incident was resolved 2025-05-19 22:28 UTC. For Iterable's live state, see https://down.guide/iterable.

How long did it last?

46m, from 2025-05-19 21:42 UTC to 2025-05-19 22:28 UTC, by the times Iterable posted.

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.