bgpreport

Network · data from 2026-11-12

AS214505 NUCLEARFALLOUT-FRA Nuclearfallout Enterprises, Inc.

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

3IPv4 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
4No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS214505, seen from no peer

Announced routes

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

185.107.96.0/24 No ROA RIR databaseALTDB, RIPE 673 100% 67
185.107.97.0/24 No ROA RIR databaseALTDB, RIPE 673 100% 67
2605:6ac0:2000::/36 No ROA RIR databaseALTDB, ARIN 636 100% 67
104.153.111.0/24 No ROA RIR databaseALTDB, ARIN 92 14% 30

AS-SET

AS214505 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 6 are in fix.csv.

  • ROA: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none185.107.96.0/24No ROA covers it. Add a ROA for AS214505, maxLength 24.673 of 673
ROA: none185.107.97.0/24No ROA covers it. Add a ROA for AS214505, maxLength 24.673 of 673
ROA: none2605:6ac0:2000::/36No ROA covers it. Add a ROA for AS214505, maxLength 36.636 of 636
ROA: none104.153.111.0/24No ROA covers it. Add a ROA for AS214505, maxLength 24.92 of 673

Route objects not announced

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

31.186.250.0/23ALTDBValid
95.172.92.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.