Network · data from 2026-11-12

AS63930 READYSERVER-SG - READY SERVER PTE LTD

Registry name: READYSERVER-SG - READY SERVER PTE LTD, SG · not in PeeringDB

20IPv4 routes 100.0% 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

0No ROA 0 with no route object for this origin

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

10Route objects not announced registered with origin AS63930, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS63930, 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.120.206.0/24	Valid	Other IRR onlyRADB	673 100%	68
45.119.203.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
45.125.192.0/24	Valid	RIR databaseAPNIC, RADB, REACH	673 100%	68
45.125.193.0/24	Valid	RIR databaseAPNIC, RADB, REACH	673 100%	68
45.125.194.0/24	Valid	RIR databaseAPNIC, RADB, REACH	673 100%	68
45.125.195.0/24	Valid	RIR databaseAPNIC, RADB, REACH	673 100%	68
103.47.208.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB, REACH	673 100%	68
103.47.209.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB, REACH	673 100%	68
103.47.210.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB, REACH	673 100%	68
103.47.211.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB, REACH	673 100%	68
103.60.10.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
103.146.96.0/24	Valid	RIR databaseRIPE	673 100%	66
103.147.171.0/24	Valid	RIR databaseRIPE	673 100%	66
103.152.174.0/24	Valid	RIR databaseRADB, RIPE	673 100%	68
103.166.154.0/24	Valid	RIR databaseRIPE	673 100%	66
103.200.208.0/24	Valid	RIR databaseAPNIC, RADB, REACH	673 100%	68
103.200.209.0/24	Valid	RIR databaseAPNIC, RADB, REACH	673 100%	68
103.200.211.0/24	Valid	RIR databaseAPNIC, RADB, REACH	673 100%	68
119.161.100.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
103.200.210.0/24	Valid	RIR databaseAPNIC, RADB, REACH	670 100%	68
2401:e780::/32	Valid	RIR databaseAPNIC, RADB	636 100%	69

AS-SET

AS63930 isn't in PeeringDB, where networks name their 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 11 are in fix.csv.

Route object: RIR1
Route object: not announced10

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	103.120.206.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

103.120.206.0/24

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

673 of 673

Route objects not announced

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


103.41.173.0/24	REACH	Invalid: origin
103.77.79.0/24	REACH	Invalid: origin
103.195.151.0/24	REACH	No ROA
103.200.208.0/22	RADB	No ROA
103.200.208.0/23	RADB	No ROA
103.200.210.0/23	RADB	No ROA
2403:a180::/32	RADB	No ROA
2a04:8806::/35	RADB	No ROA
2a04:dd83::/32	RADB	No ROA
2a04:dd84::/32	RADB	No ROA

103.41.173.0/24

REACH

Invalid: origin

103.77.79.0/24

REACH

Invalid: origin

103.195.151.0/24

REACH

No ROA

103.200.208.0/22

RADB

No ROA

103.200.208.0/23

RADB

No ROA

103.200.210.0/23

RADB

No ROA

2403:a180::/32

RADB

No ROA

2a04:8806::/35

RADB

No ROA

2a04:dd83::/32

RADB

No ROA

2a04:dd84::/32

RADB

No 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.