asn.dev

Observed topology

AS52648 Consorcio Conecte

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52648: 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
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6121
AS53087TELY Ltda.ResidentialIPv4113
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv642

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS52829NEWLINE TELECOMUnclassifiedIPv4 IPv6329
AS53118NETLINE TELECOMUnclassifiedIPv4 IPv6153
AS52812WRLINK TELECOMUnclassifiedIPv4 IPv6152
AS52768Alsol Provedor de Internet LtdaUnclassifiedIPv4 IPv695

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6504
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6372
AS52829NEWLINE TELECOMUnclassifiedIPv4 IPv6329
AS53118NETLINE TELECOMUnclassifiedIPv4 IPv6184
AS53087TELY Ltda.ResidentialIPv4166
AS52812WRLINK TELECOMUnclassifiedIPv4 IPv6152
AS52768Alsol Provedor de Internet LtdaUnclassifiedIPv4 IPv695

Provenance

Where this comes from

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