Iterable Outage History

Iterable is up right now

There were 8 Iterable outages since February 16, 2026 totaling 7h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.iterable.com

Notice April 16, 2026

Journey pages are not responding

Detected by Pingoru
Apr 16, 2026, 10:09 AM UTC
Resolved
Apr 16, 2026, 10:59 AM UTC
Duration
49m
Timeline · 3 updates
  1. investigating Apr 16, 2026, 10:09 AM UTC

    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.

  2. monitoring Apr 16, 2026, 10:45 AM UTC

    Journey pages are loading normally following the fix. Engineering will continue monitoring.

  3. resolved Apr 16, 2026, 10:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 14, 2026

Elevated API Error Rates in US Region

Detected by Pingoru
Apr 14, 2026, 06:02 PM UTC
Resolved
Apr 14, 2026, 08:37 PM UTC
Duration
2h 34m
Affected: Global API SuccessGlobal API Ingestion
Timeline · 5 updates
  1. investigating Apr 14, 2026, 06:02 PM UTC

    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.

  2. monitoring Apr 14, 2026, 06:46 PM UTC

    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.

  3. monitoring Apr 14, 2026, 07:17 PM UTC

    Our engineering team is continuing to work on improving success rates for all API endpoints including Bulk Update. Next update in 60 minutes.

  4. monitoring Apr 14, 2026, 08:27 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Apr 14, 2026, 08:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 25, 2026

Ingestion and processing delay

Detected by Pingoru
Mar 25, 2026, 07:00 PM UTC
Resolved
Mar 25, 2026, 07:22 PM UTC
Duration
22m
Affected: Journey ProcessingJourney ProcessingJourney ProcessingUser UpdatesUser UpdatesUser UpdatesList UploadsList UploadsList Updates
Timeline · 3 updates
  1. investigating Mar 25, 2026, 07:00 PM UTC

    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 is occurring. If you are experiencing delayed data visibility or suspect missing updates, please contact our Support team so we can review your specific projects as part of this incident. Next update 1pm PT

  2. monitoring Mar 25, 2026, 07:17 PM UTC

    We have caught up with ingestion. Currently monitoring our systems.

  3. resolved Mar 25, 2026, 07:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 17, 2026

Customers on c102 are experiencing degraded performance

Detected by Pingoru
Mar 17, 2026, 06:07 PM UTC
Resolved
Mar 17, 2026, 07:21 PM UTC
Duration
1h 13m
Affected: Email SendsJourney ProcessingPush SendsSMS SendsUser UpdatesList UpdatesUser Deletions
Timeline · 4 updates
  1. investigating Mar 17, 2026, 06:07 PM UTC

    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.

  2. investigating Mar 17, 2026, 06:43 PM UTC

    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.

  3. monitoring Mar 17, 2026, 07:00 PM UTC

    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.

  4. resolved Mar 17, 2026, 07:21 PM UTC

    We 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.

Read the full incident report →

Minor March 16, 2026

Proof Send Functionality Degraded

Detected by Pingoru
Mar 16, 2026, 04:18 PM UTC
Resolved
Mar 16, 2026, 06:50 PM UTC
Duration
2h 31m
Affected: Global Proof Sends
Timeline · 3 updates
  1. investigating Mar 16, 2026, 04:18 PM UTC

    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.

  2. monitoring Mar 16, 2026, 05:09 PM UTC

    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.

  3. resolved Mar 16, 2026, 06:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 24, 2026

Email send delays for some US-hosted SparkPost traffic

Detected by Pingoru
Feb 24, 2026, 07:51 PM UTC
Resolved
Feb 24, 2026, 07:52 PM UTC
Duration
1m
Affected: Global Campaign Sends
Timeline · 2 updates
  1. monitoring Feb 24, 2026, 07:51 PM UTC

    Email sends for US-hosted customers using SparkPost were delayed due to elevated 5xx errors and increased API latency from SparkPost’s Transmissions API. EU-hosted traffic was not impacted. All customers using ESPs other than Sparkpost were similarly not impacted. SparkPost has indicated the incident is resolved. We’re monitoring outbound email queues to ensure sends are fully processing as expected. If you continue to experience issues, please contact Support.

  2. resolved Feb 24, 2026, 07:52 PM UTC

    SparkPost’s API issue has been resolved, and we’re no longer seeing elevated 5xx errors or increased latency. Incident has resolved.

Read the full incident report →

Major February 24, 2026

app.iterable.com was unavailable in the US region, returning 502 Bad Gateway errors to users.

Detected by Pingoru
Feb 24, 2026, 06:18 PM UTC
Resolved
Feb 24, 2026, 06:30 PM UTC
Duration
11m
Affected: Global Web Application
Timeline · 3 updates
  1. investigating Feb 24, 2026, 06:18 PM UTC

    We are currently investigating an issue where users could not access app.iterable.com and received 502 Bad Gateway errors. EU users were not affected.

  2. monitoring Feb 24, 2026, 06:21 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 24, 2026, 06:30 PM UTC

    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, and 504 errors. EU region was unaffected.

Read the full incident report →

Notice February 16, 2026

Delayed sends from 7am to 9am ET (retro-active)

Detected by Pingoru
Feb 16, 2026, 03:35 PM UTC
Resolved
Feb 16, 2026, 12:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 16, 2026, 03:35 PM UTC

    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 customers received 500 responses to API requests, they should re-try those calls.

Read the full incident report →

Looking to track Iterable downtime and outages?

Pingoru polls Iterable's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Iterable reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Iterable alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Iterable for free

5 free monitors · No credit card required