asn.dev

Observed topology

AS27747 Telecentro S.A.

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS27747: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv64,995
AS3356Level 3 Parent, LLCTransitIPv4 IPv64,794
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv63,422
AS174Cogent Communications, LLCTransitIPv4 IPv62,383
AS22927de ArgentinaMobileIPv4 IPv61,792

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263756INTERNET SRLResidentialIPv4201
AS273240SAUnclassifiedIPv4108
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv693
AS19315S.A.UnclassifiedIPv452

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv65,023
AS3356Level 3 Parent, LLCTransitIPv4 IPv64,847
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv63,699
AS174Cogent Communications, LLCTransitIPv4 IPv62,476
AS22927de ArgentinaMobileIPv4 IPv61,795
AS263756INTERNET SRLResidentialIPv4201
AS273240SAUnclassifiedIPv4108
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv693
AS19315S.A.UnclassifiedIPv452

Provenance

Where this comes from

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