Incidents | Linq

Investigating Subset of Lines being down

Thu, 21 May 2026 01:30:00 -0000

We 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 your lines.

Investigating Subset of Lines being down

Thu, 21 May 2026 00:16:00 -0000

Lines are starting to come back online. We will update here when we're completely back to normal operations.

Linq Blue API recovered

Thu, 21 May 2026 00:01:21 +0000

Linq Blue API recovered

Investigating Subset of Lines being down

Thu, 21 May 2026 00:00:00 -0000

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

Investigating Subset of Lines being down

Wed, 20 May 2026 23:53:00 -0000

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.

Investigating Subset of Lines being down

Wed, 20 May 2026 23:35:00 -0000

We're investigating a subset of lines being down.

Linq Blue API went down

Wed, 20 May 2026 23:29:24 +0000

Linq Blue API went down

Momentary Outage API Gateway

Tue, 19 May 2026 13:40:00 -0000

We 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.

Momentary Outage API Gateway

Tue, 19 May 2026 13:36:00 -0000

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

High Error Rates

Wed, 13 May 2026 22:58:00 -0000

We have located the root cause and all affected lines should be operating normally again.

High Error Rates

Wed, 13 May 2026 22:31:00 -0000

We're experiencing service degradation/high error rates for some partners. Investigating and will update with more info.

Linq Blue API recovered

Wed, 13 May 2026 03:26:53 +0000

Linq Blue API recovered

Linq Blue API went down

Wed, 13 May 2026 03:14:39 +0000

Linq Blue API went down

Networking: Primary ISP Maintenance

Thu, 07 May 2026 04:00:47 -0000

Our primary fiber provider is going to be performing upgrades. The maintenance is expected to take place over a 360-minute period. Linq has failover configurations in place for our internet providers. We do not anticipate a full service outage; however, you may experience increased network latencies during this window while traffic is rerouted across redundant paths. --- :date: **Maintenance Window** UTC: May 7, 2026 - 04:00a to May 7, 2026 10:00a UTC Pacific: May 6, 2026 - 09:00p to May 7, 2026 03:00a PDT --- Our team will be monitoring the situation throughout the maintenance window and is prepared to respond to any issues that arise. If you have any questions or concerns, please don't hesitate to reach out. We'll follow up with a post-maintenance confirmation once the fiber provider gives us the all clear.

API V2 Degradation

Thu, 23 Apr 2026 18:41:00 -0000

All queues have caught back up and Latency has returned to normal for the V2 API.

API V2 Degradation

Thu, 23 Apr 2026 17:36:00 -0000

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.

Linq Phone recovered

Thu, 23 Apr 2026 17:06:13 +0000

Linq Phone recovered

Platform API recovered

Thu, 23 Apr 2026 17:06:13 +0000

Platform API recovered

API V2 Degradation

Thu, 23 Apr 2026 17:01:00 -0000

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.

Linq Phone went down

Thu, 23 Apr 2026 16:56:14 +0000

Linq Phone went down

API V2 Degradation

Thu, 23 Apr 2026 16:54:00 -0000

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

Platform API went down

Thu, 23 Apr 2026 16:53:09 +0000

Platform API went down

API V2 Degradation

Tue, 14 Apr 2026 23:00:00 -0000

We have identified the root cause and will be continuing to monitor the situation. All services are operating normally now.

Linq Phone recovered

Tue, 14 Apr 2026 22:55:09 +0000

Linq Phone recovered

API V2 Degradation

Tue, 14 Apr 2026 22:50:00 -0000

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

Platform API recovered

Tue, 14 Apr 2026 22:38:29 +0000

Platform API recovered

Linq Phone went down

Tue, 14 Apr 2026 22:36:10 +0000

Linq Phone went down

Platform API went down

Tue, 14 Apr 2026 22:32:52 +0000

Platform API went down

API V2 Degradation

Tue, 14 Apr 2026 22:32:00 -0000

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.

Some Linq Lines in Degraded State

Mon, 13 Apr 2026 16:00:00 -0000

We have been in touch with affected partners and are working on resolution options for any customers still impacted. If you believe you have been impacted and haven't spoken to anyone regarding the problems you've had, please reach out to support at <[email protected]>, and we will work towards a resolution as quickly as possible.

Some Linq Lines in Degraded State

Fri, 10 Apr 2026 23:06:00 -0000

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.

Some Linq Lines in Degraded State

Fri, 10 Apr 2026 20:00:00 -0000

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.

Some Linq Lines in Degraded State

Fri, 10 Apr 2026 18:39:00 -0000

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.

Some Linq Lines in Degraded State

Fri, 10 Apr 2026 17:43:00 -0000

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.

Some Linq Lines in Degraded State

Fri, 10 Apr 2026 14:27:00 -0000

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.

Attachment Errors

Wed, 08 Apr 2026 19:11:00 -0000

The source of the 403 errors for attachment download was found, and the fix has been implemented. Attachments should work as expected again.

Attachment Errors

Wed, 08 Apr 2026 18:58:00 -0000

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

Service Degradation for API V3

Wed, 08 Apr 2026 17:07:00 -0000

We will continue to monitor, but the service degradation has been mitigated and all services are operating as expected now.

Service Degradation for API V3

Wed, 08 Apr 2026 17:01:00 -0000

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

Partial outage at Data Center

