Incidents reported on status page for Linq https://status.linqapp.com/ https://d1lppblt9t2x15.cloudfront.net/logos/4039a2ddb51ba418b5097353f9eb8e99.png https://status.linqapp.com/ en 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/ Fri, 05 Sep 2025 08:18:48 +0000 https://status.linqapp.com/#89bd05c52fbef4d721d708258ca891cbd1c245053b18063d526819a3f57aa0c5 Linq Blue API recovered https://status.linqapp.com/ Fri, 05 Sep 2025 04:54:16 +0000 https://status.linqapp.com/#89bd05c52fbef4d721d708258ca891cbd1c245053b18063d526819a3f57aa0c5 Linq Blue API went down 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/ Fri, 22 Aug 2025 04:27:30 +0000 https://status.linqapp.com/#9ab51b76ebb6c843caecde54152a063daeae5012487135a8c5ebf368647cffc3 Linq Blue recovered https://status.linqapp.com/ Fri, 22 Aug 2025 04:27:30 +0000 https://status.linqapp.com/#9ab51b76ebb6c843caecde54152a063daeae5012487135a8c5ebf368647cffc3 Platform API recovered https://status.linqapp.com/ Fri, 22 Aug 2025 04:16:00 +0000 https://status.linqapp.com/#9ab51b76ebb6c843caecde54152a063daeae5012487135a8c5ebf368647cffc3 Linq Blue went down https://status.linqapp.com/ Fri, 22 Aug 2025 04:16:00 +0000 https://status.linqapp.com/#9ab51b76ebb6c843caecde54152a063daeae5012487135a8c5ebf368647cffc3 Platform API went down 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/ Thu, 21 Aug 2025 17:33:30 +0000 https://status.linqapp.com/#e0eb5a0dd2b32385919ff8470c88f96a58fd55e5f13a79aa179232b66ceea8e0 Linq Blue recovered https://status.linqapp.com/ Thu, 21 Aug 2025 17:33:30 +0000 https://status.linqapp.com/#e0eb5a0dd2b32385919ff8470c88f96a58fd55e5f13a79aa179232b66ceea8e0 Platform API recovered https://status.linqapp.com/ Thu, 21 Aug 2025 17:26:59 +0000 https://status.linqapp.com/#e0eb5a0dd2b32385919ff8470c88f96a58fd55e5f13a79aa179232b66ceea8e0 Linq Blue went down https://status.linqapp.com/ Thu, 21 Aug 2025 17:26:59 +0000 https://status.linqapp.com/#e0eb5a0dd2b32385919ff8470c88f96a58fd55e5f13a79aa179232b66ceea8e0 Platform API went down https://status.linqapp.com/ Thu, 21 Aug 2025 15:04:18 +0000 https://status.linqapp.com/#03d4099ddeed9d14bee14c476b58cd90cff4ae50a717a5bf8e44499980e9597e Linq Blue recovered https://status.linqapp.com/ Thu, 21 Aug 2025 15:04:18 +0000 https://status.linqapp.com/#03d4099ddeed9d14bee14c476b58cd90cff4ae50a717a5bf8e44499980e9597e Platform API recovered https://status.linqapp.com/ Thu, 21 Aug 2025 14:55:48 +0000 https://status.linqapp.com/#03d4099ddeed9d14bee14c476b58cd90cff4ae50a717a5bf8e44499980e9597e Linq Blue went down https://status.linqapp.com/ Thu, 21 Aug 2025 14:55:48 +0000 https://status.linqapp.com/#03d4099ddeed9d14bee14c476b58cd90cff4ae50a717a5bf8e44499980e9597e Platform API went down https://status.linqapp.com/ Tue, 19 Aug 2025 21:03:27 +0000 https://status.linqapp.com/#ab7a7da222097a4ce4d50cb2fa185bcf9c9ac1ef84413fb851b0a59609af74e5 Linq Blue recovered https://status.linqapp.com/ Tue, 19 Aug 2025 21:03:27 +0000 https://status.linqapp.com/#ab7a7da222097a4ce4d50cb2fa185bcf9c9ac1ef84413fb851b0a59609af74e5 Platform API recovered https://status.linqapp.com/ Tue, 19 Aug 2025 20:50:46 +0000 https://status.linqapp.com/#ab7a7da222097a4ce4d50cb2fa185bcf9c9ac1ef84413fb851b0a59609af74e5 Linq Blue went down https://status.linqapp.com/ Tue, 19 Aug 2025 20:50:46 +0000 https://status.linqapp.com/#ab7a7da222097a4ce4d50cb2fa185bcf9c9ac1ef84413fb851b0a59609af74e5 Platform API went down https://status.linqapp.com/ Fri, 18 Jul 2025 17:14:16 +0000 https://status.linqapp.com/#1c01ea4d58b230c50843e21bcfce00789778f50186741c8abadef4d776d8e0f6 Linq Blue API recovered https://status.linqapp.com/ Fri, 18 Jul 2025 17:08:05 +0000 https://status.linqapp.com/#1c01ea4d58b230c50843e21bcfce00789778f50186741c8abadef4d776d8e0f6 Linq Blue API went down 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/ Thu, 17 Jul 2025 03:34:56 +0000 https://status.linqapp.com/#f252b146b52b9572849906a23c106d08fc162cafabc0793f91f3279a857f3314 Linq Blue API recovered https://status.linqapp.com/ Thu, 17 Jul 2025 03:24:37 +0000 https://status.linqapp.com/#f252b146b52b9572849906a23c106d08fc162cafabc0793f91f3279a857f3314 Linq Blue API went down https://status.linqapp.com/ Thu, 17 Jul 2025 03:06:55 +0000 https://status.linqapp.com/#369a1b482f5997998e524dc28c65d1af7f21623a845f979bc61fc2143d6db346 Linq Blue API recovered https://status.linqapp.com/ Thu, 17 Jul 2025 03:01:48 +0000 https://status.linqapp.com/#369a1b482f5997998e524dc28c65d1af7f21623a845f979bc61fc2143d6db346 Linq Blue API went down 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/ Tue, 15 Jul 2025 14:55:47 +0000 https://status.linqapp.com/#b3f6aae5830b198516cd755447bc731812044b50fe8e9137ce399696d6fde186 Linq Blue API recovered https://status.linqapp.com/ Tue, 15 Jul 2025 14:46:20 +0000 https://status.linqapp.com/#b3f6aae5830b198516cd755447bc731812044b50fe8e9137ce399696d6fde186 Linq Blue API went down https://status.linqapp.com/ Tue, 15 Jul 2025 14:31:39 +0000 https://status.linqapp.com/#7adc4e98593a2ed9b73e2ce124043a33a6f8f122f1f98b95f00261d9ba9f20d1 Linq Blue API recovered https://status.linqapp.com/ Tue, 15 Jul 2025 14:25:27 +0000 https://status.linqapp.com/#7adc4e98593a2ed9b73e2ce124043a33a6f8f122f1f98b95f00261d9ba9f20d1 Linq Blue API went down https://status.linqapp.com/ Mon, 14 Jul 2025 17:27:28 +0000 https://status.linqapp.com/#78d2e71ad70df42757b36e99539fa4df2c463e5bce867370ade8b140a695d50e Linq Blue recovered https://status.linqapp.com/ Mon, 14 Jul 2025 17:27:28 +0000 https://status.linqapp.com/#78d2e71ad70df42757b36e99539fa4df2c463e5bce867370ade8b140a695d50e Platform API recovered https://status.linqapp.com/ Mon, 14 Jul 2025 17:21:05 +0000 https://status.linqapp.com/#78d2e71ad70df42757b36e99539fa4df2c463e5bce867370ade8b140a695d50e Linq Blue went down https://status.linqapp.com/ Mon, 14 Jul 2025 17:21:05 +0000 https://status.linqapp.com/#78d2e71ad70df42757b36e99539fa4df2c463e5bce867370ade8b140a695d50e Platform API went down 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.