The ingestion delay has fully caught up and there are no further delays. Thank you for your patience as we worked through this today. If you have any questions or concerns please contact us at support@iterable.com.
Posted Sep 03, 2020 - 17:05 PDT
Update
The majority of ingestion delay has recovered, and list uploads and bulk updates are also catching up steadily. Our team will continue to monitor the progress. Next update by 5pm PDT.
Posted Sep 03, 2020 - 14:10 PDT
Update
Our engineering team has identified the underlying issue for the ingestion delay and put in the fix to mitigate it. We will continue to monitor the recovery process. Next update at 2pm PDT.
Posted Sep 03, 2020 - 13:03 PDT
Update
Our engineering team is continuing to work on a fix for the current ingestion delays. A subset of customers are still impacted. No data is being dropped, only delayed. We will continue working on improving ingestion rates and monitoring the situation. Next update at 1 pm PDT
Posted Sep 03, 2020 - 11:36 PDT
Update
Ingestion delays are still present for a subset of customers. Our system continues to process through the backlog of data. The engineering team is actively monitoring the situation. Next update at 14:30 EST/11:30 PST.
Posted Sep 03, 2020 - 09:44 PDT
Update
Our engineering team is continuing to make progress on fixing the underlying issue to help reduce the current ingestion lag. Next update at 12.30pm EST/09:30am PDT.
Posted Sep 03, 2020 - 08:39 PDT
Update
Our engineering team is continuing to make progress on fixing the underlying issue to help reduce the current ingestion lag. Next update at 4.30pm BST/11.30am EST.
Posted Sep 03, 2020 - 07:43 PDT
Update
Our engineering team is continuing to make progress on fixing the underlying issue to help reduce the current ingestion lag. Next update at 3.30pm BST.
Posted Sep 03, 2020 - 06:33 PDT
Identified
A small subset of our customers may be experiencing delays for user updates, list uploads, and event track API calls. Our engineering teams have identified the underlying cause and are working on a fix. No data is being lost, only delayed. Next update at 2.30pm BST.