Linx Outage History
Linx is up right nowPingoru has recorded 5 incidents for Linx: 3 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 1 | 2 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 1 | 2 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 744 (0%) |
| November 2026 | 1 | 7 of 142 (5%) |
Incidents, newest first
Major November 3, 2026 Documentation site (docs.linxsecurity.io) unavailable 7h 10m Documentation (docs.linxsecurity.io)
Started Nov 03, 2026, 07:34 AM UTC· resolved Nov 03, 2026, 02:45 PM UTC
- investigating Nov 03, 2026, 07:34 AM UTC
Our documentation site, docs.linxsecurity.io, is currently unavailable due to an ongoing outage at our documentation hosting provider, GitBook. The Linx platform itself is not affected and continues to operate normally. We are monitoring the provider's status and will post an update as soon as the documentation site is restored.
- resolved Nov 03, 2026, 02:45 PM UTC
docs.linxsecurity.io is available again. GitBook is still reporting an ongoing incident, so we're monitoring and will resolve this report once they confirm full recovery.
- resolved Nov 04, 2026, 08:04 AM UTC
docs.linxsecurity.io has been fully available since yesterday. This report is resolved. The Linx platform was not affected at any point.
Minor August 6, 2026 AI Assistant - Chat requests failing 1h 40m AI Assistant (app.linxsecurity.io), AI Assistant (app.linxsecurity.io)
Started Aug 06, 2026, 12:30 PM UTC· resolved Aug 06, 2026, 02:10 PM UTC
- investigating Aug 06, 2026, 12:30 PM UTC
We are aware of an issue affecting the AI Assistant chat functionality. Users may experience errors when submitting chat requests. Our team has identified the root cause and is working on a fix.
- investigating Aug 06, 2026, 02:10 PM UTC
Fix has been deployed, and AI Chat is fully operational.
Minor June 22, 2026 AI Assistant - Chat requests failing 1h 58m AI Assistant (app.linxsecurity.io), AI Assistant (app.linxsecurity.io)
Started Jun 22, 2026, 01:17 PM UTC· resolved Jun 22, 2026, 03:15 PM UTC
- investigating Jun 22, 2026, 01:17 PM UTC
We are aware of an issue affecting the AI Assistant chat functionality. Users may experience errors when submitting chat requests. Our team has identified the root cause and is working on a fix.
- resolved Jun 22, 2026, 03:15 PM UTC
Fix has been deployed, and AI Chat is fully operational.
Major October 20, 2025 AWS Incident Causing Outage in US-East-1 5h 58m AI Assistant (app.linxsecurity.io), AI Assistant (app.linxsecurity.io)
Started Oct 20, 2025, 02:53 PM UTC· resolved Oct 20, 2025, 08:51 PM UTC
- investigating Oct 20, 2025, 02:53 PM UTC
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 [email protected] 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.
- investigating Oct 20, 2025, 03:45 PM UTC
No root cause and resolution from AWS still, we are still following up.
- investigating Oct 20, 2025, 04:57 PM UTC
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.
- investigating Oct 20, 2025, 06:18 PM UTC
AWS is still applying mitigations. Network issues are improving, and next update is expected in the upcoming hour.
- investigating Oct 20, 2025, 07:23 PM UTC
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.
- resolved Oct 20, 2025, 08:51 PM UTC
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.
Major October 20, 2025 AWS Incident Causing Outage in US-East-1 2h 56m AI Assistant (app.linxsecurity.io), AI Assistant (app.linxsecurity.io)
Started Oct 20, 2025, 07:15 AM UTC· resolved Oct 20, 2025, 10:11 AM UTC
- investigating Oct 20, 2025, 07:15 AM UTC
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 [email protected] 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.
- investigating Oct 20, 2025, 09:09 AM UTC
Update - We are continuing to investigate this issue.
- resolved Oct 20, 2025, 10:11 AM UTC
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/.
- investigating Oct 20, 2025, 10:11 AM UTC
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/.