Observed topology

AS266451 ROUTERNET PROVEDOR DE ACESSO LTDA ME

Residential APNIC

Upstreams 3 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266451: 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
AS14840	BR.Digital Telecom	Unclassified	IPv4 IPv6	229
AS28343	UNIFIQUE TELECOMUNICACOES S/A	Unclassified	IPv4 IPv6	47
AS16735	ALGAR TELECOM S/A	Unclassified	IPv4	22

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS268954	MARAU NET TECNOLOGIA LTDA	Residential	IPv4 IPv6	77
AS271187	Garbin Center Informatica Ltda Me	Unclassified	IPv4 IPv6	71

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS14840	BR.Digital Telecom	Unclassified	IPv4 IPv6	371
AS268954	MARAU NET TECNOLOGIA LTDA	Residential	IPv4 IPv6	77
AS271187	Garbin Center Informatica Ltda Me	Unclassified	IPv4 IPv6	71
AS28343	UNIFIQUE TELECOMUNICACOES S/A	Unclassified	IPv4 IPv6	58
AS16735	ALGAR TELECOM S/A	Unclassified	IPv4	22
AS266489	ZANCHET E PAIM TELECOM LTDA ME	Unclassified	IPv4	5

Provenance

Where this comes from

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