Network · data from 2026-11-12
AS56497 MORS-AS Company with additional liability "New Technologies"
Registry name: MORS-AS Company with additional liability "New Technologies", BY · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS56497, 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.
| 91.149.172.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 91.149.175.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 93.125.58.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 93.125.93.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 93.125.94.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 93.125.95.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 178.172.221.0/24 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS56497 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 8 are in fix.csv.
- ROA: none7
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.149.172.0/24 | No ROA covers it. Add a ROA for AS56497, maxLength 24. |
| ROA: none | 91.149.175.0/24 | No ROA covers it. Add a ROA for AS56497, maxLength 24. |
| ROA: none | 93.125.58.0/24 | No ROA covers it. Add a ROA for AS56497, maxLength 24. |
| ROA: none | 93.125.93.0/24 | No ROA covers it. Add a ROA for AS56497, maxLength 24. |
| ROA: none | 93.125.94.0/24 | No ROA covers it. Add a ROA for AS56497, maxLength 24. |
| ROA: none | 93.125.95.0/24 | No ROA covers it. Add a ROA for AS56497, maxLength 24. |
| ROA: none | 178.172.221.0/24 | No ROA covers it. Add a ROA for AS56497, maxLength 24. |
Route objects not announced
Route objects with origin AS56497 whose prefix no peer sees AS56497 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 213.184.237.64/27 | RIPE | 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.