asn.dev

Observed topology

AS21267 Wavenet-AS21267 Wavenet Limited

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 24

Networks observed carrying traffic for AS21267: 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 IPv62,079
AS6939Hurricane Electric LLCTransitIPv4 IPv6459
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6166
AS33891Core-Backbone GmbHHostingIPv4110
AS50304Blix Solutions ASUnclassifiedIPv4110
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv656
AS24482SG.GSHostingIPv4 IPv656
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv656
AS48185team.blue NVUnclassifiedIPv4 IPv656
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv656

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS29676Gradwell Communications LimitedUnclassifiedIPv4840

Adjacency

Adjacent networks

All 26

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv62,079
AS29676Gradwell Communications LimitedUnclassifiedIPv4840
AS6939Hurricane Electric LLCTransitIPv4 IPv6585
AS2914NTT America, Inc.TransitIPv4392
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6208
AS33891Core-Backbone GmbHHostingIPv4138
AS50304Blix Solutions ASUnclassifiedIPv4138
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv670
AS24482SG.GSHostingIPv4 IPv670
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv670

Provenance

Where this comes from

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