bgpreport

Network · data from 2026-11-12

AS46015 Exabytes Network Malaysia

Registry name: EXABYTES-AS-AP - Exa Bytes Network Sdn.Bhd., MY · PeeringDB

24IPv4 routes 91.7% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
12Route objects not announced registered with origin AS46015, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS46015, 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.144.61.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.139.183.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
42.1.60.0/22 Valid RIR databaseAPNIC, RADB 673 100% 66
43.252.212.0/22 Valid RIR databaseAPNIC, RADB 673 100% 66
43.252.213.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
45.127.4.0/22 Valid RIR databaseAPNIC 673 100% 66
103.6.196.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.6.196.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.6.198.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.18.244.0/22 Valid RIR databaseAPNIC 673 100% 66
103.18.244.0/24 Valid RIR databaseAPNIC 673 100% 66
103.233.0.0/22 Valid RIR databaseAPNIC, RADB 673 100% 66
103.233.0.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
110.4.40.0/21 Valid RIR databaseAPNIC, RADB 673 100% 66
110.4.42.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
110.4.44.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
110.4.45.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
110.4.47.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
117.53.152.0/22 Valid RIR databaseAPNIC, RADB 673 100% 66
137.59.108.0/22 Valid RIR databaseAPNIC, RADB 673 100% 66
137.59.109.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
123.100.224.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
203.142.4.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
43.252.212.0/24 Valid RIR databaseAPNIC, RADB 670 100% 66
2402:6c00::/32 Valid RIR databaseAPNIC 636 100% 67

AS-SET

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

  • ROA: none2
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none103.144.61.0/24No ROA covers it. Add a ROA for AS46015, maxLength 24.673 of 673
ROA: none103.139.183.0/24No ROA covers it. Add a ROA for AS46015, maxLength 24.672 of 673

Route objects not announced

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

43.252.212.0/23APNIC, RADBValid
43.252.214.0/23APNIC, RADBValid
43.252.214.0/24APNIC, RADBValid
43.252.215.0/24APNIC, RADBValid
103.6.196.0/23APNIC, RADBValid
103.6.197.0/24APNIC, RADBValid
103.6.198.0/23APNIC, RADBValid
103.6.199.0/24APNIC, RADBValid
110.4.40.0/24APNICValid
110.4.41.0/24APNIC, RADBValid
110.4.43.0/24APNIC, RADBValid
110.4.46.0/24APNIC, RADBValid

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.