Delays impacting contact segmentation

The refresh status of segments is now fully lined up with reality.

All shards are now caught up.

Another shard has now recovered. 2 of 16 remain lagged. The issue affecting delayed refresh status is also mostly recovered.

One shard has now recovered. 3 of 16 remain lagged.

4 of 16 shards are again experiencing processing delays.

We are now investigating some segments being suck in a refreshing state, even though the refresh has actually fully completed.

All shards caught up overnight. We are now investigating delays in processing scheduled segment-contact re-evaluation affecting a small number of records this morning.

Another shard is now fully recovered. 2 of 16 shards remain impacted. We expect this to clear in the next few hours. We will next post an update early tomorrow morning.

One of the four affected shards has now recovered. 3 of 16 remain affected by this issue.

To clarify, real-time processing of contacts in existing segments is not impacted, and is functioning as normal. This issue only affects 4 of the 16 segment refresh processing shards. Another update will be posted within the next 2 hours.

We're experiencing processing backlogs on 4 of our 16 segmentation shards. Each customer gets allocated to 4 shards, and each segment allocated to one of these 4 shards for processing. Any segment that lives in one of the backlogged shards will experience processing delays exceeding 1 hour.