asn.dev

Observed topology

AS263343 PC2 TELECOM

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263343: 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
AS265269MEGA TELE INFORMATICAUnclassifiedIPv4 IPv689
AS271084TRYMNET PROVEDORUnclassifiedIPv4 IPv684
AS61922CNX TELECOMResidentialIPv4 IPv678
AS52573Une Telecom LtdaResidentialIPv4 IPv664
AS61929RODRIGUES E NECKEL LTDA - MEUnclassifiedIPv4 IPv631
AS263558RD TELECOM LTDA -MEResidentialIPv4 IPv615
AS53048CELANTE SERVICOS DE TELECOMUNICACOES LTDA - EPPUnclassifiedIPv4 IPv69
AS264997Direct Telecom LtdaUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS53153CINTE TELECOM COMERCIO E SERVICOS LTDAUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS265269MEGA TELE INFORMATICAUnclassifiedIPv4 IPv689
AS271084TRYMNET PROVEDORUnclassifiedIPv4 IPv684
AS61922CNX TELECOMResidentialIPv4 IPv678
AS52573Une Telecom LtdaResidentialIPv4 IPv664
AS61929RODRIGUES E NECKEL LTDA - MEUnclassifiedIPv4 IPv631
AS263558RD TELECOM LTDA -MEResidentialIPv4 IPv615
AS53048CELANTE SERVICOS DE TELECOMUNICACOES LTDA - EPPUnclassifiedIPv4 IPv69
AS264997Direct Telecom LtdaUnclassifiedIPv42
AS53153CINTE TELECOM COMERCIO E SERVICOS LTDAUnclassifiedIPv41

Provenance

Where this comes from

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