Observed topology

AS270966 AS270966 - 4W NET ES TELECOMUNICACOES LTDA

Hosting RIPE Network Services

Upstreams 1 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270966: 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
AS4230	CLARO S.A.	Residential	IPv6	32

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS263450	NORTE BRASIL NETWORK TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	825
AS61674	SPEED WIRELESS SERVICOS DE COMUNICACAO MULTIMIDIA	Unclassified	IPv4 IPv6	500
AS268707	4W NET ES TELECOMUNICACOES LTDA	Unclassified	IPv4	61
AS269485	JRNETWORKS Telecom	Unclassified	IPv4	58
AS272460	Ms Fibra Ltda	Unclassified	IPv6	32

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS4230	CLARO S.A.	Residential	IPv4 IPv6	1,693
AS263450	NORTE BRASIL NETWORK TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	1,092
AS61674	SPEED WIRELESS SERVICOS DE COMUNICACAO MULTIMIDIA	Unclassified	IPv4 IPv6	500
AS263934	InfoRR Solucoes em Tecnologia	Unclassified	IPv4	441
AS268707	4W NET ES TELECOMUNICACOES LTDA	Unclassified	IPv4	298
AS272460	Ms Fibra Ltda	Unclassified	IPv4 IPv6	154
AS269485	JRNETWORKS Telecom	Unclassified	IPv4	58

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.