Comparison Overview
London Internet Exchange (LINX)

London Internet Exchange (LINX)
London, GB
Last Update: 10/03/2026
Founded in 1994, the London Internet Exchange (LINX) is one of the world's leading Internet exchange points (IXPs), providing peering services to over 900 autonomous systems (ASNs) globally. As a member-owned, not-for-profit organisation, LINX operates IXPs in London...

e&
Abu Dhabi, Abu Dhabi, AE
Last Update: 08/09/2026
We're a global technology group focused on innovation and collaboration to create a better future for all. Since 1976, we've been pioneering new technologies and expanding our reach to more people and places. Today, we provide services to over 163 million customers acro...
Compliance Ranges Comparison

London Internet Exchange (LINX)







e&






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for London Internet Exchange (LINX) in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for e& in 2026.
Incident History - London Internet Exchange (LINX) (X = Date, Y = Severity)
London Internet Exchange (LINX) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - e& (X = Date, Y = Severity)
e& cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

London Internet Exchange (LINX)

e&
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.