Network · data from 2026-11-12
AS24435 Supernet Transit ASN
Registry name: SUPERNET-PAKISTAN-AS-AP - Supernet Limited Transit Autonomous System Number, PK · PeeringDB
60IPv4 routes
91.7% RPKI valid · 98.3% with a route object
41IPv6 routes
100.0% RPKI valid · 100.0% with a route object
1RPKI invalid
1 origin · 0 maxLength
4No ROA
1 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
22Route objects not announced
registered with origin AS24435, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS24435, 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.
| 156.238.83.0/24 | Invalid: origin | RIR databaseAFRINIC | 2 0%low visibility |
| 116.0.48.0/22 | No ROA | Other origin only | 673 100% |
| 156.149.208.0/20 | No ROA | RIR databaseAPNIC | 672 100% |
| 134.144.244.0/24 | No ROA | RIR databaseAPNIC, RADB | 670 100% |
| 134.144.245.0/24 | No ROA | RIR databaseAPNIC, RADB | 670 100% |
| 27.0.184.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.27.22.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.0.35.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.0.36.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 116.0.37.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 116.0.39.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 116.0.45.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 116.0.48.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 116.0.49.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 116.0.50.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 116.0.51.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 116.0.52.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 116.0.53.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 116.0.54.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 175.111.0.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 175.111.2.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 175.111.3.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 175.111.4.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 203.130.0.0/20 | Valid | RIR databaseAPNIC | 673 100% |
| 203.130.1.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.3.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.4.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.7.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.8.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.11.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.13.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.16.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.17.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.18.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.19.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.20.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.21.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.130.22.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.23.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.24.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.25.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.26.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.28.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.29.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.31.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 175.111.4.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 175.111.5.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.130.0.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.130.2.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 203.130.5.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.130.6.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.130.9.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.130.10.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.130.12.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.130.15.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.130.26.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.130.27.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.130.28.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.130.30.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.130.14.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 2001:fe8:3::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:fe8:11::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:fe8:4001::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:fe8:4002::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:fe8:5005::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:fe8:8121::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:fe8:9000::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:fe8:c003::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:fe8:8100::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2001:fe8:8101::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2001:fe8:8111::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2001:fe8:8130::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2001:fe8:8131::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2001:fe8:5000::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2001:fe8::/48 | Valid | RIR databaseAPNIC, RADB | 631 99% |
| 2001:fe8:1::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:2::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:9::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:10::/48 | Valid | RIR databaseAPNIC, RADB | 631 99% |
| 2001:fe8:48::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:4003::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:4011::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:4100::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:4101::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:5001::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:5002::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:5003::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:5004::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:5006::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:5007::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:6000::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:6001::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:6002::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:6003::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:6004::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:6005::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:6006::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:6007::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:8110::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:c001::/48 | Valid | RIR databaseAPNIC | 631 99% |
| 2001:fe8:c002::/48 | Valid | RIR databaseAPNIC | 631 99% |
AS-SET
AS24435'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 28 are in fix.csv.
- ROA: origin1
- ROA: none4
- Route object: none1
- Route object: not announced22
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 156.238.83.0/24 | ROAs covering it name AS17561, not AS24435. If AS24435 should announce it, add a ROA for AS24435. |
| ROA: none | 116.0.48.0/22 | No ROA covers it. Add a ROA for AS24435, maxLength 22. |
| Route object: none | 116.0.48.0/22 | Route objects for it name AS38193. Add a route object with origin AS24435 in the RIR database for the space. |
| ROA: none | 156.149.208.0/20 | No ROA covers it. Add a ROA for AS24435, maxLength 20. |
| ROA: none | 134.144.244.0/24 | No ROA covers it. Add a ROA for AS24435, maxLength 24. |
| ROA: none | 134.144.245.0/24 | No ROA covers it. Add a ROA for AS24435, maxLength 24. |
Route objects not announced
Route objects with origin AS24435 whose prefix no peer sees AS24435 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.27.20.0/22 | APNIC, RADB | No ROA |
| 103.255.128.0/22 | APNIC | No ROA |
| 156.238.82.0/24 | AFRINIC | Invalid: origin |
| 175.111.0.0/21 | APNIC | No ROA |
| 175.111.0.0/23 | APNIC | Valid |
| 175.111.1.0/24 | APNIC | Valid |
| 203.130.0.0/19 | APNIC, RADB | No ROA |
| 203.130.0.0/22 | APNIC | Invalid: maxLength |
| 203.130.16.0/20 | RADB | No ROA |
| 203.130.16.0/21 | RADB | No ROA |
| 203.130.16.0/22 | RADB | No ROA |
| 203.130.16.0/23 | RADB | No ROA |
| 203.130.18.0/23 | RADB | No ROA |
| 203.130.20.0/22 | RADB | No ROA |
| 203.130.20.0/23 | RADB | No ROA |
| 203.130.22.0/23 | RADB | No ROA |
| 203.130.24.0/21 | RADB | No ROA |
| 203.130.24.0/22 | APNIC, RADB | No ROA |
| 203.130.24.0/23 | RADB | No ROA |
| 2001:fe8::/32 | APNIC, RADB | No ROA |
| 2001:fe8:4000::/48 | APNIC | Valid |
| 2001:fe8:c100::/48 | APNIC | 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.