Network · data from 2026-11-12
AS7620 TOSSBANK-AS-KR-KR - Toss Bank
Registry name: TOSSBANK-AS-KR-KR - Toss Bank, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7620, 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.
| 59.17.47.128/25 | No ROA | None | 16 2%low visibility |
| 59.16.28.192/28 | No ROA | None | 13 2%low visibility |
| 121.142.120.96/28 | No ROA | None | 13 2%low visibility |
| 121.254.147.208/28 | No ROA | Nonecovered by 121.254.147.0/24 | 13 2%low visibility |
| 211.119.131.208/28 | No ROA | Nonecovered by 211.119.131.0/24 | 13 2%low visibility |
| 211.174.52.208/28 | No ROA | Nonecovered by 211.174.52.0/24 | 13 2%low visibility |
| 211.222.63.192/28 | No ROA | None | 13 2%low visibility |
| 211.234.105.208/28 | No ROA | Nonecovered by 211.234.0.0/17 | 13 2%low visibility |
| 218.156.27.192/28 | No ROA | None | 13 2%low visibility |
AS-SET
AS7620 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 38 are in fix.csv.
- ROA: none9
- Route object: none9
- Route object: not announced20
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 59.17.47.128/25 | No ROA covers it. Add a ROA for AS7620, maxLength 25. |
| Route object: none | 59.17.47.128/25 | No route object for it. Add a route object with origin AS7620 in the RIR database for the space. |
| ROA: none | 59.16.28.192/28 | No ROA covers it. Add a ROA for AS7620, maxLength 28. |
| Route object: none | 59.16.28.192/28 | No route object for it. Add a route object with origin AS7620 in the RIR database for the space. |
| ROA: none | 121.142.120.96/28 | No ROA covers it. Add a ROA for AS7620, maxLength 28. |
| Route object: none | 121.142.120.96/28 | No route object for it. Add a route object with origin AS7620 in the RIR database for the space. |
| ROA: none | 121.254.147.208/28 | No ROA covers it. Add a ROA for AS7620, maxLength 28. |
| Route object: none | 121.254.147.208/28 | No route object for it. A route object for 121.254.147.0/24 with origin AS7620 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS7620 in the RIR database for the space. |
| ROA: none | 211.119.131.208/28 | No ROA covers it. Add a ROA for AS7620, maxLength 28. |
| Route object: none | 211.119.131.208/28 | No route object for it. A route object for 211.119.131.0/24 with origin AS7620 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS7620 in the RIR database for the space. |
| ROA: none | 211.174.52.208/28 | No ROA covers it. Add a ROA for AS7620, maxLength 28. |
| Route object: none | 211.174.52.208/28 | No route object for it. A route object for 211.174.52.0/24 with origin AS7620 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS7620 in the RIR database for the space. |
| ROA: none | 211.222.63.192/28 | No ROA covers it. Add a ROA for AS7620, maxLength 28. |
| Route object: none | 211.222.63.192/28 | No route object for it. Add a route object with origin AS7620 in the RIR database for the space. |
| ROA: none | 211.234.105.208/28 | No ROA covers it. Add a ROA for AS7620, maxLength 28. |
| Route object: none | 211.234.105.208/28 | No route object for it. A route object for 211.234.0.0/17 with origin AS7620 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS7620 in the RIR database for the space. |
| ROA: none | 218.156.27.192/28 | No ROA covers it. Add a ROA for AS7620, maxLength 28. |
| Route object: none | 218.156.27.192/28 | No route object for it. Add a route object with origin AS7620 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7620 whose prefix no peer sees AS7620 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 58.184.125.0/24 | RADB | No ROA |
| 58.184.126.0/24 | RADB | No ROA |
| 121.254.147.0/24 | RADB | No ROA |
| 203.234.101.0/24 | RADB | No ROA |
| 203.234.107.0/24 | NTTCOM | No ROA |
| 203.242.112.0/21 | RADB | No ROA |
| 210.102.32.0/19 | RADB | No ROA |
| 210.106.224.0/19 | RADB | No ROA |
| 210.180.0.0/19 | RADB | No ROA |
| 210.180.224.0/19 | RADB | No ROA |
| 210.218.224.0/19 | RADB | No ROA |
| 211.36.224.0/19 | RADB | No ROA |
| 211.39.78.0/24 | NTTCOM, RADB | No ROA |
| 211.39.79.0/24 | RADB | No ROA |
| 211.45.192.0/18 | RADB | No ROA |
| 211.119.131.0/24 | RADB | No ROA |
| 211.174.52.0/24 | RADB | No ROA |
| 211.234.0.0/17 | RADB | No ROA |
| 211.236.96.0/24 | NTTCOM, RADB | No ROA |
| 211.250.238.0/23 | 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.