asn.dev

Observed topology

AS52714 AS52714 - Firemicro Informatica

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52714: 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
AS263444Open X Tecnologia LtdaUnclassifiedIPv4 IPv6235
AS6939Hurricane Electric LLCTransitIPv4 IPv6110
AS53180INFORTEL COMUNICACOES LTDAResidentialIPv4 IPv630
AS24482SG.GSHostingIPv4 IPv68
AS35280F5 Networks SARLHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv68
AS25091IP-Max SAUnclassifiedIPv62
AS52554S. A. da Silva JuniorUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269584A&SNet ProvedorUnclassifiedIPv4 IPv6129
AS268454DEBORAH SILVA SANTOS MEUnclassifiedIPv4 IPv693

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263444Open X Tecnologia LtdaUnclassifiedIPv4 IPv6452
AS269584A&SNet ProvedorUnclassifiedIPv4 IPv6129
AS6939Hurricane Electric LLCTransitIPv4 IPv6110
AS268454DEBORAH SILVA SANTOS MEUnclassifiedIPv4 IPv693
AS53180INFORTEL COMUNICACOES LTDAResidentialIPv4 IPv632
AS24482SG.GSHostingIPv4 IPv611
AS35280F5 Networks SARLHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv68
AS25091IP-Max SAUnclassifiedIPv62
AS52554S. A. da Silva JuniorUnclassifiedIPv42

Provenance

Where this comes from

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