Link11 Outage History

Started Oct 04, 2026, 07:51 PM UTC· resolved Oct 05, 2026, 02:00 PM UTC

1. investigating Oct 04, 2026, 07:51 PM UTC

   We are currently investigating some intermittent issues with our phone lines. Some of the calls are not being properly forwarded. Please use the following International number as the main one for the time being in case you having issues using our other numbers +972 73 200 52 00 — Link11 Customer Support Team

2. resolved Oct 05, 2026, 02:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 24, 2026, 08:55 PM UTC· resolved Sep 24, 2026, 10:47 PM UTC

1. investigating Sep 24, 2026, 08:55 PM UTC

   We are currently investigating intermittent errors / degraded performance in SG. If you are experiencing impact beyond the above, please contact our support team through the usual channels. — Link11 Customer Support Team

2. identified Sep 24, 2026, 09:17 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Sep 24, 2026, 09:27 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Sep 24, 2026, 10:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 16, 2026, 07:40 AM UTC· resolved Aug 16, 2026, 03:18 PM UTC

1. investigating Aug 15, 2026, 05:09 AM UTC

   We are currently investigating a potential issue affecting Link11 WAAP and Infrastructures connections in FFM7 (FR5). Traffic is being rerouted to alternative locations where possible. Our engineering teams are actively investigating with high priority. Customer traffic protection remains our top focus, and we will share a further update as soon as we have more information. If you are experiencing impact beyond the above, please contact our support team through the usual channels. — Link11 Customer Support Team

2. identified Aug 15, 2026, 06:28 AM UTC

   Datacenter outage occurring in FFM7 Equinix, due to a leaking chiller loop that is causing high temperatures. The customer traffic has been re-routed from affected systems.

3. identified Aug 15, 2026, 09:06 AM UTC

   We are still waiting for on-site access to the datacenter (FFM7 Equinix) to address the leaking chiller loop causing high temperatures. Customer traffic remains rerouted away from the affected systems, and our engineering team continues to monitor the situation closely. We understand the impact this ongoing incident may have and appreciate your patience. We will share the next update as soon as we have confirmation of access or further developments. If you're experiencing impact beyond what's described here, please reach out to our support team through the usual channels.

4. identified Aug 15, 2026, 12:17 PM UTC

   Aug 15, 2026 - 12:15 UTC: Update - Restoration work at the affected datacenter FFM7 (FR5 Equinix) is ongoing and is being carried out by the facility operator. On-site access to our equipment has not yet been possible; we are in continuous contact with the operator to obtain access as soon as conditions allow. Customer traffic remains rerouted away from the affected systems. As parts of our infrastructure at this location are still unavailable, full service verification is ongoing and some management and reporting functions may be temporarily limited. We will provide the next update as soon as we have confirmed access to the site or further relevant developments. If you are experiencing impact beyond what is described here, please contact our support team through the usual channels.

5. identified Aug 15, 2026, 02:53 PM UTC

   Aug 15, 2026 - 14:53 UTC Update - Restoration work at the affected datacenter (FFM7 Equinix) is still ongoing. The facility operator has confirmed that leaks in the chilled water cooling system caused water ingress into parts of the facility, resulting in the loss of cooling and elevated temperatures that forced affected systems offline. The leaks have since been isolated and the operator is working on restoring the cooling infrastructure. However, access to the affected areas - including our equipment - remains restricted for safety reasons, and no on-site work has been possible yet. We remain in continuous contact with the operator and have recovery hardware and personnel on standby to begin restoration as soon as access is granted. Customer traffic remains rerouted away from the affected systems. Some management and reporting functions remain temporarily limited. We will provide the next update as soon as we have additional information, at the latest by 16:55 UTC (18:50 CEST). If you are experiencing impact beyond what is described here, please contact our support team through the usual channels.

6. identified Aug 15, 2026, 06:35 PM UTC

   Update - Restoration work at the affected datacenter (FFM7 Equinix) is still ongoing. The facility operator has confirmed that leaks in the chilled water cooling system caused water ingress into parts of the facility, resulting in the loss of cooling and elevated temperatures that forced affected systems offline. The leaks have since been isolated and the operator has restored cooling for the majority of the datacenter. However, access to the affected areas - including our equipment - remains restricted for safety reasons, and no on-site work has been possible yet. We remain in continuous contact with the operator and have recovery hardware and personnel on standby to begin restoration as soon as access is granted. Customer traffic remains rerouted away from the affected systems. Some management and reporting functions remain temporarily limited. We will provide the next update as soon as we have additional information, at the latest by 19:00 UTC (21:00 CEST). If you are experiencing impact beyond what is described here, please contact our support team through the usual channels.

