Iterable Outage History

Iterable experienced a 38-minute web application outage affecting both US and EU regions, preventing users from logging into the web app and causing slow page loads. API traffic, email sends, webhooks, and journeys continued to function normally throughout the incident. The engineering team identified and deployed a fix, fully restoring web application access across both regions.

Iterable experienced an issue where Journey pages became unresponsive for 52 minutes. Engineering applied a fix that restored normal loading functionality for the affected pages. The incident was resolved and the service returned to normal operation.

Iterable experienced elevated error rates on several API endpoints in the US region, including Bulk Update, Register Device, and Target endpoints. The incident affected API functionality for 2.6 hours while the engineering team worked to restore normal service levels. The issue was resolved with improved success rates gradually restored across all affected endpoints.

Iterable's ingestion service experienced an issue that caused delays in list uploads and events appearing in the platform, with some customers experiencing delays of 30+ minutes across clusters 22, 25, and 16. The engineering team resolved the incident by rolling back to a previous stable version across all affected clusters and verified the deployments were successful. The incident lasted 25 minutes and was fully resolved after the team confirmed ingestion had caught up and systems were stable.

Iterable's c102 Elasticsearch cluster went into a red state, causing widespread API 500 errors, failed searches, and near-zero data ingestion rates with up to 20-minute delays across multiple pipelines. Customers experienced failures across multiple API endpoints and search functionality. Engineering restored the cluster to green state and cleared all backlogs within 1.3 hours, returning all services to normal operation.

Iterable's proof send functionality was degraded starting at 9:00 AM PT, preventing proof emails from being sent as expected. The engineering team implemented a fix within approximately 1 hour, restoring proof sending functionality. The incident was fully resolved after 2.6 hours of monitoring to ensure stability.

Email sends for US-hosted Iterable customers using SparkPost experienced delays due to elevated 5xx errors and increased API latency from SparkPost's Transmissions API. EU-hosted customers were not affected by this issue. The incident was resolved after 5 minutes when SparkPost fixed their API issues, restoring normal email processing.

Iterable's app.iterable.com experienced a major outage in the US region from 9:50 am to 10:15 am Pacific Time, causing users to receive 502 Bad Gateway errors when trying to access both the web application and API. The EU region remained unaffected throughout the incident. The service was fully restored after 14 minutes once a fix was implemented and traffic was restored to the US region.