Network · data from 2026-11-12
AS39578 MAXIMA Ltd "Maxima"
Registry name: MAXIMA Ltd "Maxima", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39578, 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.204.181.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 31.204.160.0/19 | No ROA | RIR databaseRIPE | 672 100% |
| 79.99.48.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 88.151.88.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 88.151.184.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 109.75.128.0/20 | No ROA | RIR databaseRIPE | 672 100% |
| 109.75.135.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 31.204.160.0/21 | No ROA | RIR databaseRIPE | 20 3%low visibility |
| 31.204.168.0/21 | No ROA | RIR databaseRIPE | 20 3%low visibility |
| 31.204.176.0/21 | No ROA | RIR databaseRIPE | 20 3%low visibility |
| 31.204.184.0/21 | No ROA | RIR databaseRIPE | 20 3%low visibility |
| 79.99.48.0/22 | No ROA | RIR databaseRIPE | 20 3%low visibility |
| 79.99.52.0/22 | No ROA | RIR databaseRIPE | 20 3%low visibility |
| 88.151.88.0/22 | No ROA | RIR databaseRIPE | 20 3%low visibility |
| 88.151.92.0/22 | No ROA | RIR databaseRIPE | 20 3%low visibility |
| 88.151.184.0/22 | No ROA | RIR databaseRIPE | 20 3%low visibility |
| 88.151.188.0/22 | No ROA | RIR databaseRIPE | 20 3%low visibility |
| 109.75.128.0/21 | No ROA | RIR databaseRIPE | 20 3%low visibility |
| 109.75.136.0/21 | No ROA | RIR databaseRIPE | 20 3%low visibility |
| 177.29.246.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
AS-SET
AS39578 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 22 are in fix.csv.
- ROA: none19
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 31.204.181.0/24 | No ROA covers it. Add a ROA for AS39578, maxLength 24. |
| ROA: none | 31.204.160.0/19 | No ROA covers it. Add a ROA for AS39578, maxLength 19. |
| ROA: none | 79.99.48.0/21 | No ROA covers it. Add a ROA for AS39578, maxLength 21. |
| ROA: none | 88.151.88.0/21 | No ROA covers it. Add a ROA for AS39578, maxLength 21. |
| ROA: none | 88.151.184.0/21 | No ROA covers it. Add a ROA for AS39578, maxLength 21. |
| ROA: none | 109.75.128.0/20 | No ROA covers it. Add a ROA for AS39578, maxLength 20. |
| ROA: none | 109.75.135.0/24 | No ROA covers it. Add a ROA for AS39578, maxLength 24. |
| ROA: none | 31.204.160.0/21 | No ROA covers it. Add a ROA for AS39578, maxLength 21. |
| ROA: none | 31.204.168.0/21 | No ROA covers it. Add a ROA for AS39578, maxLength 21. |
| ROA: none | 31.204.176.0/21 | No ROA covers it. Add a ROA for AS39578, maxLength 21. |
| ROA: none | 31.204.184.0/21 | No ROA covers it. Add a ROA for AS39578, maxLength 21. |
| ROA: none | 79.99.48.0/22 | No ROA covers it. Add a ROA for AS39578, maxLength 22. |
| ROA: none | 79.99.52.0/22 | No ROA covers it. Add a ROA for AS39578, maxLength 22. |
| ROA: none | 88.151.88.0/22 | No ROA covers it. Add a ROA for AS39578, maxLength 22. |
| ROA: none | 88.151.92.0/22 | No ROA covers it. Add a ROA for AS39578, maxLength 22. |
| ROA: none | 88.151.184.0/22 | No ROA covers it. Add a ROA for AS39578, maxLength 22. |
| ROA: none | 88.151.188.0/22 | No ROA covers it. Add a ROA for AS39578, maxLength 22. |
| ROA: none | 109.75.128.0/21 | No ROA covers it. Add a ROA for AS39578, maxLength 21. |
| ROA: none | 109.75.136.0/21 | No ROA covers it. Add a ROA for AS39578, maxLength 21. |
Route objects not announced
Route objects with origin AS39578 whose prefix no peer sees AS39578 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 154.86.7.0/24 | AFRINIC, RADB | Valid |
| 154.88.69.0/24 | AFRINIC, RADB | Valid |
| 154.196.239.0/24 | AFRINIC, RADB | Valid |
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.