7. identified Aug 15, 2026, 09:41 PM UTC

   Update - Restoration work at the affected datacenter (FFM7 Equinix) is still ongoing. The facility operator has confirmed that leaks in the chilled water cooling system caused water ingress into parts of the facility, resulting in the loss of cooling and elevated temperatures that forced affected systems offline. The leaks have since been isolated and the operator has restored cooling for the majority of the datacenter. However, access to the affected areas - including our equipment - remains restricted for safety reasons, and no on-site work has been possible yet. We remain in continuous contact with the operator and have recovery hardware and personnel on standby to begin restoration as soon as access is granted. Customer traffic remains rerouted away from the affected systems. Some management and reporting functions remain temporarily limited. We will provide the next update as soon as we have additional information, at the latest by 23:59 UTC. If you are experiencing impact beyond what is described here, please contact our support team through the usual channels.

8. identified Aug 16, 2026, 01:48 AM UTC

   Update - Restoration work at the affected datacenter (FFM7 Equinix) is still ongoing. The facility operator has confirmed that leaks in the chilled water cooling system caused water ingress into parts of the facility, resulting in the loss of cooling and elevated temperatures that forced affected systems offline. The leaks have since been isolated and the operator has restored cooling for the majority of the datacenter. However, access to the affected areas - including our equipment - remains restricted for safety reasons, and no on-site work has been possible yet. We remain in continuous contact with the operator and have recovery hardware and personnel on standby to begin restoration as soon as access is granted. Customer traffic remains rerouted away from the affected systems. Some management and reporting functions remain temporarily limited. We will provide the next update as soon as we have additional information, at the latest by 03:59 UTC. If you are experiencing impact beyond what is described here, please contact our support team through the usual channels.

9. identified Aug 16, 2026, 04:42 AM UTC

   Update - Restoration work at the affected datacenter (FFM7 Equinix) is still ongoing. The facility operator has confirmed that leaks in the chilled water cooling system caused water ingress into parts of the facility, resulting in the loss of cooling and elevated temperatures that forced affected systems offline. The leaks have since been isolated and the operator has restored cooling for the majority of the datacenter. However, access to the affected areas - including our equipment - remains restricted for safety reasons, and no on-site work has been possible yet. We remain in continuous contact with the operator and have recovery hardware and personnel on standby to begin restoration as soon as access is granted. Customer traffic remains rerouted away from the affected systems. Some management and reporting functions remain temporarily limited. We will provide the next update as soon as we have additional information, at the latest by 07:00 UTC. If you are experiencing impact beyond what is described here, please contact our support team through the usual channels.

10. identified Aug 16, 2026, 06:35 AM UTC

    Aug 16, 2026 - 06:35 UTC We have now been granted access to the affected datacenter FFM7 (FRA5 Equinix). The facility operator has completed cooling restoration, and temperatures in the affected areas have returned to normal operating ranges. Our technicians are on their way to the site and will begin with a detailed assessment of our equipment, followed by a controlled, staged restoration of the affected systems. Replacement hardware has been prepared in advance and is available if required. Customer traffic remains rerouted away from the affected systems and stays protected throughout the restoration. Some management and reporting functions remain temporarily limited; restoring these is being worked on in parallel. As the restoration will be performed carefully in stages, we cannot yet provide a completion time. We will provide the next update once the on-site assessment is complete, at the latest by 10:00 UTC. If you are experiencing impact beyond what is described here, please contact our support team through the usual channels.

11. identified Aug 16, 2026, 07:40 AM UTC

    Update - Aug 16, 2026 - 07:40 UTC Our technicians have arrived at the datacenter FFM7 (FRA5 Equinix) and have started the on-site assessment of our equipment. Once the assessment is complete, the controlled, staged restoration of the affected systems will begin. Customer traffic remains rerouted away from the affected systems. Some management and reporting functions remain temporarily limited. We will provide the next update once the assessment results are available, at the latest by 12:00 UTC (14:00 CEST). If you are experiencing impact beyond what is described here, please contact our support team through the usual channels.

