Looking for an update now? Check the current status, or follow Iterable for future changes.
94.7%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
90%
30
3
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
We are continuing to investigate the issue but are seeing positive signs of recovery. API endpoints for user updates are back to normal success rates. Next update at 3:45 PM EDT or sooner.
investigating
We are currently investigating an issue leading to slowness and timeouts across all API user update endpoints beginning at 2:45 PM EDT. Next update at 3:15 PM EDT
Global Web ApplicationGlobal API SuccessGlobal Journey Processing
monitoring
The intermittent platform issues have been mitigated and there is currently no ongoing customer impact. The observed customer impact window was approximately 9:25 a.m.–11:13 a.m. EDT. We will continue to monitor the issue.
investigating
We're currently investigating an issue for EU customers with platform slowness, intermittent 502/503 Gateway errors, and Journey changes failing to save
Subset of customers using Twilio for SMS seeing a portion of messages getting droppped
A subset of customers using Twilio for SMS sending may have some messages getting dropped due to an incident on Twilio’s side with impact currently ranging from 5%-20%. We are actively monitoring the impact and status updates from Twilio.
There is not impact to customers using any other SMS providers.
Next update: by 11:30am PT
Legacy Incident Archive
9 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
Email Send Delays with Partial Sparkpost outage on US-WEST-2.
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor Sparkpost outage as they work to continue draining the backlog of delayed messages.
Sparkpost estimates that they expect to have most email delivered within the next 30-45 minutes.
monitoring
We are continuing to monitor Sparkpost outage as they work to continue draining the backlog of delayed messages.
monitoring
We are currently experiencing email delivery delays due to a partial outage affecting SparkPost's US-West-2 region. Emails continue to be accepted and queued, but delivery is delayed. Our team is working closely with SparkPost to resolve this issue. We will provide updates as more information becomes available. Next update in 15m.
investigating
Email sends delayed for US-hosted customers using SparkPost in US-WEST-2 region.
Iterable Application Issues in US Datacenter
criticalSource not attested
Last archived state: resolved
View archived record details
identified
We are continuing to work on a fix for this issue.
identified
Iterable engineering has identified the issue and is currently deployed a fix across the US environment. We are starting to see successful logins on the Iterable application.
investigating
We are currently investigating an issue impacting the main Iterable application in the US region.
June 2026
WhatsApp Messaging Delays and Failures
Source not attested
Last archived state: resolved
View archived record details
identified
We are aware of an issue affecting WhatsApp messaging. Some customers may experience delays or failures sending WhatsApp messages. This appears to be caused by an external service disruption, and we are monitoring for updates. We will share another update by 1pm PST or sooner if new information becomes available.
May 2026
Iterable Web Application Outage - US and EU Regions
criticalSource not attested
Last archived state: resolved
View archived record details
identified
Our engineering team is continuing to work toward a full resolution. While we have mostly restored web application access, there may be some pages within the web app that periodically fail to load until the fix is fully rolled out across the entire application. Next update by 5:30PM PDT or sooner.
investigating
Engineering has identified a fix and is in the process of deploying to both EU and US web environments to resolve the issue. Next update at 5PM PDT or sooner.
investigating
We are currently investigating an issue involving users being unable to access the Iterable web app. API traffic, Sends, and Journeys already in progress are unaffected. This outage is limited to the Iterable web application itself.
April 2026
Journey pages are not responding
Source not attested
Last archived state: resolved
View archived record details
investigating
We’re currently investigating an issue where Journey pages are not responding. Engineering is actively applying a fix and will continue investigating the root cause. Next update at 4:00 PM PST / 11:00 PM GMT.
Elevated API Error Rates in US Region
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our engineering team is continuing to work on improving success rates for all API endpoints including Bulk Update. Next update in 60 minutes.
monitoring
We are seeing improved success rates on the Register Device and Target endpoints. Our engineering team is continuing to work on other endpoints including Bulk Update. Next update within 30 minutes.
investigating
We are currently experiencing elevated error rates on several API endpoints in our US region, including Bulk Update, Register Device, and Target. We are actively working to resolve this issue and will provide another update within 30 minutes.
March 2026
Ingestion and processing delay
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have caught up with ingestion. Currently monitoring our systems.
investigating
Current status
We have identified an issue in our ingestion service that can cause some updates to be delayed.
Customer impact
Some customers are seeing delays in list uploads and events appearing in Iterable, in some cases taking 30+ minutes to render.
Clusters impacted 22,25,16
Rolled back to a previous stable version across all affected clusters and verified the deployments. We are monitoring ingestion lag and key metrics to confirm performance is stabilizing and that no new update loss ...
Customers on c102 are experiencing degraded performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Engineering has restored C102 back to a "green" state and ingestion and API calls are succeeding again for this cluster. We will continue to monitor until we are fully through the accumulated backlog. Next update at 1 PM PDT or sooner.
investigating
Engineering is continuing to investigate this issue. At this time there is no improvement yet to any customers on C102. Next Update at 12:15 PDT or sooner.
investigating
We are currently investigating an issue for one of ES clusters - c102 - The cluster is in a red state, leading to very slow ingestion and widespread API 500 errors.
Customers are experiencing failed searches and errors on multiple API endpoints. Ingestion rates are near zero, with lag up to 20 minutes and increasing for internal, realtime, and bulk data pipelines.
Proof Send Functionality Degraded
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The engineering team has implemented a fix and proofs are now successfully sending. We will continue to monitor. Next update at 12:00 PST or earlier.
investigating
We have been alerted to an issue where proofs sends are not being sent as expected as of 9:00 am PT. Iterable Engineers are actively investigating the issue. Next update by 11:00 am PT or sooner.