Mon, 06 Apr 2026 23:41:00 -0000

We have verified that all lines are back up and operational. Closing the incident and continuing to monitor the systems. Thank you for your patience.

Partial outage at Data Center

Mon, 06 Apr 2026 22:47:00 -0000

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.

Partial outage at Data Center

Mon, 06 Apr 2026 21:52:00 -0000

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.

Partial outage at Data Center

Mon, 06 Apr 2026 21:35:00 -0000

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.

Investigating issue with partner webhook deliveries on v3 API

Fri, 03 Apr 2026 21:55:00 -0000

Resolved: We have identified the root cause of the webhook delivery delays and have confirmed that all systems are fully back to normal. Between approximately 4:14 PM CST and 4:40 PM CST, inbound messages on the v3 API platform experienced a multi-minute delay in webhook deliveries. No messages were lost — all were processed successfully. The issue has been resolved and we are confident the platform is operating normally. We will continue to monitor to ensure stability.

Investigating issue with partner webhook deliveries on v3 API

Fri, 03 Apr 2026 21:47:00 -0000

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.

Investigating issue with partner webhook deliveries on v3 API

Fri, 03 Apr 2026 21:36:00 -0000

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.

Partial outage at Data Center

Wed, 01 Apr 2026 23:39:00 -0000

All services have been fully restored. The partial outage at our data center has been resolved and all affected lines are back online. We will be conducting a thorough review of the root cause and implementing safeguards to prevent a recurrence in the future. We will continue to monitor the situation closely to ensure stability. We apologize for any disruption this may have caused and appreciate your patience throughout the incident.

Partial outage at Data Center

Wed, 01 Apr 2026 22:38:00 -0000

We are actively bringing affected lines back online. Upon further investigation, the issue impacted only a portion of the lines at the data center — not all lines — so the overall scope of the outage is narrower than initially anticipated. We will post a final update here once all services are fully restored. Thank you for your continued patience.

Partial outage at Data Center

Wed, 01 Apr 2026 22:33:00 -0000

We have identified the root cause of this outage. The issue is isolated to a single Linq data center, so not all lines are affected — however, a significant portion of lines routed through this facility are currently impacted. Our team is actively working on a resolution and we expect to have services restored as quickly as possible. We will continue to provide updates as we make progress. Thank you for your patience.

Partial outage at Data Center

Wed, 01 Apr 2026 22:13:00 -0000

We're currently investigating increased Webhook failures and error rates at one of our data centers

Momentary Outage at One Data Center

Wed, 01 Apr 2026 21:01:00 -0000

The data center is back up and operating normally now.

Momentary Outage at One Data Center

Wed, 01 Apr 2026 20:55:00 -0000

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.

Webhook delivery delayed for v3

Thu, 19 Mar 2026 22:50:00 -0000

Webhooks on v3 delayed between 11:42p - 11:50p UTC. Service has been returned and there are no longer excessive delays.

Webhook delivery delayed for v3

Thu, 19 Mar 2026 22:42:00 -0000

Webhooks on v3 are seeing delays of up to 7 minutes

High Volume Traffic

Thu, 19 Mar 2026 19:28:00 -0000

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.

Networking: Primary ISP Failover at Data Center

Tue, 17 Mar 2026 21:38:00 -0000

Our primary ISP rerouted traffic to bypass a larger scale outage. Service has been restored, and we have successfully switched back over to utilizing them at all data centers, but will continue to monitor and update when the issue is fully resolved. All systems have been operating normally based on our monitoring, during their outage.

Networking: Primary ISP Failover at Data Center

Tue, 17 Mar 2026 17:50:00 -0000

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.

Linq Blue API - Increased Latency

Wed, 11 Mar 2026 03:57:00 -0000

Resolved: Both the v2 and v3 APIs have returned to normal latency levels. This incident is now resolved. We will continue to monitor for any elevated latency or error rates. Thank you for your patience.

Linq Blue API - Increased Latency

Wed, 11 Mar 2026 03:45:00 -0000

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.

Linq Blue API - Increased Latency

Wed, 11 Mar 2026 03:41:00 -0000

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.

Linq Blue API - Increased Latency

Wed, 11 Mar 2026 03:36:00 -0000

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.

V2 Webhook Delivery and Processing Delays

Mon, 09 Mar 2026 21:56:00 -0000

The queue latency is back to normal and we'll continue to monitor the system's performance.

V2 Webhook Delivery and Processing Delays

Mon, 09 Mar 2026 21:15:00 -0000

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.

V2 Webhook Delivery and Processing Delays

Mon, 09 Mar 2026 20:30:00 -0000

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

V2 Webhook Delivery and Processing Delays

Mon, 09 Mar 2026 19:30:00 -0000

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.

Increased V2 API Webhook Latencies

Sat, 07 Mar 2026 21:31:00 -0000

The queue latency is back to normal and we'll continue to monitor the system, but functionality has returned to back to normal now.

Increased V2 API Webhook Latencies

Sat, 07 Mar 2026 21:21:00 -0000

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.

Increased V2 API Webhook Latencies

Sat, 07 Mar 2026 21:15:00 -0000

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

Increased V2 API Webhook Latencies

Sat, 07 Mar 2026 20:57:00 -0000

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.

Increased V2 API Webhook Latencies

Sat, 07 Mar 2026 20:45:00 -0000

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

