Network · data from 2026-11-12
AS44467 IRN-STC-AS PJSC Rostelecom
Registry name: IRN-STC-AS PJSC Rostelecom, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44467, 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.
| 83.239.47.0/24 | Invalid: origin | None | 66 10%low visibility |
| 83.239.44.0/24 | Valid | None | 672 100% |
| 83.239.46.0/24 | Valid | None | 672 100% |
| 85.173.3.0/24 | Valid | Nonecovered by 85.173.0.0/22 | 672 100% |
| 83.239.45.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS44467 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 6 are in fix.csv.
- ROA: origin1
- Route object: none4
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 83.239.47.0/24 | ROAs covering it name AS12389, AS25490, not AS44467. If AS44467 should announce it, add a ROA for AS44467. |
| Route object: none | 83.239.47.0/24 | No route object for it. Add a route object with origin AS44467 in the RIR database for the space. |
| Route object: none | 83.239.44.0/24 | No route object for it. Add a route object with origin AS44467 in the RIR database for the space. |
| Route object: none | 83.239.46.0/24 | No route object for it. Add a route object with origin AS44467 in the RIR database for the space. |
| Route object: none | 85.173.3.0/24 | No route object for it. A route object for 85.173.0.0/22 with origin AS44467 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44467 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS44467 whose prefix no peer sees AS44467 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 85.173.0.0/22 | RIPE | Invalid: origin |
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.