asn.dev

Observed topology

AS272559 AS272559 - ULISSES DE OLIVEIRA SANTOS - ME

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS272559: 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 LLCTransitIPv6362
AS24482SG.GSHostingIPv624
AS37721Virtual Technologies & SolutionsResidentialIPv623
AS35280F5 Networks SARLHostingIPv620
AS13786Seabras 1 USA, LLCUnclassifiedIPv68
AS2914NTT America, Inc.TransitIPv65
AS11432Telium Telecomunicacoes LtdaHostingIPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269561M.M. Brito da Silva - MultimidiaUnclassifiedIPv491

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6397
AS269561M.M. Brito da Silva - MultimidiaUnclassifiedIPv491
AS2914NTT America, Inc.TransitIPv4 IPv633
AS24482SG.GSHostingIPv4 IPv627
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv625
AS35280F5 Networks SARLHostingIPv4 IPv622
AS13786Seabras 1 USA, LLCUnclassifiedIPv4 IPv619
AS11432Telium Telecomunicacoes LtdaHostingIPv4 IPv615

Provenance

Where this comes from

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