Network · data from 2026-11-12
AS49732 TYVASVIAZINFORM-AS Joint Stock Company Tyvasviazinform
Registry name: TYVASVIAZINFORM-AS Joint Stock Company Tyvasviazinform, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49732, 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.
| 195.42.154.0/23 | No ROA | Other origin only | 673 100% |
| 94.230.254.0/24 | Valid | Nonecovered by 94.230.254.0/23 | 673 100% |
| 94.230.240.0/24 | Valid | Nonecovered by 94.230.240.0/23 | 672 100% |
| 94.230.241.0/24 | Valid | Nonecovered by 94.230.240.0/23 | 672 100% |
| 94.230.242.0/24 | Valid | Nonecovered by 94.230.242.0/23 | 672 100% |
| 94.230.240.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 94.230.254.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.193.196.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 94.230.252.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 185.193.199.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.193.198.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 94.230.240.0/23 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 94.230.250.0/23 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 185.193.196.0/23 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS49732 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 14 are in fix.csv.
- ROA: none1
- Route object: none5
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 195.42.154.0/23 | No ROA covers it. Add a ROA for AS49732, maxLength 23. |
| Route object: none | 195.42.154.0/23 | Route objects for it name AS44693. Add a route object with origin AS49732 in the RIR database for the space. |
| Route object: none | 94.230.254.0/24 | No route object for it. A route object for 94.230.254.0/23 with origin AS49732 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49732 in the RIR database for the space. |
| Route object: none | 94.230.240.0/24 | No route object for it. A route object for 94.230.240.0/23 with origin AS49732 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49732 in the RIR database for the space. |
| Route object: none | 94.230.241.0/24 | No route object for it. A route object for 94.230.240.0/23 with origin AS49732 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49732 in the RIR database for the space. |
| Route object: none | 94.230.242.0/24 | No route object for it. A route object for 94.230.242.0/23 with origin AS49732 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49732 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS49732 whose prefix no peer sees AS49732 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 94.230.242.0/23 | RIPE | Valid |
| 94.230.244.0/23 | RIPE | Valid |
| 94.230.246.0/23 | RIPE | Valid |
| 94.230.248.0/23 | RIPE | Valid |
| 185.193.196.0/24 | RIPE | Valid |
| 185.193.197.0/24 | RIPE | Valid |
| 185.193.198.0/23 | RIPE | Valid |
| 2a0b:980::/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.