Network · data from 2026-11-12
AS23560 METLIFEKOREA-AS-KR-KR - MetLife Korea
Registry name: METLIFEKOREA-AS-KR-KR - MetLife Korea, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23560, 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.
| 61.41.206.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 61.32.178.160/27 | No ROA | Other IRR onlyRADB | 3 0%low visibility |
| 61.40.138.0/26 | No ROA | Other IRR onlyRADB | 3 0%low visibility |
AS-SET
AS23560 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 9 are in fix.csv.
- ROA: none3
- Route object: RIR3
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 61.41.206.0/24 | No ROA covers it. Add a ROA for AS23560, maxLength 24. |
| Route object: RIR | 61.41.206.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 61.32.178.160/27 | No ROA covers it. Add a ROA for AS23560, maxLength 27. |
| Route object: RIR | 61.32.178.160/27 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 61.40.138.0/26 | No ROA covers it. Add a ROA for AS23560, maxLength 26. |
| Route object: RIR | 61.40.138.0/26 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23560 whose prefix no peer sees AS23560 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 60.196.11.48/28 | RADB | No ROA |
| 210.101.135.128/26 | RADB | No ROA |
| 219.240.136.64/26 | 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.