asn.dev

Observed topology

AS51906 RECAST-AS

Unclassified RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51906: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6250
AS13237euNetworks GmbHUnclassifiedIPv4 IPv6218
AS3223Voxility LLPHostingIPv4179
AS6939Hurricane Electric LLCTransitIPv4 IPv6127
AS24961WIIT AGHostingIPv4 IPv6116
AS24482SG.GSHostingIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205868recast IT GmbH & Co. KGUnclassifiedIPv4 IPv6217

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13237euNetworks GmbHUnclassifiedIPv4 IPv6350
AS3356Level 3 Parent, LLCTransitIPv4 IPv6276
AS3223Voxility LLPHostingIPv4238
AS205868recast IT GmbH & Co. KGUnclassifiedIPv4 IPv6217
AS6939Hurricane Electric LLCTransitIPv4 IPv6127
AS24961WIIT AGHostingIPv4 IPv6116
AS24482SG.GSHostingIPv49

Provenance

Where this comes from

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