asn.dev

Observed topology

AS52527 AS52527 - IWNET TELECOM LTDA ME

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52527: 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
AS264144ASAP GLOBAL TELECOMUnclassifiedIPv4 IPv6642
AS3356Level 3 Parent, LLCTransitIPv4 IPv6623
AS6939Hurricane Electric LLCTransitIPv4 IPv6501
AS52468UFINET PANAMA S.A.UnclassifiedIPv445
AS266409SECW TELECOMUnclassifiedIPv444
AS24482SG.GSHostingIPv4 IPv643

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267998ASA GROUP MONITORAMENTO E SERVICOS DE TELECOMUnclassifiedIPv4 IPv6398
AS271666JOSE HERNANI PEREIRA DE SOUZAUnclassifiedIPv4 IPv6389
AS267530TJ Telecom LTDA MEHostingIPv4 IPv6215
AS267366PLAYNET TELECOMUnclassifiedIPv4183
AS268643ga de matosUnclassifiedIPv435

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS264144ASAP GLOBAL TELECOMUnclassifiedIPv4 IPv61,331
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,016
AS6939Hurricane Electric LLCTransitIPv4 IPv6714
AS267998ASA GROUP MONITORAMENTO E SERVICOS DE TELECOMUnclassifiedIPv4 IPv6398
AS271666JOSE HERNANI PEREIRA DE SOUZAUnclassifiedIPv4 IPv6389
AS267530TJ Telecom LTDA MEHostingIPv4 IPv6215
AS268643ga de matosUnclassifiedIPv4 IPv6190
AS267366PLAYNET TELECOMUnclassifiedIPv4183
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6104
AS24482SG.GSHostingIPv4 IPv664

All 11 adjacent →

Provenance

Where this comes from

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