Iterable Status

All Systems Operational

Web Application Operational

API Operational

Email Sending Operational

Email Links Operational

Workflows Operational

Push Sending Operational

SMS Sending Operational

System Webhooks Operational

Analytics Processing Operational

List Upload Operational

User Updates Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

System Metrics Month Week Day

Web App Latency

Fetching

Links API Success Rate

Fetching

Links Latency

Fetching

Message Sending API Success Rate

Fetching

Message Sending API Latency

Fetching

User Update and Track API Latency

Fetching

Past Incidents

Feb 21, 2019

No incidents reported today.

Feb 20, 2019

No incidents reported.

Feb 19, 2019

No incidents reported.

Feb 18, 2019

No incidents reported.

Feb 17, 2019

Data ingestion delays

Resolved - There is no longer any lag for ingestion and we are resolving the issue. Please reach out to your CSM or support@iterable.com if you have questions.
Feb 17, 06:26 UTC

Update - We are still seeing data ingestion delays for some customers. We have identified the source of the problem and made configuration changes to the system to allow it to catch up. Next update will be at 10:30 PM.
Feb 17, 05:25 UTC

Identified - We're seeing further delays with data ingestion for a subset of customers. Currently, affected customers are seeing upwards of a 90-minute lag between submitting new data and it being ingested. That lag is decreasing but may take some time to fully-resolve. Our engineering team is currently working on reducing the lag further. Next update before 9:30pm Pacific Time.
Feb 17, 03:54 UTC

Feb 16, 2019

Data ingestion delays

Resolved - There is no lag for any ingestion services anymore and we are resolving this issue. Please reach out to your CSM or support@iterable.com if you have questions.
Feb 16, 18:28 UTC

Update - Ingestion services have worked through most of the backlog overnight but there still remains a lag for a small amount of customers. We will continue to monitor and when are confident there is no lag we will update this incident to resolved.
Feb 16, 16:44 UTC

Update - No major updates as our ingestion service continues to work its way through the backlog of events. We expect to see everything return to normal overnight and will provide an update tomorrow morning.
Feb 16, 05:26 UTC

Identified - Data ingestion is continuing to improve, and configuration changes are starting to take effect. This should allow the rate of ingestion to increase. Next update: 8:30pm Pacific Time.
Feb 16, 02:31 UTC

Update - We're still seeing data ingestion delays for some customers. The engineering team is continuing to work on configuration changes to allow our systems to catch up. Bulk updates continue to be more impacted than non-bulk, and we're seeing some improvement in most cases. Next update: 6:30pm Pacific Time
Feb 16, 01:32 UTC

Investigating - We are seeing some lag with data ingestion for a subset of customers. This incident is similar to the incident yesterday morning. Our engineering team is working on identifying the root cause and determining the best path for remediation. This lag is most likely to affect bulk uploads, but may also impact other data ingestion endpoints too. Next update by 5:30pm Pacific Time.
Feb 16, 00:28 UTC

Feb 15, 2019

No incidents reported.

Feb 14, 2019

Data Ingestion Slow For Some Customers

Resolved - All clusters have caught up from the backlog. We are moving this incident to resolved. If you have any questions please reach out to your CSM or support@iterable.com.
Feb 14, 19:39 UTC

Monitoring - The one remaining cluster continues to improve. We are moving this incident to monitoring and when we are confident that all clusters are fully functional we will resolve this incident. Next update will be at 12:30 PST or sooner.
Feb 14, 18:34 UTC

Update - One of our server clusters has caught up from the backlog this morning and is not experiencing any lag. There is one remaining cluster with a backlog, but it is making steady progress toward recovery. When that cluster has no lag we will change this incident to monitoring. Next update will be at 10:30 AM PDT if not sooner.
Feb 14, 17:35 UTC

Update - Improvement continues to be made by our engineering team. Lag is limited to bulk updates and list uploads only. Both areas are slowly recovering. Next update will be at 09:30 AM PDT
Feb 14, 16:33 UTC

Update - Engineering is continuing to work on the issue as lag time continues to improve. We will continue monitoring and the next update will be at 08:30 AM PDT
Feb 14, 15:32 UTC

Identified - The cause has been identified and a fix is being worked on by our engineering team. The next update will be at 07:30 AM PDT
Feb 14, 14:17 UTC

Investigating - Currently some of our customers are experiencing slow data ingestion, with delays up to 90 minutes right now due to issues with a particular server cluster. We are starting to see the delay reduce however. Next update by 6:30am Pacific Time.
Feb 14, 13:35 UTC

Feb 13, 2019

No incidents reported.

Feb 12, 2019

No incidents reported.

Feb 11, 2019

No incidents reported.

Feb 10, 2019

No incidents reported.

Feb 9, 2019

No incidents reported.

Feb 8, 2019

No incidents reported.

Feb 7, 2019

No incidents reported.