Linq Outage History

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

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.

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.

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.

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.

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.

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.

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.

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

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

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.

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.

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.

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.

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.

There was an approx 5 minute outage at one of our data centers. As a result, some partners outbound messages would have failed, and you would have received a message.failed webhook for any messages that didn't dispatch successfully during the outage.

Webhooks on v3 are seeing delays of up to 7 minutes

We're experiencing high volume today and the v2 API could experience some increased latency as a result. There is currently no issues with latency, but we are monitoring and will update if we start to see any problems.

Our primary ISP at one of our data centers is currently experiencing an outage. We have seamlessly failed over to our backup ISP, and all systems are operating normally based on our monitoring. Please let us know if you experience any issues. Our team is actively monitoring the situation as we work with our primary ISP to restore service.

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.

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.

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.

V2 API webhook delivery and processing is delayed by 2+ minutes currently. The team is aware of the cause and working to fix the issue. Note: V3 API is not affected.

We have identified the root cause and are in the process of implementing mitigations and monitoring queue latencies for V2.

We are seeing the queues trending down towards normal now. I will take a little more time for it to get back to normal while the system catches up.

The V2 API webhooks latency is at 10+minutes currently. We are working on mitigating this currently.

V2 API webhook delivery and processing is delayed by 20+ minutes currently. The team is aware of the cause and working to fix the issue. Note: V3 API is not affected.

We have identified the root cause and are in the process of implementing mitigations and monitoring queue latencies for V2.

We are seeing the queues trending down towards normal now. it's just going to take a little more time for it to get back to normal while the system catches up.

We are currently investigating an issue affecting our v3 API. Increased error rates have been observed, and our team is actively working to identify and resolve the root cause. We will provide updates as more information becomes available.

Error rates on the v3 API are trending downward and the service appears to be stabilizing. The incident occurred between 3:43 PM and 3:59 PM CST. We will continue monitoring and provide a final update once we have confirmed full recovery.