Network · data from 2026-11-12
AS31264 STIM-COMPUTING-AS ADVANIA NORGE AS
Registry name: STIM-COMPUTING-AS ADVANIA NORGE AS, NO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS31264, 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.
| 176.221.89.0/24 | No ROA | Nonecovered by 176.221.88.0/21 | 670 100% |
| 95.128.104.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 176.221.88.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 217.173.240.0/20 | No ROA | RIR databaseRIPE | 672 100% |
| 91.199.63.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.7.136.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 185.80.60.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 185.7.138.0/23 | No ROA | RIR databaseRIPE | 670 100% |
| 185.120.100.0/22 | No ROA | RIR databaseRIPE | 670 100% |
| 185.220.208.0/22 | No ROA | RIR databaseRIPE | 670 100% |
| 2a02:2838::/32 | No ROA | RIR databaseRIPE | 636 100% |
| 2a06:9900::/29 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
AS31264 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 20 are in fix.csv.
- ROA: none12
- Route object: none1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 176.221.89.0/24 | No ROA covers it. Add a ROA for AS31264, maxLength 24. |
| Route object: none | 176.221.89.0/24 | No route object for it. A route object for 176.221.88.0/21 with origin AS31264 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31264 in the RIR database for the space. |
| ROA: none | 95.128.104.0/21 | No ROA covers it. Add a ROA for AS31264, maxLength 21. |
| ROA: none | 176.221.88.0/21 | No ROA covers it. Add a ROA for AS31264, maxLength 21. |
| ROA: none | 217.173.240.0/20 | No ROA covers it. Add a ROA for AS31264, maxLength 20. |
| ROA: none | 91.199.63.0/24 | No ROA covers it. Add a ROA for AS31264, maxLength 24. |
| ROA: none | 185.7.136.0/23 | No ROA covers it. Add a ROA for AS31264, maxLength 23. |
| ROA: none | 185.80.60.0/22 | No ROA covers it. Add a ROA for AS31264, maxLength 22. |
| ROA: none | 185.7.138.0/23 | No ROA covers it. Add a ROA for AS31264, maxLength 23. |
| ROA: none | 185.120.100.0/22 | No ROA covers it. Add a ROA for AS31264, maxLength 22. |
| ROA: none | 185.220.208.0/22 | No ROA covers it. Add a ROA for AS31264, maxLength 22. |
| ROA: none | 2a02:2838::/32 | No ROA covers it. Add a ROA for AS31264, maxLength 32. |
| ROA: none | 2a06:9900::/29 | No ROA covers it. Add a ROA for AS31264, maxLength 29. |
Route objects not announced
Route objects with origin AS31264 whose prefix no peer sees AS31264 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 85.208.88.0/22 | RIPE | No ROA |
| 85.208.88.0/23 | RIPE | No ROA |
| 185.7.136.0/22 | RIPE | No ROA |
| 185.80.60.0/23 | RIPE | No ROA |
| 185.80.62.0/24 | RIPE | No ROA |
| 217.173.240.0/22 | RIPE | No ROA |
| 217.173.252.0/22 | 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.