The engineering team identified the issues that caused the lag in one of our server clusters. There is no longer any lag time for this cluster and we are resolving this issue. Thank you for your patience and if you have any questions please reach out to your CSM or support@iterable.com.
Posted Jan 31, 2019 - 23:31 PST
Investigating
The team is still hard at work trying to determine a root cause for data ingestion delays - our recovery times are taking longer than originally expected. We've been able to add additional compute resources that are helping reduce lag times, and expect to see everything back to normal in about two hours. Engineers will continue to work on the issue and we will provide the next update before 6am Pacific Time.
Posted Jan 31, 2019 - 21:11 PST
Update
Our Engineering Team is continuing to work on speeding up ingestion for the server with degraded performance and have made good progress. We will continue to monitor the server as it begins to catch up. Next update at 9 PM PST.
Posted Jan 31, 2019 - 19:44 PST
Identified
We've identified the cause of data ingestion delays for the affected server cluster and we are taking steps to catch up on the backlog of events still awaiting processing. As of right now we're not sure how long until we're back to normal, but progress is being made. Next update by 5:45pm Pacific Time.
Posted Jan 31, 2019 - 16:43 PST
Investigating
One server cluster is experiencing delays ingesting new information. This is affecting several actions within Iterable. The engineering team believes this is due to high traffic and are currently working on a fix. This is not impacting all customers. Next update will be before 5 PM PST.
Posted Jan 31, 2019 - 16:00 PST
This incident affected: Global Analytics Processing.