Network · data from 2026-11-12

AS38532 Exabytes Network Singapore

Registry name: EXABYTES-AS-AP - Exabytes Network (Singapore) Pte. Ltd., SG · PeeringDB

18IPv4 routes 94.4% RPKI valid · 94.4% with a route object

3IPv6 routes 66.7% RPKI valid · 100.0% with a route object

1RPKI invalid 0 origin · 1 maxLength

1No ROA 1 with no route object for this origin

1Low visibility seen by under 10% of full-table peers

24Route objects not announced registered with origin AS38532, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38532, 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.7.8.0/24	Invalid: maxLength	Nonecovered by 103.7.8.0/22	42 6%low visibility	26
2001:df0:480::/48	No ROA	Other IRR onlyRADB	636 100%	67
43.227.231.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
43.229.84.0/22	Valid	RIR databaseAPNIC, RADB, REACH	673 100%	68
43.229.128.0/23	Valid	RIR databaseAPNIC, REACH	673 100%	68
43.229.130.0/24	Valid	RIR databaseAPNIC, REACH	673 100%	68
103.7.8.0/22	Valid	RIR databaseAPNIC, RADB, REACH	673 100%	68
103.14.212.0/22	Valid	RIR databaseAPNIC	673 100%	68
103.26.40.0/22	Valid	RIR databaseAPNIC, RADB, REACH	673 100%	68
103.36.92.0/22	Valid	RIR databaseAPNIC, RADB, REACH	673 100%	68
103.53.172.0/22	Valid	RIR databaseAPNIC, RADB, REACH	673 100%	68
103.62.7.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
103.254.255.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
113.11.248.0/21	Valid	RIR databaseAPNIC, RADB, REACH	673 100%	68
113.197.32.0/21	Valid	RIR databaseAPNIC, RADB, REACH	673 100%	68
116.12.48.0/21	Valid	RIR databaseAPNIC, RADB, REACH	673 100%	68
124.6.60.0/22	Valid	RIR databaseAPNIC	673 100%	68
124.6.63.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.26.41.0/24	Valid	RIR databaseAPNIC, REACH	671 100%	68
2400:1480::/48	Valid	RIR databaseAPNIC	636 100%	67
2407:d200::/32	Valid	RIR databaseAPNIC	636 100%	67

103.7.8.0/24

Invalid: maxLength

Nonecovered by 103.7.8.0/22

42 6%low visibility

2001:df0:480::/48

No ROA

Other IRR onlyRADB

636 100%

43.227.231.0/24

Valid

RIR databaseAPNIC, RADB

673 100%

43.229.84.0/22

Valid

RIR databaseAPNIC, RADB, REACH

673 100%

43.229.128.0/23

Valid

RIR databaseAPNIC, REACH

673 100%

43.229.130.0/24

Valid

RIR databaseAPNIC, REACH

673 100%

103.7.8.0/22

Valid

RIR databaseAPNIC, RADB, REACH

673 100%

103.14.212.0/22

Valid

RIR databaseAPNIC

673 100%

103.26.40.0/22

Valid

RIR databaseAPNIC, RADB, REACH

673 100%

103.36.92.0/22

Valid

RIR databaseAPNIC, RADB, REACH

673 100%

103.53.172.0/22

Valid

RIR databaseAPNIC, RADB, REACH

673 100%

103.62.7.0/24

Valid

RIR databaseAPNIC, RADB

673 100%

103.254.255.0/24

Valid

RIR databaseAPNIC, RADB

673 100%

113.11.248.0/21

Valid

RIR databaseAPNIC, RADB, REACH

673 100%

113.197.32.0/21

Valid

RIR databaseAPNIC, RADB, REACH

673 100%

116.12.48.0/21

Valid

RIR databaseAPNIC, RADB, REACH

673 100%

124.6.60.0/22

Valid

RIR databaseAPNIC

673 100%

124.6.63.0/24

Valid

RIR databaseAPNIC

673 100%

103.26.41.0/24

Valid

RIR databaseAPNIC, REACH

671 100%

