asn.dev

Observed topology

AS263129 AS263129 - Wavemax Internet

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263129: 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
AS52771GIGA BYTE TELECOMUNICACOES LTDAResidentialIPv4 IPv6335
AS267059NETVIP MTResidentialIPv484
AS6939Hurricane Electric LLCTransitIPv642
AS24482SG.GSHostingIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268262INNOVA TECNOLOGIA LTDA MEUnclassifiedIPv4 IPv6497
AS262803NETULTRA PROVEDOR DE INTERNETUnclassifiedIPv4 IPv698
AS265282DOMINA NET TELECOMResidentialIPv413

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52771GIGA BYTE TELECOMUNICACOES LTDAResidentialIPv4 IPv6859
AS268262INNOVA TECNOLOGIA LTDA MEUnclassifiedIPv4 IPv6497
AS262803NETULTRA PROVEDOR DE INTERNETUnclassifiedIPv4 IPv698
AS6939Hurricane Electric LLCTransitIPv4 IPv692
AS267059NETVIP MTResidentialIPv484
AS263629ALLREDE TELECOM MT / BRASIL TECPARUnclassifiedIPv625
AS265282DOMINA NET TELECOMResidentialIPv413
AS24482SG.GSHostingIPv4 IPv68
AS35280F5 Networks SARLHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv62

Provenance

Where this comes from

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