asn.dev

Observed topology

AS56701 AVANTA-AS LLC "AVANTA TELECOM"

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS56701: 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
AS3216PJSC "Vimpelcom"MobileIPv4330
AS12389PJSC RostelecomResidentialIPv4312
AS31500Global Network Management IncUnclassifiedIPv4172
AS31133PJSC MegaFonMobileIPv4146
AS6939Hurricane Electric LLCTransitIPv4132
AS8551Bezeq International Ltd.UnclassifiedIPv422
AS24482SG.GSHostingIPv422
AS37721Virtual Technologies & SolutionsResidentialIPv422
AS48362Stadtwerke FeldkirchResidentialIPv422
AS49673Truenetwork LLCUnclassifiedIPv422

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS61324D-TELEKOM LLCUnclassifiedIPv433
AS202248YA.RU LLCUnclassifiedIPv428

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS3216PJSC "Vimpelcom"MobileIPv4330
AS12389PJSC RostelecomResidentialIPv4312
AS31500Global Network Management IncUnclassifiedIPv4184
AS31133PJSC MegaFonMobileIPv4160
AS6939Hurricane Electric LLCTransitIPv4132
AS61324D-TELEKOM LLCUnclassifiedIPv433
AS202248YA.RU LLCUnclassifiedIPv428
AS56655Gigahost ASUnclassifiedIPv427
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv427
AS50673Serverius Holding B.V.UnclassifiedIPv425

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.