Network · data from 2026-11-12
AS9628 TONGYANGLIFE-AS-KR-KR - TONGYANG LIFE INSURANCE CO., LTD.
Registry name: TONGYANGLIFE-AS-KR-KR - TONGYANG LIFE INSURANCE CO., LTD., KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9628, 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.143.176.0/24 | No ROA | None | 673 100% |
| 103.143.177.0/24 | No ROA | None | 673 100% |
| 211.172.155.0/24 | No ROA | None | 673 100% |
| 211.172.156.0/24 | No ROA | None | 673 100% |
AS-SET
AS9628 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 25 are in fix.csv.
- ROA: none4
- Route object: none4
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.143.176.0/24 | No ROA covers it. Add a ROA for AS9628, maxLength 24. |
| Route object: none | 103.143.176.0/24 | No route object for it. Add a route object with origin AS9628 in the RIR database for the space. |
| ROA: none | 103.143.177.0/24 | No ROA covers it. Add a ROA for AS9628, maxLength 24. |
| Route object: none | 103.143.177.0/24 | No route object for it. Add a route object with origin AS9628 in the RIR database for the space. |
| ROA: none | 211.172.155.0/24 | No ROA covers it. Add a ROA for AS9628, maxLength 24. |
| Route object: none | 211.172.155.0/24 | No route object for it. Add a route object with origin AS9628 in the RIR database for the space. |
| ROA: none | 211.172.156.0/24 | No ROA covers it. Add a ROA for AS9628, maxLength 24. |
| Route object: none | 211.172.156.0/24 | No route object for it. Add a route object with origin AS9628 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9628 whose prefix no peer sees AS9628 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.34.253.0/24 | RADB | No ROA |
| 61.34.254.0/24 | RADB | No ROA |
| 203.230.4.0/23 | RADB | No ROA |
| 203.230.12.0/24 | RADB | No ROA |
| 203.230.13.0/24 | RADB | No ROA |
| 203.230.14.0/24 | RADB | No ROA |
| 203.230.18.0/23 | RADB | No ROA |
| 203.247.168.0/24 | RADB | No ROA |
| 203.247.169.0/24 | RADB | No ROA |
| 210.110.139.0/24 | RADB | No ROA |
| 210.110.140.0/23 | RADB | No ROA |
| 210.110.142.0/24 | RADB | No ROA |
| 210.110.253.0/24 | RADB | No ROA |
| 210.119.32.0/22 | RADB | No ROA |
| 210.119.102.0/23 | RADB | No ROA |
| 211.241.100.0/24 | NTTCOM, RADB | No ROA |
| 221.145.236.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.