asn.dev

Observed topology

AS263347 CEDNET PROVEDOR INTERNET

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263347: 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
AS10429TELEFONICA BRASIL S.AResidentialIPv4 IPv61,103
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6929
AS6939Hurricane Electric LLCTransitIPv4 IPv6298
AS24482SG.GSHostingIPv4 IPv626
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv625
AS52863UPX TECNOLOGIA LTDAUnclassifiedIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269643CENTRAL NETWORKS E TECNLOGIAUnclassifiedIPv4 IPv6152
AS268396LOPES & TINOCO LTDAUnclassifiedIPv4 IPv6120
AS2733454EDGE TECNOLOGIA LTDA MEUnclassifiedIPv61

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS10429TELEFONICA BRASIL S.AResidentialIPv4 IPv61,222
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv61,079
AS6939Hurricane Electric LLCTransitIPv4 IPv6298
AS269643CENTRAL NETWORKS E TECNLOGIAUnclassifiedIPv4 IPv6152
AS268396LOPES & TINOCO LTDAUnclassifiedIPv4 IPv6120
AS24482SG.GSHostingIPv4 IPv628
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv627
AS52863UPX TECNOLOGIA LTDAUnclassifiedIPv46
AS2733454EDGE TECNOLOGIA LTDA MEUnclassifiedIPv61

Provenance

Where this comes from

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