12. identified Aug 16, 2026, 09:26 AM UTC

    Update - Aug 16, 2026 - 09:25 UTC The on-site assessment has been completed and we have started to gracefully power the affected location (FFM7) back up. Systems are being brought online in a controlled, staged sequence to ensure a safe and stable recovery. Customer traffic remains rerouted away from the affected systems and will only be moved back once the location is fully verified as stable. Some management and reporting functions remain temporarily limited and are expected to recover progressively as systems come back online. We will provide the next update once the power-up sequence has progressed, at the latest by 15:00 UTC (17:00 CEST). If you are experiencing impact beyond what is described here, please contact our support team through the usual channels.

13. monitoring Aug 16, 2026, 10:10 AM UTC

    Aug 16, 2026 - 10:10 UTC All services at the affected location (FFM7) are back up and operating as expected. We will continue to monitor the system health closely. Please note: customer BGP sessions towards FFM7 have not been re-enabled yet. They will be brought back gracefully after an additional monitoring period has passed, to ensure a stable and safe return of traffic. Customer traffic remains served via alternative locations until then and stays fully protected - no action is required on your side. We will provide the next update once customer BGP sessions are being re-enabled, at the latest by 14:00 UTC (16:00 CEST). If you are experiencing impact beyond what is described here, please contact our support team through the usual channels.

14. resolved Aug 16, 2026, 03:18 PM UTC

    Aug 16, 2026 - 15:20 UTC All customer BGP sessions have been re-enabled and have re-established successfully. Infrastructure Protection services at FFM7 are fully active again, and transit connections have been restored. All services are operating normally. We will continue to monitor system health closely over the coming hours before resolving this incident. Please note: traffic statistics from the incident timeframe may currently not be displayed for some services. We are investigating whether this data can be restored and will handle this separately from the incident itself - live traffic data and reporting are working normally. Thank you for your patience during this incident. A root cause analysis will be made available to affected customers once our investigation is complete. If you are experiencing any residual issues, please contact our support team through the usual channels.

Read the full incident report →

Started Aug 11, 2026, 04:07 PM UTC· resolved Aug 11, 2026, 10:14 PM UTC

1. investigating Aug 11, 2026, 04:07 PM UTC

   [Investigating] Potential Issue – Link11 WAAP / Secure CDN We are currently investigating a potential issue affecting Link11 WAAP and Secure CDN. Customers whose services are delivered via our Singapore and Hong Kong locations may experience increased latency, intermittent errors, or degraded performance. Traffic is being rerouted to alternative locations where possible. Our engineering teams are actively investigating with high priority. Customer traffic protection remains our top focus, and we will share a further update as soon as we have more information. If you are experiencing impact beyond the above, please contact our support team through the usual channels. — Link11 Customer Support Team

2. investigating Aug 11, 2026, 04:07 PM UTC

   We are continuing to investigate this issue.

3. investigating Aug 11, 2026, 04:12 PM UTC

   We are continuing to investigate this issue.

4. resolved Aug 11, 2026, 10:14 PM UTC

   Dear valued customer, The backbone routing has been restored and we are awaiting updates and details on what occurred. We sincerely apologize for this situation and promise you to undertake all necessary actions to avoid such inconveniences in the future. If you have any further questions, write to us at [email protected].

Read the full incident report →

Started Jul 06, 2026, 07:41 AM UTC· resolved Jul 06, 2026, 02:10 PM UTC

1. investigating Jul 06, 2026, 07:41 AM UTC

   We are currently investigating an elevated rate of timeout errors affecting European regions, observed on traffic from the Link11 Cloud to customer backends.

2. investigating Jul 06, 2026, 10:21 AM UTC

   We are continuing to investigate this issue.

3. resolved Jul 06, 2026, 02:10 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 05, 2026, 12:43 PM UTC· resolved Jul 06, 2026, 07:24 AM UTC

1. investigating Jul 05, 2026, 12:43 PM UTC

   We are currently investigating a potential issue that may be impacting service availability or performance. Our team is working to identify the cause and will provide updates as soon as more informaton is available.

2. monitoring Jul 05, 2026, 03:30 PM UTC

   At approximately 11:20 CET, the Link11 Singapore node experienced a high traffic condition as a result of multiple attacks against the Link11 customer base. Link11 was able to mitigate the majority of the attack; however a portion of the attack was able to saturate a backbone segment that was used by the WAAP platform for internal process communication, resulting in slow poxy responses. This intermittent saturation occurred from 11:20 to 13:30 CET before NetOPS were able to optimize routing.