Investigating elevated v3 API error rates

Fri, 06 Mar 2026 22:16:00 -0000

This incident has been resolved. The v3 API is fully operational and error rates have returned to normal levels. We have identified the root cause of the issue and are actively working to mitigate the potential for recurrence in the future. Thank you for your patience.

Investigating elevated v3 API error rates

Fri, 06 Mar 2026 22:03:00 -0000

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.

Investigating elevated v3 API error rates

Fri, 06 Mar 2026 21:58:00 -0000

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.

Linq Blue API recovered

Mon, 02 Mar 2026 12:25:53 +0000

Linq Blue API recovered

Linq Blue API went down

Mon, 02 Mar 2026 10:05:56 +0000

Linq Blue API went down

Scheduled Network Upgrades

Mon, 02 Mar 2026 10:00:00 -0000

We will be performing scheduled network upgrades on Monday, March 2nd starting at 4:00 AM CST. The maintenance window is expected to last 2 hours. During this time, the v2 and v3 APIs may be temporarily unavailable.

Increased latency on v3 API

Fri, 27 Feb 2026 19:13:00 -0000

We have seen a return to normal state. The v3 API latency has returned to expected levels. Thank you for your patience.

Increased latency on v3 API

Fri, 27 Feb 2026 18:09:00 -0000

We are currently seeing increased latency on the v3 API. Our team is actively working on resolving the issue. We will post an update once the issue is resolved.

Linq Blue API v2 - Degraded Performance

Mon, 23 Feb 2026 19:12:00 -0000

This incident has been resolved. Linq Blue API v2 queues and performance have fully returned to normal. Thank you for your patience.

Linq Blue API v2 - Degraded Performance

Mon, 23 Feb 2026 19:10:00 -0000

Queues have returned to normal levels. We are continuing to monitor to ensure everything remains stable, but based on our monitoring the issue appears to be resolved. We will post a final update once we have confirmed full resolution.

Linq Blue API v2 - Degraded Performance

Mon, 23 Feb 2026 18:55:00 -0000

Note: The V3 API is not affected by this incident and is operating normally.

Linq Blue API v2 - Degraded Performance

Mon, 23 Feb 2026 18:51:00 -0000

We have identified the cause of the issue and are seeing latency begin to improve. We expect performance to return to normal levels shortly. We will continue to monitor and provide further updates.

Linq Blue API v2 - Degraded Performance

Mon, 23 Feb 2026 18:44:00 -0000

Linq Blue API v2 is currently experiencing degraded status. Queues are delayed, which means inbound webhook triggers will be delayed as a result. Our team is actively working to resolve the issue. We will provide further updates as they become available.

V3 API Outage

Fri, 20 Feb 2026 22:05:00 -0000

We have implemented a fix and are continuing to monitor the service and any further remediations.

V3 API Outage

Fri, 20 Feb 2026 22:00:00 -0000

V3 Platform API is currently experiencing elevated 5xx errors. Investigating

Linq Blue API Service Degredation

Fri, 20 Feb 2026 15:54:00 -0000

A fix has been implemented, and the incident should be resolved for Linq Blue API partners. We will continue to verify and monitor the incident and update if any more service disruption occurs.

Linq Blue API Service Degredation

Fri, 20 Feb 2026 15:28:00 -0000

We have identified the root cause of the incident and are in the process of implementing a fix for it.

Linq Blue API Service Degredation

Fri, 20 Feb 2026 15:15:00 -0000

The Linq Blue API is currently experiencing service degradation for some partners. We're currently investigating and will update soon with an update.

Linq Blue and Linq Blue API Degradation

Tue, 10 Feb 2026 23:20:00 -0000

The service degradation for Linq Blue and it's API have been resolved.

Linq Blue and Linq Blue API Degradation

Tue, 10 Feb 2026 21:15:00 -0000

We're currently seeing increased latencies in one of our data centers. This is causing service degradation for Linq Blue and Linq Blue API. Currently investigating and working on remediations. Expect increased latencies with some failures until the incident is mitigated.

Network Instability at Data Center - Increased Latency

Sat, 31 Jan 2026 08:18:00 -0000

**Resolved** - our primary ISP, experienced an outage beginning at 12:35 AM CST. We failed over to our backup ISP (Spectrum), but the network load exceeded it's capacity, resulting in increased latency and intermittent failures rather than a complete outage. Primary ISP service was restored at 1:27 AM CST, and all services are now operating normally. **Next Steps:** - We will increase our bandwidth with our backup ISP to handle full load during future failovers - Begin process to test another primary ISP option as an additional redundant connection to our data centers

Network Instability at Data Center - Increased Latency

Sat, 31 Jan 2026 06:38:00 -0000

We are experiencing network instability at one of our data centers due to an upstream provider issue. We have failed over to our backup ISP and are actively monitoring the situation. We will provide updates as more information becomes available.

Network Instability at Data Center - Increased Latency and Errors

Wed, 28 Jan 2026 20:11:00 -0000

**Resolved** - Between 1:25 PM CST and 1:37 PM CST today, we experienced network instability at one of our data centers. During this period, some users may have experienced increased latency and elevated error rates. Our team identified and resolved the issue. All systems are now operating normally. We apologize for any inconvenience this may have caused.

V2 Messaging API - Increased Load Monitoring

