We've deployed updates to our internal block(s) state machine(s) which suffered from high latencies in the case where flows contained large (> 100k) numbers of cycles within them.

We've also rolled back any load balancer policies related to this incident.

At 11:40 AM, we started proactively rolling out a more protective load balancer policy to isolate the requests which were triggering latency spikes, and have not observed any latency spikes since then.

We've identified a set of mitigations and are planning a load balancer policy change.