bgpreport

Network · data from 2026-11-12

AS399274 CONNECT-INTERNET-BY-JASPER-REMC - Jasper County REMC

Registry name: CONNECT-INTERNET-BY-JASPER-REMC - Jasper County REMC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS399274, 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.
64.52.12.0/23 No ROA None 673 100% 67
69.8.96.0/20 No ROA None 673 100% 67
69.8.109.0/24 No ROA None 673 100% 67
209.87.176.0/22 No ROA None 673 100% 67
2606:1cc0::/32 No ROA None 635 100% 68
2606:1cc0::/36 No ROA None 635 100% 68

AS-SET

AS399274 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: none6
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: none64.52.12.0/23No ROA covers it. Add a ROA for AS399274, maxLength 23.673 of 673
Route object: none64.52.12.0/23No route object for it. Add a route object with origin AS399274 in the RIR database for the space.673 of 673
ROA: none69.8.96.0/20No ROA covers it. Add a ROA for AS399274, maxLength 20.673 of 673
Route object: none69.8.96.0/20No route object for it. Add a route object with origin AS399274 in the RIR database for the space.673 of 673
ROA: none69.8.109.0/24No ROA covers it. Add a ROA for AS399274, maxLength 24.673 of 673
Route object: none69.8.109.0/24No route object for it. Add a route object with origin AS399274 in the RIR database for the space.673 of 673
ROA: none209.87.176.0/22No ROA covers it. Add a ROA for AS399274, maxLength 22.673 of 673
Route object: none209.87.176.0/22No route object for it. Add a route object with origin AS399274 in the RIR database for the space.673 of 673
ROA: none2606:1cc0::/32No ROA covers it. Add a ROA for AS399274, maxLength 32.635 of 636
Route object: none2606:1cc0::/32No route object for it. Add a route object with origin AS399274 in the RIR database for the space.635 of 636
ROA: none2606:1cc0::/36No ROA covers it. Add a ROA for AS399274, maxLength 36.635 of 636
Route object: none2606:1cc0::/36No route object for it. Add a route object with origin AS399274 in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS399274 is announced.

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.