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/765275 Fri, 12 Dec 2025 09:00:21 -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 09:00:21 -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 09:00:21 -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 09:00:21 -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 09:00:21 -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/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/ Tue, 28 Oct 2025 04:23:46 +0000 https://status.linqapp.com/#9fe4078241d1f268b320e30a9d834e2b9bc31ec57956011d59ddf42beae8324f Linq Blue API recovered https://status.linqapp.com/ Tue, 28 Oct 2025 04:14:11 +0000 https://status.linqapp.com/#9fe4078241d1f268b320e30a9d834e2b9bc31ec57956011d59ddf42beae8324f Linq Blue API went down 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/ Tue, 21 Oct 2025 00:02:04 +0000 https://status.linqapp.com/#9c3ca94c870fa540dd30a35cf5e75ec309776e6bf83b67b8304e880027d02d09 Linq Phone recovered https://status.linqapp.com/ Tue, 21 Oct 2025 00:02:01 +0000 https://status.linqapp.com/#f7db0d186d405072786d6cc12b2d5e49cb22e7ad3f1a1dd27e3404ccd602a067 Linq Blue API recovered https://status.linqapp.com/ Mon, 20 Oct 2025 23:53:41 +0000 https://status.linqapp.com/#c2641650dfecaba537094db6a59c16985c6b679a25d3c80e11784c7e8052943b Linq Blue recovered https://status.linqapp.com/ Mon, 20 Oct 2025 23:53:41 +0000 https://status.linqapp.com/#c2641650dfecaba537094db6a59c16985c6b679a25d3c80e11784c7e8052943b Platform API recovered 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/ Mon, 20 Oct 2025 22:43:09 +0000 https://status.linqapp.com/#9c3ca94c870fa540dd30a35cf5e75ec309776e6bf83b67b8304e880027d02d09 Linq Phone went down https://status.linqapp.com/ Mon, 20 Oct 2025 22:42:02 +0000 https://status.linqapp.com/#c2641650dfecaba537094db6a59c16985c6b679a25d3c80e11784c7e8052943b Linq Blue went down https://status.linqapp.com/ Mon, 20 Oct 2025 22:42:02 +0000 https://status.linqapp.com/#c2641650dfecaba537094db6a59c16985c6b679a25d3c80e11784c7e8052943b Platform API went down 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/ Mon, 20 Oct 2025 19:05:13 +0000 https://status.linqapp.com/#1fac96d21c630934cfb5c23b1380bc96536b9e03d91599786fdab58b10f4a16c Linq Blue recovered https://status.linqapp.com/ Mon, 20 Oct 2025 19:05:13 +0000 https://status.linqapp.com/#1fac96d21c630934cfb5c23b1380bc96536b9e03d91599786fdab58b10f4a16c Platform API recovered https://status.linqapp.com/ Mon, 20 Oct 2025 18:47:02 +0000 https://status.linqapp.com/#1fac96d21c630934cfb5c23b1380bc96536b9e03d91599786fdab58b10f4a16c Linq Blue went down https://status.linqapp.com/ Mon, 20 Oct 2025 18:47:02 +0000 https://status.linqapp.com/#1fac96d21c630934cfb5c23b1380bc96536b9e03d91599786fdab58b10f4a16c Platform API went down https://status.linqapp.com/ Mon, 20 Oct 2025 18:41:20 +0000 https://status.linqapp.com/#cfda2784613c035a9492d91fac8c315d718518e8b5b250c220f345e6df86557c Linq Blue recovered https://status.linqapp.com/ Mon, 20 Oct 2025 18:41:20 +0000 https://status.linqapp.com/#cfda2784613c035a9492d91fac8c315d718518e8b5b250c220f345e6df86557c Platform API recovered https://status.linqapp.com/ Mon, 20 Oct 2025 18:35:06 +0000 https://status.linqapp.com/#cfda2784613c035a9492d91fac8c315d718518e8b5b250c220f345e6df86557c Linq Blue went down https://status.linqapp.com/ Mon, 20 Oct 2025 18:35:06 +0000 https://status.linqapp.com/#cfda2784613c035a9492d91fac8c315d718518e8b5b250c220f345e6df86557c Platform API went down https://status.linqapp.com/ Mon, 20 Oct 2025 18:14:13 +0000 https://status.linqapp.com/#d9d436275aa62f3477791dd4cfd82ed4c26ad1adbe0d9a6bbbcddf23982c3457 Linq Blue recovered https://status.linqapp.com/ Mon, 20 Oct 2025 18:14:13 +0000 https://status.linqapp.com/#d9d436275aa62f3477791dd4cfd82ed4c26ad1adbe0d9a6bbbcddf23982c3457 Platform API recovered https://status.linqapp.com/ Mon, 20 Oct 2025 18:08:10 +0000 https://status.linqapp.com/#d9d436275aa62f3477791dd4cfd82ed4c26ad1adbe0d9a6bbbcddf23982c3457 Linq Blue went down https://status.linqapp.com/ Mon, 20 Oct 2025 18:08:10 +0000 https://status.linqapp.com/#d9d436275aa62f3477791dd4cfd82ed4c26ad1adbe0d9a6bbbcddf23982c3457 Platform API went down https://status.linqapp.com/ Mon, 20 Oct 2025 18:03:40 +0000 https://status.linqapp.com/#c1be94d16cd71a7ab589eeacff7cf77410937cf25fa429dd07d36117dc496e5a Linq Blue recovered https://status.linqapp.com/ Mon, 20 Oct 2025 18:03:40 +0000 https://status.linqapp.com/#c1be94d16cd71a7ab589eeacff7cf77410937cf25fa429dd07d36117dc496e5a Platform API recovered https://status.linqapp.com/ Mon, 20 Oct 2025 17:53:16 +0000 https://status.linqapp.com/#c1be94d16cd71a7ab589eeacff7cf77410937cf25fa429dd07d36117dc496e5a Linq Blue went down https://status.linqapp.com/ Mon, 20 Oct 2025 17:53:16 +0000 https://status.linqapp.com/#c1be94d16cd71a7ab589eeacff7cf77410937cf25fa429dd07d36117dc496e5a Platform API went down https://status.linqapp.com/ Mon, 20 Oct 2025 17:50:47 +0000 https://status.linqapp.com/#fb332b3b6bfe3057f9aca3c4782e2931d5ea25884be57f63dbf169eeb0cee102 Linq Blue recovered https://status.linqapp.com/ Mon, 20 Oct 2025 17:50:47 +0000 https://status.linqapp.com/#fb332b3b6bfe3057f9aca3c4782e2931d5ea25884be57f63dbf169eeb0cee102 Platform API 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/ Mon, 20 Oct 2025 17:40:24 +0000 https://status.linqapp.com/#fb332b3b6bfe3057f9aca3c4782e2931d5ea25884be57f63dbf169eeb0cee102 Linq Blue went down https://status.linqapp.com/ Mon, 20 Oct 2025 17:40:24 +0000 https://status.linqapp.com/#fb332b3b6bfe3057f9aca3c4782e2931d5ea25884be57f63dbf169eeb0cee102 Platform API went down 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/ Mon, 20 Oct 2025 16:38:44 +0000 https://status.linqapp.com/#4139ca14c6a8b7cbd4ca40607b8ce8002bb257759a9fe701ff446be672cc7273 Linq Blue recovered https://status.linqapp.com/ Mon, 20 Oct 2025 16:38:44 +0000 https://status.linqapp.com/#4139ca14c6a8b7cbd4ca40607b8ce8002bb257759a9fe701ff446be672cc7273 Platform API recovered https://status.linqapp.com/ Mon, 20 Oct 2025 16:27:22 +0000 https://status.linqapp.com/#4139ca14c6a8b7cbd4ca40607b8ce8002bb257759a9fe701ff446be672cc7273 Linq Blue went down https://status.linqapp.com/ Mon, 20 Oct 2025 16:27:22 +0000 https://status.linqapp.com/#4139ca14c6a8b7cbd4ca40607b8ce8002bb257759a9fe701ff446be672cc7273 Platform API went down https://status.linqapp.com/ Mon, 20 Oct 2025 16:25:10 +0000 https://status.linqapp.com/#82c12a51a757099fe1e2e3a63bbe5f6a5db777693d4523c928998a5e0bcd5be6 Linq Blue recovered https://status.linqapp.com/ Mon, 20 Oct 2025 16:25:10 +0000 https://status.linqapp.com/#82c12a51a757099fe1e2e3a63bbe5f6a5db777693d4523c928998a5e0bcd5be6 Platform API recovered 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/ Mon, 20 Oct 2025 16:18:47 +0000 https://status.linqapp.com/#82c12a51a757099fe1e2e3a63bbe5f6a5db777693d4523c928998a5e0bcd5be6 Linq Blue went down https://status.linqapp.com/ Mon, 20 Oct 2025 16:18:47 +0000 https://status.linqapp.com/#82c12a51a757099fe1e2e3a63bbe5f6a5db777693d4523c928998a5e0bcd5be6 Platform API went down 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/ Mon, 20 Oct 2025 14:46:46 +0000 https://status.linqapp.com/#f7db0d186d405072786d6cc12b2d5e49cb22e7ad3f1a1dd27e3404ccd602a067 Linq Blue API went down 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/ Tue, 07 Oct 2025 19:13:56 +0000 https://status.linqapp.com/#e24a1e726bbfdb4480fd46addf728b6cdca0a0077309fada8549fc00768489d8 Linq Blue recovered https://status.linqapp.com/ Tue, 07 Oct 2025 19:13:56 +0000 https://status.linqapp.com/#e24a1e726bbfdb4480fd46addf728b6cdca0a0077309fada8549fc00768489d8 Platform API recovered https://status.linqapp.com/ Tue, 07 Oct 2025 19:07:05 +0000 https://status.linqapp.com/#e24a1e726bbfdb4480fd46addf728b6cdca0a0077309fada8549fc00768489d8 Linq Blue went down https://status.linqapp.com/ Tue, 07 Oct 2025 19:07:05 +0000 https://status.linqapp.com/#e24a1e726bbfdb4480fd46addf728b6cdca0a0077309fada8549fc00768489d8 Platform API went down 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/ 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/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.