bgpreport

Network · data from 2026-11-12

AS134204 Business Network

Registry name: BUSINESSNETWORK-AS-AP - Business Network, BD · PeeringDB

19IPv4 routes 100.0% RPKI valid · 100.0% with a route object
15IPv6 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
2Low visibility seen by under 10% of full-table peers
17Route objects not announced registered with origin AS134204, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134204, 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.211.31.0/24 Valid RIR databaseAPNIC 673 100% 67
103.58.72.0/22 Valid RIR databaseAPNIC 672 100% 67
103.58.72.0/24 Valid RIR databaseAPNIC 672 100% 68
103.58.73.0/24 Valid RIR databaseAPNIC 672 100% 68
103.58.74.0/24 Valid RIR databaseAPNIC 672 100% 68
103.58.75.0/24 Valid RIR databaseAPNIC 672 100% 68
103.122.46.0/24 Valid RIR databaseAPNIC 672 100% 68
103.122.47.0/24 Valid RIR databaseAPNIC 672 100% 68
103.138.122.0/24 Valid RIR databaseAPNIC 672 100% 68
103.138.123.0/24 Valid RIR databaseAPNIC 672 100% 68
103.211.28.0/24 Valid RIR databaseAPNIC 672 100% 68
103.211.29.0/24 Valid RIR databaseAPNIC 672 100% 68
103.211.30.0/24 Valid RIR databaseAPNIC 672 100% 68
138.252.84.0/24 Valid RIR databaseAPNIC 672 100% 68
203.76.220.0/22 Valid RIR databaseAPNIC 672 100% 67
203.76.220.0/24 Valid RIR databaseAPNIC 672 100% 68
203.76.221.0/24 Valid RIR databaseAPNIC 672 100% 68
203.76.222.0/24 Valid RIR databaseAPNIC 672 100% 68
203.76.223.0/24 Valid RIR databaseAPNIC 672 100% 68
2400:4d40::/32 Valid RIR databaseAPNIC 636 100% 69
2400:4d40::/36 Valid RIR databaseAPNIC 636 100% 69
2400:4d40:1000::/36 Valid RIR databaseAPNIC 636 100% 69
2400:4d40:2000::/36 Valid RIR databaseAPNIC 636 100% 69
2400:4d40:3000::/36 Valid RIR databaseAPNIC 636 100% 69
2400:4d40:4000::/36 Valid RIR databaseAPNIC 636 100% 69
2400:4d40:5000::/36 Valid RIR databaseAPNIC 636 100% 69
2400:4d40:6000::/36 Valid RIR databaseAPNIC 636 100% 69
2400:4d40:7000::/36 Valid RIR databaseAPNIC 636 100% 69
2400:4d40:8000::/36 Valid RIR databaseAPNIC 636 100% 69
2400:4d40:9000::/36 Valid RIR databaseAPNIC 636 100% 69
2400:4d40:a000::/36 Valid RIR databaseAPNIC 636 100% 69
2400:4d40:e000::/36 Valid RIR databaseAPNIC 636 100% 69
2400:4d40:b000::/36 Valid RIR databaseAPNIC 42 7%low visibility 29
2400:4d40:c000::/36 Valid RIR databaseAPNIC 42 7%low visibility 29

AS-SET

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

  • Route object: not announced17

Route objects not announced

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

103.12.72.0/22APNICValid
103.12.72.0/23APNICValid
103.12.72.0/24APNICValid
103.12.73.0/24APNICValid
103.12.74.0/23APNICValid
103.12.74.0/24APNICValid
103.12.75.0/24APNICValid
103.58.72.0/23APNICValid
103.58.74.0/23APNICValid
103.211.28.0/22APNICValid
160.250.82.0/24APNICValid
180.94.28.0/24APNICValid
180.94.29.0/24APNICValid
203.76.220.0/23APNICValid
203.76.222.0/23APNICValid
2400:4d40:d000::/36APNICValid
2400:4d40:f000::/36APNICValid

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.