Linq Outage History

Linq is up right now

Pingoru has recorded 34 incidents for Linq: 34 in the last 12 months and 7 in the last 90 days.

Source: status.linqapp.com

34incidents recorded
34last 12 months
7last 90 days
5 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOctNov3
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov1%
Pingoru began tracking Linq in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20261380 of 720 (11%)
May 2026611 of 744 (1%)
June 2026016 of 720 (2%)
July 202600 of 744 (0%)
August 202612 of 744 (0%)
September 202621 of 720 (0%)
October 202621 of 744 (0%)
November 202634 of 430 (1%)

Linq reliability, month by month

In the last 12 months, Linq posted 34 incidents on its official status page. Since Pingoru began tracking it in April 2026, at least one incident was open 2% of the time. Half of the incidents with a known end in the last 12 months were over within 28 minutes; the longest, "Some Linq Lines in Degraded State" on April 10, 2026, lasted 3 days 1 hour. The components affected most often were Linq V3 API (7 incidents) and Linq V2 API (1).

  • November 2026 (so far): 3 incidents, an incident was open less than 1% of the time, the longest lasted 55 minutes.
  • October 2026: 2 incidents, an incident was open less than 1% of the time, the longest lasted 2 hours 47 minutes.
  • September 2026: 2 incidents, an incident was open less than 1% of the time, the longest lasted 44 minutes.
  • August 2026: 1 incident, an incident was open less than 1% of the time, the longest lasted 1 hour 47 minutes.
  • July 2026: no incidents.
  • June 2026: no new incidents; one that began earlier was open 2% of the time.
  • May 2026: 6 incidents, an incident was open 1% of the time, the longest lasted 1 day.
  • April 2026 (tracking began this month): 13 incidents, an incident was open 11% of the time, the longest lasted 3 days 1 hour.

Incidents, newest first

Minor November 17, 2026 Webhook delivery delays 8m

Started Nov 17, 2026, 11:07 PM UTC· resolved Nov 17, 2026, 11:15 PM UTC

  1. investigating Nov 17, 2026, 11:07 PM UTC

    Problem We experienced delays processing messages. Impact We experienced delayed webhook deliveries from 4:59pm to 5:09pm CST on November 17. We have fully drained the backlog, and webhook delivery delays were resolved at 5:09pm CST.

  2. resolved Nov 17, 2026, 11:15 PM UTC

    We experienced delayed webhook deliveries from 4:59pm to 5:09pm CST on November 17. We have fully drained the backlog, and webhook delivery delays were resolved at 5:09pm CST.

Read the full incident report →

Minor November 11, 2026 Reported Apple service disruption affecting Linq 55m Linq V3 API, Linq V2 API

Started Nov 11, 2026, 12:28 AM UTC· resolved Nov 11, 2026, 01:23 AM UTC

  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.

Read the full incident report →

Minor November 5, 2026 Investigating Increased Latencies 3m Linq V3 API

Started Nov 05, 2026, 04:40 PM UTC· resolved Nov 05, 2026, 04:43 PM UTC

  1. investigating Nov 05, 2026, 04:40 PM UTC

    We're investigating some increased latencies with our Linq V3 API.

  2. resolved Nov 05, 2026, 05:00 PM UTC

    Resolved: Between 10:39 and 10:43 AM CT, some API requests saw increased latency and a small number of errors. The issue has been resolved and the API is operating normally. We’re making changes to prevent this from happening again in the future.

Read the full incident report →

Minor October 31, 2026 Webhook Delivery Degradation 2h 47m Linq V3 API

Started Oct 31, 2026, 11:38 PM UTC· resolved Nov 01, 2026, 02:25 AM UTC

  1. resolved Nov 01, 2026, 02:25 AM UTC

    From 23:38 UTC on October 31, 2026 to 02:25 UTC on November 1, 2026, webhook notifications were delayed and in some cases not delivered for a subset of phone lines. Messages continued to send and arrive during this time, but some webhooks for events in this window may never have reached the webhook endpoint. The issue is resolved and webhook delivery is back to normal. Please reach out to us if you have any questions.

  2. investigating Nov 01, 2026, 02:25 AM UTC

    Webhook notifications delayed for a subset of phone lines. Messages continue to send and arrive, but some webhooks for events are impacted.

Read the full incident report →

Minor October 9, 2026 Degraded message sending and receiving 21m Linq V3 API

Started Oct 09, 2026, 10:36 PM UTC· resolved Oct 09, 2026, 10:58 PM UTC

  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

Read the full incident report →

Minor September 29, 2026 Increased Errors with Authentication 10m Linq V3 API

Started Sep 29, 2026, 02:49 PM UTC· resolved Sep 29, 2026, 02:59 PM UTC

  1. identified Sep 29, 2026, 02:49 PM UTC

    We are seeing an increase in authentication errors in our V3 platform and have identified the problem and are deploying a fix.

  2. resolved Sep 29, 2026, 02:59 PM UTC

    We saw a brief increase in authentication errors with the V3 platform. It affected approx 3% of authenticated requests for ~9m total. It has been corrected and we're continuing to monitor.

