bgpreport

Network · data from 2026-11-12

AS46292 Blue Riverstone

Registry name: MOJAVEWIFI-COM-CA-1 - Mojavewifi.com LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS46292, 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.
142.202.76.0/24 No ROA Nonecovered by 142.202.76.0/22 673 100% 67
142.202.77.0/24 No ROA Nonecovered by 142.202.76.0/22 671 100% 67
142.202.78.0/24 No ROA Nonecovered by 142.202.76.0/22 671 100% 67
142.202.79.0/24 No ROA Nonecovered by 142.202.76.0/22 671 100% 67
2605:8d40::/32 No ROA Other IRR onlyRADB 634 100% 69

AS-SET

AS46292's PeeringDB record names no 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: none5
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none142.202.76.0/24No ROA covers it. Add a ROA for AS46292, maxLength 24.673 of 673
Route object: none142.202.76.0/24No route object for it. A route object for 142.202.76.0/22 with origin AS46292 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46292 in the RIR database for the space.673 of 673
ROA: none142.202.77.0/24No ROA covers it. Add a ROA for AS46292, maxLength 24.671 of 673
Route object: none142.202.77.0/24No route object for it. A route object for 142.202.76.0/22 with origin AS46292 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46292 in the RIR database for the space.671 of 673
ROA: none142.202.78.0/24No ROA covers it. Add a ROA for AS46292, maxLength 24.671 of 673
Route object: none142.202.78.0/24No route object for it. A route object for 142.202.76.0/22 with origin AS46292 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46292 in the RIR database for the space.671 of 673
ROA: none142.202.79.0/24No ROA covers it. Add a ROA for AS46292, maxLength 24.671 of 673
Route object: none142.202.79.0/24No route object for it. A route object for 142.202.76.0/22 with origin AS46292 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46292 in the RIR database for the space.671 of 673
ROA: none2605:8d40::/32No ROA covers it. Add a ROA for AS46292, maxLength 32.634 of 636
Route object: RIR2605:8d40::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

74.62.185.0/24RADBValid
142.202.76.0/22RADBNo 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.