bgpreport

Network · data from 2026-11-12

AS400475 NUCLEARFALLOUT-DAL - Nuclearfallout Enterprises, Inc.

Registry name: NUCLEARFALLOUT-DAL - 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
5Route objects not announced registered with origin AS400475, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS400475, 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.106.0/24 No ROA Other IRR onlyALTDB 673 100% 67
162.248.90.0/24 No ROA Other IRR onlyALTDB 673 100% 67
162.248.91.0/24 No ROA Other IRR onlyALTDB 673 100% 67
192.223.29.0/24 No ROA Other IRR onlyALTDB 673 100% 67
74.91.114.0/24 No ROA Other IRR onlyALTDB 672 100% 67
74.91.120.0/24 No ROA Other IRR onlyALTDB 672 100% 67
74.91.126.0/24 No ROA Other IRR onlyALTDB 672 100% 67
2605:6ac0:5000::/36 No ROA Other IRR onlyALTDB 635 100% 67
104.153.111.0/24 No ROA Other IRR onlyALTDB 70 10% 30

AS-SET

AS400475 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 23 are in fix.csv.

  • ROA: none9
  • Route object: RIR9
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none104.153.106.0/24No ROA covers it. Add a ROA for AS400475, maxLength 24.673 of 673
Route object: RIR104.153.106.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none162.248.90.0/24No ROA covers it. Add a ROA for AS400475, maxLength 24.673 of 673
Route object: RIR162.248.90.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none162.248.91.0/24No ROA covers it. Add a ROA for AS400475, maxLength 24.673 of 673
Route object: RIR162.248.91.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none192.223.29.0/24No ROA covers it. Add a ROA for AS400475, maxLength 24.673 of 673
Route object: RIR192.223.29.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none74.91.114.0/24No ROA covers it. Add a ROA for AS400475, maxLength 24.672 of 673
Route object: RIR74.91.114.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none74.91.120.0/24No ROA covers it. Add a ROA for AS400475, maxLength 24.672 of 673
Route object: RIR74.91.120.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none74.91.126.0/24No ROA covers it. Add a ROA for AS400475, maxLength 24.672 of 673
Route object: RIR74.91.126.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none2605:6ac0:5000::/36No ROA covers it. Add a ROA for AS400475, maxLength 36.635 of 636
Route object: RIR2605:6ac0:5000::/36Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
ROA: none104.153.111.0/24No ROA covers it. Add a ROA for AS400475, maxLength 24.70 of 673
Route object: RIR104.153.111.0/24Route object only in ALTDB. Add it in the RIR database for the space.70 of 673

Route objects not announced

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

66.85.15.0/24ALTDBNo ROA
66.150.214.0/24ALTDBNo ROA
66.151.244.0/24ALTDBNo ROA
72.5.102.0/24ALTDBNo ROA
74.201.57.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.