bgpreport

Network · data from 2026-11-12

AS60981 TRIANGLE-AS Triangle Networks Ltd

Registry name: TRIANGLE-AS Triangle Networks Ltd, GB · not in PeeringDB

4IPv4 routes 25.0% RPKI valid · 75.0% with a route object
3IPv6 routes 0.0% RPKI valid · 66.7% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS60981, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS60981, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

81.91.96.0/21 No ROA Other origin only 673 100% 67
2001:b70::/32 No ROA Other origin only 636 100% 67
185.14.136.0/22 No ROA RIR databaseRIPE 673 100% 67
185.179.208.0/22 No ROA RIR databaseRIPE 673 100% 67
2a03:b040::/32 No ROA RIR databaseRIPE 635 100% 67
2a0a:9080::/29 No ROA RIR databaseRIPE 634 100% 67
213.146.186.0/23 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS60981 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 10 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none81.91.96.0/21No ROA covers it. Add a ROA for AS60981, maxLength 21.673 of 673
Route object: none81.91.96.0/21Route objects for it name AS25061. Add a route object with origin AS60981 in the RIR database for the space.673 of 673
ROA: none2001:b70::/32No ROA covers it. Add a ROA for AS60981, maxLength 32.636 of 636
Route object: none2001:b70::/32Route objects for it name AS25061. Add a route object with origin AS60981 in the RIR database for the space.636 of 636
ROA: none185.14.136.0/22No ROA covers it. Add a ROA for AS60981, maxLength 22.673 of 673
ROA: none185.179.208.0/22No ROA covers it. Add a ROA for AS60981, maxLength 22.673 of 673
ROA: none2a03:b040::/32No ROA covers it. Add a ROA for AS60981, maxLength 32.635 of 636
ROA: none2a0a:9080::/29No ROA covers it. Add a ROA for AS60981, maxLength 29.634 of 636

Route objects not announced

Route objects with origin AS60981 whose prefix no peer sees AS60981 announce. Many are kept on purpose (backup routes, space announced only in some places).

130.117.125.0/24RADBNo ROA
2a0a:9085::/32RIPENo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.