Network · data from 2026-11-12
AS38090 PearlAbyss
Registry name: PEARLABYSS-AS-KR-KR - pearlabyss, KR · PeeringDB
15IPv4 routes
0.0% RPKI valid · 53.3% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
15No ROA
7 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
20Route objects not announced
registered with origin AS38090, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS38090, 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.188.16.0/24 | No ROA | Nonecovered by 211.188.16.0/20 | 673 100% |
| 211.188.17.0/24 | No ROA | Nonecovered by 211.188.16.0/20 | 673 100% |
| 211.188.18.0/23 | No ROA | Nonecovered by 211.188.16.0/20 | 673 100% |
| 211.188.20.0/24 | No ROA | Nonecovered by 211.188.16.0/20 | 673 100% |
| 211.188.21.0/24 | No ROA | Nonecovered by 211.188.16.0/20 | 673 100% |
| 211.188.24.0/23 | No ROA | Nonecovered by 211.188.16.0/20 | 673 100% |
| 211.188.30.0/23 | No ROA | Nonecovered by 211.188.16.0/20 | 673 100% |
| 103.97.48.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.97.49.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 123.253.172.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 211.188.22.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 211.188.28.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.74.0.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 103.74.0.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 103.97.50.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
AS38090's PeeringDB record names no 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 50 are in fix.csv.
- ROA: none15
- Route object: none7
- Route object: RIR8
- Route object: not announced20
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 211.188.16.0/24 | No ROA covers it. Add a ROA for AS38090, maxLength 24. |
| Route object: none | 211.188.16.0/24 | No route object for it. A route object for 211.188.16.0/20 with origin AS38090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38090 in the RIR database for the space. |
| ROA: none | 211.188.17.0/24 | No ROA covers it. Add a ROA for AS38090, maxLength 24. |
| Route object: none | 211.188.17.0/24 | No route object for it. A route object for 211.188.16.0/20 with origin AS38090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38090 in the RIR database for the space. |
| ROA: none | 211.188.18.0/23 | No ROA covers it. Add a ROA for AS38090, maxLength 23. |
| Route object: none | 211.188.18.0/23 | No route object for it. A route object for 211.188.16.0/20 with origin AS38090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38090 in the RIR database for the space. |
| ROA: none | 211.188.20.0/24 | No ROA covers it. Add a ROA for AS38090, maxLength 24. |
| Route object: none | 211.188.20.0/24 | No route object for it. A route object for 211.188.16.0/20 with origin AS38090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38090 in the RIR database for the space. |
| ROA: none | 211.188.21.0/24 | No ROA covers it. Add a ROA for AS38090, maxLength 24. |
| Route object: none | 211.188.21.0/24 | No route object for it. A route object for 211.188.16.0/20 with origin AS38090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38090 in the RIR database for the space. |
| ROA: none | 211.188.24.0/23 | No ROA covers it. Add a ROA for AS38090, maxLength 23. |
| Route object: none | 211.188.24.0/23 | No route object for it. A route object for 211.188.16.0/20 with origin AS38090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38090 in the RIR database for the space. |
| ROA: none | 211.188.30.0/23 | No ROA covers it. Add a ROA for AS38090, maxLength 23. |
| Route object: none | 211.188.30.0/23 | No route object for it. A route object for 211.188.16.0/20 with origin AS38090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38090 in the RIR database for the space. |
| ROA: none | 103.97.48.0/23 | No ROA covers it. Add a ROA for AS38090, maxLength 23. |
| Route object: RIR | 103.97.48.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.97.49.0/24 | No ROA covers it. Add a ROA for AS38090, maxLength 24. |
| Route object: RIR | 103.97.49.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 123.253.172.0/24 | No ROA covers it. Add a ROA for AS38090, maxLength 24. |
| Route object: RIR | 123.253.172.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.188.22.0/23 | No ROA covers it. Add a ROA for AS38090, maxLength 23. |
| Route object: RIR | 211.188.22.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.188.28.0/24 | No ROA covers it. Add a ROA for AS38090, maxLength 24. |
| Route object: RIR | 211.188.28.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.74.0.0/22 | No ROA covers it. Add a ROA for AS38090, maxLength 22. |
| Route object: RIR | 103.74.0.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.74.0.0/23 | No ROA covers it. Add a ROA for AS38090, maxLength 23. |
| Route object: RIR | 103.74.0.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.97.50.0/23 | No ROA covers it. Add a ROA for AS38090, maxLength 23. |
| Route object: RIR | 103.97.50.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38090 whose prefix no peer sees AS38090 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.74.0.0/24 | RADB | No ROA |
| 103.74.1.0/24 | RADB | No ROA |
| 103.74.2.0/23 | RADB | No ROA |
| 103.74.2.0/24 | RADB | No ROA |
| 103.74.3.0/24 | RADB | No ROA |
| 103.97.48.0/22 | RADB | No ROA |
| 103.97.48.0/24 | RADB | No ROA |
| 103.97.50.0/24 | RADB | No ROA |
| 103.97.51.0/24 | RADB | No ROA |
| 110.14.172.0/24 | NTTCOM | No ROA |
| 114.29.128.0/18 | RADB | No ROA |
| 123.253.172.0/22 | RADB | No ROA |
| 123.253.173.0/24 | RADB | No ROA |
| 123.253.174.0/24 | RADB | No ROA |
| 123.253.175.0/24 | RADB | No ROA |
| 124.137.228.0/24 | NTTCOM | No ROA |
| 124.137.229.0/24 | NTTCOM | No ROA |
| 211.188.16.0/20 | RADB | No ROA |
| 211.188.26.0/24 | RADB | No ROA |
| 211.188.27.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.