asn.dev

Observed topology

AS16265 LeaseWeb Network B.V.

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS16265: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS60781LeaseWeb Netherlands B.V.HostingIPv4 IPv612,310
AS28753Leaseweb Deutschland GmbHHostingIPv4 IPv63,792
AS205544Leaseweb UK LimitedHostingIPv4 IPv62,624
AS30633Leaseweb USA, Inc.HostingIPv4 IPv61,725
AS59253LEASEWEB SINGAPORE PTE. LTD.HostingIPv4 IPv61,280
AS133752LEASEWEB HONG KONG LIMITEDHostingIPv4 IPv6606
AS134351Leaseweb Japan K.K.UnclassifiedIPv4 IPv6558
AS32613Leaseweb Canada Inc.HostingIPv4 IPv6340
AS136988LEASEWEB AUSTRALIA PTY LIMITEDUnclassifiedIPv4 IPv622

Adjacency

Adjacent networks

All 59

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

ASNetworkTypeFamiliesPaths seen
AS60781LeaseWeb Netherlands B.V.HostingIPv4 IPv612,310
AS28753Leaseweb Deutschland GmbHHostingIPv4 IPv63,792
AS6939Hurricane Electric LLCTransitIPv4 IPv63,159
AS205544Leaseweb UK LimitedHostingIPv4 IPv62,624
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv62,364
AS30633Leaseweb USA, Inc.HostingIPv4 IPv61,725
AS59253LEASEWEB SINGAPORE PTE. LTD.HostingIPv4 IPv61,280
AS24482SG.GSHostingIPv4 IPv61,147
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv6977
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv6931

All 59 adjacent →

Provenance

Where this comes from

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