Skip to main content
Iterable

Resolved: api-hightraffic Errors in Europe

Degraded Lasted 0m · started · Iterable's page

Level
confirmed
Worst impact
Degraded
Components
Global API Success
Regions
eu

What to do

  • Check whether you use Iterable Global API Success in eu. 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-09-11 16:37 UTC and 2025-09-11 16:37 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

    Status: Resolved Between 3:50 pm and 5:55 pm CEST customers in our EUDC (European Data Center) region may have experienced an increased 5xx error rate, approximately 10-15%, when making api requests. This issue was isolated to Europe; no impact was observed in other regions. If customers have any questions if they were impacted please reach out to support@iterable.com

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

Is Iterable still down?

No, this incident was resolved 2025-09-11 16:37 UTC. For Iterable's live state, see https://down.guide/iterable.

How long did it last?

0m, from 2025-09-11 16:37 UTC to 2025-09-11 16:37 UTC, by the times Iterable posted.

What was affected?

Iterable named Global API Success in eu.

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.