asn.dev

Observed topology

AS262818 g j pereira

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262818: 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
AS28220Alares Cabo Servicos de Telecomunicacoes S.A.ResidentialIPv4 IPv6317
AS266460NetGo Telecomunicacoes do BrasilResidentialIPv4 IPv6100

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271592NETS PROVEDOR DE INTERNET TELECOM LTDAUnclassifiedIPv4 IPv6230
AS265999Cianet Provedor de Internet EIRELIUnclassifiedIPv4 IPv6161
AS273810CM TECNOLOGIA INTEGRADA LTDAUnclassifiedIPv4 IPv682
AS268438ELADIO FERREIRA DOS SANTOS NETO-MEUnclassifiedIPv463
AS266092R. COSTA DO NASCIMENTOUnclassifiedIPv430
AS272184ANTONIO HAROLDO P DE SOUZAUnclassifiedIPv628

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28220Alares Cabo Servicos de Telecomunicacoes S.A.ResidentialIPv4 IPv6907
AS271592NETS PROVEDOR DE INTERNET TELECOM LTDAUnclassifiedIPv4 IPv6230
AS266460NetGo Telecomunicacoes do BrasilResidentialIPv4 IPv6190
AS265999Cianet Provedor de Internet EIRELIUnclassifiedIPv4 IPv6161
AS273810CM TECNOLOGIA INTEGRADA LTDAUnclassifiedIPv4 IPv6147
AS268438ELADIO FERREIRA DOS SANTOS NETO-MEUnclassifiedIPv463
AS272184ANTONIO HAROLDO P DE SOUZAUnclassifiedIPv4 IPv649
AS266092R. COSTA DO NASCIMENTOUnclassifiedIPv430

Provenance

Where this comes from

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