Event ingestion delays

Incident Report for Iterable

Resolved

Everything still looks good and events are continuing to be ingested with no lag, so this issue is now resolved. Thanks for your patience if you were impacted this afternoon. As always, please reach out to support@iterable.com if you experience any issues.

Posted Jan 17, 2019 - 20:12 PST

Monitoring

Both server clusters are now fully-caught up, and there should be no lag with ingesting any events.

Posted Jan 17, 2019 - 19:02 PST

Investigating

Two server clusters are experiencing delays ingesting event data. This means that workflows may process using old data, or may be delayed in processing. As a result outbound messages may be delayed. Our engineers are close to identifying the root cause. This is not impacting all customers, but those that are impacted will see a lag of between 20 and 45 minutes. Next update by 6:30pm Pacific.

Posted Jan 17, 2019 - 17:30 PST

This incident affected: Global API Success.