Iterable logo

Is Iterable Down?

MarketingLive status, outages, and incident history

No. Iterable is up right now.

Every monitored Iterable system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · 60s while moving

Know the moment Iterable breaks

Iterable is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

Official Iterable status page
How we know: the official Iterable status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Iterable Component Status

The main Iterable systems on this page. All 488 are operational right now.

488operational
Cluster 10 » Email Sends
Operational
Cluster 10 » Journey Processing
Operational
Cluster 10 » List Uploads
Operational

485 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Cluster 10 » Push Sends, Cluster 10 » SMS Sends, Cluster 10 » User Deletions, Cluster 10 » User Updates, Cluster 100 » Email Sends, Cluster 100 » Journey Processing, Cluster 100 » List Updates, Cluster 100 » Push Sends, Cluster 100 » SMS Sends, Cluster 100 » User Deletions, Cluster 100 » User Updates, Cluster 101 » Email Sends, and 473 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Iterable Outages & Incidents

Incident history from the official Iterable status page, including resolution updates.

Timeouts on User Update API EndpointsResolved Sep 22, 2026 · 56 minResolved

All API issues are now resolved and the user update endpoints are fully operational. If you continue to experience any issues, please contact Support. --- [2026-09-22T12:14:21.327-07:00] (monitoring) 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. --- [2026-09-22T12:15:31.232-07:00] (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

EU platform slowness and gateway errorsResolved Sep 10, 2026 · 2h 22mResolved

We 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. --- [2026-09-10T09:09:44.399-07:00] (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. --- [2026-09-10T07:54:40.184-07:00] (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 dropppedResolved Sep 1, 2026 · 58 minResolved

Twilio 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 to. No further updates will be posted. --- [2026-09-01T10:19:19.781-07:00] (identified) 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

Iterable Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Iterable incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 3 days with incidentsSep 25

Live Iterable Outage Reports

Problems reported by engineers using Iterable. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Iterable problems reported yet.

Something wrong with Iterable on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Iterable

Iterable publishes a public status page at status.iterable.com covering 200 components, including Global Web Application, Email Sends and Emails Sends. PulsAPI tracks Iterable outages, degraded performance and incident history in real time, alongside the rest of your marketing stack.

Over the past 30 days, PulsAPI has measured Iterable uptime at 100.00%. Response times, incident history, and SLA tracking for Iterable are available on the PulsAPI dashboard.

Iterable Status FAQ

Is Iterable down right now?

The verdict at the top of this page comes from the latest poll of the official Iterable status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Iterable is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Iterable recovers.

How do I check Iterable uptime history?

PulsAPI tracks Iterable uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Iterable changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Iterable outages?

PulsAPI reads the official Iterable status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Iterable components?

Yes. PulsAPI monitors 488 individual Iterable components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Iterable goes down?

Yes. Create a free account and subscribe to Iterable: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Iterable to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Iterable problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Iterable?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Iterable plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Iterable with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services