bgpreport

Network · data from 2026-11-12

AS55405 Exabytes Enterprise MY02

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55405, 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.139.182.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
103.13.122.0/23 Valid RIR databaseAPNIC, RADB 673 100% 68
103.13.123.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
202.157.182.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.162.26.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
103.162.27.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68

AS-SET

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

  • ROA: none1
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: none103.139.182.0/24No ROA covers it. Add a ROA for AS55405, maxLength 24.672 of 673

Route objects not announced

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

103.13.122.0/24APNIC, RADBValid
117.121.240.0/24APNICInvalid: origin
202.157.176.0/20NTTCOM, RADBNo ROA
202.157.176.0/21NTTCOM, RADBNo ROA
202.157.176.0/22NTTCOM, RADBNo ROA
202.157.178.0/23NTTCOM, RADBNo ROA
202.157.179.0/24NTTCOM, RADBNo ROA
202.157.180.0/22NTTCOM, RADBNo ROA
202.157.184.0/21NTTCOM, RADBNo ROA
202.157.184.0/22NTTCOM, RADBNo ROA
202.157.188.0/22NTTCOM, RADBNo ROA
203.142.0.0/22APNIC, NTTCOM, RADBNo ROA
203.142.0.0/23NTTCOM, RADBNo ROA
203.142.0.0/24NTTCOM, RADBNo ROA
203.142.1.0/24NTTCOM, RADBNo ROA
203.142.2.0/23NTTCOM, RADBNo ROA
203.142.2.0/24NTTCOM, RADBNo ROA
203.142.3.0/24NTTCOM, 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.