Read the full incident report →

Minor September 22, 2026 Elevated Error Rates 44m Linq V3 API

Started Sep 22, 2026, 09:11 AM UTC· resolved Sep 22, 2026, 09:55 AM UTC

  1. resolved Sep 22, 2026, 09:14 AM UTC

    We saw a momentary increase in errors for approximately 3 minutes

Read the full incident report →

Minor August 13, 2026 Partial degradation on some lines due to network hardware maintenance 1h 47m Linq V3 API

Started Aug 13, 2026, 08:31 AM UTC· resolved Aug 13, 2026, 10:19 AM UTC

  1. identified Aug 13, 2026, 08:31 AM UTC

    Some Linq partner phone lines are currently experiencing degradation while networking hardware at one of our data centers runs an update. An on-site engineer is working to get everything restored as soon as possible. We will update this status page once service is fully restored.

  2. identified Aug 13, 2026, 09:41 AM UTC

    To restore service as quickly as possible, we are moving the affected lines over to backup networking equipment. We expect to be live on the backup equipment shortly and will post another update once service is fully restored.

  3. resolved Aug 13, 2026, 09:42 AM UTC

    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.

Read the full incident report →

Minor May 31, 2026 High Error Rates 1d Linq Blue, Linq Blue API

Started May 31, 2026, 03:39 PM UTC· resolved Jun 01, 2026, 03:54 PM UTC

  1. investigating May 31, 2026, 04:23 PM UTC

    Update: We have identified the issue resulting in elevated error rates. We are working to resolve these issues, and will provide additional updates as soon as possible.

  2. investigating May 31, 2026, 04:33 PM UTC

    Update: A fix has been successfully implemented, and we are starting to see services recover. We are currently monitoring the systems to ensure full stability.

  3. investigating May 31, 2026, 05:18 PM UTC

    We are seeing some recovery. We've identified the issue but we're working to bring all services back online now.

Read the full incident report →

Minor May 21, 2026 Linq Blue API recovered –

Started May 21, 2026, 12:01 AM UTC· resolved May 21, 2026, 12:01 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major May 20, 2026 Investigating Subset of Lines being down 1h 55m Platform API, Linq Blue API

Started May 20, 2026, 11:35 PM UTC· resolved May 21, 2026, 01:30 AM UTC

  1. investigating May 20, 2026, 11:35 PM UTC

    We're investigating a subset of lines being down.

  2. investigating May 20, 2026, 11:53 PM UTC

    We have a grid level power failure at one of our datacenters affecting a subset of our partners. We will continue to update as we receive more info.

Read the full incident report →

Major May 19, 2026 Momentary Outage API Gateway 4m Platform API, Linq Blue, Linq Blue API

Started May 19, 2026, 01:36 PM UTC· resolved May 19, 2026, 01:40 PM UTC

  1. investigating May 19, 2026, 01:36 PM UTC

    We had an approx 2 to 3 minute outage where traffic would have experienced increased errors. Investigating.

Read the full incident report →

Minor May 13, 2026 High Error Rates 27m Linq Blue, Linq Blue API

Started May 13, 2026, 10:31 PM UTC· resolved May 13, 2026, 10:58 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 13, 2026 Linq Blue API recovered –

Started May 13, 2026, 03:26 AM UTC· resolved May 13, 2026, 03:26 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 23, 2026 Platform API recovered –

Started Apr 23, 2026, 05:06 PM UTC· resolved Apr 23, 2026, 05:06 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 23, 2026 Linq Phone recovered –

Started Apr 23, 2026, 05:06 PM UTC· resolved Apr 23, 2026, 05:06 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 23, 2026 API V2 Degradation 1h 47m Linq Blue, Linq Blue API

Started Apr 23, 2026, 04:54 PM UTC· resolved Apr 23, 2026, 06:41 PM UTC

  1. investigating Apr 23, 2026, 04:54 PM UTC

    We experienced high error rates for our V2 API. We're currently investigating.

  2. investigating Apr 23, 2026, 05:01 PM UTC

    We have identified the cause and implementing mitigations/fixes. We will update soon when the incident is resolved. Currently the degradation is continuing to cause higher than normal error rates for the V2 api.

  3. investigating Apr 23, 2026, 05:36 PM UTC

    We have been implementing mitigations and have seen lower error rates. We're continuing to work on the issue further and will continue to monitor the issue.

Read the full incident report →

Minor April 14, 2026 Linq Phone recovered –

Started Apr 14, 2026, 10:55 PM UTC· resolved Apr 14, 2026, 10:55 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 14, 2026 Platform API recovered –

Started Apr 14, 2026, 10:38 PM UTC· resolved Apr 14, 2026, 10:38 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 14, 2026 API V2 Degradation 28m Web & Mobile Apps, Linq Blue, Linq Blue API

