Linq incident

Linq Blue API - Increased Latency

Resolved after 21 minutes, affecting Linq Blue API, on March 11, 2026.

investigating Mar 11, 2026, 03:45 AM UTC

Update: Latency on the v3 API has returned to normal. We are still monitoring v3 error rates, but latency is back to expected levels. The v2 API is still experiencing the same elevated latency (~10+ minutes). Our team continues to work on resolving this. We will provide further updates as the situation progresses.

Started
Mar 11, 2026, 03:36 AM UTC
Resolved
Mar 11, 2026, 03:57 AM UTC
Duration
21m
Detected by Pingoru
Mar 11, 2026, 03:36 AM UTC

Affected components

Linq Blue API

Update timeline

  1. investigating Mar 11, 2026, 03:36 AM UTC

    The Linq Blue API is currently experiencing increased above average latency. Our team is actively investigating and working to resolve the issue. We will provide updates as more information becomes available.

  2. investigating Mar 11, 2026, 03:41 AM UTC

    Update: We are currently seeing approximately a few minutes of latency on the v3 API and a little over 10 minutes of latency on the v2 API. We understand this may be causing some confusion and we appreciate your patience. Our team is actively working to bring latency back to normal levels. If you are experiencing issues, please note that requests are still being processed, just with the delays noted above.

  3. investigating Mar 11, 2026, 03:45 AM UTC

    Update: Latency on the v3 API has returned to normal. We are still monitoring v3 error rates, but latency is back to expected levels. The v2 API is still experiencing the same elevated latency (~10+ minutes). Our team continues to work on resolving this. We will provide further updates as the situation progresses.

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 →