asn.dev

Observed topology

AS12180 INTERNAP-2BLK - Unitas Global

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12180: 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
AS1828Unitas GlobalUnclassifiedIPv4 IPv62,151

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS27229Webhosting.Net, Inc.HostingIPv4590
AS32228ISN CommunicationsUnclassifiedIPv4454
AS32488CompassMSP, LLC.UnclassifiedIPv4232
AS401048Supreme ServersUnclassifiedIPv4 IPv6113
AS53865Peer-Point Services, LLC.UnclassifiedIPv475
AS26555AVM,LPUnclassifiedIPv461
AS46897Rack Wizards IncUnclassifiedIPv460
AS394175RingLogix LLCUnclassifiedIPv460
AS395951ZIPDATA.NETUnclassifiedIPv453

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS1828Unitas GlobalUnclassifiedIPv4 IPv63,989
AS27229Webhosting.Net, Inc.HostingIPv4590
AS32228ISN CommunicationsUnclassifiedIPv4454
AS32488CompassMSP, LLC.UnclassifiedIPv4232
AS3855Logic Communications LtdResidentialIPv4140
AS401048Supreme ServersUnclassifiedIPv4 IPv6113
AS53865Peer-Point Services, LLC.UnclassifiedIPv475
AS26555AVM,LPUnclassifiedIPv461
AS46897Rack Wizards IncUnclassifiedIPv460
AS394175RingLogix LLCUnclassifiedIPv460

All 11 adjacent →

Provenance

Where this comes from

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