Started Apr 14, 2026, 10:32 PM UTC· resolved Apr 14, 2026, 11:00 PM UTC

  1. investigating Apr 14, 2026, 10:32 PM UTC

    We experienced high error rates for our V2 API for approximately 3 minutes. The service appears to be back but with elevated latencies. We're monitoring and will update shortly with new status reports.

  2. investigating Apr 14, 2026, 10:50 PM UTC

    Continuing to investigate root cause, but it appears that the V2 service has stabilized now.

Read the full incident report →

Minor April 10, 2026 Some Linq Lines in Degraded State 3d 1h Linq Blue, Linq Blue API

Started Apr 10, 2026, 02:27 PM UTC· resolved Apr 13, 2026, 04:00 PM UTC

  1. investigating Apr 10, 2026, 02:27 PM UTC

    We are investigating some Linq Lines that are having issues and are in a Limited/Degraded State currently. We have a team focused on investigating and resolving this as quickly as possible. Please keep an eye on your line statuses in the Linq Dashboard. Meanwhile, we will be posting updates here, as well, as the issue is investigated and eventually resolved.

  2. investigating Apr 10, 2026, 05:43 PM UTC

    The status of the affected lines has not changed. Our team is actively working to resolve the affected lines at this moment. We do not yet have a solid ETA for when full resolution will be completed. In the meantime, please monitor https://dashboard.linqapp.com/api-tooling/phone-numbers as it will automatically reflect the status of affected lines as they are updated.

  3. investigating Apr 10, 2026, 06:39 PM UTC

    Our team is still actively working to bring the affected lines back online. We appreciate your patience as we work toward a resolution. Please continue to check https://dashboard.linqapp.com/api-tooling/phone-numbers for the latest status of affected lines, as it will update automatically as lines are restored.

  4. investigating Apr 10, 2026, 08:00 PM UTC

    We are still actively working to bring the affected lines back online. We will continue to update here on the status page, but for line specifics, please continue to check https://dashboard.linqapp.com/api-tooling/phone-numbers for the latest status of affected lines, as it will update automatically as lines are restored. We appreciate your patience as we work toward a resolution.

  5. investigating Apr 10, 2026, 11:06 PM UTC

    We're continuing to work towards complete resolution for affected lines. Partners that have been affected have been directly communicated with about further steps. We will not be posting as frequently, but please reach out in slack or via email if you have any questions or concerns. We will resolve the issue once we are confident all partners are no longer have degraded lines.

Read the full incident report →

Minor April 8, 2026 Attachment Errors 13m Platform API

Started Apr 08, 2026, 06:58 PM UTC· resolved Apr 08, 2026, 07:11 PM UTC

  1. investigating Apr 08, 2026, 06:58 PM UTC

    Investigating reports of elevated 4xx errors in the v3 API for attachments.

Read the full incident report →

Minor April 8, 2026 Service Degradation for API V3 6m Platform API

Started Apr 08, 2026, 05:01 PM UTC· resolved Apr 08, 2026, 05:07 PM UTC

  1. investigating Apr 08, 2026, 05:01 PM UTC

    The v3 API was degraded and experienced elevated 5xx errors for approx 6m. The issue was mitigated, and we are operating normally again.

Read the full incident report →

Major April 6, 2026 Partial outage at Data Center 2h 6m Platform API, Linq Blue, Linq Blue API

Started Apr 06, 2026, 09:35 PM UTC· resolved Apr 06, 2026, 11:41 PM UTC

  1. investigating Apr 06, 2026, 09:35 PM UTC

    There is a partial outage at one of our Data Centers. It's affecting a small subset of Partners/Lines and we're working on getting a list together of those affected.

  2. investigating Apr 06, 2026, 09:52 PM UTC

    Power has been restored, and we've contacted the partners that were affected. We're currently validating that everything is flowing again as expected and will update when we have the all clear.

  3. investigating Apr 06, 2026, 10:47 PM UTC

    Most lines are back online now with just a few remaining. We'll continue to monitor recovery and update when they are all back up and running.

Read the full incident report →

Minor April 3, 2026 Investigating issue with partner webhook deliveries on v3 API 19m Platform API, Linq Blue API

Started Apr 03, 2026, 09:36 PM UTC· resolved Apr 03, 2026, 09:55 PM UTC

  1. investigating Apr 03, 2026, 09:36 PM UTC

    We are currently investigating an issue affecting partner webhook deliveries on the v3 API platform. Some partners may experience delayed or failed webhook notifications. Our engineering team is actively looking into the root cause and working toward a resolution. We will provide updates as more information becomes available.

  2. investigating Apr 03, 2026, 09:47 PM UTC

    Update: Webhook deliveries on the v3 API platform appear to have returned to normal at this time. Our team is still investigating the root cause of the earlier delays to ensure stability going forward. We will continue to monitor and provide further updates as needed.

Read the full incident report →