Wed, 28 Jan 2026 00:11:00 -0000

We've seen better latency on our V2 API today and have continued to find efficiencies and improve things. Marking this status as resolved.

V2 Messaging API - Increased Load Monitoring

Tue, 27 Jan 2026 13:07:00 -0000

Yesterday, our V2 Messaging API experienced increased load. We completed work overnight to help maintain low normal under the load. We will be actively monitoring performance throughout the day.

V2 & V3 APIs experiencing issues

Thu, 22 Jan 2026 18:19:00 -0000

This incident has been resolved. A nightly deployment caused part of our infrastructure to enter an incorrect state, which affected messaging for most of the Linq blue platform between approximately 11pm and 3am CT. We've identified the root cause and are implementing changes to prevent this from happening again. Thank you for your patience.

V2 & V3 APIs experiencing issues

Thu, 22 Jan 2026 10:03:00 -0000

We have seen V2 and V3 APIs return to normal. The team will continue to monitor until the morning and we will work towards implementing mitigations to prevent this in the future. Thank you for your patience.

V2 & V3 APIs experiencing issues

Thu, 22 Jan 2026 08:55:00 -0000

V3 API is looking much more recovered. We are continuing to monitor the situation and will provide further updates.

V2 & V3 APIs experiencing issues

Thu, 22 Jan 2026 08:18:00 -0000

V2 API is now mostly fully back online. We experienced a brief period where duplicate messages were being sent outbound when a message was sent via the V2 API, but that issue has now been resolved. V3 API is still something we are actively working on. We will continue to provide updates as we make progress.

V2 & V3 APIs experiencing issues

Thu, 22 Jan 2026 06:37:00 -0000

We are seeing some of the V2 API coming back online and recovering, however we do not expect this to be the final solution for V2 and V3 APIs. Most of the online status is currently on the V2 API for Blue lines. We are continuing to monitor and will provide further updates.

V2 & V3 APIs experiencing issues

Thu, 22 Jan 2026 05:48:00 -0000

We have identified the issue and our team is online working to resolve it as soon as possible. We will provide further updates shortly. Thank you for your patience.

V2 & V3 APIs experiencing issues

Thu, 22 Jan 2026 04:50:00 -0000

Our API platforms are currently experiencing downtime. Our team is actively working to resolve the pressure on the system. We will provide updates as the situation progresses. Thank you for your patience.

V2 API Platform Experiencing Heavy Load

Wed, 21 Jan 2026 16:57:00 -0000

The team has pushed optimizations to handle the load more gracefully. We have seen a return to the performance we expect. Thank you for your patience.

V2 API Platform Experiencing Heavy Load

Tue, 20 Jan 2026 19:37:00 -0000

Our V2 API platform is currently experiencing heavy load, which may be affecting performance and latency for some users. Our team is actively working to resolve the pressure on the system. We will provide updates as the situation progresses. Thank you for your patience.

API Issue Resolved

Mon, 05 Jan 2026 23:09:00 -0000

Update: The API issue has been resolved. The incident occurred from 4:54pm to 4:55pm CST and was quickly addressed by our team. All API services are now functioning as expected.

API Issue Resolved

Mon, 05 Jan 2026 23:01:00 -0000

We experienced a brief issue affecting our API services. Our team identified the root cause and implemented a fix. The issue has been resolved and all API services are now operating normally.

Database upgrade maintenance

Fri, 12 Dec 2025 10:00:00 -0000

We'll be upgrading our database infrastructure to ensure continued compatibility and performance. During this maintenance window, all Linq services will be temporarily unavailable for up to 1 hour. All inbound messages received during the downtime will be automatically synced once the upgrade is complete. The platform will return to full functionality immediately after the maintenance window. We expect actual downtime to be 30 minutes to 1 hour, but have scheduled the extended 2-hour window to ensure we have adequate time for a smooth upgrade process. We'll monitor throughout and post updates as the maintenance progresses.

Brief slowdown and timeouts between 11:57am–12:14pm CST

Fri, 28 Nov 2025 19:55:00 -0000

Between 11:57am and 12:14pm CST, some customers may have seen slower response times and increased request timeouts. We identified the issue and blocked the unexpected inbound traffic causing the overload. Systems recovered immediately after the block was put in place.

Investigating an incident impacting Linq Blue

Mon, 24 Nov 2025 04:18:00 -0000

As of 9:51 PM CST, services have remained stable. Our downstream provider has deployed a fix to resolve the issue on their end. We're continuing to monitor closely but expect normal operations at this time. We'll provide further updates if anything changes.

Investigating an incident impacting Linq Blue

Mon, 24 Nov 2025 03:59:00 -0000

We've seen stability since 9:51 PM CST. We're continuing to monitor closely while our downstream provider works on the root cause.

Investigating an incident impacting Linq Blue

Mon, 24 Nov 2025 03:48:00 -0000

As of 9:48 PM CST, we're seeing intermittent downtime of Linq Blue. Our downstream provider has dispatched a response team to work on the issue. We're continuing to deploy our switch to our backup provider. We'll keep you updated as both efforts progress.

Investigating an incident impacting Linq Blue

Mon, 24 Nov 2025 03:32:00 -0000

As of 9:29 PM CST, the Linq Blue network has come back online. However, the underlying issue is not yet resolved, so we expect continued degraded network performance until we complete our resolution efforts. We're continuing to work on a permanent fix and will provide updates.

