bgpreport

Network · data from 2026-11-12

AS8025 BRIGHTOK-AS - BrightNet Oklahoma

Registry name: BRIGHTOK-AS - BrightNet Oklahoma, US · not in PeeringDB

22IPv4 routes 36.4% RPKI valid · 81.8% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
13No ROA 4 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
19Route objects not announced registered with origin AS8025, seen from no peer

Announced routes

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

69.12.112.0/20 Invalid: origin Other origin only 2 0%low visibility 2
162.242.88.0/23 No ROA None 2 0%low visibility 2
162.242.104.0/24 No ROA None 2 0%low visibility 2
192.133.7.0/24 No ROA None 2 0%low visibility 2
23.139.48.0/24 No ROA Other IRR onlyRADB 673 100% 67
170.92.63.0/24 No ROA Other IRR onlyRADB 673 100% 67
192.236.92.0/22 No ROA Other IRR onlyRADB 673 100% 67
192.236.118.0/23 No ROA Other IRR onlyRADB 673 100% 67
199.253.0.0/21 No ROA Other IRR onlyRADB 673 100% 67
199.253.8.0/23 No ROA Other IRR onlyRADB 673 100% 67
204.249.192.0/20 No ROA Other IRR onlyRADB 673 100% 67
205.159.237.0/24 No ROA Other IRR onlyRADB 673 100% 67
205.162.224.0/20 No ROA Other IRR onlyRADB 673 100% 67
205.240.128.0/20 No ROA Other IRR onlyRADB 673 100% 67
66.103.112.0/20 Valid RIR databaseARIN 673 100% 67
67.206.96.0/19 Valid RIR databaseARIN, RADB 673 100% 67
67.207.224.0/19 Valid RIR databaseARIN, RADB 673 100% 67
69.8.0.0/18 Valid RIR databaseARIN, RADB 673 100% 67
69.170.224.0/19 Valid RIR databaseARIN, RADB 673 100% 67
72.9.64.0/19 Valid RIR databaseARIN, RADB 673 100% 67
216.137.16.0/20 Valid RIR databaseARIN 673 100% 67
205.142.232.0/22 Valid RIR databaseARIN 671 100% 67

AS-SET

AS8025 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 47 are in fix.csv.

  • ROA: origin1
  • ROA: none13
  • Route object: none4
  • Route object: RIR10
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: origin69.12.112.0/20ROAs covering it name AS393844, not AS8025. If AS8025 should announce it, add a ROA for AS8025.2 of 673
Route object: none69.12.112.0/20Route objects for it name AS393844. Add a route object with origin AS8025 in the RIR database for the space.2 of 673
ROA: none162.242.88.0/23No ROA covers it. Add a ROA for AS8025, maxLength 23.2 of 673
Route object: none162.242.88.0/23No route object for it. Add a route object with origin AS8025 in the RIR database for the space.2 of 673
ROA: none162.242.104.0/24No ROA covers it. Add a ROA for AS8025, maxLength 24.2 of 673
Route object: none162.242.104.0/24No route object for it. Add a route object with origin AS8025 in the RIR database for the space.2 of 673
ROA: none192.133.7.0/24No ROA covers it. Add a ROA for AS8025, maxLength 24.2 of 673
Route object: none192.133.7.0/24No route object for it. Add a route object with origin AS8025 in the RIR database for the space.2 of 673
ROA: none23.139.48.0/24No ROA covers it. Add a ROA for AS8025, maxLength 24.673 of 673
Route object: RIR23.139.48.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none170.92.63.0/24No ROA covers it. Add a ROA for AS8025, maxLength 24.673 of 673
Route object: RIR170.92.63.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.236.92.0/22No ROA covers it. Add a ROA for AS8025, maxLength 22.673 of 673
Route object: RIR192.236.92.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.236.118.0/23No ROA covers it. Add a ROA for AS8025, maxLength 23.673 of 673
Route object: RIR192.236.118.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.253.0.0/21No ROA covers it. Add a ROA for AS8025, maxLength 21.673 of 673
Route object: RIR199.253.0.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.253.8.0/23No ROA covers it. Add a ROA for AS8025, maxLength 23.673 of 673
Route object: RIR199.253.8.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.249.192.0/20No ROA covers it. Add a ROA for AS8025, maxLength 20.673 of 673
Route object: RIR204.249.192.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none205.159.237.0/24No ROA covers it. Add a ROA for AS8025, maxLength 24.673 of 673
Route object: RIR205.159.237.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none205.162.224.0/20No ROA covers it. Add a ROA for AS8025, maxLength 20.673 of 673
Route object: RIR205.162.224.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none205.240.128.0/20No ROA covers it. Add a ROA for AS8025, maxLength 20.673 of 673
Route object: RIR205.240.128.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

38.21.32.0/21RADBNo ROA
38.66.16.0/22RADBNo ROA
50.30.128.0/17RADBNo ROA
66.253.128.0/17RADBNo ROA
68.180.0.0/17RADBNo ROA
68.234.128.0/17RADBNo ROA
69.27.150.0/24RADBNo ROA
72.9.64.0/20ARIN, RADBValid
76.10.0.0/18RADBNo ROA
96.63.192.0/18RADBNo ROA
141.193.143.0/24RADBNo ROA
192.154.131.0/24RADBNo ROA
198.90.110.0/23RADBNo ROA
198.206.193.0/24RADBNo ROA
208.65.224.0/21RADBNo ROA
216.171.0.0/18RADBNo ROA
2600:3800::/28RADBNo ROA
2600:3800::/30RADBNo ROA
2607:f750::/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.