3. monitoring Jul 06, 2026, 07:24 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Jul 06, 2026, 07:24 AM UTC

   We are continuing to monitor for any further issues.

Read the full incident report →

Started Jun 24, 2026, 11:03 AM UTC· resolved Jun 24, 2026, 11:54 AM UTC

1. investigating Jun 24, 2026, 11:03 AM UTC

   We are currently experiencing an elevated rate of error messages across our monitoring systems. Connectivity to multiple sites appears to be interrupted. Our engineering team is actively investigating the issue and working to identify the root cause. We will provide a further update as soon as we have more information. We apologize for any inconvenience this may cause.

2. investigating Jun 24, 2026, 11:19 AM UTC

   A fix has been deployed. A recent change to our load balancer configuration has been reverted and connectivity should resume promptly. We are continuing to monitor all systems to confirm full recovery.

3. monitoring Jun 24, 2026, 11:20 AM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Jun 24, 2026, 11:44 AM UTC

   We are continuing to monitor for any further issues.

5. resolved Jun 24, 2026, 11:54 AM UTC

   This incident has been resolved. All operations have been fully restored, and our systems are performing normally. The root cause was identified as a load balancer configuration change which has been reverted. We thank you for your patience and apologize for any disruption caused.

Read the full incident report →

Started Jun 08, 2026, 06:49 AM UTC· resolved Jun 10, 2026, 03:11 PM UTC

1. investigating Jun 08, 2026, 06:46 AM UTC

   We are currently experiencing connectivity issues at our Miami site affecting GRE tunnels terminated in this location. Link11 is actively working with its transport providers to restore services as quickly as possible. We will provide further updates as soon as more information becomes available.

2. monitoring Jun 08, 2026, 07:13 AM UTC

   Cogent has restored data transport service on one of the affected lines, and the Miami site and associated services are now reachable. We are continuing to monitor the situation to ensure stability while work continues to fully restore redundancy. A further update will follow once services are confirmed fully restored.

3. resolved Jun 08, 2026, 12:57 PM UTC

   The Miami site and associated services remain reachable via the restored line. However, not all transport lines have been restored yet, so the site is currently operating without full redundancy. Link11 is continuing to work with the transport provider to bring the remaining lines back into service. We will provide a further update once full redundancy has been restored.

Read the full incident report →

Started Apr 14, 2026, 11:43 PM UTC· resolved Apr 14, 2026, 11:52 PM UTC

1. investigating Apr 14, 2026, 11:43 PM UTC

   We are currently investigating a potential issue that may be impacting service availability or performance. Our team is working to identify the cause and will provide updates as soon as more information is available. Affected Products: • Cloud Insights / Network DDoS Detector ⚠️ Restoring full service is our highest priority. Our teams are fully engaged, and we will share further updates here as new information becomes available. Thank you for your understanding and trust.

2. identified Apr 14, 2026, 11:48 PM UTC

   We have identified the root cause of the issue and are actively working on a solution. Further updates will be provided as progress is made.

3. monitoring Apr 14, 2026, 11:50 PM UTC

   A fix has been implemented and services are currently stable. We are closely monitoring the system to ensure continued stability and will mark this incident as resolved once we confirm full recovery.

4. resolved Apr 14, 2026, 11:52 PM UTC

   The issue has been resolved and all services are operating normally. We will continue to monitor and have initiated a full post-incident review to prevent recurrence. Post-incident details, including the Root Cause Analysis (RCA) and the Post-Incident Improvement Plan (PIIP), are available upon request via Link11 Support or your designated account contact.

Read the full incident report →

Started Mar 24, 2026, 02:23 AM UTC· resolved Mar 24, 2026, 03:28 AM UTC

1. investigating Mar 24, 2026, 02:23 AM UTC

   We would like to inform you that our teams are currently investigating a potential intermittent issue on some of the proxies in LN network within our DSS2(DOSarrest platform). Our engineering and operations teams are actively analyzing the situation, and we will provide further updates as soon as additional details become available. We appreciate your understanding and will share more information as soon as we have it. If you have any questions or notice unexpected behavior, please contact our Support team.

2. identified Mar 24, 2026, 02:54 AM UTC

   The issue has been identified and a fix is being implemented.

