Maintenance has completed

At approximately 4:38 AM CT, the affected lines came back online and service has been restored. We are marking this incident as resolved. Thank you for your patience.

Maintenance has completed

We had a blip in networking at one data center causing some messages to delay or fail. It has recovered and lines are responding as they should.

This was from ~10:32 - 10:43a ET

We are marking this incident as resolved after having observed the system changes for approximately 24hrs and having been stable since. Our team is continuing to implement long term improvements and solutions to further remediate and improve on this. Thank you all for your patience.

We have implemented a fix and latencies are back within normal ranges.

We have resolved the issues with the API. We're continuing to monitor for further issues.

The incident is over and Linq is operating normal again.

We're continuing to monitor the issue, but it appears there was approx 5m of delayed/degraded messaging through our application. It has recovered now and is operating as expected.

The times were 1:04p to 1:09p CST

Maintenance has concluded

We have finished implementing some mitigation measures. The message latency has normalized.

This incident has been resolved. Inbound message delivery and outbound message timeouts have returned to normal, and all systems are operating as expected. Thank you for your patience.

Post-mortem

Impact window: ~10:08 AM – 12:30 PM CT, May 31, 2026

Summary: Starting around 10:08 AM CT, some customers experienced delays and failures when sending messages and receiving inbound message events, along with elevated timeouts or 5xx API responses. Message sending and inbound delivery were restored by ~11:25 AM CT; we declared full resolution at ~12:30 PM CT after confirming stability.

Cause: A component in our message-processing pipeline became overloaded during a peak in traffic and stopped processing correctly, interrupting message delivery for a subset of traffic.

Resolution: We rebalanced and restored the affected component, then verified end-to-end recovery. The platform is fully operational.