bgpreport

Network · data from 2026-11-12

AS32374 NUCLEARFALLOUT-LAX - Nuclearfallout Enterprises, Inc.

Registry name: NUCLEARFALLOUT-LAX - Nuclearfallout Enterprises, Inc., US · not in PeeringDB

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

Announced routes

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

104.153.109.0/24 No ROA Other IRR onlyRADB 673 100% 67
162.248.93.0/24 No ROA Other IRR onlyRADB 673 100% 67
74.91.118.0/24 No ROA Other IRR onlyALTDB 672 100% 67
2605:6ac0:3000::/36 No ROA Other IRR onlyALTDB, RADB 634 100% 67
2605:6ac0:7000::/36 No ROA Other IRR onlyALTDB 634 100% 67
104.153.111.0/24 No ROA Other IRR onlyALTDB 28 4%low visibility 12

AS-SET

AS32374 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 16 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none104.153.109.0/24No ROA covers it. Add a ROA for AS32374, maxLength 24.673 of 673
Route object: RIR104.153.109.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.248.93.0/24No ROA covers it. Add a ROA for AS32374, maxLength 24.673 of 673
Route object: RIR162.248.93.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none74.91.118.0/24No ROA covers it. Add a ROA for AS32374, maxLength 24.672 of 673
Route object: RIR74.91.118.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none2605:6ac0:3000::/36No ROA covers it. Add a ROA for AS32374, maxLength 36.634 of 636
Route object: RIR2605:6ac0:3000::/36Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636
ROA: none2605:6ac0:7000::/36No ROA covers it. Add a ROA for AS32374, maxLength 36.634 of 636
Route object: RIR2605:6ac0:7000::/36Route object only in ALTDB. Add it in the RIR database for the space.634 of 636
ROA: none104.153.111.0/24No ROA covers it. Add a ROA for AS32374, maxLength 24.28 of 673
Route object: RIR104.153.111.0/24Route object only in ALTDB. Add it in the RIR database for the space.28 of 673

Route objects not announced

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

64.94.100.0/23RADBNo ROA
66.150.155.0/24RADBNo ROA
66.150.188.0/24RADBNo ROA
66.151.138.0/24ALTDBNo 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.