asn.dev

Observed topology

AS215439 PLAY2GO-NET

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS215439: 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
AS58212dataforest GmbHUnclassifiedIPv44,202
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv62,468
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv4 IPv61,793
AS52025ParadoxNetworks LimitedUnclassifiedIPv436
AS20473The Constant Company, LLCHostingIPv412
AS9002RETN LimitedUnclassifiedIPv49
AS62403PletX GmbHUnclassifiedIPv44
AS30823aurologic GmbHHostingIPv42
AS35598INETCOM CARRIER LLCUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS219337FZCOUnclassifiedIPv42,329
AS49993JSC NovocomUnclassifiedIPv456
AS213229MITELIS SECURITY LIMITEDUnclassifiedIPv634

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS58212dataforest GmbHUnclassifiedIPv4 IPv65,206
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv63,058
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv4 IPv62,513
AS219337FZCOUnclassifiedIPv42,329
AS9002RETN LimitedUnclassifiedIPv4170
AS49993JSC NovocomUnclassifiedIPv4112
AS52025ParadoxNetworks LimitedUnclassifiedIPv436
AS213229MITELIS SECURITY LIMITEDUnclassifiedIPv634
AS20473The Constant Company, LLCHostingIPv412
AS62403PletX GmbHUnclassifiedIPv44

All 12 adjacent →

Provenance

Where this comes from

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