Network · data from 2026-11-12
AS202468 AbrArvan-AS Noyan Abr Arvan Co. ( Private Joint Stock)
Registry name: AbrArvan-AS Noyan Abr Arvan Co. ( Private Joint Stock), IR · not in PeeringDB
87IPv4 routes
100.0% RPKI valid · 85.1% with a route object
9IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
13 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
52Route objects not announced
registered with origin AS202468, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS202468, 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.
| 94.101.189.0/24 | Valid | Nonecovered by 94.101.188.0/22 | 672 100% |
| 95.38.237.0/24 | Valid | Nonecovered by 95.38.236.0/23 | 672 100% |
| 5.253.26.0/24 | Valid | Nonecovered by 5.253.26.0/23 | 671 100% |
| 5.253.27.0/24 | Valid | Nonecovered by 5.253.26.0/23 | 671 100% |
| 94.101.183.0/24 | Valid | Nonecovered by 94.101.180.0/22 | 671 100% |
| 94.101.188.0/24 | Valid | Nonecovered by 94.101.188.0/22 | 671 100% |
| 94.101.190.0/24 | Valid | Nonecovered by 94.101.188.0/22 | 671 100% |
| 94.101.191.0/24 | Valid | Nonecovered by 94.101.188.0/22 | 671 100% |
| 95.38.112.0/22 | Valid | Other origin onlycovered by 95.38.112.0/21 | 671 100% |
| 95.38.116.0/22 | Valid | Nonecovered by 95.38.112.0/21 | 671 100% |
| 95.38.236.0/24 | Valid | Nonecovered by 95.38.236.0/23 | 671 100% |
| 95.38.238.0/24 | Valid | Nonecovered by 95.38.238.0/23 | 671 100% |
| 95.38.239.0/24 | Valid | Nonecovered by 95.38.238.0/23 | 671 100% |
| 37.32.28.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 37.152.185.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.152.186.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 37.152.188.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 45.82.138.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 45.156.192.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 95.38.164.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 95.38.180.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 95.38.188.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 95.38.232.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 95.38.234.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 185.226.116.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.231.180.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.239.104.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.121.120.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 188.121.124.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 188.121.127.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.213.196.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 5.253.24.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 37.32.2.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 37.32.4.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 37.32.8.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 37.32.12.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 37.32.20.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 37.32.24.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 37.152.176.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 37.152.184.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.82.136.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 45.140.228.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 45.156.180.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 94.101.176.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 94.101.180.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 94.101.182.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 94.101.184.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 95.38.108.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 95.38.160.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 95.38.162.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 95.38.166.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 95.38.176.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 95.38.176.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 95.38.178.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 95.38.186.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 95.38.190.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 128.0.105.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.74.165.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.97.116.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.206.92.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.220.224.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.220.227.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.228.236.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.228.237.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.228.238.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.239.105.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.239.106.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 188.121.96.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 188.121.104.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 188.121.108.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 188.121.112.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 188.121.126.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.176.241.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.176.242.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 37.32.16.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 37.32.17.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 37.32.18.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 37.32.19.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 37.32.36.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 85.198.48.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 85.198.52.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 95.38.182.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 95.38.184.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 188.121.100.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 188.121.116.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 37.32.1.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 2a07:3902:100::/40 | Valid | RIR databaseRIPE | 634 100% |
| 2a07:3902:200::/40 | Valid | RIR databaseRIPE | 634 100% |
| 2a07:3902:300::/40 | Valid | RIR databaseRIPE | 634 100% |
| 2a07:3902:400::/40 | Valid | RIR databaseRIPE | 634 100% |
| 2a07:3902:500::/40 | Valid | RIR databaseRIPE | 634 100% |
| 2a07:3903::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a07:3904::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a07:3906::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a07:3900::/29 | Valid | RIR databaseRIPE | 633 100% |
| 185.220.225.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS202468 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 65 are in fix.csv.
- Route object: none13
- Route object: not announced52
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 94.101.189.0/24 | No route object for it. A route object for 94.101.188.0/22 with origin AS202468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202468 in the RIR database for the space. |
| Route object: none | 95.38.237.0/24 | No route object for it. A route object for 95.38.236.0/23 with origin AS202468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202468 in the RIR database for the space. |
| Route object: none | 5.253.26.0/24 | No route object for it. A route object for 5.253.26.0/23 with origin AS202468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202468 in the RIR database for the space. |
| Route object: none | 5.253.27.0/24 | No route object for it. A route object for 5.253.26.0/23 with origin AS202468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202468 in the RIR database for the space. |
| Route object: none | 94.101.183.0/24 | No route object for it. A route object for 94.101.180.0/22 with origin AS202468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202468 in the RIR database for the space. |
| Route object: none | 94.101.188.0/24 | No route object for it. A route object for 94.101.188.0/22 with origin AS202468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202468 in the RIR database for the space. |
| Route object: none | 94.101.190.0/24 | No route object for it. A route object for 94.101.188.0/22 with origin AS202468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202468 in the RIR database for the space. |
| Route object: none | 94.101.191.0/24 | No route object for it. A route object for 94.101.188.0/22 with origin AS202468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202468 in the RIR database for the space. |
| Route object: none | 95.38.112.0/22 | Route objects for it name AS41881. A route object for 95.38.112.0/21 with origin AS202468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202468 in the RIR database for the space. |
| Route object: none | 95.38.116.0/22 | No route object for it. A route object for 95.38.112.0/21 with origin AS202468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202468 in the RIR database for the space. |
| Route object: none | 95.38.236.0/24 | No route object for it. A route object for 95.38.236.0/23 with origin AS202468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202468 in the RIR database for the space. |
| Route object: none | 95.38.238.0/24 | No route object for it. A route object for 95.38.238.0/23 with origin AS202468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202468 in the RIR database for the space. |
| Route object: none | 95.38.239.0/24 | No route object for it. A route object for 95.38.238.0/23 with origin AS202468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202468 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202468 whose prefix no peer sees AS202468 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.253.24.0/22 | RIPE | Valid |
| 5.253.26.0/23 | RIPE | Valid |
| 37.32.0.0/19 | RIPE | Valid |
| 37.32.0.0/20 | RIPE | Valid |
| 37.32.0.0/22 | RIPE | Valid |
| 37.32.0.0/24 | RIPE | Valid |
| 37.32.3.0/24 | RIPE | Valid |
| 37.32.16.0/20 | RIPE | Valid |
| 37.32.16.0/22 | RIPE | Valid |
| 37.152.176.0/20 | RIPE | Valid |
| 37.152.176.0/22 | RIPE | Valid |
| 37.152.180.0/22 | RIPE | Valid |
| 45.82.136.0/22 | RIPE | Valid |
| 85.198.48.0/20 | RIPE | Valid |
| 85.198.56.0/22 | RIPE | Valid |
| 85.198.60.0/22 | RIPE | Valid |
| 94.101.176.0/20 | RIPE | Valid |
| 94.101.180.0/22 | RIPE | Valid |
| 94.101.180.0/24 | RIPE | Valid |
| 94.101.184.0/21 | RIPE | Valid |
| 94.101.188.0/22 | RIPE | Valid |
| 95.38.108.0/24 | RIPE | Valid |
| 95.38.109.0/24 | RIPE | Valid |
| 95.38.112.0/21 | RIPE | Valid |
| 95.38.112.0/23 | RIPE | Valid |
| 95.38.114.0/23 | RIPE | Valid |
| 95.38.116.0/23 | RIPE | Valid |
| 95.38.118.0/23 | RIPE | Valid |
| 95.38.160.0/21 | RIPE | Valid |
| 95.38.232.0/21 | RIPE | Valid |
| 95.38.236.0/23 | RIPE | Valid |
| 95.38.238.0/23 | RIPE | Valid |
| 185.97.116.0/24 | RIPE | Valid |
| 185.97.117.0/24 | RIPE | Valid |
| 185.97.118.0/24 | RIPE | Valid |
| 185.97.119.0/24 | RIPE | Valid |
| 185.220.224.0/22 | RIPE | Valid |
| 185.220.224.0/23 | RIPE | Valid |
| 185.228.236.0/22 | RIPE | Valid |
| 185.228.239.0/24 | RIPE | Valid |
| 185.239.104.0/22 | RIPE | Valid |
| 188.121.96.0/19 | RIPE | Valid |
| 188.121.120.0/21 | RIPE | Valid |
| 193.176.240.0/22 | RIPE | Valid |
| 193.176.240.0/24 | RIPE | Valid |
| 193.176.242.0/24 | RIPE | Valid |
| 193.176.243.0/24 | RIPE | Valid |
| 2a07:3900::/48 | RIPE | Valid |
| 2a07:3900:1::/48 | RIPE | Valid |
| 2a07:3902::/32 | RIPE | Valid |
| 2a07:3907::/32 | RIPE | Valid |
| 2a07:3907::/40 | 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.