3. resolved Mar 24, 2026, 03:28 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 09, 2026, 09:32 AM UTC· resolved Mar 09, 2026, 05:02 PM UTC

1. investigating Mar 09, 2026, 09:32 AM UTC

   We would like to inform you that our teams are currently investigating a potential issue within our infrastructure. At this stage, we have not identified any confirmed impact on service performance or availability. This message is being shared proactively to keep you fully informed. Our engineering and operations teams are actively analyzing the situation, and we will provide further updates as soon as additional details become available. Please note: -Your services may not be affected, and if any impact occurs, we currently expect it to be minimal. -We are informing you early to ensure full transparency while our investigation is ongoing. -No action is required from your side at this moment. We appreciate your understanding and will share more information as soon as we have it. If you have any questions or notice unexpected behavior, please contact our Support team.

2. monitoring Mar 09, 2026, 12:56 PM UTC

   We temporarily disabled the environment responsible for the recent connectivity issues, implemented a fix, and have since re-enabled it. Since doing so, we have not observed any further issues, and overall connectivity remains stable. Our teams continue to monitor the situation closely to ensure ongoing reliability and quickly address any anomalies that may arise. Thank you for your patience and understanding while we worked to resolve this.

3. resolved Mar 09, 2026, 05:02 PM UTC

   Restarting the affected network services resolved the immediate issue and service has been confirmed stabilized. Nevertheless, at this point in time, the exact trigger is not yet confirmed. Our team is actively investigating contributing factors and implementing additional monitoring and safeguards to react once needed.

Read the full incident report →

Started Mar 03, 2026, 11:43 AM UTC· resolved Mar 04, 2026, 09:47 AM UTC

1. investigating Mar 03, 2026, 11:43 AM UTC

   We are currently investigating networking issues within the Link11 Backbone that are affecting multiple customers across different services. The impact may include partial packet loss, slow responses, or intermittent unavailability. At this stage, it is not yet clear which services are affected or whether the issue originates within the Link11 network or with external connectivity providers. Our engineering teams are actively analyzing the situation and working to restore stable connectivity as quickly as possible. We will provide further updates as soon as new information becomes available. Thank you for your patience and understanding.

2. monitoring Mar 03, 2026, 12:40 PM UTC

   We have isolated the environment responsible for the recent connectivity issues and implemented a bypass to route traffic away from the affected segment. With this change in place, overall connectivity has significantly improved, and the previously observed disruptions should now be largely reduced or no longer present. Our teams continue to monitor the situation closely to ensure stability and identify any remaining anomalies. Thank you for your patience and understanding while we are working on this.

3. resolved Mar 04, 2026, 09:47 AM UTC

   The connectivity issues impacting parts of the Link11 Backbone have been fully resolved. Following our previous mitigation steps, our engineering teams deployed a permanent fix to the affected systems. After implementing and verifying the correction, the systems were successfully brought back into production and reintegrated into our infrastructure. All components have been running stable since 06:30 UTC, and no further anomalies have been observed. We continue to monitor the platform closely, but no additional impact is expected. Thank you for your patience and cooperation throughout this incident.

Read the full incident report →

Started Feb 16, 2026, 09:10 PM UTC· resolved Feb 17, 2026, 07:32 PM UTC

1. investigating Feb 16, 2026, 09:05 PM UTC

   We are currently experiencing an issue with one of our 10G linecard in our Zurich location. The issue is related to an FPC, which has affected associated filters. To mitigate customer impact, traffic has been proactively bypassed around the affected filters. We continue to investigate the root cause and are working toward a permanent resolution.

2. investigating Feb 16, 2026, 09:55 PM UTC

   We are currently experiencing a temporary service disruption in our Zurich location. Customers connected via our Zurich POP area may experience temporary service disruption. Our engineering team is actively monitoring the situation and working to bring all services back to full capacity as quickly as possible.

3. investigating Feb 16, 2026, 10:02 PM UTC

   We are continuing to investigate this issue.

4. investigating Feb 16, 2026, 11:08 PM UTC

   Following the technician’s investigation at the Data Center, we were unable to repair the linecard. A replacement is scheduled for tomorrow, and we will provide updates once the replacement is completed. Thank you for your patience and understanding.

5. investigating Feb 16, 2026, 11:09 PM UTC

   We are continuing to investigate this issue.

