asn.dev

Observed topology

AS62005 BV-EU-AS

Unclassified RIPE

Upstreams 24 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 22
Adjacent (IPv6) 17
Upstream graph Who carries AS62005, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS62005 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 24

Networks observed carrying traffic for AS62005: 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.

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv62,396
AS56630Melbikomas UABHostingIPv4 IPv6815
AS9002RETN LimitedUnclassifiedIPv4 IPv6612
AS8849Melbikomas UABHostingIPv4 IPv6589
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv6439
AS6939Hurricane Electric LLCTransitIPv4 IPv6291
AS206446CLOUD LEASE LtdHostingIPv4 IPv6254
AS5511Orange S.A.TransitIPv4 IPv6164
AS42708Glesys ABUnclassifiedIPv4 IPv693
AS3303Swisscom (Schweiz) AGResidentialIPv430

All 24 upstreams →

Transit

Downstream networks

inferred

Networks for which AS62005 was observed as the last hop before the origin, meaning it appears to provide them transit.

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 24

Every AS seen directly next to AS62005 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv62,396
AS56630Melbikomas UABHostingIPv4 IPv6815
AS9002RETN LimitedUnclassifiedIPv4 IPv6612
AS8849Melbikomas UABHostingIPv4 IPv6589
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv6439
AS6939Hurricane Electric LLCTransitIPv4 IPv6291
AS206446CLOUD LEASE LtdHostingIPv4 IPv6254
AS5511Orange S.A.TransitIPv4 IPv6164
AS42708Glesys ABUnclassifiedIPv4 IPv693
AS3303Swisscom (Schweiz) AGResidentialIPv430

All 24 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.