bgpreport

Network · data from 2026-11-12

AS401263 NUCLEARFALLOUT-NYC - Nuclearfallout Enterprises, Inc.

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS401263, 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.107.0/24 No ROA RIR databaseALTDB, ARIN 673 100% 67
162.248.95.0/24 No ROA RIR databaseALTDB, ARIN 673 100% 67
192.223.24.0/24 No ROA RIR databaseALTDB, ARIN 673 100% 67
192.223.27.0/24 No ROA RIR databaseALTDB, ARIN 673 100% 67
192.223.31.0/24 No ROA RIR databaseALTDB, ARIN 673 100% 67
74.91.116.0/24 No ROA RIR databaseALTDB, ARIN 672 100% 67
74.91.123.0/24 No ROA RIR databaseALTDB, ARIN 669 99% 67
2605:6ac0:1000::/36 No ROA RIR databaseALTDB, ARIN 634 100% 68
104.153.111.0/24 No ROA RIR databaseALTDB, ARIN 150 22% 39

AS-SET

AS401263 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: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none104.153.107.0/24No ROA covers it. Add a ROA for AS401263, maxLength 24.673 of 673
ROA: none162.248.95.0/24No ROA covers it. Add a ROA for AS401263, maxLength 24.673 of 673
ROA: none192.223.24.0/24No ROA covers it. Add a ROA for AS401263, maxLength 24.673 of 673
ROA: none192.223.27.0/24No ROA covers it. Add a ROA for AS401263, maxLength 24.673 of 673
ROA: none192.223.31.0/24No ROA covers it. Add a ROA for AS401263, maxLength 24.673 of 673
ROA: none74.91.116.0/24No ROA covers it. Add a ROA for AS401263, maxLength 24.672 of 673
ROA: none74.91.123.0/24No ROA covers it. Add a ROA for AS401263, maxLength 24.669 of 673
ROA: none2605:6ac0:1000::/36No ROA covers it. Add a ROA for AS401263, maxLength 36.634 of 636
ROA: none104.153.111.0/24No ROA covers it. Add a ROA for AS401263, maxLength 24.150 of 673

Route objects not announced

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

63.251.20.0/24ALTDBNo ROA
66.150.121.0/24ALTDBNo ROA
70.42.74.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.