bgpreport

Network · data from 2026-11-12

AS153038 Business Zone

Registry name: BUSINESSZONELIMITED-AS-BD - Business Zone Limited, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS153038, 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.214.216.0/24 Invalid: origin Other origin only 0 0%low visibility 1
103.131.102.0/24 Valid RIR databaseAPNIC 673 100% 69
103.185.21.0/24 Valid RIR databaseAPNIC 673 100% 69
160.236.135.0/24 Valid RIR databaseAPNIC 673 100% 68
220.152.113.0/24 Valid RIR databaseAPNIC 673 100% 69
103.20.89.0/24 Valid RIR databaseAPNIC 672 100% 67
103.83.233.0/24 Valid RIR databaseAPNIC 672 100% 67
103.155.27.0/24 Valid RIR databaseAPNIC 672 100% 67
103.156.189.0/24 Valid RIR databaseAPNIC 672 100% 69
103.214.217.0/24 Valid RIR databaseAPNIC 672 100% 67
116.204.140.0/24 Valid RIR databaseAPNIC 672 100% 67
116.204.141.0/24 Valid RIR databaseAPNIC 672 100% 67
116.204.142.0/24 Valid RIR databaseAPNIC 672 100% 67
116.204.143.0/24 Valid RIR databaseAPNIC 672 100% 67
160.236.134.0/24 Valid RIR databaseAPNIC 672 100% 67
160.250.83.0/24 Valid RIR databaseAPNIC 672 100% 67
203.89.126.0/24 Valid RIR databaseAPNIC 672 100% 67
2400:c7c0:20::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:21::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:22::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:23::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:24::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:25::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:26::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:27::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:28::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:29::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:3e::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:3f::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:43e0::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:43e1::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:43e2::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:43e3::/48 Valid RIR databaseAPNIC 634 100% 70
2400:c7c0:43e4::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:43e5::/48 Valid RIR databaseAPNIC 634 100% 70
2400:c7c0:43e6::/48 Valid RIR databaseAPNIC 634 100% 69
2400:c7c0:43e7::/48 Valid RIR databaseAPNIC 634 100% 70
2400:c7c0:43e8::/48 Valid RIR databaseAPNIC 633 100% 70
160.236.134.0/23 Valid RIR databaseAPNIC 2 0%low visibility 2
160.187.116.0/24 Valid RIR databaseAPNIC 0 0%low visibility 2
2400:c7c0:43e0::/43 Valid RIR databaseAPNIC 0 0%low visibility 1
2403:21c0:1000::/36 Valid RIR databaseAPNIC 0 0%low visibility 1

AS-SET

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

  • ROA: origin1
  • Route object: none1
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: origin103.214.216.0/24ROAs covering it name AS150774, not AS153038. If AS153038 should announce it, add a ROA for AS153038.0 of 673
Route object: none103.214.216.0/24Route objects for it name AS150774. Add a route object with origin AS153038 in the RIR database for the space.0 of 673

Route objects not announced

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

116.204.140.0/22APNICValid
116.204.140.0/23APNICValid
116.204.142.0/23APNICValid
2400:c7c0::/32APNICValid
2400:c7c0::/48APNICValid
2400:c7c0:20::/43APNICValid
2400:c7c0:2a::/48APNICValid
2400:c7c0:2b::/48APNICValid
2400:c7c0:2c::/48APNICValid
2400:c7c0:2d::/48APNICValid
2400:c7c0:2e::/48APNICValid
2400:c7c0:2f::/48APNICValid
2400:c7c0:30::/48APNICValid
2400:c7c0:31::/48APNICValid
2400:c7c0:32::/48APNICValid
2400:c7c0:33::/48APNICValid
2400:c7c0:34::/48APNICValid
2400:c7c0:35::/48APNICValid
2400:c7c0:36::/48APNICValid
2400:c7c0:37::/48APNICValid
2400:c7c0:38::/48APNICValid
2400:c7c0:39::/48APNICValid
2400:c7c0:3a::/48APNICValid
2400:c7c0:3b::/48APNICValid
2400:c7c0:3c::/48APNICValid
2400:c7c0:3d::/48APNICValid
2400:c7c0:43c0::/43APNICValid
2400:c7c0:43c0::/48APNICValid
2403:21c0::/32APNICValid
2403:21c0::/36APNICValid
2403:21c0:2000::/36APNICValid
2406:9d40:f00::/40APNICValid

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.