asn.dev

Observed topology

AS274664 AS274664 - UBBY INTERNET LTDA

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS274664: 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
AS53102S.I. TELECOM. SERVICOS DE TELEFONIA LTDA EPPResidentialIPv4 IPv675
AS6939Hurricane Electric LLCTransitIPv648
AS52468UFINET PANAMA S.A.UnclassifiedIPv639
AS24482SG.GSHostingIPv63
AS37721Virtual Technologies & SolutionsResidentialIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262579GE Network Provedor de Internet LTDAUnclassifiedIPv4120
AS270844AXION3 TELECOM LTDAUnclassifiedIPv4 IPv679

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6187
AS262579GE Network Provedor de Internet LTDAUnclassifiedIPv4120
AS6939Hurricane Electric LLCTransitIPv4 IPv691
AS270844AXION3 TELECOM LTDAUnclassifiedIPv4 IPv679
AS53102S.I. TELECOM. SERVICOS DE TELEFONIA LTDA EPPResidentialIPv4 IPv675
AS24482SG.GSHostingIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67

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.