asn.dev

Observed topology

AS60981 TRIANGLE-AS

Unclassified RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS60981: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6197
AS174Cogent Communications, LLCTransitIPv4 IPv678
AS6939Hurricane Electric LLCTransitIPv626
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS48185team.blue NVUnclassifiedIPv4 IPv66
AS9002RETN LimitedUnclassifiedIPv64
AS34549meerfarbig GmbH & Co. KGHostingIPv64
AS17639Converge ICT Solutions Inc.UnclassifiedIPv62
AS25091IP-Max SAUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS201261The Watershed Arts Trust LtdUnclassifiedIPv44

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6321
AS25061Associated Networks (UK) LimitedHostingIPv4120
AS174Cogent Communications, LLCTransitIPv4 IPv678
AS6939Hurricane Electric LLCTransitIPv626
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS48185team.blue NVUnclassifiedIPv4 IPv66
AS9002RETN LimitedUnclassifiedIPv64
AS34549meerfarbig GmbH & Co. KGHostingIPv64
AS201261The Watershed Arts Trust LtdUnclassifiedIPv44

Provenance

Where this comes from

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