Network · data from 2026-11-12
AS17569 CALL24-AS-KR-KR - 24si infocall co. ltd
Registry name: CALL24-AS-KR-KR - 24si infocall co. ltd, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17569, 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.195.172.192/26 | No ROA | None | 14 2%low visibility |
| 112.172.35.240/28 | No ROA | None | 13 2%low visibility |
| 220.126.241.16/28 | No ROA | None | 13 2%low visibility |
AS-SET
AS17569 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 69 are in fix.csv.
- ROA: none3
- Route object: none3
- Route object: not announced63
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 211.195.172.192/26 | No ROA covers it. Add a ROA for AS17569, maxLength 26. |
| Route object: none | 211.195.172.192/26 | No route object for it. Add a route object with origin AS17569 in the RIR database for the space. |
| ROA: none | 112.172.35.240/28 | No ROA covers it. Add a ROA for AS17569, maxLength 28. |
| Route object: none | 112.172.35.240/28 | No route object for it. Add a route object with origin AS17569 in the RIR database for the space. |
| ROA: none | 220.126.241.16/28 | No ROA covers it. Add a ROA for AS17569, maxLength 28. |
| Route object: none | 220.126.241.16/28 | No route object for it. Add a route object with origin AS17569 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17569 whose prefix no peer sees AS17569 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 58.143.202.0/24 | RADB | No ROA |
| 58.143.203.0/24 | RADB | No ROA |
| 58.143.204.0/24 | RADB | No ROA |
| 58.143.206.0/24 | RADB | No ROA |
| 58.143.207.0/24 | RADB | No ROA |
| 203.83.128.0/24 | RADB | No ROA |
| 203.83.129.0/24 | RADB | No ROA |
| 203.83.130.0/24 | RADB | No ROA |
| 203.83.131.0/24 | RADB | No ROA |
| 203.83.132.0/24 | RADB | No ROA |
| 203.83.133.0/24 | RADB | No ROA |
| 203.83.134.0/24 | RADB | No ROA |
| 203.83.135.0/24 | RADB | No ROA |
| 203.83.144.0/24 | RADB | No ROA |
| 203.83.145.0/24 | RADB | No ROA |
| 203.83.146.0/24 | RADB | No ROA |
| 203.83.147.0/24 | RADB | No ROA |
| 203.83.148.0/24 | RADB | No ROA |
| 203.83.149.0/24 | RADB | No ROA |
| 203.83.150.0/24 | RADB | No ROA |
| 203.83.157.0/24 | RADB | No ROA |
| 203.83.159.0/24 | RADB | No ROA |
| 203.239.3.0/26 | RADB | No ROA |
| 210.96.19.0/24 | RADB | No ROA |
| 210.122.94.0/24 | RADB | No ROA |
| 210.124.87.0/24 | RADB | No ROA |
| 211.118.207.0/24 | RADB | No ROA |
| 211.234.128.0/17 | RADB | No ROA |
| 211.235.0.0/19 | RADB | No ROA |
| 211.235.0.0/24 | RADB | No ROA |
| 211.235.1.0/24 | RADB | No ROA |
| 211.235.2.0/24 | RADB | No ROA |
| 211.235.3.0/24 | RADB | No ROA |
| 211.235.4.0/24 | RADB | No ROA |
| 211.235.5.0/24 | RADB | No ROA |
| 211.235.6.0/24 | RADB | No ROA |
| 211.235.7.0/24 | RADB | No ROA |
| 211.235.8.0/24 | RADB | No ROA |
| 211.235.9.0/24 | RADB | No ROA |
| 211.235.10.0/24 | RADB | No ROA |
| 211.235.11.0/24 | RADB | No ROA |
| 211.235.12.0/24 | RADB | No ROA |
| 211.235.13.0/24 | RADB | No ROA |
| 211.235.14.0/24 | RADB | No ROA |
| 211.235.15.0/24 | RADB | No ROA |
| 211.235.16.0/24 | RADB | No ROA |
| 211.235.17.0/24 | RADB | No ROA |
| 211.235.18.0/24 | RADB | No ROA |
| 211.235.19.0/24 | RADB | No ROA |
| 211.235.20.0/24 | RADB | No ROA |
| 211.235.21.0/24 | RADB | No ROA |
| 211.235.22.0/24 | RADB | No ROA |
| 211.235.23.0/24 | RADB | No ROA |
| 211.235.24.0/24 | RADB | No ROA |
| 211.235.25.0/24 | RADB | No ROA |
| 211.235.26.0/24 | RADB | No ROA |
| 211.235.27.0/24 | RADB | No ROA |
| 211.235.28.0/24 | RADB | No ROA |
| 211.235.29.0/24 | RADB | No ROA |
| 211.235.30.0/24 | RADB | No ROA |
| 211.235.31.0/24 | RADB | No ROA |
| 211.252.233.0/24 | RADB | No ROA |
| 211.252.234.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.