Linq Platform Outage History
22 incidents recorded over the last 365 days, 21 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Linq Platform Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 2, 2026 | Webhook Delivery DegradationFrom 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… | -2582 min | Resolved |
| Oct 9, 2026 | Degraded message sending and receivingthe issue has been resolved on AWS end and we are working with AWS on root cause analysis | 21 min | Resolved |
| Sep 29, 2026 | Increased Errors with AuthenticationWe 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. | -7 min | Resolved |
| Sep 29, 2026 | Maintenance EventMaintenance has started | 1h 30m | Resolved |
| Sep 22, 2026 | Elevated Error RatesWe saw a momentary increase in errors for approximately 3 minutes | -61 min | Resolved |
| Aug 20, 2026 | Maintenance Window for Phone LinesMaintenance has started | 41h 22m | Resolved |
| Aug 13, 2026 | Partial degradation on some lines due to network hardware maintenanceAt 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. | 1h 10m | Resolved |
| Jul 27, 2026 | Partial Degradation in One Data CenterWe 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 | 17 min | Resolved |
| Jul 22, 2026 | Increased Error Rate for Message DeliveryWe 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… | 14 min | Resolved |
| Jul 8, 2026 | Increased Latency and Error RatesWe have implemented a fix and latencies are back within normal ranges. | 58 min | Resolved |
| Jun 30, 2026 | API IncidentWe have resolved the issues with the API. We're continuing to monitor for further issues. | 1h 1m | Resolved |
| Jun 30, 2026 | Slow MessagingThe incident is over and Linq is operating normal again. | -3 min | Resolved |
| Jun 24, 2026 | Delayed MessagesWe'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… | 0 min | Resolved |
| Jun 12, 2026 | Maintenance: platform upgrades and configuration changesMaintenance has concluded | 2h 58m | Resolved |
| Jun 11, 2026 | Investigating Delayed MessagesWe have finished implementing some mitigation measures. The message latency has normalized. | -2 min | Resolved |
| Jun 7, 2026 | Investigating slow inbound messages and outbound delivery timeoutsThis 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. | 14 min | Resolved |
| Jun 1, 2026 | High Error Rates**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… | -1314 min | Resolved |
| May 20, 2026 | Investigating Subset of Lines being downWe have confirmed that all lines affected have been restored and are processing messages again. Closing the incident and will continue to monitor. Please reach out if you suspect there are further issues with any of… | 2h 5m | Resolved |
| May 19, 2026 | Momentary Outage at API GatewayWe believe that we have fully recovered, but are continuing to dig deeper and determine what the ultimate root cause of this outage was and will be implementing mitigations to keep this from happening in the future. | -7 min | Resolved |
| May 13, 2026 | High Error RatesWe have located the root cause and all affected lines should be operating normally again. | 26 min | Resolved |
| Apr 23, 2026 | API V2 DegradationAll v2 API queues have processed any backlog they had and latency/error rates are back to normal. | 1h 48m | Resolved |
| Mar 31, 2026 | Networking: Primary ISP Emergency MaintenanceWe're scheduling Linq Maintenance for an upcoming emergency maintenance window scheduled by our upstream fiber provider, that may affect Linq services. The maintenance is expected to take place over a 60 minute period… | 12h 21m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Linq Platform incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Linq Platform Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Linq Platform acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Linq Platform outage in this window ran 1d 17h, against a mean recovery of 4h 27m. If you depend on Linq Platform in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.