asn.dev

Observed topology

AS266242 AS266242 - VIANET GUARACIAMA EIRELI ME

Hosting LACNIC Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266242: 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
AS52928NORTETEL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6484

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269459PROVEDOR RODRIGUES FERREIRA LTDAUnclassifiedIPv4 IPv6484
AS61885MGNETMOC LTDAUnclassifiedIPv4 IPv6400
AS268667NET MAIS SOLUCOES EM REDE LTDA - MEUnclassifiedIPv4 IPv6228
AS267173NetMontes Telecomunicacoes e Servicos LtdaUnclassifiedIPv4192
AS271285MG TELECOMUnclassifiedIPv453

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52928NORTETEL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv61,841
AS269459PROVEDOR RODRIGUES FERREIRA LTDAUnclassifiedIPv4 IPv6484
AS61885MGNETMOC LTDAUnclassifiedIPv4 IPv6400
AS268667NET MAIS SOLUCOES EM REDE LTDA - MEUnclassifiedIPv4 IPv6228
AS267173NetMontes Telecomunicacoes e Servicos LtdaUnclassifiedIPv4192
AS271285MG TELECOMUnclassifiedIPv453

Provenance

Where this comes from

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