asn.dev

Observed topology

AS53184 VERO S.A

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS53184: 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
AS13786Seabras 1 USA, LLCUnclassifiedIPv4 IPv6935
AS28258VERO S.AResidentialIPv4 IPv6683
AS24482SG.GSHostingIPv4 IPv650
AS35280F5 Networks SARLHostingIPv429
AS37721Virtual Technologies & SolutionsResidentialIPv429

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS28669VERO S.AResidentialIPv4177
AS53085VERO S.AResidentialIPv617
AS273474TODA SOLUCAO WEBUnclassifiedIPv61

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13786Seabras 1 USA, LLCUnclassifiedIPv4 IPv61,113
AS28258VERO S.AResidentialIPv4 IPv6683
AS28669VERO S.AResidentialIPv4177
AS24482SG.GSHostingIPv4 IPv650
AS35280F5 Networks SARLHostingIPv429
AS37721Virtual Technologies & SolutionsResidentialIPv429
AS6939Hurricane Electric LLCTransitIPv624
AS53085VERO S.AResidentialIPv624
AS273474TODA SOLUCAO WEBUnclassifiedIPv61

Provenance

Where this comes from

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