bgpreport

Network · data from 2026-11-12

AS4769 Exabytes Enterprise MY01

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS4769, 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.
203.142.6.0/24 Invalid: maxLength Nonecovered by 203.142.6.0/23 42 6%low visibility 26
103.13.120.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
203.142.6.0/23 Valid RIR databaseAPNIC, NTTCOM 673 100% 66
203.142.7.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.13.121.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
103.13.120.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 47 7%low visibility 33

AS-SET

AS4769'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.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: maxLength203.142.6.0/24ROA 203.142.6.0/23 AS4769 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 203.142.6.0/24.42 of 673
Route object: none203.142.6.0/24No route object for it. A route object for 203.142.6.0/23 with origin AS4769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4769 in the RIR database for the space.42 of 673

Route objects not announced

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

123.100.224.0/22NTTCOM, RADBNo ROA
123.100.224.0/23NTTCOMNo ROA
123.100.226.0/23NTTCOMNo ROA
203.142.4.0/22NTTCOM, RADBNo ROA
203.142.4.0/23NTTCOM, RADBNo 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.