Network · data from 2026-11-12
AS17850 KFBBLOCKCHAIN-AS-KR-KR - Korea Federation of Banks
Registry name: KFBBLOCKCHAIN-AS-KR-KR - Korea Federation of Banks, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17850, 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.
| 211.168.153.0/24 | No ROA | None | 673 100% |
| 211.168.158.0/24 | No ROA | None | 673 100% |
| 211.168.208.0/24 | No ROA | None | 673 100% |
AS-SET
AS17850 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 27 are in fix.csv.
- ROA: none3
- Route object: none3
- Route object: not announced21
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 211.168.153.0/24 | No ROA covers it. Add a ROA for AS17850, maxLength 24. |
| Route object: none | 211.168.153.0/24 | No route object for it. Add a route object with origin AS17850 in the RIR database for the space. |
| ROA: none | 211.168.158.0/24 | No ROA covers it. Add a ROA for AS17850, maxLength 24. |
| Route object: none | 211.168.158.0/24 | No route object for it. Add a route object with origin AS17850 in the RIR database for the space. |
| ROA: none | 211.168.208.0/24 | No ROA covers it. Add a ROA for AS17850, maxLength 24. |
| Route object: none | 211.168.208.0/24 | No route object for it. Add a route object with origin AS17850 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17850 whose prefix no peer sees AS17850 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.97.112.0/20 | NTTCOM, RADB | No ROA |
| 125.7.192.0/18 | RADB | No ROA |
| 125.7.192.0/21 | NTTCOM, RADB | No ROA |
| 125.7.200.0/21 | NTTCOM, RADB | No ROA |
| 125.7.208.0/20 | NTTCOM, RADB | No ROA |
| 125.7.224.0/21 | NTTCOM, RADB | No ROA |
| 125.7.232.0/21 | NTTCOM | No ROA |
| 125.7.240.0/20 | NTTCOM, RADB | No ROA |
| 163.180.192.0/20 | RADB | No ROA |
| 163.180.208.0/20 | RADB | No ROA |
| 163.180.224.0/20 | RADB | No ROA |
| 163.180.240.0/24 | RADB | No ROA |
| 163.180.242.0/23 | RADB | No ROA |
| 163.180.244.0/22 | RADB | No ROA |
| 163.180.248.0/21 | RADB | No ROA |
| 182.252.0.0/20 | RADB | No ROA |
| 210.221.192.0/19 | NTTCOM, RADB | No ROA |
| 211.237.16.0/20 | NTTCOM, RADB | No ROA |
| 211.237.16.0/21 | NTTCOM | No ROA |
| 211.237.24.0/21 | NTTCOM | No ROA |
| 211.238.240.0/20 | NTTCOM, 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.