Investigating an incident impacting Linq Blue

Mon, 24 Nov 2025 03:17:00 -0000

Our downstream provider is responding to the incident and we're tracking progress with them. We're also initiating fallback to our backup provider in case the outage continues. We'll continue to provide updates as the situation develops.

Investigating an incident impacting Linq Blue

Mon, 24 Nov 2025 02:58:00 -0000

We've reopened the issue with our downstream provider and are continuing to monitor. We'll provide updates as soon as we have more information.

Investigating an incident impacting Linq Blue

Mon, 24 Nov 2025 02:50:00 -0000

We're seeing a recurrence of the earlier connectivity issues. Linq Blue and Linq Blue API are currently experiencing disruptions. Our team is actively investigating. We'll provide updates as soon as we have more information.

Investigating an incident impacting Linq Blue

Mon, 24 Nov 2025 02:30:00 -0000

Our reporting shows significant connectivity issues between 7:53 pm CST and 8:00 pm CST. During this window, requests to interact with Linq Blue experienced very high error rates. The issue resolved at 8:00 pm CST. - Sending: Any messages that needed to be sent during this period can be retried. - Receiving: Any messages received during this period should be synced, with a brief delay after downtime ended.

Investigating an incident impacting Linq Blue

Mon, 24 Nov 2025 02:28:00 -0000

We’ve identified the root cause as a network/ISP issue with a downstream provider. Service for Linq Blue and Linq Blue API has been restored and systems are operating normally.

Investigating an incident impacting Linq Blue

Mon, 24 Nov 2025 02:02:00 -0000

We’re investigating an incident affecting Linq Blue.

Linq Blue API queue delays causing higher message latency

Thu, 20 Nov 2025 05:13:00 -0000

Latency for Linq Blue API remained stable and normal through tonight’s peak. Compared to previous nights with elevated latency, performance met expectations and the recent improvements proved impactful. We’ll continue real‑time monitoring as overnight traffic ramps and post updates if conditions change.

Linq Blue API queue delays causing higher message latency

Thu, 20 Nov 2025 00:17:00 -0000

Latency for Linq Blue API has remained stable at normal levels through today’s peak usage. As we head into the busier evening hours, a dedicated team is focused on real‑time monitoring to keep performance steady. We’ll post updates if conditions change.

Linq Blue API queue delays causing higher message latency

Wed, 19 Nov 2025 14:39:00 -0000

Latency for Linq Blue API stayed normal overnight. A dedicated team is focused solely on monitoring and responding to latency as we enter today’s peak usage, with one goal: keeping performance stable. We’ll post updates if conditions change.

Linq Blue API queue delays causing higher message latency

Wed, 19 Nov 2025 05:38:00 -0000

Latency for Linq Blue API briefly spiked; we identified the offending component and killed it. Latency has returned to normal, and we’re continuing to monitor and ship safeguards for peak traffic that we expect tomorrow.

Linq Blue API queue delays causing higher message latency

Wed, 19 Nov 2025 05:15:00 -0000

Latency for Linq Blue API may be elevated with occasional timeouts as we deploy changes. The team is monitoring closely and adjusting in real time. We’ll share updates as additional fixes roll out tonight.

Linq Blue API queue delays causing higher message latency

Wed, 19 Nov 2025 03:15:00 -0000

Latency for Linq Blue API has returned to normal. We’re continuing to deploy fixes targeting peak/high‑traffic periods. We’ll post updates as changes roll out tonight.

Linq Blue API queue delays causing higher message latency

Wed, 19 Nov 2025 02:21:00 -0000

We’ve deployed an initial change to Linq Blue API that has reduced message latency; metrics show improvement versus baseline. The team is continuing work tonight to roll out additional fixes to further stabilize and reduce queue delays. We’ll share another update as new changes are deployed or if conditions shift.

Linq Blue API queue delays causing higher message latency

Wed, 19 Nov 2025 01:30:00 -0000

We’re seeing delays in Linq Blue API queues, resulting in higher-than-normal latency for sending and receiving messages. The team is actively investigating and working on mitigation tonight. We’ll post updates as we progress.

Cloudflare incident impacting our platform.

Tue, 18 Nov 2025 16:41:00 -0000

Things have returned to normal. Cloudflare’s incident has been mostly resolved, and our platform performance is back to expected levels. We’ll keep watching things closely. Cloudflare status: https://www.cloudflarestatus.com/

Cloudflare incident impacting our platform.

Tue, 18 Nov 2025 13:31:00 -0000

We've made some updates to circumvent cloudflare temporarily for some key paths (including our partner api) and parts of our platform are now available again. We are continuing to monitor the situation and will return our system to it's prior configurations once cloudflare gives us the all clear.

Cloudflare incident impacting our platform.

Tue, 18 Nov 2025 11:48:00 -0000

Cloudflare is having a major issue and it’s causing parts of our system to go up and down intermittently. Some requests may fail or behave inconsistently. We’re monitoring their outage and working to mitigate where we can on our side until things stabilize. Cloudflare’s status page: https://www.cloudflarestatus.com/

Brief Network Interruption

Wed, 05 Nov 2025 18:43:00 -0000

