Network · data from 2026-11-12
AS9701 VIAWEB-AS-KR-KR - viaweb
Registry name: VIAWEB-AS-KR-KR - viaweb, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9701, 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.
| 103.194.252.128/25 | No ROA | Nonecovered by 103.194.252.0/24 | 16 2%low visibility |
| 121.140.42.0/25 | No ROA | None | 16 2%low visibility |
| 128.134.244.0/25 | No ROA | None | 16 2%low visibility |
| 175.197.49.128/25 | No ROA | None | 16 2%low visibility |
| 61.82.144.192/26 | No ROA | None | 14 2%low visibility |
| 103.194.255.0/27 | No ROA | Nonecovered by 103.194.255.0/24 | 14 2%low visibility |
| 211.104.158.0/27 | No ROA | None | 14 2%low visibility |
| 211.104.158.32/27 | No ROA | None | 14 2%low visibility |
| 103.194.252.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 103.194.253.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 103.194.254.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 103.194.255.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS9701 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 58 are in fix.csv.
- ROA: none12
- Route object: none8
- Route object: RIR4
- Route object: not announced34
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.194.252.128/25 | No ROA covers it. Add a ROA for AS9701, maxLength 25. |
| Route object: none | 103.194.252.128/25 | No route object for it. A route object for 103.194.252.0/24 with origin AS9701 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS9701 in the RIR database for the space. |
| ROA: none | 121.140.42.0/25 | No ROA covers it. Add a ROA for AS9701, maxLength 25. |
| Route object: none | 121.140.42.0/25 | No route object for it. Add a route object with origin AS9701 in the RIR database for the space. |
| ROA: none | 128.134.244.0/25 | No ROA covers it. Add a ROA for AS9701, maxLength 25. |
| Route object: none | 128.134.244.0/25 | No route object for it. Add a route object with origin AS9701 in the RIR database for the space. |
| ROA: none | 175.197.49.128/25 | No ROA covers it. Add a ROA for AS9701, maxLength 25. |
| Route object: none | 175.197.49.128/25 | No route object for it. Add a route object with origin AS9701 in the RIR database for the space. |
| ROA: none | 61.82.144.192/26 | No ROA covers it. Add a ROA for AS9701, maxLength 26. |
| Route object: none | 61.82.144.192/26 | No route object for it. Add a route object with origin AS9701 in the RIR database for the space. |
| ROA: none | 103.194.255.0/27 | No ROA covers it. Add a ROA for AS9701, maxLength 27. |
| Route object: none | 103.194.255.0/27 | No route object for it. A route object for 103.194.255.0/24 with origin AS9701 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS9701 in the RIR database for the space. |
| ROA: none | 211.104.158.0/27 | No ROA covers it. Add a ROA for AS9701, maxLength 27. |
| Route object: none | 211.104.158.0/27 | No route object for it. Add a route object with origin AS9701 in the RIR database for the space. |
| ROA: none | 211.104.158.32/27 | No ROA covers it. Add a ROA for AS9701, maxLength 27. |
| Route object: none | 211.104.158.32/27 | No route object for it. Add a route object with origin AS9701 in the RIR database for the space. |
| ROA: none | 103.194.252.0/24 | No ROA covers it. Add a ROA for AS9701, maxLength 24. |
| Route object: RIR | 103.194.252.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.194.253.0/24 | No ROA covers it. Add a ROA for AS9701, maxLength 24. |
| Route object: RIR | 103.194.253.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.194.254.0/24 | No ROA covers it. Add a ROA for AS9701, maxLength 24. |
| Route object: RIR | 103.194.254.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.194.255.0/24 | No ROA covers it. Add a ROA for AS9701, maxLength 24. |
| Route object: RIR | 103.194.255.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9701 whose prefix no peer sees AS9701 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.250.128.0/17 | RADB | No ROA |
| 61.250.128.0/18 | NTTCOM, REACH | No ROA |
| 61.250.172.0/22 | RADB | No ROA |
| 61.250.192.0/18 | NTTCOM, RADB, REACH | No ROA |
| 103.194.252.0/22 | RADB | No ROA |
| 203.233.91.0/24 | REACH | No ROA |
| 210.103.192.0/24 | REACH | No ROA |
| 210.103.193.0/24 | REACH | No ROA |
| 210.103.194.0/24 | REACH | No ROA |
| 210.127.32.0/23 | RADB | No ROA |
| 210.127.32.0/24 | REACH | No ROA |
| 210.127.33.0/24 | REACH | No ROA |
| 210.127.34.0/24 | RADB, REACH | No ROA |
| 210.127.36.0/24 | RADB, REACH | No ROA |
| 210.127.41.0/24 | RADB, REACH | No ROA |
| 210.127.44.0/24 | RADB, REACH | No ROA |
| 210.127.54.0/24 | RADB, REACH | No ROA |
| 211.41.160.0/19 | NTTCOM, REACH | No ROA |
| 211.47.128.0/19 | NTTCOM, REACH | No ROA |
| 211.47.128.0/20 | RADB | No ROA |
| 211.47.144.0/20 | RADB | No ROA |
| 211.116.224.0/19 | NTTCOM, REACH | No ROA |
| 211.116.224.0/20 | RADB | No ROA |
| 211.189.128.0/19 | NTTCOM, REACH | No ROA |
| 211.235.224.0/19 | NTTCOM, REACH | No ROA |
| 211.237.128.0/20 | NTTCOM, REACH | No ROA |
| 211.241.128.0/17 | NTTCOM, RADB, REACH | No ROA |
| 211.254.0.0/17 | REACH | No ROA |
| 211.254.0.0/18 | NTTCOM | No ROA |
| 211.254.64.0/18 | NTTCOM, RADB | No ROA |
| 211.255.0.0/18 | RADB | No ROA |
| 211.255.0.0/19 | NTTCOM, REACH | No ROA |
| 211.255.32.0/19 | NTTCOM, REACH | No ROA |
| 218.36.0.0/17 | NTTCOM, RADB, REACH | 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.