Linq incident

Degraded message sending and receiving

Resolved after 21 minutes, affecting Linq V3 API, on October 9, 2026.

resolved Oct 09, 2026, 10:58 PM UTC

the issue has been resolved on AWS end and we are working with AWS on root cause analysis

Started
Oct 09, 2026, 10:36 PM UTC
Resolved
Oct 09, 2026, 10:58 PM UTC
Duration
21m
Detected by Pingoru
Oct 09, 2026, 10:36 PM UTC

Affected components

Linq V3 API

Update timeline

  1. investigating Oct 09, 2026, 10:36 PM UTC

    Team is responding to reports of issues. Will post updates here.

  2. identified Oct 09, 2026, 10:44 PM UTC

    Partial recovery, still monitoring An issue with our infrastructure provider disrupted sending and receiving messages starting around 5:20 PM CT. We’ve seen significant recovery since then, but we’re not fully confident the issue is resolved. Our team is working on it and will post again soon.

  3. identified Oct 09, 2026, 10:50 PM UTC

    Messages are sending and receiving again, but latency is still well above normal. Delivery and webhooks may be slower while we work to fully recover. Our team is actively working on it and will post again soon.

  4. identified Oct 09, 2026, 10:57 PM UTC

    Latency has come down significantly. Our team continues to monitor closely and will post again once we confirm things are fully stable.

  5. resolved Oct 09, 2026, 10:58 PM UTC

    the issue has been resolved on AWS end and we are working with AWS on root cause analysis

Your product runs on more than Linq

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →