bgpreport

Network · data from 2026-11-12

AS133034 Virtual American Companies (BD)

Registry name: VACL-AS-AP - Virtual American Companies (BD) Limited, BD · PeeringDB

7IPv4 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
7Route objects not announced registered with origin AS133034, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS133034, 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.251.232.0/24 Valid RIR databaseAPNIC 673 100% 69
103.251.233.0/24 Valid RIR databaseAPNIC 673 100% 69
103.251.234.0/24 Valid RIR databaseAPNIC 673 100% 69
103.251.235.0/24 Valid RIR databaseAPNIC 673 100% 69
121.46.70.0/24 Valid RIR databaseAPNIC 673 100% 69
103.156.126.0/24 Valid RIR databaseAPNIC 672 100% 67
103.156.127.0/24 Valid RIR databaseAPNIC 672 100% 67
2400:a740::/48 Valid RIR databaseAPNIC 636 100% 69
2400:a740:1::/48 Valid RIR databaseAPNIC 636 100% 69

AS-SET

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

  • Route object: not announced7

Route objects not announced

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

103.156.126.0/23APNICValid
103.251.232.0/22APNICValid
103.251.232.0/23APNICValid
103.251.234.0/23APNICValid
2400:a740::/32APNICValid
2400:a740:2::/48APNICValid
2400:a740:3::/48APNICValid

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.