Network · data from 2026-11-12
AS43267 SEVEREN-MSK-NET JSC "Severen-Telecom"
Registry name: SEVEREN-MSK-NET JSC "Severen-Telecom", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43267, 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.
| 82.112.187.0/24 | No ROA | Nonecovered by 82.112.186.0/23 | 673 100% |
| 78.140.217.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 82.112.186.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 82.112.188.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 82.112.188.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 82.112.189.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 85.235.200.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 85.235.206.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 91.196.72.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.196.73.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.196.74.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 176.221.24.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 82.112.184.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 91.196.72.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 185.253.184.0/22 | No ROA | RIR databaseRIPE | 670 100% |
AS-SET
AS43267 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: none15
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 82.112.187.0/24 | No ROA covers it. Add a ROA for AS43267, maxLength 24. |
| Route object: none | 82.112.187.0/24 | No route object for it. A route object for 82.112.186.0/23 with origin AS43267 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43267 in the RIR database for the space. |
| ROA: none | 78.140.217.0/24 | No ROA covers it. Add a ROA for AS43267, maxLength 24. |
| ROA: none | 82.112.186.0/23 | No ROA covers it. Add a ROA for AS43267, maxLength 23. |
| ROA: none | 82.112.188.0/22 | No ROA covers it. Add a ROA for AS43267, maxLength 22. |
| ROA: none | 82.112.188.0/24 | No ROA covers it. Add a ROA for AS43267, maxLength 24. |
| ROA: none | 82.112.189.0/24 | No ROA covers it. Add a ROA for AS43267, maxLength 24. |
| ROA: none | 85.235.200.0/22 | No ROA covers it. Add a ROA for AS43267, maxLength 22. |
| ROA: none | 85.235.206.0/23 | No ROA covers it. Add a ROA for AS43267, maxLength 23. |
| ROA: none | 91.196.72.0/24 | No ROA covers it. Add a ROA for AS43267, maxLength 24. |
| ROA: none | 91.196.73.0/24 | No ROA covers it. Add a ROA for AS43267, maxLength 24. |
| ROA: none | 91.196.74.0/24 | No ROA covers it. Add a ROA for AS43267, maxLength 24. |
| ROA: none | 176.221.24.0/22 | No ROA covers it. Add a ROA for AS43267, maxLength 22. |
| ROA: none | 82.112.184.0/21 | No ROA covers it. Add a ROA for AS43267, maxLength 21. |
| ROA: none | 91.196.72.0/22 | No ROA covers it. Add a ROA for AS43267, maxLength 22. |
| ROA: none | 185.253.184.0/22 | No ROA covers it. Add a ROA for AS43267, maxLength 22. |
Route objects not announced
Route objects with origin AS43267 whose prefix no peer sees AS43267 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.112.184.0/23 | RIPE | No ROA |
| 82.112.190.0/24 | RIPE | No ROA |
| 82.112.191.0/24 | RIPE | No ROA |
| 2a06:aa80::/32 | 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.