Network · data from 2026-11-12
AS51158 MTREND-AS OOO SET
Registry name: MTREND-AS OOO SET, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51158, 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.
| 31.130.248.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 194.28.212.0/22 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS51158 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 14 are in fix.csv.
- ROA: none2
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 31.130.248.0/21 | No ROA covers it. Add a ROA for AS51158, maxLength 21. |
| ROA: none | 194.28.212.0/22 | No ROA covers it. Add a ROA for AS51158, maxLength 22. |
Route objects not announced
Route objects with origin AS51158 whose prefix no peer sees AS51158 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.130.248.0/24 | RIPE | No ROA |
| 31.130.249.0/24 | RIPE | No ROA |
| 31.130.250.0/24 | RIPE | No ROA |
| 31.130.251.0/24 | RIPE | No ROA |
| 31.130.252.0/24 | RIPE | No ROA |
| 31.130.253.0/24 | RIPE | No ROA |
| 31.130.254.0/24 | RIPE | No ROA |
| 31.130.255.0/24 | RIPE | No ROA |
| 194.28.212.0/24 | RIPE | No ROA |
| 194.28.213.0/24 | RIPE | No ROA |
| 194.28.214.0/24 | RIPE | No ROA |
| 194.28.215.0/24 | 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.