Connectivity was briefly interrupted due to a transient network issue. The connection is now stable, and all systems are operating normally. We’re monitoring closely to ensure continued stability. No data loss occurred. Messages sent during the interruption that failed may need to be retried, but messages received during that time were delivered normally. Start: 12:25 PM CST End: 12:31 PM CST

Scheduled Network Maintenance — Linq Blue

Tue, 28 Oct 2025 04:00:00 -0000

**Summary:** Linq Blue sending will be temporarily unavailable for up to 15 minutes during scheduled maintenance. **Description:** We’ll be performing scheduled network maintenance to improve performance and stability. During this window, Linq Blue sending may be unavailable for up to 15 minutes, though we don’t expect downtime to last the entire maintenance window. All other Linq Platform services, including the dashboard and APIs, will remain online. Any inbound messages received during the downtime will be automatically synced once connectivity is restored. **Maintenance window:** **Start:** Monday, October 27 · 11:00 PM CDT **End:** Tuesday, October 28 · 4:00 AM CDT We’ll monitor throughout the window and post an update once maintenance is complete.

Service disruption due to AWS outage

Tue, 21 Oct 2025 04:33:00 -0000

All systems fully recovered; working on root cause prevention.

Service disruption due to AWS outage

Tue, 21 Oct 2025 03:34:00 -0000

Processing queues have cleared up, and message flow is moving faster across the platform. We’re still implementing a long-term fix to address the root cause, and during that work, some delays may continue intermittently. We’ll post another update once the fix is fully deployed and performance stabilizes.

Service disruption due to AWS outage

Tue, 21 Oct 2025 02:37:00 -0000

We’re currently seeing delayed processing across parts of the platform. Some messages and requests may take longer than usual to complete. Our team is investigating and monitoring system performance closely. We’ll share another update as soon as processing times return to normal.

Service disruption due to AWS outage

Tue, 21 Oct 2025 01:54:00 -0000

All systems have remained stable, and message delivery across Linq Blue and the Platform API is fully operational. We’re marking this incident as resolved, but we’ll continue to keep a close eye on system performance to ensure no new issues arise. Thank you for your patience throughout today’s outage.

Service disruption due to AWS outage

Tue, 21 Oct 2025 00:18:00 -0000

We’ve successfully redeployed all instances, and all are now reporting healthy. System performance has largely returned to normal, and message delivery is functioning as expected. While things appear stable, we’re continuing to monitor closely to ensure there’s no regression or lingering instability. Any messages received during the downtime should now sync correctly into Linq Blue as systems continue processing queued inbound traffic.

Service disruption due to AWS outage

Tue, 21 Oct 2025 00:05:00 -0000

We’ve seen some instances deploy successfully, and parts of the platform are beginning to recover. However, we’re not yet seeing full restoration across all systems. Some requests and message sends are now succeeding, while others may still fail intermittently. We’re continuing to work toward full recovery and will share another update as progress continues.

Service disruption due to AWS outage

Mon, 20 Oct 2025 23:09:00 -0000

We’re currently experiencing a major disruption across our systems. Most services are failing due to our inability to spin up new instances, and several existing instances are in a degraded state. Our team is actively working to restore capacity and stability as quickly as possible. We’ll continue to provide updates as we make progress.

Service disruption due to AWS outage

Mon, 20 Oct 2025 22:49:00 -0000

We’re currently seeing increased error rates across parts of our platform and are investigating the cause. Some Linq Blue message sends and API requests may be failing or delayed. We’ll share another update as soon as we have more information.

Service disruption due to AWS outage

Mon, 20 Oct 2025 22:08:00 -0000

Our systems are largely stable, but we’re still seeing some intermittent issues due to a few backend instances remaining in a degraded state following the AWS outage. This can cause certain requests to fail randomly, depending on which server they’re routed to. As a result, some inbound Linq Blue messages may still experience short delays before being picked up and processed. We’re continuing to monitor closely and are working to ensure all instances are fully healthy before closing this incident.

Service disruption due to AWS outage

Mon, 20 Oct 2025 21:41:00 -0000

Our systems have returned to normal operation, and message delivery across Linq Blue and the Platform API is performing as expected. We haven’t yet received an official all-clear from AWS, so we’ll keep this incident open while we monitor to ensure stability and confirm there’s no regression. We’ll post a final update once AWS confirms full resolution.

Service disruption due to AWS outage

Mon, 20 Oct 2025 20:40:00 -0000

We continue to see health metrics trending in the right direction, and most services are coming back online. Linq Blue message delivery and Platform API performance have both improved significantly. We’ll continue to monitor closely to ensure all systems return to a fully healthy state before marking this incident resolved.

Service disruption due to AWS outage

Mon, 20 Oct 2025 19:13:00 -0000

We’re starting to see signs of recovery across our systems as AWS services stabilize. Linq Blue message delivery and API performance are gradually improving. That said, we’re still observing some intermittent errors and delays, so we’re not marking this incident as fully resolved yet. We’ll continue to monitor closely and post another update once we’re confident services have fully recovered.

Service disruption due to AWS outage

Mon, 20 Oct 2025 17:49:00 -0000

We’re still waiting on updates from AWS regarding their ongoing outage. Our platform remains unstable, and outbound Linq Blue messages are still not sending successfully. Inbound messages to Linq Blue numbers are syncing inconsistently and may be delayed longer than usual while systems recover. We’re continuing to monitor closely and will update as soon as AWS provides more information or stability returns.

