asn.dev

Observed topology

AS200005 ASAVIE-TECHNOLOGIES-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS200005: 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
AS20940Akamai International B.V.HostingIPv41,711
AS13237euNetworks GmbHUnclassifiedIPv4258
AS6939Hurricane Electric LLCTransitIPv4 IPv6183
AS31122Digiweb ltdUnclassifiedIPv4 IPv6176
AS1299Arelion Sweden ABTransitIPv430
AS3356Level 3 Parent, LLCTransitIPv429
AS3303Swisscom (Schweiz) AGResidentialIPv48
AS9002RETN LimitedUnclassifiedIPv64
AS20562Broadband Hosting B.V.HostingIPv41

Transit

Downstream networks

inferred

Networks for which AS200005 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS20940Akamai International B.V.HostingIPv41,711
AS13237euNetworks GmbHUnclassifiedIPv4258
AS6939Hurricane Electric LLCTransitIPv4 IPv6183
AS31122Digiweb ltdUnclassifiedIPv4 IPv6176
AS1299Arelion Sweden ABTransitIPv430
AS3356Level 3 Parent, LLCTransitIPv429
AS3303Swisscom (Schweiz) AGResidentialIPv48
AS9002RETN LimitedUnclassifiedIPv64
AS20562Broadband Hosting B.V.HostingIPv41

Provenance

Where this comes from

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