bgpreport

Network · data from 2026-11-12

AS9387 Augere Pakistan

Registry name: SHARPTEL-AS-AP - SHARP TELECOM (PRIVATE) LIMITED, PK · PeeringDB

23IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
70Route objects not announced registered with origin AS9387, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9387, 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.11.60.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
113.203.234.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
113.203.235.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
113.203.236.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
113.203.237.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
113.203.238.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
113.203.239.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
113.203.240.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
116.0.60.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
122.50.2.0/24 Valid RIR databaseAPNIC 673 100% 66
180.178.128.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
180.178.129.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
180.178.132.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
180.178.133.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
180.178.134.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
180.178.135.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
180.178.137.0/24 Valid RIR databaseAPNIC 673 100% 66
180.178.138.0/24 Valid RIR databaseAPNIC 673 100% 66
180.178.139.0/24 Valid RIR databaseAPNIC 673 100% 66
180.178.172.0/24 Valid RIR databaseAPNIC 673 100% 66
180.178.175.0/24 Valid RIR databaseAPNIC 673 100% 66
180.178.136.0/24 Valid RIR databaseAPNIC 672 100% 67
180.178.174.0/24 Valid RIR databaseAPNIC 672 100% 67
2401:4100::/33 Valid RIR databaseAPNIC 631 99% 67
2401:4100:8000::/48 Valid RIR databaseAPNIC 631 99% 67

AS-SET

AS9387'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 70 are in fix.csv.

  • Route object: not announced70

Route objects not announced

Route objects with origin AS9387 whose prefix no peer sees AS9387 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.77.8.0/22RADBNo ROA
103.151.27.0/24APNICInvalid: origin
113.203.192.0/19RADBNo ROA
113.203.192.0/20RADBNo ROA
113.203.208.0/22RADBNo ROA
113.203.212.0/22RADBNo ROA
113.203.216.0/21RADBNo ROA
113.203.226.0/24APNICInvalid: origin
113.203.232.0/22RADBNo ROA
113.203.233.0/24APNIC, RADBValid
113.203.236.0/22RADBNo ROA
113.203.244.0/22RADBNo ROA
113.203.244.0/24APNICInvalid: origin
113.203.252.0/24RADBNo ROA
113.203.253.0/24RADBNo ROA
113.203.254.0/24RADBNo ROA
113.203.255.0/24RADBNo ROA
115.167.72.0/24APNICInvalid: origin
115.167.74.0/24APNICInvalid: origin
115.167.75.0/24APNICInvalid: origin
116.0.60.0/22RADB, RIPE-NONAUTHNo ROA
119.73.0.0/20APNICInvalid: origin
119.73.0.0/24APNICInvalid: origin
119.73.1.0/24APNICInvalid: origin
119.73.2.0/24APNICInvalid: origin
119.73.3.0/24APNICInvalid: origin
119.73.4.0/24APNICInvalid: origin
119.73.5.0/24APNICInvalid: origin
119.73.6.0/24APNICInvalid: origin
119.73.7.0/24APNICInvalid: origin
119.73.8.0/24APNICInvalid: origin
119.73.9.0/24APNICInvalid: origin
119.73.10.0/24APNICInvalid: origin
119.73.11.0/24APNICInvalid: origin
119.73.12.0/24APNICInvalid: origin
119.73.13.0/24APNICInvalid: origin
119.73.14.0/24APNIC, RADBValid
119.73.15.0/24APNIC, RADBValid
119.73.32.0/20APNICInvalid: origin
119.73.32.0/24APNIC, RADBValid
119.73.33.0/24APNIC, RADBValid
119.73.34.0/24APNIC, RADBValid
119.73.35.0/24APNIC, RADBValid
119.73.36.0/24APNIC, RADBValid
119.73.37.0/24APNIC, RADBValid
119.73.38.0/24APNICInvalid: origin
119.73.39.0/24APNICInvalid: origin
119.73.40.0/24APNICInvalid: origin
119.73.41.0/24APNICInvalid: origin
119.73.42.0/24APNICInvalid: origin
119.73.43.0/24APNICInvalid: origin
119.73.44.0/24APNICInvalid: origin
119.73.45.0/24APNICInvalid: origin
119.73.46.0/24APNICInvalid: origin
119.73.47.0/24APNICInvalid: origin
122.50.0.0/24APNIC, RADBValid
139.190.52.0/24RADBNo ROA
139.190.53.0/24RADBNo ROA
139.190.54.0/24RADBNo ROA
139.190.55.0/24RADBNo ROA
180.178.128.0/21RADBNo ROA
180.178.136.0/21RADBNo ROA
180.178.144.0/20RADBNo ROA
180.178.176.0/20RADBNo ROA
180.178.184.0/24RADBNo ROA
202.5.134.0/24RADBNo ROA
202.92.18.0/24APNICInvalid: origin
203.170.69.0/24RADBNo ROA
223.29.224.0/20RADBNo ROA
2401:4100::/32APNIC, RADBValid

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.