asn.dev

Observed topology

AS273500 AS273500 - YPN TECNOLOGIA LTDA

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS273500: 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
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv682
AS267576Conet TelecomResidentialIPv4 IPv678
AS6939Hurricane Electric LLCTransitIPv436
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv634
AS35280F5 Networks SARLHostingIPv4 IPv68
AS24482SG.GSHostingIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269430TERA TELECOM LTDA MEUnclassifiedIPv4 IPv684
AS267576Conet TelecomResidentialIPv458
AS269551J. VIEIRA DE LUCENA J J NETUnclassifiedIPv449

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS267576Conet TelecomResidentialIPv4 IPv6136
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6135
AS37468Angola CablesUnclassifiedIPv4101
AS269430TERA TELECOM LTDA MEUnclassifiedIPv4 IPv684
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv668
AS269551J. VIEIRA DE LUCENA J J NETUnclassifiedIPv449
AS6939Hurricane Electric LLCTransitIPv436
AS24482SG.GSHostingIPv4 IPv610
AS35280F5 Networks SARLHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv46

Provenance

Where this comes from

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