Network · data from 2026-11-12
AS211995 a2z
Registry name: a2z A2Z Technologies CJSC, AZ · PeeringDB
49IPv4 routes
98.0% RPKI valid · 71.4% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
1No ROA
14 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
3Route objects not announced
registered with origin AS211995, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS211995, 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.26.9.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 109.237.112.0/24 | Valid | Nonecovered by 109.237.112.0/21 | 673 100% |
| 109.237.115.0/24 | Valid | Nonecovered by 109.237.112.0/21 | 673 100% |
| 109.237.117.0/24 | Valid | Nonecovered by 109.237.112.0/21 | 673 100% |
| 109.237.118.0/24 | Valid | Nonecovered by 109.237.112.0/21 | 673 100% |
| 109.237.119.0/24 | Valid | Nonecovered by 109.237.112.0/21 | 673 100% |
| 109.237.120.0/24 | Valid | Nonecovered by 109.237.120.0/22 | 673 100% |
| 109.237.121.0/24 | Valid | Nonecovered by 109.237.120.0/22 | 673 100% |
| 109.237.123.0/24 | Valid | Nonecovered by 109.237.120.0/22 | 673 100% |
| 109.237.113.0/24 | Valid | Nonecovered by 109.237.112.0/21 | 672 100% |
| 109.237.116.0/24 | Valid | Nonecovered by 109.237.112.0/21 | 672 100% |
| 185.55.36.0/24 | Valid | Nonecovered by 185.55.36.0/22 | 672 100% |
| 185.55.37.0/24 | Valid | Nonecovered by 185.55.36.0/22 | 672 100% |
| 185.55.38.0/24 | Valid | Nonecovered by 185.55.36.0/22 | 672 100% |
| 185.55.39.0/24 | Valid | Nonecovered by 185.55.36.0/22 | 672 100% |
| 130.0.11.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.77.3.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.136.207.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.233.35.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.164.222.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.142.158.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.22.225.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.22.226.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.22.227.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.22.228.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.22.229.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.22.230.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.22.231.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.22.232.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.22.233.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.22.234.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.22.235.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.22.236.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.22.237.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.22.238.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.22.239.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.237.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.191.194.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.191.195.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.191.196.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.191.197.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.191.198.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.191.199.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.191.200.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.191.201.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.191.202.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.191.203.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.191.204.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.191.205.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a10:d880::/29 | Valid | RIR databaseRIPE | 630 99% |
AS-SET
AS211995'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 18 are in fix.csv.
- ROA: none1
- Route object: none14
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 195.26.9.0/24 | No ROA covers it. Add a ROA for AS211995, maxLength 24. |
| Route object: none | 109.237.112.0/24 | No route object for it. A route object for 109.237.112.0/21 with origin AS211995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211995 in the RIR database for the space. |
| Route object: none | 109.237.115.0/24 | No route object for it. A route object for 109.237.112.0/21 with origin AS211995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211995 in the RIR database for the space. |
| Route object: none | 109.237.117.0/24 | No route object for it. A route object for 109.237.112.0/21 with origin AS211995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211995 in the RIR database for the space. |
| Route object: none | 109.237.118.0/24 | No route object for it. A route object for 109.237.112.0/21 with origin AS211995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211995 in the RIR database for the space. |
| Route object: none | 109.237.119.0/24 | No route object for it. A route object for 109.237.112.0/21 with origin AS211995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211995 in the RIR database for the space. |
| Route object: none | 109.237.120.0/24 | No route object for it. A route object for 109.237.120.0/22 with origin AS211995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211995 in the RIR database for the space. |
| Route object: none | 109.237.121.0/24 | No route object for it. A route object for 109.237.120.0/22 with origin AS211995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211995 in the RIR database for the space. |
| Route object: none | 109.237.123.0/24 | No route object for it. A route object for 109.237.120.0/22 with origin AS211995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211995 in the RIR database for the space. |
| Route object: none | 109.237.113.0/24 | No route object for it. A route object for 109.237.112.0/21 with origin AS211995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211995 in the RIR database for the space. |
| Route object: none | 109.237.116.0/24 | No route object for it. A route object for 109.237.112.0/21 with origin AS211995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211995 in the RIR database for the space. |
| Route object: none | 185.55.36.0/24 | No route object for it. A route object for 185.55.36.0/22 with origin AS211995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211995 in the RIR database for the space. |
| Route object: none | 185.55.37.0/24 | No route object for it. A route object for 185.55.36.0/22 with origin AS211995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211995 in the RIR database for the space. |
| Route object: none | 185.55.38.0/24 | No route object for it. A route object for 185.55.36.0/22 with origin AS211995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211995 in the RIR database for the space. |
| Route object: none | 185.55.39.0/24 | No route object for it. A route object for 185.55.36.0/22 with origin AS211995 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211995 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS211995 whose prefix no peer sees AS211995 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.237.112.0/21 | RIPE | Invalid: maxLength |
| 109.237.120.0/22 | RIPE | Invalid: maxLength |
| 185.55.36.0/22 | 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.