6. investigating Feb 17, 2026, 12:01 PM UTC

   Our technician has arrived at the Frankfurt site and collected the replacement card. They are now en route to Zurich, Switzerland. Next update: ETA approximately 5 hours.

7. resolved Feb 17, 2026, 07:32 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 04, 2026, 05:48 PM UTC· resolved Feb 04, 2026, 05:48 PM UTC

1. resolved Feb 04, 2026, 05:48 PM UTC

   Link11 experienced an issue within the NetFlow processing system that led to possible false positive attack‑mode triggers at 15:15 UTC across several customer environments on the DDoS infrastructure platform. The underlying issue has been resolved, and all systems are operating normally again. We are continuing to investigate the root cause and will share a detailed RCA as soon as the analysis is completed.

Read the full incident report →

Started Feb 03, 2026, 02:03 PM UTC· resolved Feb 03, 2026, 03:43 PM UTC

1. investigating Feb 03, 2026, 02:03 PM UTC

   We have observed issues with triggering attack mode based on NetFlow limits. Our team is actively investigating and working on a resolution. We will provide further updates as soon as more information becomes available. All other protection mechanisms remain fully operational and unaffected.

2. resolved Feb 03, 2026, 03:43 PM UTC

   The issue has been resolved. This was limited to an internal logging issue and did not affect customers or protection.

Read the full incident report →

Started Jan 22, 2026, 03:42 PM UTC· resolved Jan 26, 2026, 06:18 PM UTC

1. monitoring Jan 22, 2026, 03:42 PM UTC

   Between 13:52 CET (12:52 UTC) and 13:56 CET (12:56 UTC), we observed a brief period of degraded network performance at our FFM‑7 location, which may have impacted all products and services. The issue has since been resolved, and traffic levels have returned to normal. Our teams are continuing to investigate the root cause with the highest priority. Further updates will be provided as soon as more information becomes available.

2. resolved Jan 26, 2026, 06:18 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 08, 2026, 05:39 PM UTC· resolved Jan 13, 2026, 04:18 PM UTC

1. investigating Jan 08, 2026, 05:39 PM UTC

   We are currently experiencing an issue affecting our reporting systems. All protection mechanisms remain fully operational. Our team is actively investigating the matter. In exceptional cases or if there is any uncertainty, please contact [email protected]. Our support team can perform an individual review to confirm whether mitigation occurred during a specific timeframe. Thank you for your understanding and patience as we work to resolve this issue.

2. resolved Jan 13, 2026, 04:18 PM UTC

   This incident has been resolved. Thank you for your understanding and patience.

Read the full incident report →

Started Dec 10, 2025, 01:47 PM UTC· resolved Dec 10, 2025, 01:47 PM UTC

1. investigating Dec 10, 2025, 01:47 PM UTC

   We apologize for the inconvenience. We had a partial outage to our ddosproxy, alarming (attack notifications) and bot mitigation to limited number of domains from 13:53 CET until 14:23 CET. We are currently investigating the cause of the problem.

2. resolved Dec 10, 2025, 01:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 21, 2025, 08:11 PM UTC· resolved Nov 21, 2025, 10:14 PM UTC

1. investigating Nov 21, 2025, 08:11 PM UTC

   Dear valued customer, Link11 has detected some issues with Bot management mitigation process. On a limited set of customers, the "Bot management" is working only in detection mode, with no active mitigation. Our team is currently working on this problem. If you have any further questions, write to us at [email protected]

2. resolved Nov 21, 2025, 10:14 PM UTC

   Dear valued customer, It was a false alert regarding the mitigation, it was never impacted, there was an issue with displaying the data. It is fixed now.

Read the full incident report →

Started Oct 21, 2025, 05:50 AM UTC· resolved Oct 21, 2025, 02:02 PM UTC

1. identified Oct 21, 2025, 05:50 AM UTC

   Dear valued customer, Link11 has encountered an unusual outage which might have affected your service. Description and possible impact: We are currently experiencing a disruption on the backbone connection between Frankfurt and London. This issue may impact production traffic in general. Our network operations team is actively investigating and taking measures to mitigate any potential service effects. Incident start: October 21, 2025 – 07:05 CEST In the unlikely case that the issue is not resolved immediately, you receive regular updates with relevant details as soon as the situation develops. If you have any further questions, write to us at [email protected]

