Network · data from 2026-11-12
AS39422 Sumy Computer Networks
Registry name: SKM-AS Oleksandr Yaremenko, UA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39422, 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.108.238.238/32 | Invalid: maxLength | Nonecovered by 176.108.236.0/22 | 0 0%low visibility |
| 176.108.232.0/23 | Valid | Nonecovered by 176.108.232.0/22 | 72 11% |
| 176.108.232.0/24 | Valid | Nonecovered by 176.108.232.0/22 | 72 11% |
| 176.108.234.0/24 | Valid | Nonecovered by 176.108.232.0/22 | 72 11% |
| 176.108.237.0/24 | Valid | Nonecovered by 176.108.236.0/22 | 72 11% |
| 176.108.238.0/23 | Valid | Nonecovered by 176.108.236.0/22 | 72 11% |
| 176.108.239.0/24 | Valid | Nonecovered by 176.108.236.0/22 | 72 11% |
| 176.108.232.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 176.108.236.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 195.182.202.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 176.108.232.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 195.182.202.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 176.108.233.0/24 | Valid | RIR databaseRIPE | 133 20% |
| 176.108.235.0/24 | Valid | RIR databaseRIPE | 133 20% |
| 195.182.203.0/24 | Valid | RIR databaseRIPE | 133 20% |
AS-SET
AS39422's PeeringDB record names no 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 9 are in fix.csv.
- ROA: maxLength1
- Route object: none7
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 176.108.238.238/32 | ROA 176.108.232.0/21 AS39422 has maxLength 21; ROA 176.108.236.0/22 AS39422 has maxLength 22; ROA 176.108.238.0/23 AS39422 has maxLength 23; ROA 176.108.238.0/24 AS39422 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 176.108.238.238/32. |
| Route object: none | 176.108.238.238/32 | No route object for it. A route object for 176.108.236.0/22 with origin AS39422 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS39422 in the RIR database for the space. |
| Route object: none | 176.108.232.0/23 | No route object for it. A route object for 176.108.232.0/22 with origin AS39422 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39422 in the RIR database for the space. |
| Route object: none | 176.108.232.0/24 | No route object for it. A route object for 176.108.232.0/22 with origin AS39422 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39422 in the RIR database for the space. |
| Route object: none | 176.108.234.0/24 | No route object for it. A route object for 176.108.232.0/22 with origin AS39422 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39422 in the RIR database for the space. |
| Route object: none | 176.108.237.0/24 | No route object for it. A route object for 176.108.236.0/22 with origin AS39422 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39422 in the RIR database for the space. |
| Route object: none | 176.108.238.0/23 | No route object for it. A route object for 176.108.236.0/22 with origin AS39422 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39422 in the RIR database for the space. |
| Route object: none | 176.108.239.0/24 | No route object for it. A route object for 176.108.236.0/22 with origin AS39422 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39422 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS39422 whose prefix no peer sees AS39422 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 176.108.236.0/24 | RIPE | 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.