Service disruption due to AWS outage

Mon, 20 Oct 2025 17:30:00 -0000

We’re now seeing intermittent errors in our main Platform API as well, related to the ongoing AWS outage impacting Linq Blue. We’re continuing to monitor closely and will post updates as conditions change.

Service disruption due to AWS outage

Mon, 20 Oct 2025 16:25:00 -0000

Most Linq Blue Message sends continue to fail, and inbound messages are syncing with delays. There have been no new updates from AWS or other affected infrastructure providers at this time. We’re continuing to monitor their status and will update as soon as recovery efforts begin. You can track AWS’s latest updates here: https://health.aws.amazon.com/health/status

Service disruption due to AWS outage

Mon, 20 Oct 2025 15:52:00 -0000

The AWS outage continues to impact Linq Blue message delivery. Most message sends are still failing, and inbound messages are syncing but remain delayed. You can follow AWS’s own service status here: https://health.aws.amazon.com/health/status We’re continuing to monitor the situation and will update as soon as AWS recovery efforts begin to stabilize services.

Service disruption due to AWS outage

Mon, 20 Oct 2025 15:16:00 -0000

We’re currently seeing most Linq Blue message sends fail due to the ongoing AWS infrastructure outage. Inbound messages are syncing successfully but with longer-than-usual delays. Our team is continuing to monitor the situation with AWS and will post updates as recovery progresses.

Service disruption due to AWS outage

Mon, 20 Oct 2025 15:04:00 -0000

During this time, attempts to send messages may fail or take longer than usual. Any incoming messages received while systems are degraded will still sync correctly into Linq Blue once service stabilizes, though delivery may be delayed. We’re monitoring AWS recovery progress and will post another update as soon as performance improves.

Service disruption due to AWS outage

Mon, 20 Oct 2025 14:58:00 -0000

We’re currently experiencing degraded performance and intermittent errors within Linq Blue due to an ongoing AWS infrastructure outage. This issue is impacting message delivery and related API requests for some users. Our team is monitoring AWS’ recovery progress and making adjustments to minimize disruption. We’ll post another update once service stability improves.

Processing Delays for Linq Blue Messaging

Fri, 17 Oct 2025 20:54:00 -0000

Partner webhook request delivery times have returned to normal. All pending requests have been processed, and systems are operating as expected. We’ll keep monitoring for stability.

Processing Delays for Linq Blue Messaging

Fri, 17 Oct 2025 20:45:00 -0000

We’re currently seeing delays of about 4–5 minutes in Partner webhook request delivery. Our team is investigating and working to bring delivery times back to normal.

Processing Delays for Linq Blue Messaging

Fri, 17 Oct 2025 20:24:00 -0000

Message processing for Linq Blue has returned to normal. All queues have cleared, and both inbound and outbound traffic are flowing as expected. We’ll continue to monitor to ensure stability.

Processing Delays for Linq Blue Messaging

Fri, 17 Oct 2025 20:16:00 -0000

We’re currently experiencing processing delays for Linq Blue Messaging. Our team is working to clear message queues, but users may see a few minutes of delay for both inbound and outbound messages. We’ll post an update once performance returns to normal.

Delayed Webhook Deliveries to API Partners

Mon, 13 Oct 2025 22:10:00 -0000

We identified and resolved an issue that caused delayed webhook deliveries to API partners between approximately 4:33 PM and 5:10 PM CST. All pending webhooks have since been processed and delivered, and message delivery latency has returned to normal levels.

Processing Delays

Tue, 07 Oct 2025 22:40:00 -0000

Things are performing much better. We’ll continue to monitor for any lingering issues.

Processing Delays

Tue, 07 Oct 2025 21:29:00 -0000

We have seen a significant recovery to the platform issues as a whole and things are performing better. Contact searches, if you use those, are still not performing how they should and timing out sometimes, we are continuing to work on that.

Processing Delays

Tue, 07 Oct 2025 19:58:00 -0000

We are still experiencing platform wide issues.

Processing Delays

Tue, 07 Oct 2025 18:06:00 -0000

Error rates for partners have decreased to normal levels. We are continuing to monitor.

Processing Delays

Tue, 07 Oct 2025 17:55:00 -0000

The queuing issues have been resolved. We are still investigating some API partners reporting higher error rates. We will followup when this is resolved.

Processing Delays

Tue, 07 Oct 2025 17:38:00 -0000

We are currently addressing delays in event processing. This may result in delayed message sending/receiving, typing indicators, reactions, and related API functionality. We are working to resolve the issue currently.

Temporary Delays in Event Processing

Tue, 30 Sep 2025 22:30:00 -0000

The issue has been fully resolved and all systems are operating normally. We have identified the root cause and deployed fixes to prevent recurrence.

Temporary Delays in Event Processing

Tue, 30 Sep 2025 22:10:00 -0000

We experienced delays in event processing starting at approximately 5:10 PM CST. This resulted in temporary delays for message sending/receiving, typing indicators, reactions, and related API functionality. The issue was resolved within 20 minutes. We have identified the root cause and are deploying fixes to prevent this from occurring again. All systems are now operating normally.

Processing Delays

Mon, 29 Sep 2025 22:21:00 -0000

