Network · data from 2026-11-12
AS8025 BRIGHTOK-AS - BrightNet Oklahoma
Registry name: BRIGHTOK-AS - BrightNet Oklahoma, US · not in PeeringDB
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 |
| 162.242.88.0/23 | No ROA | None | 2 0%low visibility |
| 162.242.104.0/24 | No ROA | None | 2 0%low visibility |
| 192.133.7.0/24 | No ROA | None | 2 0%low visibility |
| 23.139.48.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 170.92.63.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 192.236.92.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 192.236.118.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 199.253.0.0/21 | No ROA | Other IRR onlyRADB | 673 100% |
| 199.253.8.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 204.249.192.0/20 | No ROA | Other IRR onlyRADB | 673 100% |
| 205.159.237.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 205.162.224.0/20 | No ROA | Other IRR onlyRADB | 673 100% |
| 205.240.128.0/20 | No ROA | Other IRR onlyRADB | 673 100% |
| 66.103.112.0/20 | Valid | RIR databaseARIN | 673 100% |
| 67.206.96.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 67.207.224.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 69.8.0.0/18 | Valid | RIR databaseARIN, RADB | 673 100% |
| 69.170.224.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 72.9.64.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 216.137.16.0/20 | Valid | RIR databaseARIN | 673 100% |
| 205.142.232.0/22 | Valid | RIR databaseARIN | 671 100% |
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
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 69.12.112.0/20 | ROAs covering it name AS393844, not AS8025. If AS8025 should announce it, add a ROA for AS8025. |
| Route object: none | 69.12.112.0/20 | Route objects for it name AS393844. Add a route object with origin AS8025 in the RIR database for the space. |
| ROA: none | 162.242.88.0/23 | No ROA covers it. Add a ROA for AS8025, maxLength 23. |
| Route object: none | 162.242.88.0/23 | No route object for it. Add a route object with origin AS8025 in the RIR database for the space. |
| ROA: none | 162.242.104.0/24 | No ROA covers it. Add a ROA for AS8025, maxLength 24. |
| Route object: none | 162.242.104.0/24 | No route object for it. Add a route object with origin AS8025 in the RIR database for the space. |
| ROA: none | 192.133.7.0/24 | No ROA covers it. Add a ROA for AS8025, maxLength 24. |
| Route object: none | 192.133.7.0/24 | No route object for it. Add a route object with origin AS8025 in the RIR database for the space. |
| ROA: none | 23.139.48.0/24 | No ROA covers it. Add a ROA for AS8025, maxLength 24. |
| Route object: RIR | 23.139.48.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 170.92.63.0/24 | No ROA covers it. Add a ROA for AS8025, maxLength 24. |
| Route object: RIR | 170.92.63.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.236.92.0/22 | No ROA covers it. Add a ROA for AS8025, maxLength 22. |
| Route object: RIR | 192.236.92.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.236.118.0/23 | No ROA covers it. Add a ROA for AS8025, maxLength 23. |
| Route object: RIR | 192.236.118.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.253.0.0/21 | No ROA covers it. Add a ROA for AS8025, maxLength 21. |
| Route object: RIR | 199.253.0.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.253.8.0/23 | No ROA covers it. Add a ROA for AS8025, maxLength 23. |
| Route object: RIR | 199.253.8.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 204.249.192.0/20 | No ROA covers it. Add a ROA for AS8025, maxLength 20. |
| Route object: RIR | 204.249.192.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 205.159.237.0/24 | No ROA covers it. Add a ROA for AS8025, maxLength 24. |
| Route object: RIR | 205.159.237.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 205.162.224.0/20 | No ROA covers it. Add a ROA for AS8025, maxLength 20. |
| Route object: RIR | 205.162.224.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 205.240.128.0/20 | No ROA covers it. Add a ROA for AS8025, maxLength 20. |
| Route object: RIR | 205.240.128.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
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/21 | RADB | No ROA |
| 38.66.16.0/22 | RADB | No ROA |
| 50.30.128.0/17 | RADB | No ROA |
| 66.253.128.0/17 | RADB | No ROA |
| 68.180.0.0/17 | RADB | No ROA |
| 68.234.128.0/17 | RADB | No ROA |
| 69.27.150.0/24 | RADB | No ROA |
| 72.9.64.0/20 | ARIN, RADB | Valid |
| 76.10.0.0/18 | RADB | No ROA |
| 96.63.192.0/18 | RADB | No ROA |
| 141.193.143.0/24 | RADB | No ROA |
| 192.154.131.0/24 | RADB | No ROA |
| 198.90.110.0/23 | RADB | No ROA |
| 198.206.193.0/24 | RADB | No ROA |
| 208.65.224.0/21 | RADB | No ROA |
| 216.171.0.0/18 | RADB | No ROA |
| 2600:3800::/28 | RADB | No ROA |
| 2600:3800::/30 | RADB | No ROA |
| 2607:f750::/32 | RADB | No 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.