asn.dev

Observed topology

AS59939 WIBO-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS59939: 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
AS59796StormWall s.r.o.UnclassifiedIPv4174
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv6152
AS1820WNET TELECOM USA Corp.ResidentialIPv4 IPv698
AS44066firstcolo GmbHUnclassifiedIPv4 IPv692
AS44600"GIGATRANS UKRAINE", LLCUnclassifiedIPv4 IPv630
AS43298Storm Networks LLCUnclassifiedIPv43

Transit

Downstream networks

inferred

Networks for which AS59939 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 AS59939 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS59796StormWall s.r.o.UnclassifiedIPv4174
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv6152
AS1820WNET TELECOM USA Corp.ResidentialIPv4 IPv698
AS44066firstcolo GmbHUnclassifiedIPv4 IPv692
AS44600"GIGATRANS UKRAINE", LLCUnclassifiedIPv4 IPv630
AS43298Storm Networks LLCUnclassifiedIPv43

Provenance

Where this comes from

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