Incidents reported on status page for Linx Security https://status.linxsecurity.io/ https://d1lppblt9t2x15.cloudfront.net/logos/e58309f0615e8017212b83db1812bf9e.jpeg https://status.linxsecurity.io/ en https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 20:51:00 -0000 https://status.linxsecurity.io/incident/747409#381bbb756306da420ac5cedb03311193612d0db9b53db541bd3050f47f5e6e9f As Service recovery across all AWS services continues to improve. And our monitoring and metrics have returned to normal in the past couple of hours, we are resolving this incident. Please feel free to reach our support if you experience any other issues. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 20:51:00 -0000 https://status.linxsecurity.io/incident/747409#381bbb756306da420ac5cedb03311193612d0db9b53db541bd3050f47f5e6e9f As Service recovery across all AWS services continues to improve. And our monitoring and metrics have returned to normal in the past couple of hours, we are resolving this incident. Please feel free to reach our support if you experience any other issues. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 20:51:00 -0000 https://status.linxsecurity.io/incident/747409#381bbb756306da420ac5cedb03311193612d0db9b53db541bd3050f47f5e6e9f As Service recovery across all AWS services continues to improve. And our monitoring and metrics have returned to normal in the past couple of hours, we are resolving this incident. Please feel free to reach our support if you experience any other issues. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 20:51:00 -0000 https://status.linxsecurity.io/incident/747409#381bbb756306da420ac5cedb03311193612d0db9b53db541bd3050f47f5e6e9f As Service recovery across all AWS services continues to improve. And our monitoring and metrics have returned to normal in the past couple of hours, we are resolving this incident. Please feel free to reach our support if you experience any other issues. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 19:23:00 -0000 https://status.linxsecurity.io/incident/747409#80dc0c64d4897b7d57e13fa7a0870d823e4b5efafba3ec505e5299b16359baa5 We continue to observe recovery across all of our AWS services. The Portal is currently usable, and seems to be stable, as well as the other components. But we are still monitoring and keeping track with AWS to verify full resolution before we resolve this issue completely. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 19:23:00 -0000 https://status.linxsecurity.io/incident/747409#80dc0c64d4897b7d57e13fa7a0870d823e4b5efafba3ec505e5299b16359baa5 We continue to observe recovery across all of our AWS services. The Portal is currently usable, and seems to be stable, as well as the other components. But we are still monitoring and keeping track with AWS to verify full resolution before we resolve this issue completely. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 19:23:00 -0000 https://status.linxsecurity.io/incident/747409#80dc0c64d4897b7d57e13fa7a0870d823e4b5efafba3ec505e5299b16359baa5 We continue to observe recovery across all of our AWS services. The Portal is currently usable, and seems to be stable, as well as the other components. But we are still monitoring and keeping track with AWS to verify full resolution before we resolve this issue completely. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 19:23:00 -0000 https://status.linxsecurity.io/incident/747409#80dc0c64d4897b7d57e13fa7a0870d823e4b5efafba3ec505e5299b16359baa5 We continue to observe recovery across all of our AWS services. The Portal is currently usable, and seems to be stable, as well as the other components. But we are still monitoring and keeping track with AWS to verify full resolution before we resolve this issue completely. https://status.linxsecurity.io/ Mon, 20 Oct 2025 18:31:40 +0000 https://status.linxsecurity.io/#f9cc7abea0010180fa1ac1a995bf08fd8e26f6f7d3b0ca1e587b3fd0064b31b0 app.linxsecurity.io recovered https://status.linxsecurity.io/ Mon, 20 Oct 2025 18:31:40 +0000 https://status.linxsecurity.io/#f9cc7abea0010180fa1ac1a995bf08fd8e26f6f7d3b0ca1e587b3fd0064b31b0 app.linxsecurity.io recovered https://status.linxsecurity.io/ Mon, 20 Oct 2025 18:31:40 +0000 https://status.linxsecurity.io/#f9cc7abea0010180fa1ac1a995bf08fd8e26f6f7d3b0ca1e587b3fd0064b31b0 app.linxsecurity.io recovered https://status.linxsecurity.io/ Mon, 20 Oct 2025 18:31:40 +0000 https://status.linxsecurity.io/#f9cc7abea0010180fa1ac1a995bf08fd8e26f6f7d3b0ca1e587b3fd0064b31b0 app.linxsecurity.io recovered https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 18:18:00 -0000 https://status.linxsecurity.io/incident/747409#3addcf973a7b8c7a6b7c7d6b00b80bf83fa13cb8662074dcd2d057ef7c4704d1 AWS is still applying mitigations. Network issues are improving, and next update is expected in the upcoming hour. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 18:18:00 -0000 https://status.linxsecurity.io/incident/747409#3addcf973a7b8c7a6b7c7d6b00b80bf83fa13cb8662074dcd2d057ef7c4704d1 AWS is still applying mitigations. Network issues are improving, and next update is expected in the upcoming hour. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 18:18:00 -0000 https://status.linxsecurity.io/incident/747409#3addcf973a7b8c7a6b7c7d6b00b80bf83fa13cb8662074dcd2d057ef7c4704d1 AWS is still applying mitigations. Network issues are improving, and next update is expected in the upcoming hour. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 18:18:00 -0000 https://status.linxsecurity.io/incident/747409#3addcf973a7b8c7a6b7c7d6b00b80bf83fa13cb8662074dcd2d057ef7c4704d1 AWS is still applying mitigations. Network issues are improving, and next update is expected in the upcoming hour. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 16:57:00 -0000 https://status.linxsecurity.io/incident/747409#4045060003db1370a1dc175a6d0b094c1300b44bf0a4d270846fdb7da5bd7cf7 AWS confirmed the root cause is an underlying internal subsystem responsible for monitoring the health of our network load balancers. Mitigation implementations are still in progress. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 16:57:00 -0000 https://status.linxsecurity.io/incident/747409#4045060003db1370a1dc175a6d0b094c1300b44bf0a4d270846fdb7da5bd7cf7 AWS confirmed the root cause is an underlying internal subsystem responsible for monitoring the health of our network load balancers. Mitigation implementations are still in progress. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 16:57:00 -0000 https://status.linxsecurity.io/incident/747409#4045060003db1370a1dc175a6d0b094c1300b44bf0a4d270846fdb7da5bd7cf7 AWS confirmed the root cause is an underlying internal subsystem responsible for monitoring the health of our network load balancers. Mitigation implementations are still in progress. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 16:57:00 -0000 https://status.linxsecurity.io/incident/747409#4045060003db1370a1dc175a6d0b094c1300b44bf0a4d270846fdb7da5bd7cf7 AWS confirmed the root cause is an underlying internal subsystem responsible for monitoring the health of our network load balancers. Mitigation implementations are still in progress. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 15:45:00 -0000 https://status.linxsecurity.io/incident/747409#1b763ef6d895ceeb7774e096330198433890c25884e4795326c178d0ecbf51b7 No root cause and resolution from AWS still, we are still following up. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 15:45:00 -0000 https://status.linxsecurity.io/incident/747409#1b763ef6d895ceeb7774e096330198433890c25884e4795326c178d0ecbf51b7 No root cause and resolution from AWS still, we are still following up. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 15:45:00 -0000 https://status.linxsecurity.io/incident/747409#1b763ef6d895ceeb7774e096330198433890c25884e4795326c178d0ecbf51b7 No root cause and resolution from AWS still, we are still following up. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 15:45:00 -0000 https://status.linxsecurity.io/incident/747409#1b763ef6d895ceeb7774e096330198433890c25884e4795326c178d0ecbf51b7 No root cause and resolution from AWS still, we are still following up. https://status.linxsecurity.io/ Mon, 20 Oct 2025 14:56:28 +0000 https://status.linxsecurity.io/#f9cc7abea0010180fa1ac1a995bf08fd8e26f6f7d3b0ca1e587b3fd0064b31b0 app.linxsecurity.io went down https://status.linxsecurity.io/ Mon, 20 Oct 2025 14:56:28 +0000 https://status.linxsecurity.io/#f9cc7abea0010180fa1ac1a995bf08fd8e26f6f7d3b0ca1e587b3fd0064b31b0 app.linxsecurity.io went down https://status.linxsecurity.io/ Mon, 20 Oct 2025 14:56:28 +0000 https://status.linxsecurity.io/#f9cc7abea0010180fa1ac1a995bf08fd8e26f6f7d3b0ca1e587b3fd0064b31b0 app.linxsecurity.io went down https://status.linxsecurity.io/ Mon, 20 Oct 2025 14:56:28 +0000 https://status.linxsecurity.io/#f9cc7abea0010180fa1ac1a995bf08fd8e26f6f7d3b0ca1e587b3fd0064b31b0 app.linxsecurity.io went down https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 14:53:00 -0000 https://status.linxsecurity.io/incident/747409#3d7c6a46ede9d8cb05f64de42955df7f4c42c338da97e934d0bbd847055bed0a We are currently experiencing a major disruption due to disruptions in the AWS US-East-1 region (https://health.aws.amazon.com/health/status) As a result: • Some Linx's services are impacted. • This is not due to an issue with our application. the disruption is driven by AWS region-wide issues. What we’re doing: • Our engineering and infrastructure teams are coordinating with AWS and monitoring the public AWS Health dashboard for updates. • We are assessing our disaster recovery (DR) plan and preparing to enable a failover or redeployment into a secondary region if required. • We will monitor for updates from AWS and will initiate the failover for our stack if we determine the outage will be prolonged. What you can do: • Please remain patient - we will provide status updates every 30 minutes (or sooner as new information becomes available). • We recommend temporarily postponing any non-critical operations until the system is fully restored. • If you have urgent business-critical needs, please contact our support team at support@linxsecurity.io with “URGENT: US-East-1 outage impact” in the subject and we’ll prioritize your request. Next update: In ~30 minutes or as soon as we have meaningful new information. Root cause & post-mortem (to follow): Once the incident is resolved, we will publish a full incident report summarizing the cause of the outage, its impact, how our DR plan responded (or will respond), and our plan for improving resilience going forward. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 14:53:00 -0000 https://status.linxsecurity.io/incident/747409#3d7c6a46ede9d8cb05f64de42955df7f4c42c338da97e934d0bbd847055bed0a We are currently experiencing a major disruption due to disruptions in the AWS US-East-1 region (https://health.aws.amazon.com/health/status) As a result: • Some Linx's services are impacted. • This is not due to an issue with our application. the disruption is driven by AWS region-wide issues. What we’re doing: • Our engineering and infrastructure teams are coordinating with AWS and monitoring the public AWS Health dashboard for updates. • We are assessing our disaster recovery (DR) plan and preparing to enable a failover or redeployment into a secondary region if required. • We will monitor for updates from AWS and will initiate the failover for our stack if we determine the outage will be prolonged. What you can do: • Please remain patient - we will provide status updates every 30 minutes (or sooner as new information becomes available). • We recommend temporarily postponing any non-critical operations until the system is fully restored. • If you have urgent business-critical needs, please contact our support team at support@linxsecurity.io with “URGENT: US-East-1 outage impact” in the subject and we’ll prioritize your request. Next update: In ~30 minutes or as soon as we have meaningful new information. Root cause & post-mortem (to follow): Once the incident is resolved, we will publish a full incident report summarizing the cause of the outage, its impact, how our DR plan responded (or will respond), and our plan for improving resilience going forward. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 14:53:00 -0000 https://status.linxsecurity.io/incident/747409#3d7c6a46ede9d8cb05f64de42955df7f4c42c338da97e934d0bbd847055bed0a We are currently experiencing a major disruption due to disruptions in the AWS US-East-1 region (https://health.aws.amazon.com/health/status) As a result: • Some Linx's services are impacted. • This is not due to an issue with our application. the disruption is driven by AWS region-wide issues. What we’re doing: • Our engineering and infrastructure teams are coordinating with AWS and monitoring the public AWS Health dashboard for updates. • We are assessing our disaster recovery (DR) plan and preparing to enable a failover or redeployment into a secondary region if required. • We will monitor for updates from AWS and will initiate the failover for our stack if we determine the outage will be prolonged. What you can do: • Please remain patient - we will provide status updates every 30 minutes (or sooner as new information becomes available). • We recommend temporarily postponing any non-critical operations until the system is fully restored. • If you have urgent business-critical needs, please contact our support team at support@linxsecurity.io with “URGENT: US-East-1 outage impact” in the subject and we’ll prioritize your request. Next update: In ~30 minutes or as soon as we have meaningful new information. Root cause & post-mortem (to follow): Once the incident is resolved, we will publish a full incident report summarizing the cause of the outage, its impact, how our DR plan responded (or will respond), and our plan for improving resilience going forward. https://status.linxsecurity.io/incident/747409 Mon, 20 Oct 2025 14:53:00 -0000 https://status.linxsecurity.io/incident/747409#3d7c6a46ede9d8cb05f64de42955df7f4c42c338da97e934d0bbd847055bed0a We are currently experiencing a major disruption due to disruptions in the AWS US-East-1 region (https://health.aws.amazon.com/health/status) As a result: • Some Linx's services are impacted. • This is not due to an issue with our application. the disruption is driven by AWS region-wide issues. What we’re doing: • Our engineering and infrastructure teams are coordinating with AWS and monitoring the public AWS Health dashboard for updates. • We are assessing our disaster recovery (DR) plan and preparing to enable a failover or redeployment into a secondary region if required. • We will monitor for updates from AWS and will initiate the failover for our stack if we determine the outage will be prolonged. What you can do: • Please remain patient - we will provide status updates every 30 minutes (or sooner as new information becomes available). • We recommend temporarily postponing any non-critical operations until the system is fully restored. • If you have urgent business-critical needs, please contact our support team at support@linxsecurity.io with “URGENT: US-East-1 outage impact” in the subject and we’ll prioritize your request. Next update: In ~30 minutes or as soon as we have meaningful new information. Root cause & post-mortem (to follow): Once the incident is resolved, we will publish a full incident report summarizing the cause of the outage, its impact, how our DR plan responded (or will respond), and our plan for improving resilience going forward. https://status.linxsecurity.io/incident/747029 Mon, 20 Oct 2025 10:11:00 -0000 https://status.linxsecurity.io/incident/747029#b8f34ee9916aae8ca0fe95dd1d416dc66812c570a1342052090ca030a8a29b91 We are seeing signs of recovery from the ongoing AWS incident impacting the US-East-1 region. We will continue to monitor the situation closely and provide an update once full recovery is confirmed. For more details from AWS, visit https://health.aws.amazon.com/. https://status.linxsecurity.io/incident/747029 Mon, 20 Oct 2025 10:11:00 -0000 https://status.linxsecurity.io/incident/747029#b8f34ee9916aae8ca0fe95dd1d416dc66812c570a1342052090ca030a8a29b91 We are seeing signs of recovery from the ongoing AWS incident impacting the US-East-1 region. We will continue to monitor the situation closely and provide an update once full recovery is confirmed. For more details from AWS, visit https://health.aws.amazon.com/. https://status.linxsecurity.io/incident/747029 Mon, 20 Oct 2025 10:11:00 -0000 https://status.linxsecurity.io/incident/747029#b8f34ee9916aae8ca0fe95dd1d416dc66812c570a1342052090ca030a8a29b91 We are seeing signs of recovery from the ongoing AWS incident impacting the US-East-1 region. We will continue to monitor the situation closely and provide an update once full recovery is confirmed. For more details from AWS, visit https://health.aws.amazon.com/. https://status.linxsecurity.io/incident/747029 Mon, 20 Oct 2025 10:11:00 -0000 https://status.linxsecurity.io/incident/747029#b8f34ee9916aae8ca0fe95dd1d416dc66812c570a1342052090ca030a8a29b91 We are seeing signs of recovery from the ongoing AWS incident impacting the US-East-1 region. We will continue to monitor the situation closely and provide an update once full recovery is confirmed. For more details from AWS, visit https://health.aws.amazon.com/. https://status.linxsecurity.io/ Mon, 20 Oct 2025 09:25:11 +0000 https://status.linxsecurity.io/#261193f4f19ee19fa3bcc90c5afb4ff8bfbadf2173989521b574acaaab70e7e9 app.linxsecurity.io recovered https://status.linxsecurity.io/ Mon, 20 Oct 2025 09:25:11 +0000 https://status.linxsecurity.io/#261193f4f19ee19fa3bcc90c5afb4ff8bfbadf2173989521b574acaaab70e7e9 app.linxsecurity.io recovered https://status.linxsecurity.io/ Mon, 20 Oct 2025 09:25:11 +0000 https://status.linxsecurity.io/#261193f4f19ee19fa3bcc90c5afb4ff8bfbadf2173989521b574acaaab70e7e9 app.linxsecurity.io recovered https://status.linxsecurity.io/ Mon, 20 Oct 2025 09:25:11 +0000 https://status.linxsecurity.io/#261193f4f19ee19fa3bcc90c5afb4ff8bfbadf2173989521b574acaaab70e7e9 app.linxsecurity.io recovered https://status.linxsecurity.io/incident/747029 Mon, 20 Oct 2025 09:09:00 -0000 https://status.linxsecurity.io/incident/747029#fa285d977813cf7384f9dc8409b63b3f8c21b252c77d2327b9c5be9f3dd3def0 Update - We are continuing to investigate this issue. https://status.linxsecurity.io/incident/747029 Mon, 20 Oct 2025 09:09:00 -0000 https://status.linxsecurity.io/incident/747029#fa285d977813cf7384f9dc8409b63b3f8c21b252c77d2327b9c5be9f3dd3def0 Update - We are continuing to investigate this issue. https://status.linxsecurity.io/incident/747029 Mon, 20 Oct 2025 09:09:00 -0000 https://status.linxsecurity.io/incident/747029#fa285d977813cf7384f9dc8409b63b3f8c21b252c77d2327b9c5be9f3dd3def0 Update - We are continuing to investigate this issue. https://status.linxsecurity.io/incident/747029 Mon, 20 Oct 2025 09:09:00 -0000 https://status.linxsecurity.io/incident/747029#fa285d977813cf7384f9dc8409b63b3f8c21b252c77d2327b9c5be9f3dd3def0 Update - We are continuing to investigate this issue. https://status.linxsecurity.io/ Mon, 20 Oct 2025 08:30:49 +0000 https://status.linxsecurity.io/#261193f4f19ee19fa3bcc90c5afb4ff8bfbadf2173989521b574acaaab70e7e9 app.linxsecurity.io went down https://status.linxsecurity.io/ Mon, 20 Oct 2025 08:30:49 +0000 https://status.linxsecurity.io/#261193f4f19ee19fa3bcc90c5afb4ff8bfbadf2173989521b574acaaab70e7e9 app.linxsecurity.io went down https://status.linxsecurity.io/ Mon, 20 Oct 2025 08:30:49 +0000 https://status.linxsecurity.io/#261193f4f19ee19fa3bcc90c5afb4ff8bfbadf2173989521b574acaaab70e7e9 app.linxsecurity.io went down https://status.linxsecurity.io/ Mon, 20 Oct 2025 08:30:49 +0000 https://status.linxsecurity.io/#261193f4f19ee19fa3bcc90c5afb4ff8bfbadf2173989521b574acaaab70e7e9 app.linxsecurity.io went down https://status.linxsecurity.io/incident/747029 Mon, 20 Oct 2025 07:15:00 -0000 https://status.linxsecurity.io/incident/747029#4ca9590f9a220dca505cfce50e375c67dbef1843e777432b6dc0649615640e3c We are currently experiencing a major disruption due to disruptions in the AWS US-East-1 region. As a result: • All of our services are impacted. • This is not due to an issue with our application. the disruption is driven by AWS region-wide issues. What we’re doing: • Our engineering and infrastructure teams are coordinating with AWS and monitoring the public AWS Health dashboard for updates. • We are assessing our disaster recovery (DR) plan and preparing to enable a failover or redeployment into a secondary region if required. • We will monitor for updates from AWS and will initiate the failover for our stack if we determine the outage will be prolonged. What you can do: • Please remain patient - we will provide status updates every 30 minutes (or sooner as new information becomes available). • We recommend temporarily postponing any non-critical operations until the system is fully restored. • If you have urgent business-critical needs, please contact our support team at support@linxsecurity.io with “URGENT: US-East-1 outage impact” in the subject and we’ll prioritize your request. Next update: In ~30 minutes or as soon as we have meaningful new information. Root cause & post-mortem (to follow): Once the incident is resolved, we will publish a full incident report summarizing the cause of the outage, its impact, how our DR plan responded (or will respond), and our plan for improving resilience going forward. https://status.linxsecurity.io/incident/747029 Mon, 20 Oct 2025 07:15:00 -0000 https://status.linxsecurity.io/incident/747029#4ca9590f9a220dca505cfce50e375c67dbef1843e777432b6dc0649615640e3c We are currently experiencing a major disruption due to disruptions in the AWS US-East-1 region. As a result: • All of our services are impacted. • This is not due to an issue with our application. the disruption is driven by AWS region-wide issues. What we’re doing: • Our engineering and infrastructure teams are coordinating with AWS and monitoring the public AWS Health dashboard for updates. • We are assessing our disaster recovery (DR) plan and preparing to enable a failover or redeployment into a secondary region if required. • We will monitor for updates from AWS and will initiate the failover for our stack if we determine the outage will be prolonged. What you can do: • Please remain patient - we will provide status updates every 30 minutes (or sooner as new information becomes available). • We recommend temporarily postponing any non-critical operations until the system is fully restored. • If you have urgent business-critical needs, please contact our support team at support@linxsecurity.io with “URGENT: US-East-1 outage impact” in the subject and we’ll prioritize your request. Next update: In ~30 minutes or as soon as we have meaningful new information. Root cause & post-mortem (to follow): Once the incident is resolved, we will publish a full incident report summarizing the cause of the outage, its impact, how our DR plan responded (or will respond), and our plan for improving resilience going forward. https://status.linxsecurity.io/incident/747029 Mon, 20 Oct 2025 07:15:00 -0000 https://status.linxsecurity.io/incident/747029#4ca9590f9a220dca505cfce50e375c67dbef1843e777432b6dc0649615640e3c We are currently experiencing a major disruption due to disruptions in the AWS US-East-1 region. As a result: • All of our services are impacted. • This is not due to an issue with our application. the disruption is driven by AWS region-wide issues. What we’re doing: • Our engineering and infrastructure teams are coordinating with AWS and monitoring the public AWS Health dashboard for updates. • We are assessing our disaster recovery (DR) plan and preparing to enable a failover or redeployment into a secondary region if required. • We will monitor for updates from AWS and will initiate the failover for our stack if we determine the outage will be prolonged. What you can do: • Please remain patient - we will provide status updates every 30 minutes (or sooner as new information becomes available). • We recommend temporarily postponing any non-critical operations until the system is fully restored. • If you have urgent business-critical needs, please contact our support team at support@linxsecurity.io with “URGENT: US-East-1 outage impact” in the subject and we’ll prioritize your request. Next update: In ~30 minutes or as soon as we have meaningful new information. Root cause & post-mortem (to follow): Once the incident is resolved, we will publish a full incident report summarizing the cause of the outage, its impact, how our DR plan responded (or will respond), and our plan for improving resilience going forward. https://status.linxsecurity.io/incident/747029 Mon, 20 Oct 2025 07:15:00 -0000 https://status.linxsecurity.io/incident/747029#4ca9590f9a220dca505cfce50e375c67dbef1843e777432b6dc0649615640e3c We are currently experiencing a major disruption due to disruptions in the AWS US-East-1 region. As a result: • All of our services are impacted. • This is not due to an issue with our application. the disruption is driven by AWS region-wide issues. What we’re doing: • Our engineering and infrastructure teams are coordinating with AWS and monitoring the public AWS Health dashboard for updates. • We are assessing our disaster recovery (DR) plan and preparing to enable a failover or redeployment into a secondary region if required. • We will monitor for updates from AWS and will initiate the failover for our stack if we determine the outage will be prolonged. What you can do: • Please remain patient - we will provide status updates every 30 minutes (or sooner as new information becomes available). • We recommend temporarily postponing any non-critical operations until the system is fully restored. • If you have urgent business-critical needs, please contact our support team at support@linxsecurity.io with “URGENT: US-East-1 outage impact” in the subject and we’ll prioritize your request. Next update: In ~30 minutes or as soon as we have meaningful new information. Root cause & post-mortem (to follow): Once the incident is resolved, we will publish a full incident report summarizing the cause of the outage, its impact, how our DR plan responded (or will respond), and our plan for improving resilience going forward.