bgpreport

Network · data from 2026-11-12

AS36097 NUGGET-SAN - Nugget Enterprises, Inc.

Registry name: NUGGET-SAN - Nugget Enterprises, Inc., US · not in PeeringDB

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

Announced routes

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

66.254.0.0/20 No ROA Nonecovered by 66.254.0.0/19 673 100% 67
66.254.16.0/20 No ROA Nonecovered by 66.254.0.0/19 673 100% 67
216.69.240.0/24 No ROA Nonecovered by 216.69.240.0/20 673 100% 67
216.69.244.0/22 No ROA Nonecovered by 216.69.240.0/20 673 100% 67
216.69.247.0/24 No ROA Nonecovered by 216.69.240.0/20 673 100% 67
216.69.252.0/22 No ROA Nonecovered by 216.69.240.0/20 673 100% 67
66.254.0.0/19 No ROA Other IRR onlyRADB 673 100% 67
216.69.248.0/23 No ROA Other IRR onlyRADB 673 100% 67
2606:f200::/32 No ROA Other IRR onlyRADB 633 100% 69
198.133.128.0/24 Valid Other IRR onlyRADB 673 100% 67

AS-SET

AS36097 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 28 are in fix.csv.

  • ROA: none9
  • Route object: none6
  • Route object: RIR4
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none66.254.0.0/20No ROA covers it. Add a ROA for AS36097, maxLength 20.673 of 673
Route object: none66.254.0.0/20No route object for it. A route object for 66.254.0.0/19 with origin AS36097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36097 in the RIR database for the space.673 of 673
ROA: none66.254.16.0/20No ROA covers it. Add a ROA for AS36097, maxLength 20.673 of 673
Route object: none66.254.16.0/20No route object for it. A route object for 66.254.0.0/19 with origin AS36097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36097 in the RIR database for the space.673 of 673
ROA: none216.69.240.0/24No ROA covers it. Add a ROA for AS36097, maxLength 24.673 of 673
Route object: none216.69.240.0/24No route object for it. A route object for 216.69.240.0/20 with origin AS36097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36097 in the RIR database for the space.673 of 673
ROA: none216.69.244.0/22No ROA covers it. Add a ROA for AS36097, maxLength 22.673 of 673
Route object: none216.69.244.0/22No route object for it. A route object for 216.69.240.0/20 with origin AS36097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36097 in the RIR database for the space.673 of 673
ROA: none216.69.247.0/24No ROA covers it. Add a ROA for AS36097, maxLength 24.673 of 673
Route object: none216.69.247.0/24No route object for it. A route object for 216.69.240.0/20 with origin AS36097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36097 in the RIR database for the space.673 of 673
ROA: none216.69.252.0/22No ROA covers it. Add a ROA for AS36097, maxLength 22.673 of 673
Route object: none216.69.252.0/22No route object for it. A route object for 216.69.240.0/20 with origin AS36097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36097 in the RIR database for the space.673 of 673
ROA: none66.254.0.0/19No ROA covers it. Add a ROA for AS36097, maxLength 19.673 of 673
Route object: RIR66.254.0.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.69.248.0/23No ROA covers it. Add a ROA for AS36097, maxLength 23.673 of 673
Route object: RIR216.69.248.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2606:f200::/32No ROA covers it. Add a ROA for AS36097, maxLength 32.633 of 636
Route object: RIR2606:f200::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR198.133.128.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

198.133.129.0/24RADBValid
216.69.240.0/20ARINNo ROA
216.69.248.0/24RADBNo ROA
216.69.249.0/24RADBNo ROA
216.69.252.0/24RADBNo ROA
216.69.253.0/24RADBNo ROA
216.69.254.0/24RADBNo ROA
216.69.255.0/24RADBNo ROA
2607:fd38::/32RADBNo 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.