asn.dev

Observed topology

AS52971 MICKS TELECOM EIRELI

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52971: 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
AS26615TIM S/AMobileIPv4 IPv6850
AS6939Hurricane Electric LLCTransitIPv4 IPv6275
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6220
AS24482SG.GSHostingIPv4 IPv619
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv615
AS35280F5 Networks SARLHostingIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS52854DIGITALSMART TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6437
AS273751Mnet TelecomUnclassifiedIPv4 IPv6158
AS266924RIACHONET TELECOMUnclassifiedIPv473
AS273660INFORTEC SERVICOS DE MULTIMIDIAUnclassifiedIPv631

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS26615TIM S/AMobileIPv4 IPv6939
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6638
AS6939Hurricane Electric LLCTransitIPv4 IPv6450
AS52854DIGITALSMART TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6437
AS273751Mnet TelecomUnclassifiedIPv4 IPv6158
AS266924RIACHONET TELECOMUnclassifiedIPv473
AS24482SG.GSHostingIPv4 IPv632
AS273660INFORTEC SERVICOS DE MULTIMIDIAUnclassifiedIPv631
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv618
AS35280F5 Networks SARLHostingIPv4 IPv65

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-19 10: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.