2. resolved Dec 10, 2025, 02:02 PM UTC

   Issue was resolved.

Read the full incident report →

Started Aug 05, 2025, 01:09 PM UTC· resolved Aug 05, 2025, 04:20 PM UTC

1. investigating Aug 05, 2025, 01:09 PM UTC

   Our DDOS proxies are continuously restarting due to an issue with HTTP/2, affecting only certain instances. HTTP/2 will be disabled temporarily for affected customers until we identify and resolve the root cause

2. resolved Aug 05, 2025, 04:20 PM UTC

   The issue has been resolved and the fix is being rolled out.

Read the full incident report →

Started Jun 26, 2025, 03:26 PM UTC· resolved Jun 26, 2025, 03:48 PM UTC

1. investigating Jun 26, 2025, 03:26 PM UTC

   Impact: Cosmetic only Start Time: 26.06.25, 09:30 UTC Affected Component: WebGUI - Infrastructure Protection Data We are currently investigating a cosmetic display issue affecting the "Infrastructure Protection" product within our WebGUI. What's Happening: Clients may observe that data for "Infrastructure Protection" is not being displayed in the WebGUI. This is a visual-only issue. Impact: Please be assured that this issue is cosmetic only. - The "Infrastructure Protection" product itself continues to function normally, and your infrastructure remains protected. - All other functionalities within the WebGUI are operating as expected. - No client operations or data are impacted by this display issue. Current Status: Our team is actively investigating the root cause of this display anomaly. There is no known workaround at this time. We understand the importance of accurate data representation and are working to resolve this as quickly as possible. We will provide updates here as soon as more information becomes available, including an estimated time to resolution.

2. resolved Jun 26, 2025, 03:48 PM UTC

   Resolved - The cosmetic display issue affecting the Infrastructure Protection data within our WebGUI has been resolved. What Happened: Between approximately 09:30 UTC today and 15:45 UTC, clients observed that data for Infrastructure Protection was not being displayed in the WebGUI. This was a cosmetic issue only. Resolution: Our engineering team has successfully implemented a fix. Data for "Infrastructure Protection" will now begin to display correctly in the WebGUI for all new incoming data from this point forward. Important Note Regarding Historical Data: Please be aware that data generated between 09:30 UTC and 15:45 UTC will not be visible in the WebGUI. This specific historical data is not recoverable for display purposes through the WebGUI, but the underlying protection and product functionality were never impacted. Impact During Incident: As previously communicated, during the period of the incident, the Infrastructure Protection itself continued to function normally, ensuring your infrastructure remained protected. All other functionalities within the WebGUI were also operating as expected. No client operations or data were impacted by the display issue itself. We thank you for your patience and understanding during this incident. We are committed to providing a reliable service and continuous improvements.

Read the full incident report →

Started Jun 10, 2025, 10:30 AM UTC· resolved Jun 10, 2025, 10:30 AM UTC

1. resolved Jun 10, 2025, 01:19 PM UTC

   We had a partial packet filter issue in Frankfurt - ffm7, London - lon2, Zurich - zrh1. The traffic was impacted between 10:31 AM UTC and 10:43 AM UTC

Read the full incident report →

Started Jun 10, 2025, 05:30 AM UTC· resolved Jun 10, 2025, 05:30 AM UTC

1. resolved Jun 10, 2025, 07:30 AM UTC

   Dear valued customer, Link11 has encountered an unusual outage which might have affected your service. Description and possible impact: Miami site was offline due to a transport problem Incident start: 05:46 UTC Incident end : 06:57 UTC If you have any further questions, write to us at [email protected]

Read the full incident report →

Started Jun 03, 2025, 02:00 AM UTC· resolved Jun 03, 2025, 04:00 AM UTC

1. resolved Jun 03, 2025, 01:24 PM UTC

   Link11 POPs affected : Frankfurt: ffm7& ffm14 London: lon2 Singapore: sgp1 06:06, CET - The clusters reported high CPU usage for local filters. 06:10, CET - Internal monitoring reported packet loss for some of the probes. SOC is escalating the events. 06:16, CET - The on-call operations team decided to reload the affected filters and escalate the issue to the Link11 engineering team for further investigation. 06:55, CET - The filter reload process is complete. Monitoring systems report no packet loss. Open points: - The engineering team should investigate the high CPU events and provide a fix. - The Operations team should improve the filter reload process.

Read the full incident report →