Observed topology

AS263440 AS263440 - WAVE UP TELECOM BRASIL LTDA - ME

Unclassified LACNIC

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 6

Upstream graph Who carries AS263440, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS263440 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS270600	BL PROVEDOR DE ACESSO A INTERNET LTDA	Residential	IPv4 IPv6	154
AS14840	BR.Digital Telecom	Unclassified	IPv4 IPv6	147
AS269096	N&K TECNOLOGIA LTDA	Unclassified	IPv4 IPv6	94
AS21574	Century Telecom Ltda	Unclassified	IPv4 IPv6	47
AS6939	Hurricane Electric LLC	Transit	IPv6	12
AS24482	SG.GS	Hosting	IPv4 IPv6	4

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS268188	ATIVA TELECOM LTDA	Residential	IPv4	401

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS268188	ATIVA TELECOM LTDA	Residential	IPv4	401
AS267613	ELETRONET S.A.	Unclassified	IPv4	330
AS14840	BR.Digital Telecom	Unclassified	IPv4 IPv6	205
AS270600	BL PROVEDOR DE ACESSO A INTERNET LTDA	Residential	IPv4 IPv6	154
AS269096	N&K TECNOLOGIA LTDA	Unclassified	IPv4 IPv6	94
AS21574	Century Telecom Ltda	Unclassified	IPv4 IPv6	47
AS6939	Hurricane Electric LLC	Transit	IPv6	12
AS24482	SG.GS	Hosting	IPv4 IPv6	11
AS37721	Virtual Technologies & Solutions	Residential	IPv4	6

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.