asn.dev

Observed topology

AS272701 AS272701 - ULTRANET LTDA

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS272701: 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
AS6939Hurricane Electric LLCTransitIPv647
AS262456ELO MULTIMIDIA LTDAResidentialIPv613
AS24482SG.GSHostingIPv63
AS269194ST1 INTERNETResidentialIPv63
AS35280F5 Networks SARLHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267535Ajust ConsultingUnclassifiedIPv4 IPv6162
AS269704G DE OLIVEIRA LIMA SERVICOS DE TELECOMUNICOESUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS267535Ajust ConsultingUnclassifiedIPv4 IPv6162
AS6939Hurricane Electric LLCTransitIPv4 IPv6129
AS269194ST1 INTERNETResidentialIPv4 IPv6108
AS269704G DE OLIVEIRA LIMA SERVICOS DE TELECOMUNICOESUnclassifiedIPv461
AS262456ELO MULTIMIDIA LTDAResidentialIPv4 IPv630
AS24482SG.GSHostingIPv4 IPv69
AS35280F5 Networks SARLHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS262503WIKI TELECOMUNICACOES EIRELIUnclassifiedIPv4 IPv65

Provenance

Where this comes from

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