bgpreport

Network · data from 2026-11-12

AS1294 NTTDATA-SERVICES-AS1 - NTT DATA Services Holdings Corporation

Registry name: NTTDATA-SERVICES-AS1 - NTT DATA Services Holdings Corporation, US · not in PeeringDB

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

Announced routes

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

65.207.122.0/24 No ROA None 673 100% 67
148.9.32.0/24 No ROA Nonecovered by 148.9.0.0/16 673 100% 66
148.9.240.0/23 No ROA Nonecovered by 148.9.0.0/16 673 100% 66
148.9.240.0/24 No ROA Nonecovered by 148.9.0.0/16 673 100% 67
148.9.241.0/24 No ROA Nonecovered by 148.9.0.0/16 673 100% 67
148.9.246.0/24 No ROA Nonecovered by 148.9.0.0/16 673 100% 66
160.109.125.0/24 No ROA Nonecovered by 160.109.0.0/16 673 100% 67
160.109.224.0/21 No ROA Nonecovered by 160.109.0.0/16 673 100% 67
66.97.191.0/24 No ROA Other IRR onlyRADB 673 100% 67
148.9.192.0/20 No ROA Other IRR onlyRADB 673 100% 67
148.9.208.0/21 No ROA Other IRR onlyRADB 673 100% 67
148.9.248.0/24 No ROA Other IRR onlyRADB 673 100% 66
160.109.97.0/24 No ROA Other IRR onlyRADB 673 100% 67
160.109.160.0/21 No ROA Other IRR onlyRADB 673 100% 67
148.9.250.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS1294 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 65 are in fix.csv.

  • ROA: none15
  • Route object: none8
  • Route object: RIR7
  • Route object: not announced35
ChangePrefix or setDetailFull-table peers
ROA: none65.207.122.0/24No ROA covers it. Add a ROA for AS1294, maxLength 24.673 of 673
Route object: none65.207.122.0/24No route object for it. Add a route object with origin AS1294 in the RIR database for the space.673 of 673
ROA: none148.9.32.0/24No ROA covers it. Add a ROA for AS1294, maxLength 24.673 of 673
Route object: none148.9.32.0/24No route object for it. A route object for 148.9.0.0/16 with origin AS1294 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1294 in the RIR database for the space.673 of 673
ROA: none148.9.240.0/23No ROA covers it. Add a ROA for AS1294, maxLength 23.673 of 673
Route object: none148.9.240.0/23No route object for it. A route object for 148.9.0.0/16 with origin AS1294 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1294 in the RIR database for the space.673 of 673
ROA: none148.9.240.0/24No ROA covers it. Add a ROA for AS1294, maxLength 24.673 of 673
Route object: none148.9.240.0/24No route object for it. A route object for 148.9.0.0/16 with origin AS1294 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1294 in the RIR database for the space.673 of 673
ROA: none148.9.241.0/24No ROA covers it. Add a ROA for AS1294, maxLength 24.673 of 673
Route object: none148.9.241.0/24No route object for it. A route object for 148.9.0.0/16 with origin AS1294 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1294 in the RIR database for the space.673 of 673
ROA: none148.9.246.0/24No ROA covers it. Add a ROA for AS1294, maxLength 24.673 of 673
Route object: none148.9.246.0/24No route object for it. A route object for 148.9.0.0/16 with origin AS1294 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1294 in the RIR database for the space.673 of 673
ROA: none160.109.125.0/24No ROA covers it. Add a ROA for AS1294, maxLength 24.673 of 673
Route object: none160.109.125.0/24No route object for it. A route object for 160.109.0.0/16 with origin AS1294 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1294 in the RIR database for the space.673 of 673
ROA: none160.109.224.0/21No ROA covers it. Add a ROA for AS1294, maxLength 21.673 of 673
Route object: none160.109.224.0/21No route object for it. A route object for 160.109.0.0/16 with origin AS1294 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1294 in the RIR database for the space.673 of 673
ROA: none66.97.191.0/24No ROA covers it. Add a ROA for AS1294, maxLength 24.673 of 673
Route object: RIR66.97.191.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none148.9.192.0/20No ROA covers it. Add a ROA for AS1294, maxLength 20.673 of 673
Route object: RIR148.9.192.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none148.9.208.0/21No ROA covers it. Add a ROA for AS1294, maxLength 21.673 of 673
Route object: RIR148.9.208.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none148.9.248.0/24No ROA covers it. Add a ROA for AS1294, maxLength 24.673 of 673
Route object: RIR148.9.248.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none160.109.97.0/24No ROA covers it. Add a ROA for AS1294, maxLength 24.673 of 673
Route object: RIR160.109.97.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none160.109.160.0/21No ROA covers it. Add a ROA for AS1294, maxLength 21.673 of 673
Route object: RIR160.109.160.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none148.9.250.0/24No ROA covers it. Add a ROA for AS1294, maxLength 24.672 of 673
Route object: RIR148.9.250.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

69.39.160.0/19RADBNo ROA
148.9.0.0/16RADBNo ROA
148.9.4.0/24RADBNo ROA
148.9.5.0/24RADBNo ROA
148.9.19.0/24RADBNo ROA
148.9.212.0/24RADBNo ROA
148.9.232.0/24RADBNo ROA
148.9.238.0/23RADBNo ROA
148.9.238.0/24RADBNo ROA
148.9.249.0/24RADBNo ROA
155.16.0.0/16RADBNo ROA
155.49.0.0/21RADBNo ROA
160.109.0.0/16RADBNo ROA
160.109.116.0/24RADBNo ROA
160.109.232.0/24RADBNo ROA
160.109.233.0/24RADBNo ROA
160.109.234.0/24RADBNo ROA
160.109.235.0/24RADBNo ROA
160.109.236.0/24RADBNo ROA
160.109.237.0/24RADBNo ROA
160.109.238.0/24RADBNo ROA
160.109.239.0/24RADBNo ROA
160.110.93.0/24RADBNo ROA
163.244.180.0/24ALTDBNo ROA
163.244.182.0/24ALTDBNo ROA
163.244.186.0/24ALTDBNo ROA
192.131.83.0/24RADBNo ROA
192.131.85.0/24RADBNo ROA
192.131.87.0/24RADBNo ROA
206.217.144.0/20RADBNo ROA
206.217.144.0/22RADBNo ROA
208.79.28.0/22RADBNo ROA
208.82.228.0/22RADBNo ROA
216.182.0.0/18RADBNo ROA
2607:f2a8::/32RADBNo 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.