asn.dev

Observed topology

AS39201 wavecom WaveCom Informatikai Kft.

Unclassified RIPE Cable/DSL/ISP

Upstreams 3 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 5
Upstream graph Who carries AS39201, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS39201 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39201: 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
AS44302NETregator Kft.UnclassifiedIPv4304
AS29278Rackhost Zrt.HostingIPv4 IPv6238
AS6939Hurricane Electric LLCTransitIPv612

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208126ViNetwork Kft.UnclassifiedIPv4 IPv6213
AS203246MOBILLAN-SAT Informatikai, Kereskedelmi es Szolgaltato KftUnclassifiedIPv4 IPv6122
AS204745Macronet System KftUnclassifiedIPv465
AS213669Varadi DanielResidentialIPv4 IPv652

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS29278Rackhost Zrt.HostingIPv4 IPv6540
AS44302NETregator Kft.UnclassifiedIPv4454
AS208126ViNetwork Kft.UnclassifiedIPv4 IPv6213
AS203246MOBILLAN-SAT Informatikai, Kereskedelmi es Szolgaltato KftUnclassifiedIPv4 IPv6122
AS204745Macronet System KftUnclassifiedIPv465
AS213669Varadi DanielResidentialIPv4 IPv652
AS6939Hurricane Electric LLCTransitIPv612

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.