Observed topology
AS51465 FIXMAP-M3NET-TRANSIT FIXMAP GROUP
Hosting RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS51465: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 18 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 15 |
| AS174 | Cogent Communications, LLC | Transit | IPv6 | 6 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 5 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 4 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv6 | 4 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 3 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv6 | 2 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv6 | 2 |
| AS34019 | Hivane Association | Unclassified | IPv6 | 2 |
Transit
Downstream networks
Networks for which AS51465 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS59460 | M3.NET Sp. zoo | Unclassified | IPv4 | 781 |
| AS50188 | KOLNET Sp. z o.o. | Unclassified | IPv4 | 660 |
| AS39816 | Volta Communications Sp.z.o.o. | Residential | IPv4 | 600 |
| AS35199 | Enformatel Sp. z o.o. | Unclassified | IPv4 | 420 |
| AS44086 | Tonetic Group Sp z o.o. | Unclassified | IPv4 | 302 |
| AS210911 | Lubonet Swiatlowod Sp. z o.o. | Unclassified | IPv4 | 300 |
| AS60589 | Liquid Systems Sp. z o.o. | Unclassified | IPv4 | 240 |
| AS198424 | HLG Internet Sp. z o.o. | Residential | IPv4 | 198 |
| AS202050 | STIMO.NET SP. Z O.O. | Unclassified | IPv4 | 197 |
| AS57101 | WADOWICENET SP Z O O | Residential | IPv4 | 180 |
Adjacency
Adjacent networks
Every AS seen directly next to AS51465 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,794 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,400 |
| AS59460 | M3.NET Sp. zoo | Unclassified | IPv4 | 781 |
| AS39816 | Volta Communications Sp.z.o.o. | Residential | IPv4 | 736 |
| AS50188 | KOLNET Sp. z o.o. | Unclassified | IPv4 | 660 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 571 |
| AS35199 | Enformatel Sp. z o.o. | Unclassified | IPv4 | 512 |
| AS44086 | Tonetic Group Sp z o.o. | Unclassified | IPv4 | 302 |
| AS60589 | Liquid Systems Sp. z o.o. | Unclassified | IPv4 | 300 |
| AS210911 | Lubonet Swiatlowod Sp. z o.o. | Unclassified | IPv4 | 300 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.