The delays in event processing have significantly improved. Message sending/receiving, typing indicators, reactions, and related API functionality are now processing normally. We are continuing to monitor the situation and investigate the root cause.

Processing Delays

Mon, 29 Sep 2025 22:10:00 -0000

We are currently investigating delays in event processing. This may result in delayed message sending/receiving, typing indicators, reactions, and related API functionality. We are actively working to resolve this issue.

Linq Blue outage due to provider maintenance

Fri, 05 Sep 2025 11:34:00 -0000

Between 11:50pm and 3:18am CDT, Linq Blue experienced an outage due to an upstream provider maintenance event that impacted our network. Service has been fully restored and systems are operating normally.

Data infrastructure maintenance

Fri, 22 Aug 2025 05:31:37 -0000

Maintenance completed

Data infrastructure maintenance

Fri, 22 Aug 2025 03:00:00 -0000

Data infrastructure maintenance is finished.

Scheduled network upgrade - Linq Blue service interruption expected

Fri, 18 Jul 2025 04:00:00 -0000

We’ll be upgrading our network tonight at 11 PM CT, which will temporarily impact Linq Blue messaging. - Messages won’t send during the maintenance window. - Any messages received during this time will be synced once we're back online. - Messages attempted during the outage will need to be resent manually. Thanks for your patience as we make improvements.

Scheduled network maintenance - Linq Blue service interruption

Wed, 16 Jul 2025 09:00:14 -0000

Due to scheduled maintenance by a service provider, Linq Blue services may experience interruptions on July 15-16, 2025, from 11:00 PM to 5:00 AM CST. During this maintenance window: - Sending iMessages through Linq Blue will be temporarily unavailable - Any Blue messages received during the outage will show up for Blue users after the network maintenance is over Our provider estimates a 30-minute service interruption within this window. We do not expect to be down for the entire 6-hour period, but recommend planning accordingly if you have critical iMessage campaigns scheduled during this time. We apologize for any inconvenience and appreciate your patience as we work with our provider to ensure continued reliable service.

Brief network maintenance

Wed, 16 Jul 2025 03:00:32 -0000

We are preparing for network upgrades tonight, July 15, 2025, at 10:00 PM CST for approximately 15 minutes. During this maintenance window: - Sending iMessages through Linq Blue will be temporarily unavailable - Any Blue messages received during the outage will show up for Blue users after the network maintenance is over Services may be briefly interrupted during this time.

Delay in Message Delivery for Linq Blue

Thu, 10 Jul 2025 13:04:00 -0000

Message delivery for Linq Blue has remained stable, and both sending and receiving are fully operational. This incident is now resolved.

Delay in Message Delivery for Linq Blue

Thu, 10 Jul 2025 00:02:00 -0000

Linq Blue performance has returned to normal for most users. Outbound and inbound messaging are operating as expected. We’ll continue monitoring and will share a final update once the issue is fully resolved.

Delay in Message Delivery for Linq Blue

Wed, 09 Jul 2025 17:45:00 -0000

We’re seeing stable performance overall for Linq Blue. Sending is operating normally, but some inbound messages to Blue numbers may still experience slight delays. We’re continuing to monitor closely and will post another update when fully resolved.

Delay in Message Delivery for Linq Blue

Wed, 09 Jul 2025 03:19:00 -0000

Sending messages through Linq Blue is working as expected. However, inbound messages to Blue numbers may still be delayed by a few minutes in some cases. We’re continuing to monitor and work on full resolution.

Delay in Message Delivery for Linq Blue

Tue, 08 Jul 2025 23:31:00 -0000

We're investigating intermittent delays affecting message sending and delivery in Linq Blue. Not all users are impacted, but some may experience a delay of a few minutes. We're working to resolve this as quickly as possible.

Service instability due to downstream provider outage

Wed, 11 Jun 2025 14:00:00 -0000

We’ve completed our investigation into yesterday’s incident and confirmed the root cause was related to infrastructure outages from two providers: Heroku and OpenAI. - At 06:03 UTC on June 10, Heroku began experiencing widespread issues that affected Linq Phone and Blue messaging reliability. - Around 11:00 UTC, OpenAI also began seeing elevated API error rates which impacted call processing and summarization. - OpenAI’s API was restored around 23:32 UTC on June 10. - Heroku confirmed full resolution at 05:19 UTC on June 11. During this window, users may have seen delayed or failed message sends, call issues, or missing summaries. Everything is now operational, and we’re continuing to monitor.

Service instability due to downstream provider outage

Wed, 11 Jun 2025 10:32:00 -0000

Everything is now back to normal. We’ve resolved today’s outage affecting Blue messaging, Linq Phone calls, and SMS.

Service instability due to downstream provider outage

Tue, 10 Jun 2025 12:16:00 -0000

We’re experiencing service instability due to an issue with one of our downstream infrastructure providers. The most noticeable impact is with Blue messaging—messages may appear delayed or failed, but often still go through shortly after. You may also see slower performance or intermittent errors in the dashboard or API. Our team is actively monitoring the situation and will post updates as we learn more.

Linq Blue is Currently Experencing Issues

Sun, 11 May 2025 05:19:00 -0000

Linq Blue is Currently Experiencing Issues the team is aware and we are working on it.

API Undergoing Maintenance

Fri, 25 Apr 2025 05:31:00 -0000

API Maintenance is done. We are fully back.