Network · data from 2026-11-12
AS211057 Astra for Telecommunication and IT Services
Registry name: ps-astra Astra for Telecommunication and IT Services, PS · PeeringDB
28IPv4 routes
92.9% RPKI valid · 64.3% with a route object
0IPv6 routes
2RPKI invalid
2 origin · 0 maxLength
0No ROA
10 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
10Route objects not announced
registered with origin AS211057, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS211057, 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.
| 82.38.114.0/24 | Invalid: origin | None | 2 0%low visibility |
| 82.38.115.0/24 | Invalid: origin | None | 2 0%low visibility |
| 154.21.100.0/24 | Valid | Nonecovered by 154.21.100.0/22 | 672 100% |
| 154.21.101.0/24 | Valid | Nonecovered by 154.21.100.0/22 | 672 100% |
| 154.21.102.0/24 | Valid | Nonecovered by 154.21.100.0/22 | 672 100% |
| 154.21.103.0/24 | Valid | Nonecovered by 154.21.100.0/22 | 672 100% |
| 154.21.164.0/24 | Valid | Nonecovered by 154.21.164.0/22 | 672 100% |
| 154.21.165.0/24 | Valid | Nonecovered by 154.21.164.0/22 | 672 100% |
| 154.21.166.0/24 | Valid | Nonecovered by 154.21.164.0/22 | 672 100% |
| 154.21.167.0/24 | Valid | Nonecovered by 154.21.164.0/22 | 672 100% |
| 46.253.91.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.41.211.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 82.41.221.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 185.71.142.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.38.112.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 92.119.12.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 92.119.14.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 92.119.15.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 185.21.120.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.21.123.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.71.140.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.71.141.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.203.66.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.253.85.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 46.253.86.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 46.253.88.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 46.253.92.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 82.41.159.0/24 | Valid | RIR databaseRADB, RIPE | 2 0%low visibility |
AS-SET
AS211057'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 22 are in fix.csv.
- ROA: origin2
- Route object: none10
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 82.38.114.0/24 | ROAs covering it name AS834, not AS211057. If AS211057 should announce it, add a ROA for AS211057. |
| Route object: none | 82.38.114.0/24 | No route object for it. Add a route object with origin AS211057 in the RIR database for the space. |
| ROA: origin | 82.38.115.0/24 | ROAs covering it name AS834, not AS211057. If AS211057 should announce it, add a ROA for AS211057. |
| Route object: none | 82.38.115.0/24 | No route object for it. Add a route object with origin AS211057 in the RIR database for the space. |
| Route object: none | 154.21.100.0/24 | No route object for it. A route object for 154.21.100.0/22 with origin AS211057 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211057 in the RIR database for the space. |
| Route object: none | 154.21.101.0/24 | No route object for it. A route object for 154.21.100.0/22 with origin AS211057 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211057 in the RIR database for the space. |
| Route object: none | 154.21.102.0/24 | No route object for it. A route object for 154.21.100.0/22 with origin AS211057 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211057 in the RIR database for the space. |
| Route object: none | 154.21.103.0/24 | No route object for it. A route object for 154.21.100.0/22 with origin AS211057 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211057 in the RIR database for the space. |
| Route object: none | 154.21.164.0/24 | No route object for it. A route object for 154.21.164.0/22 with origin AS211057 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211057 in the RIR database for the space. |
| Route object: none | 154.21.165.0/24 | No route object for it. A route object for 154.21.164.0/22 with origin AS211057 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211057 in the RIR database for the space. |
| Route object: none | 154.21.166.0/24 | No route object for it. A route object for 154.21.164.0/22 with origin AS211057 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211057 in the RIR database for the space. |
| Route object: none | 154.21.167.0/24 | No route object for it. A route object for 154.21.164.0/22 with origin AS211057 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211057 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS211057 whose prefix no peer sees AS211057 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.143.8.0/22 | ARIN | Valid |
| 38.247.40.0/22 | ARIN | Valid |
| 154.21.100.0/22 | ARIN | Valid |
| 154.21.164.0/22 | ARIN | Valid |
| 185.21.120.0/22 | RIPE | No ROA |
| 185.21.121.0/24 | RIPE | Valid |
| 185.21.122.0/24 | RIPE | Valid |
| 185.71.140.0/23 | RIPE | Valid |
| 185.203.66.0/25 | RIPE | Invalid: maxLength |
| 185.203.66.128/25 | RIPE | Invalid: maxLength |
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.