bgpreport

Network · data from 2026-11-12

AS17787 PSEB-AS-PK - Pakistan Software Export Board

Registry name: PSEB-AS-PK - Pakistan Software Export Board, PK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17787, 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.
203.215.166.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 67
203.215.168.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 68
203.215.170.0/24 No ROA RIR databaseAPNIC 673 100% 67
203.215.173.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 67
203.215.175.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 68
203.215.176.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 68
203.215.177.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 66
203.215.181.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 67
203.215.182.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 67
203.215.183.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 68
203.215.186.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 68
203.215.160.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.215.161.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
203.215.162.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
203.215.164.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
203.215.172.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68

AS-SET

AS17787 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 55 are in fix.csv.

  • ROA: none11
  • Route object: not announced44
ChangePrefix or setDetailFull-table peers
ROA: none203.215.166.0/24No ROA covers it. Add a ROA for AS17787, maxLength 24.673 of 673
ROA: none203.215.168.0/24No ROA covers it. Add a ROA for AS17787, maxLength 24.673 of 673
ROA: none203.215.170.0/24No ROA covers it. Add a ROA for AS17787, maxLength 24.673 of 673
ROA: none203.215.173.0/24No ROA covers it. Add a ROA for AS17787, maxLength 24.673 of 673
ROA: none203.215.175.0/24No ROA covers it. Add a ROA for AS17787, maxLength 24.673 of 673
ROA: none203.215.176.0/24No ROA covers it. Add a ROA for AS17787, maxLength 24.673 of 673
ROA: none203.215.177.0/24No ROA covers it. Add a ROA for AS17787, maxLength 24.673 of 673
ROA: none203.215.181.0/24No ROA covers it. Add a ROA for AS17787, maxLength 24.673 of 673
ROA: none203.215.182.0/24No ROA covers it. Add a ROA for AS17787, maxLength 24.673 of 673
ROA: none203.215.183.0/24No ROA covers it. Add a ROA for AS17787, maxLength 24.673 of 673
ROA: none203.215.186.0/24No ROA covers it. Add a ROA for AS17787, maxLength 24.673 of 673

Route objects not announced

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

203.215.160.0/19RADBNo ROA
203.215.160.0/20RADBNo ROA
203.215.160.0/21RADBNo ROA
203.215.160.0/22RADBNo ROA
203.215.160.0/23RADBNo ROA
203.215.162.0/23RADBNo ROA
203.215.164.0/22RADBNo ROA
203.215.164.0/23RADBNo ROA
203.215.166.0/23RADBNo ROA
203.215.168.0/21RADBNo ROA
203.215.168.0/22RADBNo ROA
203.215.168.0/23RADBNo ROA
203.215.170.0/23RADBNo ROA
203.215.172.0/22RADBNo ROA
203.215.172.0/23RADBNo ROA
203.215.174.0/23RADBNo ROA
203.215.176.0/20RADBNo ROA
203.215.176.0/21APNIC, RADBNo ROA
203.215.176.0/22APNIC, RADBNo ROA
203.215.176.0/23APNIC, RADBNo ROA
203.215.178.0/23APNIC, RADBNo ROA
203.215.178.0/24APNICInvalid: origin
203.215.179.0/24APNIC, RADBNo ROA
203.215.180.0/22APNIC, RADBNo ROA
203.215.180.0/23APNIC, RADBNo ROA
203.215.180.0/24APNICInvalid: origin
203.215.182.0/23APNIC, RADBNo ROA
203.215.184.0/21RADBNo ROA
203.215.184.0/22RADBNo ROA
203.215.184.0/23RADBNo ROA
203.215.184.0/24RADBNo ROA
203.215.185.0/24RADBNo ROA
203.215.186.0/23RADBNo ROA
203.215.187.0/24RADBNo ROA
203.215.188.0/22RADBNo ROA
203.215.188.0/23RADBNo ROA
203.215.188.0/24RADBNo ROA
203.215.189.0/24RADBNo ROA
203.215.190.0/23RADBNo ROA
203.215.190.0/24RADBNo ROA
203.215.191.0/24RADBNo ROA
2403:a500::/32RADBNo ROA
2405:c00:64::/48APNIC, RADBNo ROA
2405:c00:1000::/48APNIC, RADBNo 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.