Iterable Outage History
19 incidents recorded over the last 365 days, 19 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Iterable Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 28, 2026 | Some customers using Sparkpost (US hosted) for email may be seeing delayed or slow sendsSparkpost is reporting that full functionality has been restored. All alerts in Iterable have resolved and we are no longer seeing customer impact. | 29 min | Resolved |
| Sep 22, 2026 | Timeouts on User Update API EndpointsAll API issues are now resolved and the user update endpoints are fully operational. If you continue to experience any issues, please contact Support. | 56 min | Resolved |
| Sep 10, 2026 | EU platform slowness and gateway errorsWe completed our monitoring and there are no further issues. The observed customer impact window was approximately 9:25 a.m.–11:13 a.m. EDT. | 2h 22m | Resolved |
| Sep 1, 2026 | Subset of customers using Twilio for SMS seeing a portion of messages getting dropppedTwilio has reported that the issue causing 5xx errors on their side has resolved and we have seen SMS sends return to normal. Customers using Twilio that saw sends get dropped should re-send those messages if they want… | 58 min | Resolved |
| Jul 24, 2026 | Email Send Delays with Partial Sparkpost outage on US-WEST-2.All Sparkpost sends that were previously delayed have been delivered and Sparkpost reports that their systems are now fully functional. If you continue to experience any issues please contact Support. | 2h 39m | Resolved |
| Jul 16, 2026 | Iterable Application Issues in US DatacenterThe issues with the Iterable application and API are now resolved and all sends and journeys that may have been delayed during the impact window have now been processed. Please reach out to Support if you continue to… | 39 min | Resolved |
| Jun 12, 2026 | WhatsApp Messaging Delays and FailuresThe issue affecting WhatsApp messaging has been resolved. Customers should no longer experience delays or failures sending WhatsApp messages. We will continue to monitor to ensure service remains stable. | 54 min | Resolved |
| May 12, 2026 | Iterable Web Application Outage - US and EU RegionsOur engineering team has completed the fix to the web application in both the US and EU regions. All services are currently functioning normally. Email sends, API traffic, webhooks, and journeys functioned normally… | 37 min | Resolved |
| Apr 16, 2026 | Journey pages are not respondingThis incident has been resolved. | 49 min | Resolved |
| Apr 14, 2026 | Elevated API Error Rates in US RegionThis incident has been resolved. | 2h 34m | Resolved |
| Mar 25, 2026 | Ingestion and processing delayThis incident has been resolved. | 22 min | Resolved |
| Mar 17, 2026 | Customers on c102 are experiencing degraded performanceWe have fully caught up with any backlog on C102 and all queries and activity through C102 are functioning normally. If you continue to experience any issues please contact Support. | 1h 13m | Resolved |
| Mar 16, 2026 | Proof Send Functionality DegradedThis incident has been resolved. | 2h 31m | Resolved |
| Feb 24, 2026 | Email send delays for some US-hosted SparkPost trafficSparkPost’s API issue has been resolved, and we’re no longer seeing elevated 5xx errors or increased latency. Incident has resolved. | 1 min | Resolved |
| Feb 24, 2026 | app.iterable.com was unavailable in the US region, returning 502 Bad Gateway errors to users.Service has fully recovered and all traffic has been restored to app.iterable.com in the US region. The incident lasted from 9:50 am to 10:15 am Pacific Time, impacting both web and API access with elevated 502, 503… | 11 min | Resolved |
| Feb 16, 2026 | Delayed sends from 7am to 9am ET (retro-active)We experienced a period of delayed sends (including proofs) as well as errors in user updates from 7am to 9am ET. The issue has been resolved. Some delayed messages may still be processing and will be sent shortly. If… | -215 min | Resolved |
| Jan 8, 2026 | Iterable web elevated error ratesThis incident has been resolved. | 1h 26m | Resolved |
| Jan 1, 2026 | API Update Timing OutThe engineering team determined that the issue has been resolved. | 21h 53m | Resolved |
| Nov 18, 2025 | Delayed Message SendsThis incident has been resolved. | 1h 52m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Iterable incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Iterable Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Iterable acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Iterable outage in this window ran 21h 53m, against a mean recovery of 2h 21m. If you depend on Iterable in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.