bgpreport

Network · data from 2026-11-12

AS4655 UNSPECIFIED - Sing Tao Electronic Daily

Registry name: UNSPECIFIED - Sing Tao Electronic Daily, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS4655, 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.
223.197.53.0/24 No ROA None 672 100% 67
203.80.0.0/22 No ROA Other IRR onlyNTTCOM, RADB, REACH 673 100% 67
203.80.0.0/24 No ROA Other IRR onlyNTTCOM 673 100% 70
203.80.1.0/24 No ROA Other IRR onlyNTTCOM 673 100% 70
203.80.2.0/24 No ROA Other IRR onlyNTTCOM 673 100% 70
203.80.3.0/24 No ROA Other IRR onlyNTTCOM 673 100% 70

AS-SET

AS4655 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 15 are in fix.csv.

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none223.197.53.0/24No ROA covers it. Add a ROA for AS4655, maxLength 24.672 of 673
Route object: none223.197.53.0/24No route object for it. Add a route object with origin AS4655 in the RIR database for the space.672 of 673
ROA: none203.80.0.0/22No ROA covers it. Add a ROA for AS4655, maxLength 22.673 of 673
Route object: RIR203.80.0.0/22Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
ROA: none203.80.0.0/24No ROA covers it. Add a ROA for AS4655, maxLength 24.673 of 673
Route object: RIR203.80.0.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none203.80.1.0/24No ROA covers it. Add a ROA for AS4655, maxLength 24.673 of 673
Route object: RIR203.80.1.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none203.80.2.0/24No ROA covers it. Add a ROA for AS4655, maxLength 24.673 of 673
Route object: RIR203.80.2.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none203.80.3.0/24No ROA covers it. Add a ROA for AS4655, maxLength 24.673 of 673
Route object: RIR203.80.3.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

202.66.86.0/24NTTCOM, RADB, REACHNo ROA
203.80.0.0/23NTTCOMNo ROA
203.80.2.0/23NTTCOMNo 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.