asn.dev

Observed topology

AS266584 Conect- Provedor de Internet Ltda EPP

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266584: 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
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6330
AS271608plus internet telecomUnclassifiedIPv474
AS52719ESPECTRO Gall LtdaUnclassifiedIPv419
AS266337MARLON LIMA GOMES MEUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS274669CloudiNet Provedor de InternetUnclassifiedIPv631
AS273694C. R. DE S. MENDES COMERCIO E SERVICOS LTDAUnclassifiedIPv61

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6362
AS271608plus internet telecomUnclassifiedIPv474
AS274669CloudiNet Provedor de InternetUnclassifiedIPv631
AS52719ESPECTRO Gall LtdaUnclassifiedIPv419
AS266337MARLON LIMA GOMES MEUnclassifiedIPv61
AS273694C. R. DE S. MENDES COMERCIO E SERVICOS LTDAUnclassifiedIPv61

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.