bgpreport

Network · data from 2026-11-12

AS60941 FTS Fujitsu Technology Solutions BV

Registry name: FTS Fujitsu Technology Solutions BV, NL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS60941, 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.

2a04:18c0::/48 No ROA Nonecovered by 2a04:18c0::/29 635 100% 67
2a04:18c0:1::/48 No ROA Nonecovered by 2a04:18c0::/29 635 100% 67
2a04:18c0:2::/48 No ROA Nonecovered by 2a04:18c0::/29 635 100% 67
2a04:18c0:3::/48 No ROA Nonecovered by 2a04:18c0::/29 635 100% 67
2a04:18c0:4::/48 No ROA Nonecovered by 2a04:18c0::/29 635 100% 67
2a04:18c0:5::/48 No ROA Nonecovered by 2a04:18c0::/29 635 100% 67
2a04:18c0:6::/48 No ROA Nonecovered by 2a04:18c0::/29 635 100% 67
2a04:18c0:7::/48 No ROA Nonecovered by 2a04:18c0::/29 635 100% 67
2a04:18c0:8::/48 No ROA Nonecovered by 2a04:18c0::/29 635 100% 67
2a04:18c0:9::/48 No ROA Nonecovered by 2a04:18c0::/29 635 100% 67
2a04:18c0:a::/48 No ROA Nonecovered by 2a04:18c0::/29 635 100% 67
185.21.56.0/22 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS60941 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 27 are in fix.csv.

  • ROA: none11
  • Route object: none11
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none2a04:18c0::/48No ROA covers it. Add a ROA for AS60941, maxLength 48.635 of 636
Route object: none2a04:18c0::/48No route object for it. A route object for 2a04:18c0::/29 with origin AS60941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60941 in the RIR database for the space.635 of 636
ROA: none2a04:18c0:1::/48No ROA covers it. Add a ROA for AS60941, maxLength 48.635 of 636
Route object: none2a04:18c0:1::/48No route object for it. A route object for 2a04:18c0::/29 with origin AS60941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60941 in the RIR database for the space.635 of 636
ROA: none2a04:18c0:2::/48No ROA covers it. Add a ROA for AS60941, maxLength 48.635 of 636
Route object: none2a04:18c0:2::/48No route object for it. A route object for 2a04:18c0::/29 with origin AS60941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60941 in the RIR database for the space.635 of 636
ROA: none2a04:18c0:3::/48No ROA covers it. Add a ROA for AS60941, maxLength 48.635 of 636
Route object: none2a04:18c0:3::/48No route object for it. A route object for 2a04:18c0::/29 with origin AS60941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60941 in the RIR database for the space.635 of 636
ROA: none2a04:18c0:4::/48No ROA covers it. Add a ROA for AS60941, maxLength 48.635 of 636
Route object: none2a04:18c0:4::/48No route object for it. A route object for 2a04:18c0::/29 with origin AS60941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60941 in the RIR database for the space.635 of 636
ROA: none2a04:18c0:5::/48No ROA covers it. Add a ROA for AS60941, maxLength 48.635 of 636
Route object: none2a04:18c0:5::/48No route object for it. A route object for 2a04:18c0::/29 with origin AS60941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60941 in the RIR database for the space.635 of 636
ROA: none2a04:18c0:6::/48No ROA covers it. Add a ROA for AS60941, maxLength 48.635 of 636
Route object: none2a04:18c0:6::/48No route object for it. A route object for 2a04:18c0::/29 with origin AS60941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60941 in the RIR database for the space.635 of 636
ROA: none2a04:18c0:7::/48No ROA covers it. Add a ROA for AS60941, maxLength 48.635 of 636
Route object: none2a04:18c0:7::/48No route object for it. A route object for 2a04:18c0::/29 with origin AS60941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60941 in the RIR database for the space.635 of 636
ROA: none2a04:18c0:8::/48No ROA covers it. Add a ROA for AS60941, maxLength 48.635 of 636
Route object: none2a04:18c0:8::/48No route object for it. A route object for 2a04:18c0::/29 with origin AS60941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60941 in the RIR database for the space.635 of 636
ROA: none2a04:18c0:9::/48No ROA covers it. Add a ROA for AS60941, maxLength 48.635 of 636
Route object: none2a04:18c0:9::/48No route object for it. A route object for 2a04:18c0::/29 with origin AS60941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60941 in the RIR database for the space.635 of 636
ROA: none2a04:18c0:a::/48No ROA covers it. Add a ROA for AS60941, maxLength 48.635 of 636
Route object: none2a04:18c0:a::/48No route object for it. A route object for 2a04:18c0::/29 with origin AS60941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60941 in the RIR database for the space.635 of 636

Route objects not announced

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

185.21.57.0/24RIPEInvalid: maxLength
185.21.58.0/23RIPEInvalid: maxLength
185.21.58.0/24RIPEInvalid: maxLength
185.21.59.0/24RIPEInvalid: maxLength
2a04:18c0::/29RIPENo 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.