bgpreport

Network · data from 2026-11-12

AS4623 CHEVALIER-AS01 - Chevalier (Internet) Limited autonomous system # 1

Registry name: CHEVALIER-AS01 - Chevalier (Internet) Limited autonomous system # 1, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS4623, 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.
202.77.10.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 66
202.77.11.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 66
202.77.12.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 66
202.77.13.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 66
202.77.15.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67

AS-SET

AS4623 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: none5
  • Route object: RIR5
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none202.77.10.0/24No ROA covers it. Add a ROA for AS4623, maxLength 24.673 of 673
Route object: RIR202.77.10.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.77.11.0/24No ROA covers it. Add a ROA for AS4623, maxLength 24.673 of 673
Route object: RIR202.77.11.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.77.12.0/24No ROA covers it. Add a ROA for AS4623, maxLength 24.673 of 673
Route object: RIR202.77.12.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.77.13.0/24No ROA covers it. Add a ROA for AS4623, maxLength 24.673 of 673
Route object: RIR202.77.13.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.77.15.0/24No ROA covers it. Add a ROA for AS4623, maxLength 24.673 of 673
Route object: RIR202.77.15.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

202.77.0.0/18NTTCOM, RADBNo ROA
202.77.0.0/23RADBNo ROA
202.77.0.0/24NTTCOM, RADBNo ROA
202.77.1.0/24NTTCOM, RADBNo ROA
202.77.2.0/24NTTCOM, RADBNo 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.