asn.dev

Observed topology

AS262893 P4 TELECOM LTDA

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262893: 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
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv61,902
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv61,050
AS6939Hurricane Electric LLCTransitIPv480
AS24482SG.GSHostingIPv4 IPv626

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS52952Millenium Com de Mat e Sist de Inf. LtdaUnclassifiedIPv463
AS262309BMBB SERVICOS DE COMUNICACAO LTDAUnclassifiedIPv428
AS264010Polli TelecomResidentialIPv4 IPv616

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv61,919
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv61,127
AS6939Hurricane Electric LLCTransitIPv491
AS52952Millenium Com de Mat e Sist de Inf. LtdaUnclassifiedIPv463
AS24482SG.GSHostingIPv4 IPv628
AS262309BMBB SERVICOS DE COMUNICACAO LTDAUnclassifiedIPv428
AS264010Polli TelecomResidentialIPv4 IPv616

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-25 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.