Network · data from 2026-11-12
AS39811 MTSNET-FAR-EAST-AS MTS PJSC
Registry name: MTSNET-FAR-EAST-AS MTS PJSC, RU · not in PeeringDB
8IPv4 routes
62.5% RPKI valid · 37.5% with a route object
6IPv6 routes
0.0% RPKI valid · 33.3% with a route object
0RPKI invalid
0 origin · 0 maxLength
9No ROA
9 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
26Route objects not announced
registered with origin AS39811, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS39811, 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.
| 78.109.46.0/24 | No ROA | Nonecovered by 78.109.46.0/23 | 673 100% |
| 188.75.216.0/23 | No ROA | Other origin only | 673 100% |
| 188.75.218.0/23 | No ROA | Other origin only | 673 100% |
| 2a02:5f83:d0::/48 | No ROA | Nonecovered by 2a02:5f83::/32 | 636 100% |
| 2a02:5f83:d1::/48 | No ROA | Nonecovered by 2a02:5f83::/32 | 636 100% |
| 2a02:5f83:d0cc::/48 | No ROA | Nonecovered by 2a02:5f83::/32 | 636 100% |
| 2a02:5f83:d1cc::/48 | No ROA | Nonecovered by 2a02:5f83::/32 | 636 100% |
| 2a02:5f80::/32 | No ROA | RIR databaseRIPE | 636 100% |
| 2a02:5f83::/32 | No ROA | RIR databaseRIPE | 636 100% |
| 213.87.102.0/24 | Valid | Nonecovered by 213.87.100.0/22 | 673 100% |
| 213.87.103.0/24 | Valid | Nonecovered by 213.87.100.0/22 | 673 100% |
| 85.140.127.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.87.96.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.87.97.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS39811 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 44 are in fix.csv.
- ROA: none9
- Route object: none9
- Route object: not announced26
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 78.109.46.0/24 | No ROA covers it. Add a ROA for AS39811, maxLength 24. |
| Route object: none | 78.109.46.0/24 | No route object for it. A route object for 78.109.46.0/23 with origin AS39811 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39811 in the RIR database for the space. |
| ROA: none | 188.75.216.0/23 | No ROA covers it. Add a ROA for AS39811, maxLength 23. |
| Route object: none | 188.75.216.0/23 | Route objects for it name AS8359. Add a route object with origin AS39811 in the RIR database for the space. |
| ROA: none | 188.75.218.0/23 | No ROA covers it. Add a ROA for AS39811, maxLength 23. |
| Route object: none | 188.75.218.0/23 | Route objects for it name AS8359. Add a route object with origin AS39811 in the RIR database for the space. |
| ROA: none | 2a02:5f83:d0::/48 | No ROA covers it. Add a ROA for AS39811, maxLength 48. |
| Route object: none | 2a02:5f83:d0::/48 | No route object for it. A route object for 2a02:5f83::/32 with origin AS39811 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39811 in the RIR database for the space. |
| ROA: none | 2a02:5f83:d1::/48 | No ROA covers it. Add a ROA for AS39811, maxLength 48. |
| Route object: none | 2a02:5f83:d1::/48 | No route object for it. A route object for 2a02:5f83::/32 with origin AS39811 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39811 in the RIR database for the space. |
| ROA: none | 2a02:5f83:d0cc::/48 | No ROA covers it. Add a ROA for AS39811, maxLength 48. |
| Route object: none | 2a02:5f83:d0cc::/48 | No route object for it. A route object for 2a02:5f83::/32 with origin AS39811 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39811 in the RIR database for the space. |
| ROA: none | 2a02:5f83:d1cc::/48 | No ROA covers it. Add a ROA for AS39811, maxLength 48. |
| Route object: none | 2a02:5f83:d1cc::/48 | No route object for it. A route object for 2a02:5f83::/32 with origin AS39811 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39811 in the RIR database for the space. |
| ROA: none | 2a02:5f80::/32 | No ROA covers it. Add a ROA for AS39811, maxLength 32. |
| ROA: none | 2a02:5f83::/32 | No ROA covers it. Add a ROA for AS39811, maxLength 32. |
| Route object: none | 213.87.102.0/24 | No route object for it. A route object for 213.87.100.0/22 with origin AS39811 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39811 in the RIR database for the space. |
| Route object: none | 213.87.103.0/24 | No route object for it. A route object for 213.87.100.0/22 with origin AS39811 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39811 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS39811 whose prefix no peer sees AS39811 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.232.166.0/23 | RIPE | No ROA |
| 46.232.166.0/24 | RIPE | No ROA |
| 77.220.60.0/23 | RIPE | No ROA |
| 78.109.46.0/23 | RIPE | No ROA |
| 80.83.228.0/22 | RIPE | No ROA |
| 80.83.232.0/22 | RIPE | No ROA |
| 80.83.236.0/22 | RIPE | No ROA |
| 80.83.237.0/24 | RIPE | Invalid: origin |
| 80.83.238.0/24 | RIPE | No ROA |
| 80.83.239.0/24 | RIPE | No ROA |
| 81.195.239.0/24 | RIPE | Invalid: origin |
| 89.22.190.0/23 | RIPE | No ROA |
| 176.118.14.0/23 | RIPE | No ROA |
| 185.59.137.0/24 | RIPE | No ROA |
| 212.188.15.0/24 | RIPE | Invalid: origin |
| 213.87.96.0/23 | RIPE | Invalid: origin |
| 213.87.98.0/23 | RIPE | Valid |
| 213.87.100.0/22 | RIPE | Invalid: origin |
| 213.87.100.0/24 | RIPE | Valid |
| 213.87.104.0/23 | RIPE | Invalid: origin |
| 213.87.104.0/24 | RIPE | Valid |
| 213.87.106.0/23 | RIPE | Valid |
| 213.87.108.0/23 | RIPE | Invalid: origin |
| 213.87.110.0/23 | RIPE | Invalid: origin |
| 213.87.246.0/24 | RIPE | Valid |
| 2a02:28:8::/47 | 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.