Network · data from 2026-11-12
AS45446 MYSOL-PK - My Solutions Corporation Ltd.
Registry name: MYSOL-PK - My Solutions Corporation Ltd., PK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45446, 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.
| 202.44.90.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 202.44.93.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 202.44.94.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 202.44.91.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
AS-SET
AS45446 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 11 are in fix.csv.
- ROA: none4
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 202.44.90.0/24 | No ROA covers it. Add a ROA for AS45446, maxLength 24. |
| Route object: RIR | 202.44.90.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 202.44.93.0/24 | No ROA covers it. Add a ROA for AS45446, maxLength 24. |
| ROA: none | 202.44.94.0/24 | No ROA covers it. Add a ROA for AS45446, maxLength 24. |
| ROA: none | 202.44.91.0/24 | No ROA covers it. Add a ROA for AS45446, maxLength 24. |
Route objects not announced
Route objects with origin AS45446 whose prefix no peer sees AS45446 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.44.80.0/21 | RADB | No ROA |
| 202.44.80.0/24 | APNIC, RADB | No ROA |
| 202.44.82.0/24 | APNIC, RADB | No ROA |
| 202.44.85.0/24 | APNIC, RADB | No ROA |
| 202.44.92.0/24 | APNIC, RADB | No ROA |
| 202.44.95.0/24 | APNIC | 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.