asn.dev

Observed topology

AS59545 VXBITS VXbits Network

Unclassified RIPE NSP

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

Transit

Upstream networks

All 25

Networks observed carrying traffic for AS59545: 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
AS2914NTT America, Inc.TransitIPv4 IPv6219
AS20562Broadband Hosting B.V.HostingIPv4130
AS24785Broadband Hosting B.V.HostingIPv472
AS200020Stichting NBIP-NaWasUnclassifiedIPv460
AS6939Hurricane Electric LLCTransitIPv650
AS50673Serverius Holding B.V.UnclassifiedIPv416
AS174Cogent Communications, LLCTransitIPv415
AS24482SG.GSHostingIPv4 IPv611
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv49

All 25 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS206348Holland Datacenters B.V.UnclassifiedIPv4244
AS202477AM BVUnclassifiedIPv4122

Adjacency

Adjacent networks

All 28

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6345
AS20562Broadband Hosting B.V.HostingIPv4245
AS206348Holland Datacenters B.V.UnclassifiedIPv4244
AS24785Broadband Hosting B.V.HostingIPv4129
AS202477AM BVUnclassifiedIPv4122
AS200020Stichting NBIP-NaWasUnclassifiedIPv460
AS6939Hurricane Electric LLCTransitIPv650
AS50673Serverius Holding B.V.UnclassifiedIPv428
AS174Cogent Communications, LLCTransitIPv421
AS24482SG.GSHostingIPv4 IPv617

All 28 adjacent →

Provenance

Where this comes from

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