Network · data from 2026-11-12
AS131284 Etisalat Afghan
Registry name: ETISALATAFG-AS-AP - Etisalat Afghan, AF · PeeringDB
47IPv4 routes
93.6% RPKI valid · 93.6% with a route object
0IPv6 routes
1RPKI invalid
1 origin · 0 maxLength
2No ROA
3 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
45Route objects not announced
registered with origin AS131284, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS131284, 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.
| 103.159.163.0/24 | Invalid: origin | Other origin only | 36 5%low visibility |
| 196.195.4.0/24 | No ROA | None | 673 100% |
| 196.195.15.0/24 | No ROA | None | 673 100% |
| 103.13.64.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.13.65.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.13.66.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.13.67.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 137.59.120.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 137.59.121.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 137.59.122.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.222.136.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.222.137.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.222.138.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.222.139.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.222.141.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.222.142.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.222.143.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.96.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.97.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.98.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.99.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.100.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.101.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.103.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.104.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.105.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.106.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.113.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.114.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.115.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.116.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.117.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.118.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.120.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.121.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.122.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.171.123.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 137.59.123.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 180.222.140.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.171.102.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.171.108.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.171.109.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.171.110.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.171.111.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.171.112.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.171.119.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.171.107.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
AS-SET
AS131284'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 51 are in fix.csv.
- ROA: origin1
- ROA: none2
- Route object: none3
- Route object: not announced45
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.159.163.0/24 | ROAs covering it name AS141447, not AS131284. If AS131284 should announce it, add a ROA for AS131284. |
| Route object: none | 103.159.163.0/24 | Route objects for it name AS141447. Add a route object with origin AS131284 in the RIR database for the space. |
| ROA: none | 196.195.4.0/24 | No ROA covers it. Add a ROA for AS131284, maxLength 24. |
| Route object: none | 196.195.4.0/24 | No route object for it. Add a route object with origin AS131284 in the RIR database for the space. |
| ROA: none | 196.195.15.0/24 | No ROA covers it. Add a ROA for AS131284, maxLength 24. |
| Route object: none | 196.195.15.0/24 | No route object for it. Add a route object with origin AS131284 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS131284 whose prefix no peer sees AS131284 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.65.58.0/23 | RADB | No ROA |
| 45.116.128.0/24 | RADB | No ROA |
| 45.125.224.0/24 | RADB | No ROA |
| 45.125.225.0/24 | RADB | No ROA |
| 103.13.64.0/22 | RADB | No ROA |
| 103.17.60.0/22 | APNIC | Valid |
| 103.53.24.0/23 | RADB | No ROA |
| 113.208.72.0/23 | RADB | No ROA |
| 121.127.32.0/21 | RADB | No ROA |
| 137.59.120.0/22 | RADB | No ROA |
| 154.59.46.0/24 | RADB | No ROA |
| 180.222.136.0/21 | APNIC, RADB | Valid |
| 202.86.16.0/21 | RADB | No ROA |
| 202.86.16.0/24 | RADB | No ROA |
| 202.86.17.0/24 | RADB | No ROA |
| 202.86.18.0/24 | RADB | No ROA |
| 202.86.19.0/24 | RADB | No ROA |
| 202.86.20.0/22 | RADB | No ROA |
| 203.171.96.0/22 | APNIC, RADB | Valid |
| 203.171.96.0/23 | APNIC, RADB | Valid |
| 203.171.98.0/23 | APNIC, RADB | Valid |
| 203.171.100.0/22 | APNIC, RADB | No ROA |
| 203.171.100.0/23 | APNIC, RADB | No ROA |
| 203.171.102.0/23 | APNIC, RADB | Valid |
| 203.171.104.0/22 | APNIC, RADB | Valid |
| 203.171.104.0/23 | APNIC, RADB | Valid |
| 203.171.106.0/23 | APNIC, RADB | Valid |
| 203.171.108.0/22 | APNIC, RADB | Valid |
| 203.171.108.0/23 | APNIC, RADB | Valid |
| 203.171.110.0/23 | APNIC, RADB | Valid |
| 203.171.112.0/22 | APNIC, RADB | Valid |
| 203.171.112.0/23 | APNIC, RADB | Valid |
| 203.171.114.0/23 | APNIC, RADB | Valid |
| 203.171.116.0/22 | APNIC, RADB | Valid |
| 203.171.116.0/23 | APNIC, RADB | Valid |
| 203.171.118.0/23 | APNIC, RADB | Valid |
| 203.171.120.0/22 | APNIC, RADB | Valid |
| 203.171.120.0/23 | APNIC, RADB | Valid |
| 203.171.122.0/23 | APNIC | Valid |
| 203.171.124.0/22 | RADB | No ROA |
| 203.171.124.0/23 | RADB | No ROA |
| 203.171.124.0/24 | APNIC, RADB | Valid |
| 203.171.125.0/24 | APNIC, RADB | Valid |
| 203.171.126.0/23 | RADB | No ROA |
| 2404:9b00::/32 | RADB | No ROA |
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.