Observed topology
AS41495 FAELIX Faelix Limited
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS41495: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29222 | Infomaniak Network SA | Hosting | IPv4 IPv6 | 210 |
| AS4455 | IX Reach Ltd | Unclassified | IPv4 IPv6 | 58 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 49 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 17 |
| AS31216 | BSO Network Solutions SAS | Unclassified | IPv4 | 15 |
| AS3223 | Voxility LLP | Hosting | IPv4 | 13 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 12 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 5 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 3 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 3 |
Transit
Downstream networks
Networks for which AS41495 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS42009 | AVR Group Limited | Unclassified | IPv4 IPv6 | 154 |
| AS210206 | Metro Security (GB) PLC | Unclassified | IPv4 IPv6 | 138 |
| AS211501 | High Tide Group Limited | Unclassified | IPv4 IPv6 | 75 |
| AS207652 | Key IoT Limited | Unclassified | IPv4 IPv6 | 64 |
| AS211175 | Caudata Ltd | Unclassified | IPv4 IPv6 | 64 |
| AS34611 | Matthew Southgate | Unclassified | IPv4 | 60 |
| AS200700 | BMC TV LTD | Residential | IPv4 | 50 |
| AS44749 | Pinnacom Ltd | Residential | IPv4 IPv6 | 44 |
| AS60431 | PNO Solutions Limited | Unclassified | IPv6 | 36 |
| AS216055 | Wren Olivia Wood | Unclassified | IPv6 | 36 |
Adjacency
Adjacent networks
Every AS seen directly next to AS41495 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29222 | Infomaniak Network SA | Hosting | IPv4 IPv6 | 243 |
| AS4455 | IX Reach Ltd | Unclassified | IPv4 IPv6 | 202 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 180 |
| AS42009 | AVR Group Limited | Unclassified | IPv4 IPv6 | 154 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 151 |
| AS210206 | Metro Security (GB) PLC | Unclassified | IPv4 IPv6 | 138 |
| AS3223 | Voxility LLP | Hosting | IPv4 | 118 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 103 |
| AS211501 | High Tide Group Limited | Unclassified | IPv4 IPv6 | 94 |
| AS207652 | Key IoT Limited | Unclassified | IPv4 IPv6 | 64 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.