Network · data from 2026-11-12
AS202391 AfraRasa-AS-1 Cooperative Afra ertebatat-e-sabet-e Rasa Co
Registry name: AfraRasa-AS-1 Cooperative Afra ertebatat-e-sabet-e Rasa Co, IR · not in PeeringDB
52IPv4 routes
98.1% RPKI valid · 92.3% with a route object
2IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
1No ROA
4 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
46Route objects not announced
registered with origin AS202391, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS202391, 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.
| 185.141.36.0/22 | No ROA | None | 670 100% |
| 194.147.164.0/24 | Valid | Nonecovered by 194.147.164.0/22 | 672 100% |
| 194.147.166.0/24 | Valid | Nonecovered by 194.147.164.0/22 | 672 100% |
| 194.147.165.0/24 | Valid | Nonecovered by 194.147.164.0/22 | 670 100% |
| 89.42.197.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.42.198.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.47.203.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.237.255.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 95.38.150.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.170.236.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.170.236.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.170.237.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.170.238.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.170.239.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.174.134.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.235.139.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.242.194.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.242.195.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.47.196.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 91.216.71.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 91.238.0.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 94.199.0.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 31.25.92.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 31.25.95.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.142.188.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.142.191.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.34.160.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.34.161.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.34.162.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 89.47.199.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 92.114.48.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 95.38.144.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 95.38.148.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 176.10.95.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.75.204.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.75.205.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.75.206.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.75.207.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.83.180.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.118.13.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.118.14.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.158.172.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.158.173.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.158.174.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.158.175.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.174.132.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.235.136.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.255.208.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 194.147.164.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 45.142.190.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.95.219.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.255.208.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 2a0a:4b80::/30 | Valid | RIR databaseRIPE | 633 100% |
| 2a13:f1c0::/29 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
AS202391 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 51 are in fix.csv.
- ROA: none1
- Route object: none4
- Route object: not announced46
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.141.36.0/22 | No ROA covers it. Add a ROA for AS202391, maxLength 22. |
| Route object: none | 185.141.36.0/22 | No route object for it. Add a route object with origin AS202391 in the RIR database for the space. |
| Route object: none | 194.147.164.0/24 | No route object for it. A route object for 194.147.164.0/22 with origin AS202391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202391 in the RIR database for the space. |
| Route object: none | 194.147.166.0/24 | No route object for it. A route object for 194.147.164.0/22 with origin AS202391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202391 in the RIR database for the space. |
| Route object: none | 194.147.165.0/24 | No route object for it. A route object for 194.147.164.0/22 with origin AS202391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202391 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202391 whose prefix no peer sees AS202391 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.25.92.0/24 | RIPE | Valid |
| 31.25.93.0/24 | RIPE | Valid |
| 31.25.93.80/32 | RIPE | Invalid: maxLength |
| 31.25.93.81/32 | RIPE | Invalid: maxLength |
| 31.25.93.82/32 | RIPE | Invalid: maxLength |
| 31.25.93.83/32 | RIPE | Invalid: maxLength |
| 31.25.93.84/32 | RIPE | Invalid: maxLength |
| 31.25.93.85/32 | RIPE | Invalid: maxLength |
| 31.25.93.86/32 | RIPE | Invalid: maxLength |
| 31.25.93.87/32 | RIPE | Invalid: maxLength |
| 31.25.93.248/32 | RIPE | Invalid: maxLength |
| 31.25.93.249/32 | RIPE | Invalid: maxLength |
| 31.25.93.250/32 | RIPE | Invalid: maxLength |
| 31.25.93.251/32 | RIPE | Invalid: maxLength |
| 31.25.93.252/32 | RIPE | Invalid: maxLength |
| 31.25.93.253/32 | RIPE | Invalid: maxLength |
| 31.25.94.0/24 | RIPE | Valid |
| 45.142.188.0/22 | RIPE | No ROA |
| 46.34.160.0/22 | RIPE | Valid |
| 46.209.162.0/24 | RIPE | Invalid: origin |
| 79.132.204.0/24 | RIPE | Valid |
| 79.132.209.0/24 | RIPE | Valid |
| 89.42.198.0/23 | RIPE | No ROA |
| 89.47.202.0/24 | RIPE | Invalid: origin |
| 92.114.48.0/24 | RIPE | Valid |
| 92.114.49.0/24 | RIPE | Valid |
| 95.38.148.0/22 | RIPE | No ROA |
| 95.38.148.0/24 | RIPE | Valid |
| 95.38.149.0/24 | RIPE | Valid |
| 95.128.198.0/24 | RIPE | No ROA |
| 185.141.36.0/24 | RIPE | Valid |
| 185.141.37.0/24 | RIPE | Valid |
| 185.141.38.0/24 | RIPE | Valid |
| 185.141.39.0/24 | RIPE | Valid |
| 185.170.236.0/23 | RIPE | Valid |
| 185.170.238.0/23 | RIPE | Valid |
| 185.255.209.0/24 | RIPE | Invalid: maxLength |
| 185.255.210.0/24 | RIPE | Invalid: maxLength |
| 185.255.211.0/24 | RIPE | Invalid: maxLength |
| 193.106.191.0/24 | RIPE | No ROA |
| 193.242.194.0/23 | RIPE | No ROA |
| 2a01:5500:fffe::/48 | RIPE | Invalid: maxLength |
| 2a05:5447::/32 | RIPE | Invalid: origin |
| 2a05:9d80::/29 | RIPE | No ROA |
| 2a0a:4b80::/29 | RIPE | No ROA |
| 2a0a:4b84::/30 | 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.