bgpreport

Network · data from 2026-11-12

AS55855 Asiasoft Online

Registry name: PLAYPARK-AS-AP - PLAYPARK PTE. LTD., SG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55855, 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.
121.52.200.0/21 No ROA Other origin only 1 0%low visibility 1
121.52.203.0/24 No ROA Other IRR onlyRADB, REACH 673 100% 67
121.52.200.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 673 100% 67
121.52.201.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 673 100% 67
121.52.202.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 673 100% 67
121.52.207.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 673 100% 67
121.52.204.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 67
121.52.206.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 67
121.52.205.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 670 100% 67

AS-SET

AS55855'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 4 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none121.52.200.0/21No ROA covers it. Add a ROA for AS55855, maxLength 21.1 of 673
Route object: none121.52.200.0/21Route objects for it name AS45352. Add a route object with origin AS55855 in the RIR database for the space.1 of 673
ROA: none121.52.203.0/24No ROA covers it. Add a ROA for AS55855, maxLength 24.673 of 673
Route object: RIR121.52.203.0/24Route object only in RADB, REACH. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS55855 is announced.

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.