asn.dev

Observed topology

AS266649 Netcity Tecnologia em Internet Ltda-ME

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266649: 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
AS53087TELY Ltda.ResidentialIPv4 IPv6128
AS266129LOCALLINK TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv692
AS269429LUCIANA P. DA SILVA-INFORMATICA-MEUnclassifiedIPv460
AS6939Hurricane Electric LLCTransitIPv634
AS269522MAISCONNECT TELECOMUnclassifiedIPv616
AS266240A2 TELECOM EIRELI - MEUnclassifiedIPv44
AS24482SG.GSHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269429LUCIANA P. DA SILVA-INFORMATICA-MEUnclassifiedIPv4118
AS266392vip telecom paraibaUnclassifiedIPv4 IPv663

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS53087TELY Ltda.ResidentialIPv4 IPv6265
AS269429LUCIANA P. DA SILVA-INFORMATICA-MEUnclassifiedIPv4178
AS266129LOCALLINK TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv692
AS266392vip telecom paraibaUnclassifiedIPv4 IPv663
AS266240A2 TELECOM EIRELI - MEUnclassifiedIPv448
AS6939Hurricane Electric LLCTransitIPv634
AS269522MAISCONNECT TELECOMUnclassifiedIPv616
AS24482SG.GSHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv61

Provenance

Where this comes from

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