bgpreport

Network · data from 2026-11-12

AS147188 RNPL-AS-AP - Rocket Network Pte. Ltd.

Registry name: RNPL-AS-AP - Rocket Network Pte. Ltd., SG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS147188, 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.31.228.0/24 No ROA RIR databaseAPNIC, NTTCOM 671 100% 67
103.31.229.0/24 No ROA RIR databaseAPNIC, NTTCOM 671 100% 67
103.31.230.0/24 No ROA RIR databaseAPNIC, NTTCOM 671 100% 67
103.31.231.0/24 No ROA RIR databaseAPNIC, NTTCOM 671 100% 67
103.47.28.0/24 No ROA RIR databaseAPNIC, NTTCOM 671 100% 67
103.47.29.0/24 No ROA RIR databaseAPNIC, NTTCOM 671 100% 67
103.47.30.0/24 No ROA RIR databaseAPNIC, NTTCOM 671 100% 67
103.47.31.0/24 No ROA RIR databaseAPNIC, NTTCOM 671 100% 67
103.226.172.0/23 No ROA RIR databaseAPNIC, NTTCOM 671 100% 67
103.142.252.0/23 No ROA RIR databaseAPNIC 670 100% 67
103.174.88.0/23 No ROA RIR databaseAPNIC 670 100% 67
2400:1120:168::/48 No ROA RIR databaseAPNIC, NTTCOM 636 100% 69

AS-SET

AS147188 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 21 are in fix.csv.

  • ROA: none12
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none103.31.228.0/24No ROA covers it. Add a ROA for AS147188, maxLength 24.671 of 673
ROA: none103.31.229.0/24No ROA covers it. Add a ROA for AS147188, maxLength 24.671 of 673
ROA: none103.31.230.0/24No ROA covers it. Add a ROA for AS147188, maxLength 24.671 of 673
ROA: none103.31.231.0/24No ROA covers it. Add a ROA for AS147188, maxLength 24.671 of 673
ROA: none103.47.28.0/24No ROA covers it. Add a ROA for AS147188, maxLength 24.671 of 673
ROA: none103.47.29.0/24No ROA covers it. Add a ROA for AS147188, maxLength 24.671 of 673
ROA: none103.47.30.0/24No ROA covers it. Add a ROA for AS147188, maxLength 24.671 of 673
ROA: none103.47.31.0/24No ROA covers it. Add a ROA for AS147188, maxLength 24.671 of 673
ROA: none103.226.172.0/23No ROA covers it. Add a ROA for AS147188, maxLength 23.671 of 673
ROA: none103.142.252.0/23No ROA covers it. Add a ROA for AS147188, maxLength 23.670 of 673
ROA: none103.174.88.0/23No ROA covers it. Add a ROA for AS147188, maxLength 23.670 of 673
ROA: none2400:1120:168::/48No ROA covers it. Add a ROA for AS147188, maxLength 48.636 of 636

Route objects not announced

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

103.47.28.0/22APNICNo ROA
103.47.28.0/23APNICNo ROA
103.47.30.0/23APNICNo ROA
103.142.252.0/24APNIC, NTTCOMNo ROA
103.142.253.0/24APNIC, NTTCOMNo ROA
103.174.88.0/24APNIC, NTTCOMNo ROA
103.174.89.0/24APNIC, NTTCOMNo ROA
103.226.172.0/24APNICNo ROA
103.226.173.0/24APNICNo 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.