Network · data from 2026-11-12
AS9277 SKB-T-AS-KR-KR - SK Broadband Co Ltd
Registry name: SKB-T-AS-KR-KR - SK Broadband Co Ltd, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9277, 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.
| 1.224.0.0/20 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS9277 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 54 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced52
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 1.224.0.0/20 | No ROA covers it. Add a ROA for AS9277, maxLength 20. |
| Route object: RIR | 1.224.0.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9277 whose prefix no peer sees AS9277 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 1.224.0.0/15 | RADB | No ROA |
| 61.98.0.0/16 | NTTCOM | No ROA |
| 61.99.0.0/16 | NTTCOM | No ROA |
| 61.101.0.0/17 | NTTCOM | No ROA |
| 61.101.128.0/18 | NTTCOM | No ROA |
| 61.101.192.0/19 | NTTCOM | No ROA |
| 61.104.0.0/16 | NTTCOM | No ROA |
| 61.105.0.0/16 | NTTCOM | No ROA |
| 61.253.0.0/16 | NTTCOM | No ROA |
| 61.254.0.0/15 | NTTCOM | No ROA |
| 152.149.100.0/22 | RADB | No ROA |
| 152.149.104.0/21 | RADB | No ROA |
| 152.149.112.0/20 | RADB | No ROA |
| 152.149.128.0/23 | RADB | No ROA |
| 203.238.128.0/18 | RADB | No ROA |
| 210.94.64.0/18 | NTTCOM, RADB | No ROA |
| 210.94.128.0/19 | RADB | No ROA |
| 210.98.224.0/19 | RADB | No ROA |
| 210.117.0.0/17 | NTTCOM, RADB | No ROA |
| 210.181.32.0/19 | RADB | No ROA |
| 210.181.64.0/18 | NTTCOM, RADB | No ROA |
| 210.205.128.0/17 | NTTCOM, RADB | No ROA |
| 210.218.128.0/18 | NTTCOM, RADB | No ROA |
| 210.219.128.0/18 | NTTCOM, RADB | No ROA |
| 210.221.0.0/17 | NTTCOM, RADB | No ROA |
| 210.221.128.0/19 | NTTCOM | No ROA |
| 210.221.168.0/23 | RADB | No ROA |
| 210.221.224.0/19 | RADB | No ROA |
| 211.33.0.0/17 | NTTCOM, RADB | No ROA |
| 211.47.192.0/19 | NTTCOM | No ROA |
| 211.49.0.0/16 | RADB | No ROA |
| 211.49.0.0/17 | NTTCOM | No ROA |
| 211.49.128.0/17 | NTTCOM | No ROA |
| 211.52.128.0/17 | NTTCOM, RADB | No ROA |
| 211.59.0.0/16 | NTTCOM, RADB | No ROA |
| 211.63.0.0/18 | RADB | No ROA |
| 211.63.0.0/19 | NTTCOM | No ROA |
| 211.109.0.0/16 | NTTCOM, RADB | No ROA |
| 211.110.0.0/16 | NTTCOM, RADB | No ROA |
| 211.116.128.0/19 | NTTCOM | No ROA |
| 211.172.240.0/20 | RADB | No ROA |
| 211.186.0.0/16 | NTTCOM, RADB | No ROA |
| 211.187.0.0/16 | NTTCOM, RADB | No ROA |
| 211.236.0.0/19 | RADB | No ROA |
| 211.238.224.0/22 | NTTCOM, RADB | No ROA |
| 211.238.228.0/22 | NTTCOM, RADB | No ROA |
| 211.238.232.0/22 | NTTCOM, RADB | No ROA |
| 211.238.236.0/22 | NTTCOM, RADB | No ROA |
| 211.243.0.0/16 | NTTCOM | No ROA |
| 211.244.0.0/16 | NTTCOM, RADB | No ROA |
| 211.245.0.0/17 | NTTCOM, RADB | No ROA |
| 211.245.128.0/17 | NTTCOM | 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.