bgpreport

Network · data from 2026-11-12

AS35251 ANTI-DDOS - NetLab Global

Registry name: ANTI-DDOS - NetLab Global, US · not in PeeringDB

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

Announced routes

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

154.12.32.0/24 No ROA Other IRR onlyRADB 673 100% 67
154.12.33.0/24 No ROA Other IRR onlyRADB 673 100% 67
154.12.34.0/24 No ROA Other IRR onlyRADB 673 100% 67
154.12.36.0/23 No ROA Other IRR onlyRADB 673 100% 67
154.12.40.0/22 No ROA Other IRR onlyRADB 673 100% 67
154.12.56.0/24 No ROA Other IRR onlyRADB 673 100% 67
154.12.57.0/24 No ROA Other IRR onlyRADB 673 100% 67
154.12.58.0/24 No ROA Other IRR onlyRADB 673 100% 67
154.13.4.0/24 No ROA Other IRR onlyRADB 673 100% 67
154.13.5.0/24 No ROA Other IRR onlyRADB 673 100% 67
154.13.7.0/24 No ROA Other IRR onlyRADB 673 100% 67
154.64.229.0/24 No ROA Other IRR onlyRADB 673 100% 67
45.138.69.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
45.138.70.0/24 Valid Other IRR onlyRADB 672 100% 67
45.138.71.0/24 Valid Other IRR onlyRADB 672 100% 67
45.158.20.0/24 Valid Other IRR onlyRADB 672 100% 67
45.158.21.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
45.158.22.0/24 Valid Other IRR onlyRADB 672 100% 67
45.158.23.0/24 Valid Other IRR onlyRADB 672 100% 67
45.138.68.0/24 Valid Other IRR onlyNTTCOM, RADB 2 0%low visibility 2

AS-SET

AS35251 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 44 are in fix.csv.

  • ROA: none12
  • Route object: RIR20
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none154.12.32.0/24No ROA covers it. Add a ROA for AS35251, maxLength 24.673 of 673
Route object: RIR154.12.32.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.12.33.0/24No ROA covers it. Add a ROA for AS35251, maxLength 24.673 of 673
Route object: RIR154.12.33.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.12.34.0/24No ROA covers it. Add a ROA for AS35251, maxLength 24.673 of 673
Route object: RIR154.12.34.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.12.36.0/23No ROA covers it. Add a ROA for AS35251, maxLength 23.673 of 673
Route object: RIR154.12.36.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.12.40.0/22No ROA covers it. Add a ROA for AS35251, maxLength 22.673 of 673
Route object: RIR154.12.40.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.12.56.0/24No ROA covers it. Add a ROA for AS35251, maxLength 24.673 of 673
Route object: RIR154.12.56.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.12.57.0/24No ROA covers it. Add a ROA for AS35251, maxLength 24.673 of 673
Route object: RIR154.12.57.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.12.58.0/24No ROA covers it. Add a ROA for AS35251, maxLength 24.673 of 673
Route object: RIR154.12.58.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.13.4.0/24No ROA covers it. Add a ROA for AS35251, maxLength 24.673 of 673
Route object: RIR154.13.4.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.13.5.0/24No ROA covers it. Add a ROA for AS35251, maxLength 24.673 of 673
Route object: RIR154.13.5.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.13.7.0/24No ROA covers it. Add a ROA for AS35251, maxLength 24.673 of 673
Route object: RIR154.13.7.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.64.229.0/24No ROA covers it. Add a ROA for AS35251, maxLength 24.673 of 673
Route object: RIR154.64.229.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR45.138.69.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.138.70.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.138.71.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.158.20.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.158.21.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.158.22.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.158.23.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.138.68.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

45.138.68.0/22RADBNo ROA
45.145.6.0/24RADBNo ROA
45.145.7.0/24RADBNo ROA
45.158.20.0/22RADBNo ROA
50.93.205.0/24ARINNo ROA
103.150.214.0/24APNICInvalid: origin
103.150.215.0/24APNICInvalid: origin
154.12.36.0/22RADBNo ROA
154.13.6.0/24RADBNo ROA
202.5.28.0/24ARIN, NTTCOM, RADBNo ROA
202.5.30.0/24NTTCOMNo ROA
2602:feda:180::/48ARINValid

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.