bgpreport

Network · data from 2026-11-12

AS61097 Cloudsoftcat Softcat PLC

Registry name: Cloudsoftcat Softcat PLC, GB · not in PeeringDB

8IPv4 routes 0.0% RPKI valid · 62.5% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS61097, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61097, 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.
130.0.80.0/22 No ROA Nonecovered by 130.0.80.0/21 673 100% 67
130.0.84.0/23 No ROA Other origin onlycovered by 130.0.84.0/22 673 100% 67
130.0.87.0/24 No ROA Other origin onlycovered by 130.0.84.0/22 673 100% 67
130.0.80.0/21 No ROA RIR databaseRIPE 673 100% 67
130.0.80.0/23 No ROA RIR databaseRIPE 673 100% 67
130.0.82.0/23 No ROA RIR databaseRIPE 673 100% 67
130.0.84.0/22 No ROA RIR databaseRIPE 673 100% 67
130.0.86.0/24 No ROA RIR databaseRIPE 673 100% 67
2a03:ff00::/32 No ROA RIR databaseRIPE 605 95% 67

AS-SET

AS61097 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 12 are in fix.csv.

  • ROA: none9
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none130.0.80.0/22No ROA covers it. Add a ROA for AS61097, maxLength 22.673 of 673
Route object: none130.0.80.0/22No route object for it. A route object for 130.0.80.0/21 with origin AS61097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61097 in the RIR database for the space.673 of 673
ROA: none130.0.84.0/23No ROA covers it. Add a ROA for AS61097, maxLength 23.673 of 673
Route object: none130.0.84.0/23Route objects for it name AS41811, AS198949. A route object for 130.0.84.0/22 with origin AS61097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61097 in the RIR database for the space.673 of 673
ROA: none130.0.87.0/24No ROA covers it. Add a ROA for AS61097, maxLength 24.673 of 673
Route object: none130.0.87.0/24Route objects for it name AS198949. A route object for 130.0.84.0/22 with origin AS61097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61097 in the RIR database for the space.673 of 673
ROA: none130.0.80.0/21No ROA covers it. Add a ROA for AS61097, maxLength 21.673 of 673
ROA: none130.0.80.0/23No ROA covers it. Add a ROA for AS61097, maxLength 23.673 of 673
ROA: none130.0.82.0/23No ROA covers it. Add a ROA for AS61097, maxLength 23.673 of 673
ROA: none130.0.84.0/22No ROA covers it. Add a ROA for AS61097, maxLength 22.673 of 673
ROA: none130.0.86.0/24No ROA covers it. Add a ROA for AS61097, maxLength 24.673 of 673
ROA: none2a03:ff00::/32No ROA covers it. Add a ROA for AS61097, maxLength 32.605 of 636

Route objects not announced

Every route object with origin AS61097 is announced.

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.