bgpreport

Network · data from 2026-11-12

AS150315 Virtury Cloud Pakistan

Registry name: VCL-AS-AP - Virtury Cloud Private Limited, PK · PeeringDB

6IPv4 routes 83.3% 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
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS150315, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS150315, 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.171.122.0/24 No ROA RIR databaseAPNIC 673 100% 66
103.99.132.0/24 Valid RIR databaseAPNIC 673 100% 66
103.99.133.0/24 Valid RIR databaseAPNIC 673 100% 66
103.153.117.0/24 Valid RIR databaseAPNIC 673 100% 66
103.172.26.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.172.27.0/24 Valid RIR databaseAPNIC 673 100% 68
2001:df2:d40::/48 Valid RIR databaseAPNIC 636 100% 69
2a0d:8140:fff::/48 Valid RIR databaseRIPE 636 100% 69

AS-SET

AS150315'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 5 are in fix.csv.

  • ROA: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none103.171.122.0/24No ROA covers it. Add a ROA for AS150315, maxLength 24.673 of 673

Route objects not announced

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

46.203.234.0/24RADB, RIPEValid
103.151.110.0/24RADBNo ROA
103.151.111.0/24RADBNo ROA
2a0f:85c1:3b8::/48RIPENo 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.