asn.dev

Observed topology

AS20562 Broadband Hosting B.V.

Hosting RIPE

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

Transit

Upstream networks

inferred

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

All 388

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

ASNetworkTypeFamiliesPaths seen
AS60404The Infrastructure Group B.V.UnclassifiedIPv4924
AS1103SURF B.V.UnclassifiedIPv4 IPv6701
AS30238Cisco Systems Ironport DivisionUnclassifiedIPv4 IPv6684
AS39647Enreach Netherlands B.V.HostingIPv4 IPv6635
AS62240Clouvider LimitedHostingIPv4580
AS31673Uniserver Internet B.V.HostingIPv4 IPv6461
AS47583Hostinger International LimitedHostingIPv4453
AS30999EMTEL LIMITEDResidentialIPv4 IPv6429
AS20559Fundaments B.V.HostingIPv4 IPv6396
AS50399Open Line BVHostingIPv4356

All 388 downstreams →

Adjacency

Adjacent networks

All 456

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

ASNetworkTypeFamiliesPaths seen
AS214982Awaser Oman LLCUnclassifiedIPv47,775
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv67,330
AS24785Broadband Hosting B.V.HostingIPv4 IPv66,523
AS1103SURF B.V.UnclassifiedIPv4 IPv66,427
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv62,946
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv62,920
AS3741Dimension DataUnclassifiedIPv42,114
AS50304Blix Solutions ASUnclassifiedIPv4 IPv61,998
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv61,670
AS48185team.blue NVUnclassifiedIPv4 IPv61,561

All 456 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.