Network · data from 2026-11-12
AS61976 SELECTEL-NSK JSC Selectel
Registry name: SELECTEL-NSK JSC Selectel, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61976, 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.
| 79.141.66.170/32 | Invalid: maxLength | Nonecovered by 79.141.66.0/24 | 1 0%low visibility |
| 92.242.62.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 92.255.62.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 109.172.96.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 111.88.172.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 130.49.208.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 136.234.124.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.42.164.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.193.90.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.193.90.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.141.64.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 2a00:ab00:6000::/36 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS61976 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 25 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced23
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 79.141.66.170/32 | ROA 79.141.64.0/20 AS61976 has maxLength 24; ROA 79.141.66.0/24 AS61976 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 79.141.66.170/32. |
| Route object: none | 79.141.66.170/32 | No route object for it. A route object for 79.141.66.0/24 with origin AS61976 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS61976 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61976 whose prefix no peer sees AS61976 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 79.141.64.0/24 | RIPE | Valid |
| 79.141.65.0/24 | RIPE | Valid |
| 79.141.66.0/24 | RIPE | Valid |
| 79.141.67.0/24 | RIPE | Valid |
| 79.141.68.0/24 | RIPE | Valid |
| 79.141.69.0/24 | RIPE | Valid |
| 79.141.70.0/24 | RIPE | Valid |
| 79.141.71.0/24 | RIPE | Valid |
| 79.141.72.0/24 | RIPE | Valid |
| 79.141.73.0/24 | RIPE | Valid |
| 79.141.74.0/24 | RIPE | Valid |
| 79.141.75.0/24 | RIPE | Valid |
| 79.141.76.0/24 | RIPE | Valid |
| 79.141.77.0/24 | RIPE | Valid |
| 79.141.78.0/24 | RIPE | Valid |
| 79.141.79.0/24 | RIPE | Valid |
| 92.255.62.0/24 | RIPE | Valid |
| 92.255.63.0/24 | RIPE | Valid |
| 185.42.164.0/24 | RIPE | Valid |
| 185.42.165.0/24 | RIPE | Valid |
| 185.42.166.0/24 | RIPE | Valid |
| 185.42.167.0/24 | RIPE | Valid |
| 185.193.91.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.