Incidents reported on status page for Linq https://status.linqapp.com/ https://d1lppblt9t2x15.cloudfront.net/logos/62fd31a09db5db692a030a0ae2d71e94.png https://status.linqapp.com/ en https://status.linqapp.com/incident/830844 Sun, 01 Mar 2026 06:00:01 -0000 https://status.linqapp.com/incident/830844#eb0d8d388a5417446f3af3d68eb737ca4b3c5a42125ba2c5504b96312012c8e8 We will be performing scheduled network upgrades on Sunday, March 1st starting at 10:00 PM PST (midnight Monday CST). The maintenance window is expected to last 2 hours. During this time, the v2 and v3 APIs may be temporarily unavailable. https://status.linqapp.com/incident/830844 Sun, 01 Mar 2026 06:00:01 -0000 https://status.linqapp.com/incident/830844#eb0d8d388a5417446f3af3d68eb737ca4b3c5a42125ba2c5504b96312012c8e8 We will be performing scheduled network upgrades on Sunday, March 1st starting at 10:00 PM PST (midnight Monday CST). The maintenance window is expected to last 2 hours. During this time, the v2 and v3 APIs may be temporarily unavailable. https://status.linqapp.com/incident/831533 Mon, 23 Feb 2026 19:12:00 -0000 https://status.linqapp.com/incident/831533#ad855d6dcfa7a799ae2e9ba1f524fb95d1cafcf77eda010cbe7b12ec66b6beae This incident has been resolved. Linq Blue API v2 queues and performance have fully returned to normal. Thank you for your patience. https://status.linqapp.com/incident/831533 Mon, 23 Feb 2026 19:10:00 -0000 https://status.linqapp.com/incident/831533#ced6330d576484b1d203307fda7812b7f4d480764d4e2712eaa126a8ece6a392 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. https://status.linqapp.com/incident/831533 Mon, 23 Feb 2026 18:55:00 -0000 https://status.linqapp.com/incident/831533#9bf7002f8ae3d7a60d8c661f4147c095e7eae7659c9d9b689e97007b75ecb7c6 Note: The V3 API is not affected by this incident and is operating normally. https://status.linqapp.com/incident/831533 Mon, 23 Feb 2026 18:51:00 -0000 https://status.linqapp.com/incident/831533#90aefc92651a54f86a2af31f76ab32455a305b052d37fdc58491d076c7f9c9ef 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. https://status.linqapp.com/incident/831533 Mon, 23 Feb 2026 18:44:00 -0000 https://status.linqapp.com/incident/831533#00508e4817267de07405d785023e843873d4f8e582769ecaada4e28f59e281e0 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. https://status.linqapp.com/incident/829802 Fri, 20 Feb 2026 22:05:00 -0000 https://status.linqapp.com/incident/829802#a26ec11bf3218f8e8187ac6473bcb016b31a64b9445dd7475615096c3595a78e We have implemented a fix and are continuing to monitor the service and any further remediations. https://status.linqapp.com/incident/829802 Fri, 20 Feb 2026 22:00:00 -0000 https://status.linqapp.com/incident/829802#3a88f723c7542c0c7b1137a735c33740022cca3a7177f626ce17925df3710843 V3 Platform API is currently experiencing elevated 5xx errors. Investigating https://status.linqapp.com/incident/829581 Fri, 20 Feb 2026 15:54:00 -0000 https://status.linqapp.com/incident/829581#b9aaabed3129cc681213c3af83b45b8174075d6c7f9e3ccaab0266b80ba88c01 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. https://status.linqapp.com/incident/829581 Fri, 20 Feb 2026 15:28:00 -0000 https://status.linqapp.com/incident/829581#b791f992c6d2196195ec0971049d41ca8b65f820361ef29943285a5cac9a5315 We have identified the root cause of the incident and are in the process of implementing a fix for it. https://status.linqapp.com/incident/829581 Fri, 20 Feb 2026 15:15:00 -0000 https://status.linqapp.com/incident/829581#1a604093154f0fa73b259a5a655c03f6669f558bdd9fb2c3d2a153d8b6f094c2 The Linq Blue API is currently experiencing service degradation for some partners. We're currently investigating and will update soon with an update. https://status.linqapp.com/incident/822772 Tue, 10 Feb 2026 23:20:00 -0000 https://status.linqapp.com/incident/822772#c96eb199508a9a0e373ef9c5f5a827888751906761b22b5895ee8eba78dec2de The service degradation for Linq Blue and it's API have been resolved. https://status.linqapp.com/incident/822772 Tue, 10 Feb 2026 23:20:00 -0000 https://status.linqapp.com/incident/822772#c96eb199508a9a0e373ef9c5f5a827888751906761b22b5895ee8eba78dec2de The service degradation for Linq Blue and it's API have been resolved. https://status.linqapp.com/incident/822772 Tue, 10 Feb 2026 21:15:00 -0000 https://status.linqapp.com/incident/822772#4b2eb58bb1d376019ab57a30a86e2ae6beeef0bceb9bce195404b64fc9b397ad 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. https://status.linqapp.com/incident/822772 Tue, 10 Feb 2026 21:15:00 -0000 https://status.linqapp.com/incident/822772#4b2eb58bb1d376019ab57a30a86e2ae6beeef0bceb9bce195404b64fc9b397ad 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. https://status.linqapp.com/ Tue, 03 Feb 2026 17:46:49 +0000 https://status.linqapp.com/#a7691de71f7ee168825935427f3899f1fbbd9523c7c9da91a606221ad0aba210 Linq Blue API recovered https://status.linqapp.com/ Tue, 03 Feb 2026 16:46:09 +0000 https://status.linqapp.com/#a7691de71f7ee168825935427f3899f1fbbd9523c7c9da91a606221ad0aba210 Linq Blue API went down https://status.linqapp.com/incident/815639 Sat, 31 Jan 2026 08:18:00 -0000 https://status.linqapp.com/incident/815639#5379231b11917996b8e36d9a930f33cff505869ae89833d6f345b4786d2a661e **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 https://status.linqapp.com/incident/815639 Sat, 31 Jan 2026 08:18:00 -0000 https://status.linqapp.com/incident/815639#5379231b11917996b8e36d9a930f33cff505869ae89833d6f345b4786d2a661e **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 https://status.linqapp.com/incident/815639 Sat, 31 Jan 2026 06:38:00 -0000 https://status.linqapp.com/incident/815639#fff2869b865d1e3a3ed14de3632775950bb359ca95ef13146d5c7c075bee8d2d 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. https://status.linqapp.com/incident/815639 Sat, 31 Jan 2026 06:38:00 -0000 https://status.linqapp.com/incident/815639#fff2869b865d1e3a3ed14de3632775950bb359ca95ef13146d5c7c075bee8d2d 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. https://status.linqapp.com/incident/813801 Wed, 28 Jan 2026 20:11:00 -0000 https://status.linqapp.com/incident/813801#60fd4c4a7eaa69130acc1118c89a1b32abc019d6eed78fdf4e42bea6abe03460 **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. https://status.linqapp.com/incident/812713 Wed, 28 Jan 2026 00:11:00 -0000 https://status.linqapp.com/incident/812713#e3b4db6dac573bbfd662a84fc926ae22fd37122d2987db1e3b70d311b540ee12 We've seen better latency on our V2 API today and have continued to find efficiencies and improve things. Marking this status as resolved. https://status.linqapp.com/incident/812713 Tue, 27 Jan 2026 13:07:00 -0000 https://status.linqapp.com/incident/812713#a71748083568003f92595a6cbe5e3b12bab92c05eeb65008c82e7a7378e02913 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 18:19:00 -0000 https://status.linqapp.com/incident/809414#f96e08e139d2593bc07f6446374930a1cbdd4f3c5af50a0d9023ce3008c82aec 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 18:19:00 -0000 https://status.linqapp.com/incident/809414#f96e08e139d2593bc07f6446374930a1cbdd4f3c5af50a0d9023ce3008c82aec 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 18:19:00 -0000 https://status.linqapp.com/incident/809414#f96e08e139d2593bc07f6446374930a1cbdd4f3c5af50a0d9023ce3008c82aec 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 10:03:00 -0000 https://status.linqapp.com/incident/809414#8b7788649e384fff543a520e9b45d12db8517f308f1ed09c518567c96e9b3124 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 10:03:00 -0000 https://status.linqapp.com/incident/809414#8b7788649e384fff543a520e9b45d12db8517f308f1ed09c518567c96e9b3124 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 10:03:00 -0000 https://status.linqapp.com/incident/809414#8b7788649e384fff543a520e9b45d12db8517f308f1ed09c518567c96e9b3124 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 08:55:00 -0000 https://status.linqapp.com/incident/809414#63dfbb3ca804e186c60e5f9cdfd29a456504cfbc3eb932e794240645841ae68a V3 API is looking much more recovered. We are continuing to monitor the situation and will provide further updates. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 08:55:00 -0000 https://status.linqapp.com/incident/809414#63dfbb3ca804e186c60e5f9cdfd29a456504cfbc3eb932e794240645841ae68a V3 API is looking much more recovered. We are continuing to monitor the situation and will provide further updates. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 08:55:00 -0000 https://status.linqapp.com/incident/809414#63dfbb3ca804e186c60e5f9cdfd29a456504cfbc3eb932e794240645841ae68a V3 API is looking much more recovered. We are continuing to monitor the situation and will provide further updates. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 08:18:00 -0000 https://status.linqapp.com/incident/809414#1bc9796e2b23eb038d3b8e6e8da5fadda271a18ac0db2e0d0731964e3ee385a4 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 08:18:00 -0000 https://status.linqapp.com/incident/809414#1bc9796e2b23eb038d3b8e6e8da5fadda271a18ac0db2e0d0731964e3ee385a4 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 08:18:00 -0000 https://status.linqapp.com/incident/809414#1bc9796e2b23eb038d3b8e6e8da5fadda271a18ac0db2e0d0731964e3ee385a4 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 06:37:00 -0000 https://status.linqapp.com/incident/809414#158f780d3f453ada77e7b0b9237ad73b8dfcaab6859ee181642f49cd7be465be 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 06:37:00 -0000 https://status.linqapp.com/incident/809414#158f780d3f453ada77e7b0b9237ad73b8dfcaab6859ee181642f49cd7be465be 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 06:37:00 -0000 https://status.linqapp.com/incident/809414#158f780d3f453ada77e7b0b9237ad73b8dfcaab6859ee181642f49cd7be465be 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. https://status.linqapp.com/ Thu, 22 Jan 2026 06:33:39 +0000 https://status.linqapp.com/#06da9d2415b32f946041694e40a3d566af3ee32cc7000706ecee0900906299b9 Linq Blue API recovered https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 05:48:00 -0000 https://status.linqapp.com/incident/809414#94c061a1d565787b6dfec8d5e959ecde4054e1e73d03472e2d1a13a89e50a9a0 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 05:48:00 -0000 https://status.linqapp.com/incident/809414#94c061a1d565787b6dfec8d5e959ecde4054e1e73d03472e2d1a13a89e50a9a0 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 05:48:00 -0000 https://status.linqapp.com/incident/809414#94c061a1d565787b6dfec8d5e959ecde4054e1e73d03472e2d1a13a89e50a9a0 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. https://status.linqapp.com/ Thu, 22 Jan 2026 05:41:44 +0000 https://status.linqapp.com/#06da9d2415b32f946041694e40a3d566af3ee32cc7000706ecee0900906299b9 Linq Blue API went down https://status.linqapp.com/ Thu, 22 Jan 2026 05:39:38 +0000 https://status.linqapp.com/#f178a9b46cb58fe562459cf90372b60b9815cf239145cd620a1c581b74993bfc Linq Blue API recovered https://status.linqapp.com/ Thu, 22 Jan 2026 05:31:54 +0000 https://status.linqapp.com/#f178a9b46cb58fe562459cf90372b60b9815cf239145cd620a1c581b74993bfc Linq Blue API went down https://status.linqapp.com/ Thu, 22 Jan 2026 05:27:39 +0000 https://status.linqapp.com/#44f33ae76a8b26bc2e7fcce23ea7950fa7944e006d8710523d2cf39e1997d608 Linq Blue API recovered https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 04:50:00 -0000 https://status.linqapp.com/incident/809414#6c31872085757bd78043f7387e6729240aa6b9d0e9b11475e6e5002cf94b26ac 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 04:50:00 -0000 https://status.linqapp.com/incident/809414#6c31872085757bd78043f7387e6729240aa6b9d0e9b11475e6e5002cf94b26ac 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. https://status.linqapp.com/incident/809414 Thu, 22 Jan 2026 04:50:00 -0000 https://status.linqapp.com/incident/809414#6c31872085757bd78043f7387e6729240aa6b9d0e9b11475e6e5002cf94b26ac 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. https://status.linqapp.com/ Thu, 22 Jan 2026 04:33:11 +0000 https://status.linqapp.com/#44f33ae76a8b26bc2e7fcce23ea7950fa7944e006d8710523d2cf39e1997d608 Linq Blue API went down https://status.linqapp.com/incident/808349 Wed, 21 Jan 2026 16:57:00 -0000 https://status.linqapp.com/incident/808349#65f197aaba392feda2c437d057b84f3e65ca0d9f42b56a64d6072933bccea9d3 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. https://status.linqapp.com/incident/808349 Wed, 21 Jan 2026 16:57:00 -0000 https://status.linqapp.com/incident/808349#65f197aaba392feda2c437d057b84f3e65ca0d9f42b56a64d6072933bccea9d3 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. https://status.linqapp.com/incident/808349 Wed, 21 Jan 2026 16:57:00 -0000 https://status.linqapp.com/incident/808349#65f197aaba392feda2c437d057b84f3e65ca0d9f42b56a64d6072933bccea9d3 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. https://status.linqapp.com/incident/808349 Wed, 21 Jan 2026 16:57:00 -0000 https://status.linqapp.com/incident/808349#65f197aaba392feda2c437d057b84f3e65ca0d9f42b56a64d6072933bccea9d3 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. https://status.linqapp.com/incident/808349 Tue, 20 Jan 2026 19:37:00 -0000 https://status.linqapp.com/incident/808349#c45c38526746d515c28512a033f964ad50d7e7bfc0ea0ef9d8ee389f443d7528 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. https://status.linqapp.com/incident/808349 Tue, 20 Jan 2026 19:37:00 -0000 https://status.linqapp.com/incident/808349#c45c38526746d515c28512a033f964ad50d7e7bfc0ea0ef9d8ee389f443d7528 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. https://status.linqapp.com/incident/808349 Tue, 20 Jan 2026 19:37:00 -0000 https://status.linqapp.com/incident/808349#c45c38526746d515c28512a033f964ad50d7e7bfc0ea0ef9d8ee389f443d7528 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. https://status.linqapp.com/incident/808349 Tue, 20 Jan 2026 19:37:00 -0000 https://status.linqapp.com/incident/808349#c45c38526746d515c28512a033f964ad50d7e7bfc0ea0ef9d8ee389f443d7528 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. https://status.linqapp.com/ Sat, 10 Jan 2026 19:10:47 +0000 https://status.linqapp.com/#e45231fdd872084a2d51c1fadb7533b5033a12342533d1e2bd8efd583f701177 Linq Blue recovered https://status.linqapp.com/ Sat, 10 Jan 2026 19:10:47 +0000 https://status.linqapp.com/#e45231fdd872084a2d51c1fadb7533b5033a12342533d1e2bd8efd583f701177 Platform API recovered https://status.linqapp.com/ Sat, 10 Jan 2026 19:05:28 +0000 https://status.linqapp.com/#e45231fdd872084a2d51c1fadb7533b5033a12342533d1e2bd8efd583f701177 Linq Blue went down https://status.linqapp.com/ Sat, 10 Jan 2026 19:05:28 +0000 https://status.linqapp.com/#e45231fdd872084a2d51c1fadb7533b5033a12342533d1e2bd8efd583f701177 Platform API went down https://status.linqapp.com/incident/798971 Mon, 05 Jan 2026 23:09:00 -0000 https://status.linqapp.com/incident/798971#4d5c5cd9a566a846c4d413f1c3d0728f79066ea775726797b10e730b41a7a041 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. https://status.linqapp.com/incident/798971 Mon, 05 Jan 2026 23:09:00 -0000 https://status.linqapp.com/incident/798971#4d5c5cd9a566a846c4d413f1c3d0728f79066ea775726797b10e730b41a7a041 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. https://status.linqapp.com/incident/798971 Mon, 05 Jan 2026 23:09:00 -0000 https://status.linqapp.com/incident/798971#4d5c5cd9a566a846c4d413f1c3d0728f79066ea775726797b10e730b41a7a041 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. https://status.linqapp.com/incident/798971 Mon, 05 Jan 2026 23:09:00 -0000 https://status.linqapp.com/incident/798971#4d5c5cd9a566a846c4d413f1c3d0728f79066ea775726797b10e730b41a7a041 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. https://status.linqapp.com/incident/798971 Mon, 05 Jan 2026 23:09:00 -0000 https://status.linqapp.com/incident/798971#4d5c5cd9a566a846c4d413f1c3d0728f79066ea775726797b10e730b41a7a041 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. https://status.linqapp.com/incident/798971 Mon, 05 Jan 2026 23:01:00 -0000 https://status.linqapp.com/incident/798971#13cf7bd37c6bba0035e5e0d8c07835868a84488f2cc6f2d146b000e35081ceef 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. https://status.linqapp.com/incident/798971 Mon, 05 Jan 2026 23:01:00 -0000 https://status.linqapp.com/incident/798971#13cf7bd37c6bba0035e5e0d8c07835868a84488f2cc6f2d146b000e35081ceef 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. https://status.linqapp.com/incident/798971 Mon, 05 Jan 2026 23:01:00 -0000 https://status.linqapp.com/incident/798971#13cf7bd37c6bba0035e5e0d8c07835868a84488f2cc6f2d146b000e35081ceef 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. https://status.linqapp.com/incident/798971 Mon, 05 Jan 2026 23:01:00 -0000 https://status.linqapp.com/incident/798971#13cf7bd37c6bba0035e5e0d8c07835868a84488f2cc6f2d146b000e35081ceef 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. https://status.linqapp.com/incident/798971 Mon, 05 Jan 2026 23:01:00 -0000 https://status.linqapp.com/incident/798971#13cf7bd37c6bba0035e5e0d8c07835868a84488f2cc6f2d146b000e35081ceef 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 12:00:00 -0000 https://status.linqapp.com/incident/765275#93f2901a49d4f1080bfb71dfff58b2e74f3081419699fbabec2a33f932bbdc1c Maintenance completed https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 12:00:00 -0000 https://status.linqapp.com/incident/765275#93f2901a49d4f1080bfb71dfff58b2e74f3081419699fbabec2a33f932bbdc1c Maintenance completed https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 12:00:00 -0000 https://status.linqapp.com/incident/765275#93f2901a49d4f1080bfb71dfff58b2e74f3081419699fbabec2a33f932bbdc1c Maintenance completed https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 12:00:00 -0000 https://status.linqapp.com/incident/765275#93f2901a49d4f1080bfb71dfff58b2e74f3081419699fbabec2a33f932bbdc1c Maintenance completed https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 12:00:00 -0000 https://status.linqapp.com/incident/765275#93f2901a49d4f1080bfb71dfff58b2e74f3081419699fbabec2a33f932bbdc1c Maintenance completed https://status.linqapp.com/ Fri, 12 Dec 2025 11:12:38 +0000 https://status.linqapp.com/#54ae1f201f622b0743ca5822fb7e5d858b51f9ca6486c3705b9a504f9ab1db40 Linq Phone recovered https://status.linqapp.com/ Fri, 12 Dec 2025 11:12:38 +0000 https://status.linqapp.com/#192fa6a15a5cab062cf82a94d6d5e81883dfde79b56c2cc5d57b5d24ee958837 Linq Blue recovered https://status.linqapp.com/ Fri, 12 Dec 2025 11:12:38 +0000 https://status.linqapp.com/#192fa6a15a5cab062cf82a94d6d5e81883dfde79b56c2cc5d57b5d24ee958837 Platform API recovered https://status.linqapp.com/ Fri, 12 Dec 2025 10:56:02 +0000 https://status.linqapp.com/#96a76351270f2ce9fe08b0655ac21d163ab397b4aa581f69bf5de2d4a03478ec Linq Blue API recovered https://status.linqapp.com/ Fri, 12 Dec 2025 10:36:10 +0000 https://status.linqapp.com/#96a76351270f2ce9fe08b0655ac21d163ab397b4aa581f69bf5de2d4a03478ec Linq Blue API went down https://status.linqapp.com/ Fri, 12 Dec 2025 10:02:32 +0000 https://status.linqapp.com/#54ae1f201f622b0743ca5822fb7e5d858b51f9ca6486c3705b9a504f9ab1db40 Linq Phone went down https://status.linqapp.com/ Fri, 12 Dec 2025 10:01:33 +0000 https://status.linqapp.com/#192fa6a15a5cab062cf82a94d6d5e81883dfde79b56c2cc5d57b5d24ee958837 Linq Blue went down https://status.linqapp.com/ Fri, 12 Dec 2025 10:01:33 +0000 https://status.linqapp.com/#192fa6a15a5cab062cf82a94d6d5e81883dfde79b56c2cc5d57b5d24ee958837 Platform API went down https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/765275 Fri, 12 Dec 2025 10:00:00 -0000 https://status.linqapp.com/incident/765275#4e4c49192809dd4fec34e704b565dbcdf11626f59c5daefa8cb84209b6c6226d 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. https://status.linqapp.com/incident/776066 Fri, 28 Nov 2025 19:55:00 -0000 https://status.linqapp.com/incident/776066#72d55b450e38a2a8254711f7ac68eea84238efa33b1323b02dc13148ac0adb7c 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. https://status.linqapp.com/incident/776066 Fri, 28 Nov 2025 19:55:00 -0000 https://status.linqapp.com/incident/776066#72d55b450e38a2a8254711f7ac68eea84238efa33b1323b02dc13148ac0adb7c 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. https://status.linqapp.com/incident/776066 Fri, 28 Nov 2025 19:55:00 -0000 https://status.linqapp.com/incident/776066#72d55b450e38a2a8254711f7ac68eea84238efa33b1323b02dc13148ac0adb7c 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. https://status.linqapp.com/incident/776066 Fri, 28 Nov 2025 19:55:00 -0000 https://status.linqapp.com/incident/776066#72d55b450e38a2a8254711f7ac68eea84238efa33b1323b02dc13148ac0adb7c 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. https://status.linqapp.com/incident/776066 Fri, 28 Nov 2025 19:55:00 -0000 https://status.linqapp.com/incident/776066#72d55b450e38a2a8254711f7ac68eea84238efa33b1323b02dc13148ac0adb7c 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 04:18:00 -0000 https://status.linqapp.com/incident/772832#8e19bd07b6fb0ed408892312ab94fcf9d36b9fa7347fdb1015b21784bccf608c 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 04:18:00 -0000 https://status.linqapp.com/incident/772832#8e19bd07b6fb0ed408892312ab94fcf9d36b9fa7347fdb1015b21784bccf608c 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 03:59:00 -0000 https://status.linqapp.com/incident/772832#4bdf2bf8ffca779dbe9c3f367cac52741a3d7b22a2c55276b29383f801c0ed93 We've seen stability since 9:51 PM CST. We're continuing to monitor closely while our downstream provider works on the root cause. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 03:59:00 -0000 https://status.linqapp.com/incident/772832#4bdf2bf8ffca779dbe9c3f367cac52741a3d7b22a2c55276b29383f801c0ed93 We've seen stability since 9:51 PM CST. We're continuing to monitor closely while our downstream provider works on the root cause. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 03:48:00 -0000 https://status.linqapp.com/incident/772832#ec1797c770db14fc235f6ecaee942d4f59bd144c92f98c2214a4e9d462452a19 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 03:48:00 -0000 https://status.linqapp.com/incident/772832#ec1797c770db14fc235f6ecaee942d4f59bd144c92f98c2214a4e9d462452a19 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 03:32:00 -0000 https://status.linqapp.com/incident/772832#8f39dc7f68553b7b35026fe838e1fcd01a003e7b4567ee2bb86d0e66efa8d0f0 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 03:32:00 -0000 https://status.linqapp.com/incident/772832#8f39dc7f68553b7b35026fe838e1fcd01a003e7b4567ee2bb86d0e66efa8d0f0 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 03:17:00 -0000 https://status.linqapp.com/incident/772832#1536b08fe425c9c980499d0ec03f036db52186de7fe6c2fe0624f9d3ba46a76e 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 03:17:00 -0000 https://status.linqapp.com/incident/772832#1536b08fe425c9c980499d0ec03f036db52186de7fe6c2fe0624f9d3ba46a76e 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 02:58:00 -0000 https://status.linqapp.com/incident/772832#1d943f8cb5e881aa7eea4f7d8d9afed799c30ebc6340aa724a7dd1ec1c85e3ae 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 02:58:00 -0000 https://status.linqapp.com/incident/772832#1d943f8cb5e881aa7eea4f7d8d9afed799c30ebc6340aa724a7dd1ec1c85e3ae 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 02:50:00 -0000 https://status.linqapp.com/incident/772832#be3783892257428dded5dc525b343661f0577b4dea0dd086400067845c08be8e 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 02:50:00 -0000 https://status.linqapp.com/incident/772832#be3783892257428dded5dc525b343661f0577b4dea0dd086400067845c08be8e 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 02:30:00 -0000 https://status.linqapp.com/incident/772832#b15e14f940f63dc2a26e1a526fdb121de3b262a475fcc491dfddac3b672a3d0b 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 02:30:00 -0000 https://status.linqapp.com/incident/772832#b15e14f940f63dc2a26e1a526fdb121de3b262a475fcc491dfddac3b672a3d0b 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 02:28:00 -0000 https://status.linqapp.com/incident/772832#8ece4b67815f402aa8104919cd135d7186144d3e502ed678baf4ae58b4bad8af 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 02:28:00 -0000 https://status.linqapp.com/incident/772832#8ece4b67815f402aa8104919cd135d7186144d3e502ed678baf4ae58b4bad8af 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. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 02:02:00 -0000 https://status.linqapp.com/incident/772832#d7c37b1bf1d98f83c1e6f03183f956bdb8e76752342ad87fc715f221531b3e42 We’re investigating an incident affecting Linq Blue. https://status.linqapp.com/incident/772832 Mon, 24 Nov 2025 02:02:00 -0000 https://status.linqapp.com/incident/772832#d7c37b1bf1d98f83c1e6f03183f956bdb8e76752342ad87fc715f221531b3e42 We’re investigating an incident affecting Linq Blue. https://status.linqapp.com/incident/769805 Thu, 20 Nov 2025 05:13:00 -0000 https://status.linqapp.com/incident/769805#f4f4ca140b08e3b33557013a9916a9ca4fa24b388da648d3b7e910abc927d39f 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. https://status.linqapp.com/incident/769805 Thu, 20 Nov 2025 05:13:00 -0000 https://status.linqapp.com/incident/769805#f4f4ca140b08e3b33557013a9916a9ca4fa24b388da648d3b7e910abc927d39f 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. https://status.linqapp.com/incident/769805 Thu, 20 Nov 2025 00:17:00 -0000 https://status.linqapp.com/incident/769805#49d44cebe33407b41e2dedebcd9f10576861f13b90694413dae05f5f2a2f017f 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. https://status.linqapp.com/incident/769805 Thu, 20 Nov 2025 00:17:00 -0000 https://status.linqapp.com/incident/769805#49d44cebe33407b41e2dedebcd9f10576861f13b90694413dae05f5f2a2f017f 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. https://status.linqapp.com/incident/769805 Wed, 19 Nov 2025 14:39:00 -0000 https://status.linqapp.com/incident/769805#664621ec44d2fced8125994a6cd999e841a9dc1843d3bbb8f517423b91f41d04 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. https://status.linqapp.com/incident/769805 Wed, 19 Nov 2025 14:39:00 -0000 https://status.linqapp.com/incident/769805#664621ec44d2fced8125994a6cd999e841a9dc1843d3bbb8f517423b91f41d04 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. https://status.linqapp.com/incident/769805 Wed, 19 Nov 2025 05:38:00 -0000 https://status.linqapp.com/incident/769805#19452f2dba461fd2a9a9d8488db466a9d845e52eb45ad3224fb9c60da2a2a48f 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. https://status.linqapp.com/incident/769805 Wed, 19 Nov 2025 05:38:00 -0000 https://status.linqapp.com/incident/769805#19452f2dba461fd2a9a9d8488db466a9d845e52eb45ad3224fb9c60da2a2a48f 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. https://status.linqapp.com/incident/769805 Wed, 19 Nov 2025 05:15:00 -0000 https://status.linqapp.com/incident/769805#4f402e4104557a4cfdedc906ac4d0a712c70dc84bb11aecd7057d2daaa2dd78e 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. https://status.linqapp.com/incident/769805 Wed, 19 Nov 2025 05:15:00 -0000 https://status.linqapp.com/incident/769805#4f402e4104557a4cfdedc906ac4d0a712c70dc84bb11aecd7057d2daaa2dd78e 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. https://status.linqapp.com/incident/769805 Wed, 19 Nov 2025 03:15:00 -0000 https://status.linqapp.com/incident/769805#32f8200a0cfda7912e4d039c77b987c9f1c55b6af96653d12bdd6de3f9366c13 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. https://status.linqapp.com/incident/769805 Wed, 19 Nov 2025 03:15:00 -0000 https://status.linqapp.com/incident/769805#32f8200a0cfda7912e4d039c77b987c9f1c55b6af96653d12bdd6de3f9366c13 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. https://status.linqapp.com/incident/769805 Wed, 19 Nov 2025 02:21:00 -0000 https://status.linqapp.com/incident/769805#83bf1974a7f244a4f8878942006232e611392a37308116b343beb31d6eb398a4 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. https://status.linqapp.com/incident/769805 Wed, 19 Nov 2025 02:21:00 -0000 https://status.linqapp.com/incident/769805#83bf1974a7f244a4f8878942006232e611392a37308116b343beb31d6eb398a4 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. https://status.linqapp.com/incident/769805 Wed, 19 Nov 2025 01:30:00 -0000 https://status.linqapp.com/incident/769805#117856fcb163311dc308b8430472df57717c93f6440da127133f1d91f82682ed 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. https://status.linqapp.com/incident/769805 Wed, 19 Nov 2025 01:30:00 -0000 https://status.linqapp.com/incident/769805#117856fcb163311dc308b8430472df57717c93f6440da127133f1d91f82682ed 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. https://status.linqapp.com/incident/768898 Tue, 18 Nov 2025 16:41:00 -0000 https://status.linqapp.com/incident/768898#f040492a4936e470f8f48c42e14a89c0650165d1dae53440d7798e1164f52304 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/ https://status.linqapp.com/incident/768898 Tue, 18 Nov 2025 16:41:00 -0000 https://status.linqapp.com/incident/768898#f040492a4936e470f8f48c42e14a89c0650165d1dae53440d7798e1164f52304 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/ https://status.linqapp.com/incident/768898 Tue, 18 Nov 2025 16:41:00 -0000 https://status.linqapp.com/incident/768898#f040492a4936e470f8f48c42e14a89c0650165d1dae53440d7798e1164f52304 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/ https://status.linqapp.com/incident/768898 Tue, 18 Nov 2025 16:41:00 -0000 https://status.linqapp.com/incident/768898#f040492a4936e470f8f48c42e14a89c0650165d1dae53440d7798e1164f52304 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/ https://status.linqapp.com/incident/768898 Tue, 18 Nov 2025 16:41:00 -0000 https://status.linqapp.com/incident/768898#f040492a4936e470f8f48c42e14a89c0650165d1dae53440d7798e1164f52304 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/ https://status.linqapp.com/incident/768898 Tue, 18 Nov 2025 13:31:00 -0000 https://status.linqapp.com/incident/768898#7c0526ba93d9586f9fa55e0f4d298fc36989368f5dd9937d2a578fe7b20ae3ad 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. https://status.linqapp.com/incident/768898 Tue, 18 Nov 2025 13:31:00 -0000 https://status.linqapp.com/incident/768898#7c0526ba93d9586f9fa55e0f4d298fc36989368f5dd9937d2a578fe7b20ae3ad 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. https://status.linqapp.com/incident/768898 Tue, 18 Nov 2025 13:31:00 -0000 https://status.linqapp.com/incident/768898#7c0526ba93d9586f9fa55e0f4d298fc36989368f5dd9937d2a578fe7b20ae3ad 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. https://status.linqapp.com/incident/768898 Tue, 18 Nov 2025 13:31:00 -0000 https://status.linqapp.com/incident/768898#7c0526ba93d9586f9fa55e0f4d298fc36989368f5dd9937d2a578fe7b20ae3ad 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. https://status.linqapp.com/incident/768898 Tue, 18 Nov 2025 13:31:00 -0000 https://status.linqapp.com/incident/768898#7c0526ba93d9586f9fa55e0f4d298fc36989368f5dd9937d2a578fe7b20ae3ad 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. https://status.linqapp.com/incident/768898 Tue, 18 Nov 2025 11:48:00 -0000 https://status.linqapp.com/incident/768898#4297987b68f92f84970c2043d59d1ca4c4c078209539a7f1d41e742f0ab8d014 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/ https://status.linqapp.com/incident/768898 Tue, 18 Nov 2025 11:48:00 -0000 https://status.linqapp.com/incident/768898#4297987b68f92f84970c2043d59d1ca4c4c078209539a7f1d41e742f0ab8d014 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/ https://status.linqapp.com/incident/768898 Tue, 18 Nov 2025 11:48:00 -0000 https://status.linqapp.com/incident/768898#4297987b68f92f84970c2043d59d1ca4c4c078209539a7f1d41e742f0ab8d014 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/ https://status.linqapp.com/incident/768898 Tue, 18 Nov 2025 11:48:00 -0000 https://status.linqapp.com/incident/768898#4297987b68f92f84970c2043d59d1ca4c4c078209539a7f1d41e742f0ab8d014 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/ https://status.linqapp.com/incident/768898 Tue, 18 Nov 2025 11:48:00 -0000 https://status.linqapp.com/incident/768898#4297987b68f92f84970c2043d59d1ca4c4c078209539a7f1d41e742f0ab8d014 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/ https://status.linqapp.com/incident/758689 Wed, 05 Nov 2025 18:43:00 -0000 https://status.linqapp.com/incident/758689#5d009761172e9569db092ed53021380f08960d458fa06a3ddf5e32c985fc680f 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 https://status.linqapp.com/incident/758689 Wed, 05 Nov 2025 18:43:00 -0000 https://status.linqapp.com/incident/758689#5d009761172e9569db092ed53021380f08960d458fa06a3ddf5e32c985fc680f 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 https://status.linqapp.com/incident/748821 Tue, 28 Oct 2025 06:45:10 -0000 https://status.linqapp.com/incident/748821#f5516ef8dc3280a26c21ad945fb56af159e21a26e01b7e8a328615fa7d45b57e Maintenance completed https://status.linqapp.com/incident/748821 Tue, 28 Oct 2025 06:45:10 -0000 https://status.linqapp.com/incident/748821#f5516ef8dc3280a26c21ad945fb56af159e21a26e01b7e8a328615fa7d45b57e Maintenance completed https://status.linqapp.com/incident/748821 Tue, 28 Oct 2025 04:00:00 -0000 https://status.linqapp.com/incident/748821#64170eb72798b59fe224737be347a50fd5e4906d11fbe2bd4a7450cdb956af93 **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. https://status.linqapp.com/incident/748821 Tue, 28 Oct 2025 04:00:00 -0000 https://status.linqapp.com/incident/748821#64170eb72798b59fe224737be347a50fd5e4906d11fbe2bd4a7450cdb956af93 **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. https://status.linqapp.com/incident/748821 Tue, 28 Oct 2025 04:00:00 -0000 https://status.linqapp.com/incident/748821#64170eb72798b59fe224737be347a50fd5e4906d11fbe2bd4a7450cdb956af93 **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. https://status.linqapp.com/incident/748821 Tue, 28 Oct 2025 04:00:00 -0000 https://status.linqapp.com/incident/748821#64170eb72798b59fe224737be347a50fd5e4906d11fbe2bd4a7450cdb956af93 **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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 04:33:00 -0000 https://status.linqapp.com/incident/747405#cef083c680d481d661d95344cdcaec2266c722ef3759a245332b8ef7e92214a3 All systems fully recovered; working on root cause prevention. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 04:33:00 -0000 https://status.linqapp.com/incident/747405#cef083c680d481d661d95344cdcaec2266c722ef3759a245332b8ef7e92214a3 All systems fully recovered; working on root cause prevention. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 04:33:00 -0000 https://status.linqapp.com/incident/747405#cef083c680d481d661d95344cdcaec2266c722ef3759a245332b8ef7e92214a3 All systems fully recovered; working on root cause prevention. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 04:33:00 -0000 https://status.linqapp.com/incident/747405#cef083c680d481d661d95344cdcaec2266c722ef3759a245332b8ef7e92214a3 All systems fully recovered; working on root cause prevention. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 04:33:00 -0000 https://status.linqapp.com/incident/747405#cef083c680d481d661d95344cdcaec2266c722ef3759a245332b8ef7e92214a3 All systems fully recovered; working on root cause prevention. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 03:34:00 -0000 https://status.linqapp.com/incident/747405#a0860869f2c80aeada720a637a841de1fd253ad8d52aa7d2394d803decbfac65 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 03:34:00 -0000 https://status.linqapp.com/incident/747405#a0860869f2c80aeada720a637a841de1fd253ad8d52aa7d2394d803decbfac65 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 03:34:00 -0000 https://status.linqapp.com/incident/747405#a0860869f2c80aeada720a637a841de1fd253ad8d52aa7d2394d803decbfac65 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 03:34:00 -0000 https://status.linqapp.com/incident/747405#a0860869f2c80aeada720a637a841de1fd253ad8d52aa7d2394d803decbfac65 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 03:34:00 -0000 https://status.linqapp.com/incident/747405#a0860869f2c80aeada720a637a841de1fd253ad8d52aa7d2394d803decbfac65 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 02:37:00 -0000 https://status.linqapp.com/incident/747405#4ce3fab060e1d88edb934033408e6fc2d8738de28cff3686681ce3b44b0525b5 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 02:37:00 -0000 https://status.linqapp.com/incident/747405#4ce3fab060e1d88edb934033408e6fc2d8738de28cff3686681ce3b44b0525b5 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 02:37:00 -0000 https://status.linqapp.com/incident/747405#4ce3fab060e1d88edb934033408e6fc2d8738de28cff3686681ce3b44b0525b5 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 02:37:00 -0000 https://status.linqapp.com/incident/747405#4ce3fab060e1d88edb934033408e6fc2d8738de28cff3686681ce3b44b0525b5 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 02:37:00 -0000 https://status.linqapp.com/incident/747405#4ce3fab060e1d88edb934033408e6fc2d8738de28cff3686681ce3b44b0525b5 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 01:54:00 -0000 https://status.linqapp.com/incident/747405#f675a163d99c85ef2b5524e6263fe222fa2bf23afc3693fc90435392279b2863 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 01:54:00 -0000 https://status.linqapp.com/incident/747405#f675a163d99c85ef2b5524e6263fe222fa2bf23afc3693fc90435392279b2863 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 01:54:00 -0000 https://status.linqapp.com/incident/747405#f675a163d99c85ef2b5524e6263fe222fa2bf23afc3693fc90435392279b2863 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 01:54:00 -0000 https://status.linqapp.com/incident/747405#f675a163d99c85ef2b5524e6263fe222fa2bf23afc3693fc90435392279b2863 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 01:54:00 -0000 https://status.linqapp.com/incident/747405#f675a163d99c85ef2b5524e6263fe222fa2bf23afc3693fc90435392279b2863 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 00:18:00 -0000 https://status.linqapp.com/incident/747405#1bcadde00b228f0079f5a187786c411c68ddd956df5ca62f935aa6afeb340148 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 00:18:00 -0000 https://status.linqapp.com/incident/747405#1bcadde00b228f0079f5a187786c411c68ddd956df5ca62f935aa6afeb340148 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 00:18:00 -0000 https://status.linqapp.com/incident/747405#1bcadde00b228f0079f5a187786c411c68ddd956df5ca62f935aa6afeb340148 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 00:18:00 -0000 https://status.linqapp.com/incident/747405#1bcadde00b228f0079f5a187786c411c68ddd956df5ca62f935aa6afeb340148 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 00:18:00 -0000 https://status.linqapp.com/incident/747405#1bcadde00b228f0079f5a187786c411c68ddd956df5ca62f935aa6afeb340148 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 00:05:00 -0000 https://status.linqapp.com/incident/747405#a580b84ce3da613afe909aac962713d5a223cdcdef90ac63d362db0664dc43a5 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 00:05:00 -0000 https://status.linqapp.com/incident/747405#a580b84ce3da613afe909aac962713d5a223cdcdef90ac63d362db0664dc43a5 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 00:05:00 -0000 https://status.linqapp.com/incident/747405#a580b84ce3da613afe909aac962713d5a223cdcdef90ac63d362db0664dc43a5 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 00:05:00 -0000 https://status.linqapp.com/incident/747405#a580b84ce3da613afe909aac962713d5a223cdcdef90ac63d362db0664dc43a5 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. https://status.linqapp.com/incident/747405 Tue, 21 Oct 2025 00:05:00 -0000 https://status.linqapp.com/incident/747405#a580b84ce3da613afe909aac962713d5a223cdcdef90ac63d362db0664dc43a5 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 23:09:00 -0000 https://status.linqapp.com/incident/747405#2b764bcd9b1d6cbb5375e4c3acd710a7b83ea30c3f868ec5ade0d1aec4c8a500 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 23:09:00 -0000 https://status.linqapp.com/incident/747405#2b764bcd9b1d6cbb5375e4c3acd710a7b83ea30c3f868ec5ade0d1aec4c8a500 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 23:09:00 -0000 https://status.linqapp.com/incident/747405#2b764bcd9b1d6cbb5375e4c3acd710a7b83ea30c3f868ec5ade0d1aec4c8a500 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 23:09:00 -0000 https://status.linqapp.com/incident/747405#2b764bcd9b1d6cbb5375e4c3acd710a7b83ea30c3f868ec5ade0d1aec4c8a500 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 23:09:00 -0000 https://status.linqapp.com/incident/747405#2b764bcd9b1d6cbb5375e4c3acd710a7b83ea30c3f868ec5ade0d1aec4c8a500 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 22:49:00 -0000 https://status.linqapp.com/incident/747405#9b62610a360108690e9541a64d60fdb2b44191482b5b019512ebe472dfc5c307 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 22:49:00 -0000 https://status.linqapp.com/incident/747405#9b62610a360108690e9541a64d60fdb2b44191482b5b019512ebe472dfc5c307 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 22:49:00 -0000 https://status.linqapp.com/incident/747405#9b62610a360108690e9541a64d60fdb2b44191482b5b019512ebe472dfc5c307 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 22:49:00 -0000 https://status.linqapp.com/incident/747405#9b62610a360108690e9541a64d60fdb2b44191482b5b019512ebe472dfc5c307 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 22:49:00 -0000 https://status.linqapp.com/incident/747405#9b62610a360108690e9541a64d60fdb2b44191482b5b019512ebe472dfc5c307 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 22:08:00 -0000 https://status.linqapp.com/incident/747405#76f3b747f9475abefcb2ea8d513ebeb75ed525c8cbc4373f1b95880b97743b84 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 22:08:00 -0000 https://status.linqapp.com/incident/747405#76f3b747f9475abefcb2ea8d513ebeb75ed525c8cbc4373f1b95880b97743b84 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 22:08:00 -0000 https://status.linqapp.com/incident/747405#76f3b747f9475abefcb2ea8d513ebeb75ed525c8cbc4373f1b95880b97743b84 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 22:08:00 -0000 https://status.linqapp.com/incident/747405#76f3b747f9475abefcb2ea8d513ebeb75ed525c8cbc4373f1b95880b97743b84 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 22:08:00 -0000 https://status.linqapp.com/incident/747405#76f3b747f9475abefcb2ea8d513ebeb75ed525c8cbc4373f1b95880b97743b84 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 21:41:00 -0000 https://status.linqapp.com/incident/747405#c0694b0b8e0b7eff0aaa53c6c825baaeffd5f732fc11c41b65f7180e8add0bfa 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 21:41:00 -0000 https://status.linqapp.com/incident/747405#c0694b0b8e0b7eff0aaa53c6c825baaeffd5f732fc11c41b65f7180e8add0bfa 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 21:41:00 -0000 https://status.linqapp.com/incident/747405#c0694b0b8e0b7eff0aaa53c6c825baaeffd5f732fc11c41b65f7180e8add0bfa 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 21:41:00 -0000 https://status.linqapp.com/incident/747405#c0694b0b8e0b7eff0aaa53c6c825baaeffd5f732fc11c41b65f7180e8add0bfa 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 21:41:00 -0000 https://status.linqapp.com/incident/747405#c0694b0b8e0b7eff0aaa53c6c825baaeffd5f732fc11c41b65f7180e8add0bfa 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 20:40:00 -0000 https://status.linqapp.com/incident/747405#1407d313bb1210ffa3150db592671939d54765a113b24fdd0b3fb0880a0c85b1 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 20:40:00 -0000 https://status.linqapp.com/incident/747405#1407d313bb1210ffa3150db592671939d54765a113b24fdd0b3fb0880a0c85b1 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 20:40:00 -0000 https://status.linqapp.com/incident/747405#1407d313bb1210ffa3150db592671939d54765a113b24fdd0b3fb0880a0c85b1 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 20:40:00 -0000 https://status.linqapp.com/incident/747405#1407d313bb1210ffa3150db592671939d54765a113b24fdd0b3fb0880a0c85b1 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 20:40:00 -0000 https://status.linqapp.com/incident/747405#1407d313bb1210ffa3150db592671939d54765a113b24fdd0b3fb0880a0c85b1 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 19:13:00 -0000 https://status.linqapp.com/incident/747405#e63b9ed7e05cc155cd19fb7ed3758208331a74caf3797d957c006e71b3747ee8 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 19:13:00 -0000 https://status.linqapp.com/incident/747405#e63b9ed7e05cc155cd19fb7ed3758208331a74caf3797d957c006e71b3747ee8 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 19:13:00 -0000 https://status.linqapp.com/incident/747405#e63b9ed7e05cc155cd19fb7ed3758208331a74caf3797d957c006e71b3747ee8 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 19:13:00 -0000 https://status.linqapp.com/incident/747405#e63b9ed7e05cc155cd19fb7ed3758208331a74caf3797d957c006e71b3747ee8 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 19:13:00 -0000 https://status.linqapp.com/incident/747405#e63b9ed7e05cc155cd19fb7ed3758208331a74caf3797d957c006e71b3747ee8 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 17:49:00 -0000 https://status.linqapp.com/incident/747405#085ea642f2ad5dac4ef6776d156d94e4776c86439c4da41286c074e7d6f96295 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 17:49:00 -0000 https://status.linqapp.com/incident/747405#085ea642f2ad5dac4ef6776d156d94e4776c86439c4da41286c074e7d6f96295 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 17:49:00 -0000 https://status.linqapp.com/incident/747405#085ea642f2ad5dac4ef6776d156d94e4776c86439c4da41286c074e7d6f96295 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 17:49:00 -0000 https://status.linqapp.com/incident/747405#085ea642f2ad5dac4ef6776d156d94e4776c86439c4da41286c074e7d6f96295 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 17:49:00 -0000 https://status.linqapp.com/incident/747405#085ea642f2ad5dac4ef6776d156d94e4776c86439c4da41286c074e7d6f96295 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 17:30:00 -0000 https://status.linqapp.com/incident/747405#f2a88e557f604bfa92b1378414bc85cc5239769e685d7b704d27132152fd3e57 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 17:30:00 -0000 https://status.linqapp.com/incident/747405#f2a88e557f604bfa92b1378414bc85cc5239769e685d7b704d27132152fd3e57 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 17:30:00 -0000 https://status.linqapp.com/incident/747405#f2a88e557f604bfa92b1378414bc85cc5239769e685d7b704d27132152fd3e57 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 17:30:00 -0000 https://status.linqapp.com/incident/747405#f2a88e557f604bfa92b1378414bc85cc5239769e685d7b704d27132152fd3e57 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 17:30:00 -0000 https://status.linqapp.com/incident/747405#f2a88e557f604bfa92b1378414bc85cc5239769e685d7b704d27132152fd3e57 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 16:25:00 -0000 https://status.linqapp.com/incident/747405#698d712b23d537b79aa777e65599ccaae8811380f1ba3e2d81d51bb3b6cbde45 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 https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 16:25:00 -0000 https://status.linqapp.com/incident/747405#698d712b23d537b79aa777e65599ccaae8811380f1ba3e2d81d51bb3b6cbde45 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 https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 15:52:00 -0000 https://status.linqapp.com/incident/747405#d1685c31c0ef86c992c0ab5842576be71e2a36cd00e27db5de737140409dea1d 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 15:52:00 -0000 https://status.linqapp.com/incident/747405#d1685c31c0ef86c992c0ab5842576be71e2a36cd00e27db5de737140409dea1d 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 15:16:00 -0000 https://status.linqapp.com/incident/747405#23146349da95e7e1cb603814ef34c5fccda9c13c20810092f82abe6fcdc1ceab 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 15:16:00 -0000 https://status.linqapp.com/incident/747405#23146349da95e7e1cb603814ef34c5fccda9c13c20810092f82abe6fcdc1ceab 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 15:04:00 -0000 https://status.linqapp.com/incident/747405#8c5675983a79e801b3d85d4ae9860515a447ffbadc6ac3f80d2c6fd8af9c158c 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 15:04:00 -0000 https://status.linqapp.com/incident/747405#8c5675983a79e801b3d85d4ae9860515a447ffbadc6ac3f80d2c6fd8af9c158c 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 14:58:00 -0000 https://status.linqapp.com/incident/747405#c77d9f87fe11d077290f13b4fa0cab81020d248afa6b32c52d32e3ab976b9577 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. https://status.linqapp.com/incident/747405 Mon, 20 Oct 2025 14:58:00 -0000 https://status.linqapp.com/incident/747405#c77d9f87fe11d077290f13b4fa0cab81020d248afa6b32c52d32e3ab976b9577 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. https://status.linqapp.com/incident/745604 Fri, 17 Oct 2025 20:54:00 -0000 https://status.linqapp.com/incident/745604#a2dda794f22ecdd959eaef309ff578048d405f3f6139c3555bc48bb5db3ca184 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. https://status.linqapp.com/incident/745604 Fri, 17 Oct 2025 20:54:00 -0000 https://status.linqapp.com/incident/745604#a2dda794f22ecdd959eaef309ff578048d405f3f6139c3555bc48bb5db3ca184 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. https://status.linqapp.com/incident/745604 Fri, 17 Oct 2025 20:45:00 -0000 https://status.linqapp.com/incident/745604#1e1a29b6b28b273d7b95ca28cf7bfe7099a7d32da4c218ae2bc79d489e8c4ee0 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. https://status.linqapp.com/incident/745604 Fri, 17 Oct 2025 20:45:00 -0000 https://status.linqapp.com/incident/745604#1e1a29b6b28b273d7b95ca28cf7bfe7099a7d32da4c218ae2bc79d489e8c4ee0 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. https://status.linqapp.com/incident/745604 Fri, 17 Oct 2025 20:24:00 -0000 https://status.linqapp.com/incident/745604#ce7f7feb5354952d3a41b5ef47da03d173325d2223e6c55812f082a8bd0e8a58 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. https://status.linqapp.com/incident/745604 Fri, 17 Oct 2025 20:24:00 -0000 https://status.linqapp.com/incident/745604#ce7f7feb5354952d3a41b5ef47da03d173325d2223e6c55812f082a8bd0e8a58 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. https://status.linqapp.com/incident/745604 Fri, 17 Oct 2025 20:16:00 -0000 https://status.linqapp.com/incident/745604#4aa72e7d5169ad338ab318f11458dbafbc263fcd7b01bbc570992a800cac5b61 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. https://status.linqapp.com/incident/745604 Fri, 17 Oct 2025 20:16:00 -0000 https://status.linqapp.com/incident/745604#4aa72e7d5169ad338ab318f11458dbafbc263fcd7b01bbc570992a800cac5b61 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. https://status.linqapp.com/incident/742965 Mon, 13 Oct 2025 22:10:00 -0000 https://status.linqapp.com/incident/742965#bfe41427cc3b3774ef72e7b2f787195816b5e11cd8d5a5e5d147a496b54c98ff 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. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 22:40:00 -0000 https://status.linqapp.com/incident/739405#d8097592f2410d6f8ec1fdea3e093f18ca851c2740215301a125e1f66606d633 Things are performing much better. We’ll continue to monitor for any lingering issues. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 22:40:00 -0000 https://status.linqapp.com/incident/739405#d8097592f2410d6f8ec1fdea3e093f18ca851c2740215301a125e1f66606d633 Things are performing much better. We’ll continue to monitor for any lingering issues. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 22:40:00 -0000 https://status.linqapp.com/incident/739405#d8097592f2410d6f8ec1fdea3e093f18ca851c2740215301a125e1f66606d633 Things are performing much better. We’ll continue to monitor for any lingering issues. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 22:40:00 -0000 https://status.linqapp.com/incident/739405#d8097592f2410d6f8ec1fdea3e093f18ca851c2740215301a125e1f66606d633 Things are performing much better. We’ll continue to monitor for any lingering issues. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 21:29:00 -0000 https://status.linqapp.com/incident/739405#94f4fc3bc18f9bcaef155b2274e714c60080bf9c2d967091c6f662572b3e3056 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. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 21:29:00 -0000 https://status.linqapp.com/incident/739405#94f4fc3bc18f9bcaef155b2274e714c60080bf9c2d967091c6f662572b3e3056 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. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 21:29:00 -0000 https://status.linqapp.com/incident/739405#94f4fc3bc18f9bcaef155b2274e714c60080bf9c2d967091c6f662572b3e3056 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. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 21:29:00 -0000 https://status.linqapp.com/incident/739405#94f4fc3bc18f9bcaef155b2274e714c60080bf9c2d967091c6f662572b3e3056 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. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 19:58:00 -0000 https://status.linqapp.com/incident/739405#3d101187db6f8b1a263be087d2ae6ade3069f9bb0cef1f0766359eb3d79305fb We are still experiencing platform wide issues. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 19:58:00 -0000 https://status.linqapp.com/incident/739405#3d101187db6f8b1a263be087d2ae6ade3069f9bb0cef1f0766359eb3d79305fb We are still experiencing platform wide issues. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 19:58:00 -0000 https://status.linqapp.com/incident/739405#3d101187db6f8b1a263be087d2ae6ade3069f9bb0cef1f0766359eb3d79305fb We are still experiencing platform wide issues. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 19:58:00 -0000 https://status.linqapp.com/incident/739405#3d101187db6f8b1a263be087d2ae6ade3069f9bb0cef1f0766359eb3d79305fb We are still experiencing platform wide issues. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 18:06:00 -0000 https://status.linqapp.com/incident/739405#258dff53fc3a02330465326dbe101346b236b639d13cbbeba53fd9d62b0f91bb Error rates for partners have decreased to normal levels. We are continuing to monitor. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 18:06:00 -0000 https://status.linqapp.com/incident/739405#258dff53fc3a02330465326dbe101346b236b639d13cbbeba53fd9d62b0f91bb Error rates for partners have decreased to normal levels. We are continuing to monitor. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 17:55:00 -0000 https://status.linqapp.com/incident/739405#5ad633adc4e76c2cdf56e35756e597cd30abed478c346c78eacb90ed7d10ce83 The queuing issues have been resolved. We are still investigating some API partners reporting higher error rates. We will followup when this is resolved. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 17:55:00 -0000 https://status.linqapp.com/incident/739405#5ad633adc4e76c2cdf56e35756e597cd30abed478c346c78eacb90ed7d10ce83 The queuing issues have been resolved. We are still investigating some API partners reporting higher error rates. We will followup when this is resolved. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 17:38:00 -0000 https://status.linqapp.com/incident/739405#46670ad684acf3517b289b203ea5584e18c3676ec0526740bbae6cbb4d4e6c90 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. https://status.linqapp.com/incident/739405 Tue, 07 Oct 2025 17:38:00 -0000 https://status.linqapp.com/incident/739405#46670ad684acf3517b289b203ea5584e18c3676ec0526740bbae6cbb4d4e6c90 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. https://status.linqapp.com/incident/735279 Tue, 30 Sep 2025 22:30:00 -0000 https://status.linqapp.com/incident/735279#36447d2014b5915b0e455522995ca64ecfba51d747f5e2ff198984a64a78ceae The issue has been fully resolved and all systems are operating normally. We have identified the root cause and deployed fixes to prevent recurrence. https://status.linqapp.com/incident/735279 Tue, 30 Sep 2025 22:30:00 -0000 https://status.linqapp.com/incident/735279#36447d2014b5915b0e455522995ca64ecfba51d747f5e2ff198984a64a78ceae The issue has been fully resolved and all systems are operating normally. We have identified the root cause and deployed fixes to prevent recurrence. https://status.linqapp.com/incident/735279 Tue, 30 Sep 2025 22:10:00 -0000 https://status.linqapp.com/incident/735279#ca0f6675eb1e65a1a9af92cb3a8b03fbfc8ab7af62ee8b340cc69fead190ceeb 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. https://status.linqapp.com/incident/735279 Tue, 30 Sep 2025 22:10:00 -0000 https://status.linqapp.com/incident/735279#ca0f6675eb1e65a1a9af92cb3a8b03fbfc8ab7af62ee8b340cc69fead190ceeb 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. https://status.linqapp.com/incident/734578 Mon, 29 Sep 2025 22:21:00 -0000 https://status.linqapp.com/incident/734578#8b1afc6d68b0fc5d6ca5907790b14b22b032f45c33eeecbb81cd7a0c34875328 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. https://status.linqapp.com/incident/734578 Mon, 29 Sep 2025 22:21:00 -0000 https://status.linqapp.com/incident/734578#8b1afc6d68b0fc5d6ca5907790b14b22b032f45c33eeecbb81cd7a0c34875328 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. https://status.linqapp.com/incident/734578 Mon, 29 Sep 2025 22:10:00 -0000 https://status.linqapp.com/incident/734578#d5c2f5259e968d9efbad143f4b6c24af2298b012714ffbc28688c4903edc6aee 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. https://status.linqapp.com/incident/734578 Mon, 29 Sep 2025 22:10:00 -0000 https://status.linqapp.com/incident/734578#d5c2f5259e968d9efbad143f4b6c24af2298b012714ffbc28688c4903edc6aee 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. https://status.linqapp.com/incident/718990 Fri, 05 Sep 2025 11:34:00 -0000 https://status.linqapp.com/incident/718990#dc6460f46d3864ff64727c22b3793f7eea51d3ec764e068bb732fd60578583c8 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. https://status.linqapp.com/incident/710223 Fri, 22 Aug 2025 05:31:37 -0000 https://status.linqapp.com/incident/710223#0ee5bb99035181bd4e6a7b7ca7c10b8ffa8573b3b18bef813e9b26c0d68d9249 Maintenance completed https://status.linqapp.com/incident/710223 Fri, 22 Aug 2025 05:31:37 -0000 https://status.linqapp.com/incident/710223#0ee5bb99035181bd4e6a7b7ca7c10b8ffa8573b3b18bef813e9b26c0d68d9249 Maintenance completed https://status.linqapp.com/incident/710223 Fri, 22 Aug 2025 05:31:37 -0000 https://status.linqapp.com/incident/710223#0ee5bb99035181bd4e6a7b7ca7c10b8ffa8573b3b18bef813e9b26c0d68d9249 Maintenance completed https://status.linqapp.com/incident/710223 Fri, 22 Aug 2025 05:31:37 -0000 https://status.linqapp.com/incident/710223#0ee5bb99035181bd4e6a7b7ca7c10b8ffa8573b3b18bef813e9b26c0d68d9249 Maintenance completed https://status.linqapp.com/incident/710223 Fri, 22 Aug 2025 03:00:00 -0000 https://status.linqapp.com/incident/710223#812357fc9d8520be655f7eb52a7301e3c64f84d41f59a5e696cb44d989242c6c Data infrastructure maintenance is finished. https://status.linqapp.com/incident/710223 Fri, 22 Aug 2025 03:00:00 -0000 https://status.linqapp.com/incident/710223#812357fc9d8520be655f7eb52a7301e3c64f84d41f59a5e696cb44d989242c6c Data infrastructure maintenance is finished. https://status.linqapp.com/incident/710223 Fri, 22 Aug 2025 03:00:00 -0000 https://status.linqapp.com/incident/710223#812357fc9d8520be655f7eb52a7301e3c64f84d41f59a5e696cb44d989242c6c Data infrastructure maintenance is finished. https://status.linqapp.com/incident/710223 Fri, 22 Aug 2025 03:00:00 -0000 https://status.linqapp.com/incident/710223#812357fc9d8520be655f7eb52a7301e3c64f84d41f59a5e696cb44d989242c6c Data infrastructure maintenance is finished. https://status.linqapp.com/incident/621419 Fri, 18 Jul 2025 06:00:00 -0000 https://status.linqapp.com/incident/621419#adbb9b815f4d7e38ba60e589d4e6d8d702c529df4b25bdd5005eae9cbfdc5f19 Maintenance completed https://status.linqapp.com/incident/621419 Fri, 18 Jul 2025 04:00:00 -0000 https://status.linqapp.com/incident/621419#2a65634f7ad32e68af7c3482c62ac07f2145faba761a97d56a12563df887ada1 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. https://status.linqapp.com/incident/621419 Fri, 18 Jul 2025 04:00:00 -0000 https://status.linqapp.com/incident/621419#2a65634f7ad32e68af7c3482c62ac07f2145faba761a97d56a12563df887ada1 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. https://status.linqapp.com/incident/620329 Wed, 16 Jul 2025 11:00:14 -0000 https://status.linqapp.com/incident/620329#0efabcf36a8f37f34e4615deef93eebd9067b9d5b53cefd075fec7a48d0f119a Maintenance completed https://status.linqapp.com/incident/620329 Wed, 16 Jul 2025 09:00:14 -0000 https://status.linqapp.com/incident/620329#fcced40aa1967f6799d8eb3623bb96d4f9b53fc6a5c417a245541777fa6a34bd 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. https://status.linqapp.com/incident/620333 Wed, 16 Jul 2025 03:15:32 -0000 https://status.linqapp.com/incident/620333#5d2b96d091e8b48938a8a6cdf1bdf44aa593a45cf5cd4794738d3dec42e7bed3 Maintenance completed https://status.linqapp.com/incident/620333 Wed, 16 Jul 2025 03:00:32 -0000 https://status.linqapp.com/incident/620333#4a2fe5773d2c9889540470d439485bfc776774fcfbaef51e79df9f3894403f29 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. https://status.linqapp.com/incident/620333 Wed, 16 Jul 2025 03:00:32 -0000 https://status.linqapp.com/incident/620333#4a2fe5773d2c9889540470d439485bfc776774fcfbaef51e79df9f3894403f29 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. https://status.linqapp.com/incident/616398 Thu, 10 Jul 2025 13:04:00 -0000 https://status.linqapp.com/incident/616398#2d731888fc0a061b9a22c16f734616a9ad62cba52a80bcb92da422a41baafde4 Message delivery for Linq Blue has remained stable, and both sending and receiving are fully operational. This incident is now resolved. https://status.linqapp.com/incident/616398 Thu, 10 Jul 2025 00:02:00 -0000 https://status.linqapp.com/incident/616398#becd3e1fbfa5e2ee53fe534c8fbcfd9519487cbe77201fae9cdbb01e4a032578 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. https://status.linqapp.com/incident/616398 Wed, 09 Jul 2025 17:45:00 -0000 https://status.linqapp.com/incident/616398#5fb1afe35f0b5c4c72dbeff3acd4a20b2c848f117514f448d9f37cddaba82917 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. https://status.linqapp.com/incident/616398 Wed, 09 Jul 2025 03:19:00 -0000 https://status.linqapp.com/incident/616398#22170c4a1abc9cf1c24f1e8c86bc70946b122ccd5371843abacb74e57a194511 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. https://status.linqapp.com/incident/616398 Tue, 08 Jul 2025 23:31:00 -0000 https://status.linqapp.com/incident/616398#8cb8884394660f57d63e7bfc4f4a81ce3dee56e50c80529e0628b45aa82c0969 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. https://status.linqapp.com/incident/600236 Wed, 11 Jun 2025 14:00:00 -0000 https://status.linqapp.com/incident/600236#3869ebc549f322006c0df092e024b4b49289d6b8850d49ed9dde4fd2e7408cf3 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. https://status.linqapp.com/incident/600236 Wed, 11 Jun 2025 14:00:00 -0000 https://status.linqapp.com/incident/600236#3869ebc549f322006c0df092e024b4b49289d6b8850d49ed9dde4fd2e7408cf3 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. https://status.linqapp.com/incident/600236 Wed, 11 Jun 2025 14:00:00 -0000 https://status.linqapp.com/incident/600236#3869ebc549f322006c0df092e024b4b49289d6b8850d49ed9dde4fd2e7408cf3 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. https://status.linqapp.com/incident/600236 Wed, 11 Jun 2025 14:00:00 -0000 https://status.linqapp.com/incident/600236#3869ebc549f322006c0df092e024b4b49289d6b8850d49ed9dde4fd2e7408cf3 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. https://status.linqapp.com/incident/600236 Wed, 11 Jun 2025 10:32:00 -0000 https://status.linqapp.com/incident/600236#bf1bc36bb260045121f4c12fc6937fac10d51bf8b38c863cd718b01a02ed7de2 Everything is now back to normal. We’ve resolved today’s outage affecting Blue messaging, Linq Phone calls, and SMS. https://status.linqapp.com/incident/600236 Wed, 11 Jun 2025 10:32:00 -0000 https://status.linqapp.com/incident/600236#bf1bc36bb260045121f4c12fc6937fac10d51bf8b38c863cd718b01a02ed7de2 Everything is now back to normal. We’ve resolved today’s outage affecting Blue messaging, Linq Phone calls, and SMS. https://status.linqapp.com/incident/600236 Wed, 11 Jun 2025 10:32:00 -0000 https://status.linqapp.com/incident/600236#bf1bc36bb260045121f4c12fc6937fac10d51bf8b38c863cd718b01a02ed7de2 Everything is now back to normal. We’ve resolved today’s outage affecting Blue messaging, Linq Phone calls, and SMS. https://status.linqapp.com/incident/600236 Wed, 11 Jun 2025 10:32:00 -0000 https://status.linqapp.com/incident/600236#bf1bc36bb260045121f4c12fc6937fac10d51bf8b38c863cd718b01a02ed7de2 Everything is now back to normal. We’ve resolved today’s outage affecting Blue messaging, Linq Phone calls, and SMS. https://status.linqapp.com/incident/600236 Tue, 10 Jun 2025 12:16:00 -0000 https://status.linqapp.com/incident/600236#8978b12b35489cfaba50e6dbfbe5eec84ecd4e7ce89c14822e046ef844cac5ce 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. https://status.linqapp.com/incident/600236 Tue, 10 Jun 2025 12:16:00 -0000 https://status.linqapp.com/incident/600236#8978b12b35489cfaba50e6dbfbe5eec84ecd4e7ce89c14822e046ef844cac5ce 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. https://status.linqapp.com/incident/600236 Tue, 10 Jun 2025 12:16:00 -0000 https://status.linqapp.com/incident/600236#8978b12b35489cfaba50e6dbfbe5eec84ecd4e7ce89c14822e046ef844cac5ce 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. https://status.linqapp.com/incident/600236 Tue, 10 Jun 2025 12:16:00 -0000 https://status.linqapp.com/incident/600236#8978b12b35489cfaba50e6dbfbe5eec84ecd4e7ce89c14822e046ef844cac5ce 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. https://status.linqapp.com/incident/560182 Sun, 11 May 2025 05:19:00 -0000 https://status.linqapp.com/incident/560182#03ecc4bbbdfd31fa0437f25fb4509abbebdba458fb48e23372b3914ca18e0643 Linq Blue is Currently Experiencing Issues the team is aware and we are working on it. https://status.linqapp.com/incident/560182 Sun, 11 May 2025 05:19:00 -0000 https://status.linqapp.com/incident/560182#03ecc4bbbdfd31fa0437f25fb4509abbebdba458fb48e23372b3914ca18e0643 Linq Blue is Currently Experiencing Issues the team is aware and we are working on it. https://status.linqapp.com/incident/560182 Sun, 11 May 2025 05:19:00 -0000 https://status.linqapp.com/incident/560182#03ecc4bbbdfd31fa0437f25fb4509abbebdba458fb48e23372b3914ca18e0643 Linq Blue is Currently Experiencing Issues the team is aware and we are working on it. https://status.linqapp.com/incident/560182 Sun, 11 May 2025 05:19:00 -0000 https://status.linqapp.com/incident/560182#03ecc4bbbdfd31fa0437f25fb4509abbebdba458fb48e23372b3914ca18e0643 Linq Blue is Currently Experiencing Issues the team is aware and we are working on it. https://status.linqapp.com/incident/551344 Fri, 25 Apr 2025 05:31:00 -0000 https://status.linqapp.com/incident/551344#fcec538e1795dc78b4972a6b57f9c09a5fd8278b1269dacda67c86055c7f87ae API Maintenance is done. We are fully back. https://status.linqapp.com/incident/551344 Fri, 25 Apr 2025 05:31:00 -0000 https://status.linqapp.com/incident/551344#fcec538e1795dc78b4972a6b57f9c09a5fd8278b1269dacda67c86055c7f87ae API Maintenance is done. We are fully back. https://status.linqapp.com/incident/551344 Fri, 25 Apr 2025 05:31:00 -0000 https://status.linqapp.com/incident/551344#fcec538e1795dc78b4972a6b57f9c09a5fd8278b1269dacda67c86055c7f87ae API Maintenance is done. We are fully back.