Linq incident

Reported Apple service disruption affecting Linq

Resolved after 55 minutes, affecting Linq V3 API and Linq V2 API, on November 11, 2026.

resolved Nov 11, 2026, 02:46 AM UTC

We’ve confirmed Contact Card errors and message send timeouts have returned to normal levels, and Linq V2 API and Linq V3 API are operating normally.

Started
Nov 11, 2026, 12:28 AM UTC
Resolved
Nov 11, 2026, 01:23 AM UTC
Duration
55m
Detected by Pingoru
Nov 11, 2026, 12:28 AM UTC

Affected components

Linq V3 APILinq V2 API

Update timeline

  1. investigating Nov 11, 2026, 12:28 AM UTC

    Apple is reporting, disruptions currently impacting multiple Apple services (including iCloud and Sign in with Apple). We’re working to confirm what Linq features are affected and the scope of impact.

  2. identified Nov 11, 2026, 12:50 AM UTC

    Contact cards continue to experience increased errors and intermittent delays alongside the reported Apple service disruption. We have also observed iMessage sending failures affecting some customers and a recent increase in message send timeouts. Chat creation, sending, typing indicators, and read receipts otherwise appear to be operating at normal levels at the API layer.

  3. monitoring Nov 11, 2026, 01:23 AM UTC

    Apple is now reporting these issues as resolved on their status page (iCloud Account & Sign In ended at 18:22 CST and Find My ended at 18:54 CST). We’re continuing to monitor Contact Card errors and message send timeouts and are ensuring lines are fully recovering.

  4. resolved Nov 11, 2026, 02:46 AM UTC

    We’ve confirmed Contact Card errors and message send timeouts have returned to normal levels, and Linq V2 API and Linq V3 API are operating normally.

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 →