asn.dev

Observed topology

AS272786 X99 INTERNET

Hosting APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS272786: 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
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6290
AS6939Hurricane Electric LLCTransitIPv4 IPv6183
AS398991X99HostingIPv492
AS60068Datacamp LimitedHostingIPv452
AS35280F5 Networks SARLHostingIPv4 IPv67
AS52320GlobeNet Cabos Submarinos Colombia, S.A.S.UnclassifiedIPv47
AS24482SG.GSHostingIPv4 IPv64
AS25091IP-Max SAUnclassifiedIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS398991X99HostingIPv4 IPv6610
AS266335CTL Provedor de Internet LTDAUnclassifiedIPv4 IPv6210
AS267355HOSTIDC INTERNET DATACENTER LTDAHostingIPv4 IPv660

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS398991X99HostingIPv4 IPv6702
AS60068Datacamp LimitedHostingIPv4608
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6439
AS6939Hurricane Electric LLCTransitIPv4 IPv6303
AS266335CTL Provedor de Internet LTDAUnclassifiedIPv4 IPv6210
AS267355HOSTIDC INTERNET DATACENTER LTDAHostingIPv4 IPv660
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv641
AS24482SG.GSHostingIPv4 IPv615
AS35280F5 Networks SARLHostingIPv4 IPv613
AS52320GlobeNet Cabos Submarinos Colombia, S.A.S.UnclassifiedIPv48

All 11 adjacent →

Provenance

Where this comes from

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