2400:1480::/48

Valid

RIR databaseAPNIC

636 100%

2407:d200::/32

Valid

RIR databaseAPNIC

636 100%

AS-SET

AS38532'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 28 are in fix.csv.

ROA: maxLength1
ROA: none1
Route object: none1
Route object: RIR1
Route object: not announced24

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	103.7.8.0/24	ROA 103.7.8.0/22 AS38532 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 103.7.8.0/24.	42 of 673
Route object: none	103.7.8.0/24	No route object for it. A route object for 103.7.8.0/22 with origin AS38532 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38532 in the RIR database for the space.	42 of 673
ROA: none	2001:df0:480::/48	No ROA covers it. Add a ROA for AS38532, maxLength 48.	636 of 636
Route object: RIR	2001:df0:480::/48	Route object only in RADB. Add it in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

103.7.8.0/24

ROA 103.7.8.0/22 AS38532 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 103.7.8.0/24.

42 of 673

Route object: none

103.7.8.0/24

No route object for it. A route object for 103.7.8.0/22 with origin AS38532 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38532 in the RIR database for the space.

42 of 673

ROA: none

2001:df0:480::/48

No ROA covers it. Add a ROA for AS38532, maxLength 48.

636 of 636

Route object: RIR

2001:df0:480::/48

Route object only in RADB. Add it in the RIR database for the space.

636 of 636

Route objects not announced

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


43.229.128.0/22	RADB	No ROA
103.7.9.0/24	REACH	Invalid: maxLength
103.26.40.0/24	REACH	Invalid: maxLength
103.62.4.0/22	APNIC, RADB	Valid
103.62.4.0/23	APNIC	Valid
103.62.4.0/24	APNIC	Valid
103.62.5.0/24	APNIC	Valid
103.62.6.0/23	APNIC	Valid
103.62.6.0/24	APNIC	Valid
103.136.85.0/24	RADB	No ROA
113.11.248.0/22	APNIC	Invalid: maxLength
113.11.248.0/23	APNIC	Invalid: maxLength
113.11.248.0/24	APNIC	Invalid: maxLength
113.197.32.0/22	APNIC	Invalid: maxLength
113.197.32.0/23	APNIC	Invalid: maxLength
113.197.32.0/24	APNIC	Invalid: maxLength
116.12.48.0/22	APNIC	Invalid: maxLength
116.12.48.0/23	APNIC	Invalid: maxLength
116.12.48.0/24	APNIC	Invalid: maxLength
124.6.60.0/23	APNIC	Valid
124.6.60.0/24	APNIC	Valid
124.6.61.0/24	APNIC	Valid
124.6.62.0/23	APNIC	Valid
124.6.62.0/24	APNIC	Valid

43.229.128.0/22

RADB

No ROA

103.7.9.0/24

REACH

Invalid: maxLength

103.26.40.0/24

REACH

Invalid: maxLength

103.62.4.0/22

APNIC, RADB

Valid

103.62.4.0/23

APNIC

Valid

103.62.4.0/24

APNIC

Valid

103.62.5.0/24

APNIC

Valid

103.62.6.0/23

APNIC

Valid

103.62.6.0/24

APNIC

Valid

103.136.85.0/24

RADB

No ROA

113.11.248.0/22

APNIC

Invalid: maxLength

113.11.248.0/23

APNIC

Invalid: maxLength

113.11.248.0/24

APNIC

Invalid: maxLength

113.197.32.0/22

APNIC

Invalid: maxLength

113.197.32.0/23

APNIC

Invalid: maxLength

113.197.32.0/24

APNIC

Invalid: maxLength

116.12.48.0/22

APNIC

Invalid: maxLength

116.12.48.0/23

APNIC

Invalid: maxLength

116.12.48.0/24

APNIC

Invalid: maxLength

124.6.60.0/23

APNIC

Valid

124.6.60.0/24

APNIC

Valid

124.6.61.0/24

APNIC

Valid

124.6.62.0/23

APNIC

Valid

124.6.62.0/24

APNIC

Valid

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.