Network · data from 2026-11-12
AS23593 BKLNETWORK-AS-KR-KR - bkl LLC
Registry name: BKLNETWORK-AS-KR-KR - bkl LLC, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23593, 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.
| 175.119.43.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.231.25.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.231.64.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.231.65.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 210.103.203.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS23593 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 21 are in fix.csv.
- ROA: none5
- Route object: RIR5
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 175.119.43.0/24 | No ROA covers it. Add a ROA for AS23593, maxLength 24. |
| Route object: RIR | 175.119.43.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.231.25.0/24 | No ROA covers it. Add a ROA for AS23593, maxLength 24. |
| Route object: RIR | 203.231.25.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.231.64.0/24 | No ROA covers it. Add a ROA for AS23593, maxLength 24. |
| Route object: RIR | 203.231.64.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.231.65.0/24 | No ROA covers it. Add a ROA for AS23593, maxLength 24. |
| Route object: RIR | 203.231.65.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.103.203.0/24 | No ROA covers it. Add a ROA for AS23593, maxLength 24. |
| Route object: RIR | 210.103.203.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23593 whose prefix no peer sees AS23593 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.239.104.0/26 | RADB | No ROA |
| 210.103.200.0/24 | RADB | No ROA |
| 210.103.201.0/24 | RADB | No ROA |
| 210.103.202.0/24 | RADB | No ROA |
| 210.103.204.0/24 | RADB | No ROA |
| 210.103.205.0/24 | RADB | No ROA |
| 210.103.206.0/24 | RADB | No ROA |
| 210.103.207.0/24 | RADB | No ROA |
| 210.103.208.0/24 | RADB | No ROA |
| 210.109.64.0/24 | RADB | No ROA |
| 210.112.123.0/24 | 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.