asn.dev

Observed topology

AS262841 AS262841 - PTI TELECOMUNICACOES LTDA

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262841: 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
AS263444Open X Tecnologia LtdaUnclassifiedIPv4 IPv6333
AS24482SG.GSHostingIPv4 IPv614
AS35280F5 Networks SARLHostingIPv4 IPv614
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv614
AS28158Ampernet Telecomunicacoes LtdaUnclassifiedIPv44
AS25091IP-Max SAUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266354KSNET EIRELI - MEUnclassifiedIPv4 IPv679

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263444Open X Tecnologia LtdaUnclassifiedIPv4 IPv6582
AS266354KSNET EIRELI - MEUnclassifiedIPv4 IPv6319
AS28158Ampernet Telecomunicacoes LtdaUnclassifiedIPv469
AS24482SG.GSHostingIPv4 IPv619
AS35280F5 Networks SARLHostingIPv4 IPv614
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv614
AS25091IP-Max SAUnclassifiedIPv62

Provenance

Where this comes from

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