bgpreport

Network · data from 2026-11-12

AS55662 Citraweb Solusi Teknologi

Registry name: IDNIC-CITRAWEB-AS-ID - CV. CITRAWEB NUSA INFOMEDIA, ID · PeeringDB

4IPv4 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
24Route objects not announced registered with origin AS55662, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55662, 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.71.8.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.71.9.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.71.10.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.71.11.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
2400:9140::/32 Valid Other IRR onlyNTTCOM, RADB 635 100% 70

AS-SET

AS55662'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 29 are in fix.csv.

  • Route object: RIR5
  • Route object: not announced24
ChangePrefix or setDetailFull-table peers
Route object: RIR103.71.8.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.71.9.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.71.10.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.71.11.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2400:9140::/32Route object only in NTTCOM, RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

49.0.24.0/22NTTCOMNo ROA
49.0.26.0/24APNICInvalid: origin
49.0.27.0/24APNICInvalid: origin
103.71.8.0/22NTTCOM, RADBValid
103.71.8.0/23NTTCOM, RADBValid
103.71.10.0/23NTTCOM, RADBValid
111.92.160.0/20NTTCOMNo ROA
111.92.160.0/21NTTCOMNo ROA
111.92.160.0/22NTTCOMNo ROA
111.92.160.0/23NTTCOMNo ROA
111.92.160.0/24NTTCOMNo ROA
111.92.161.0/24NTTCOMNo ROA
111.92.162.0/23NTTCOMNo ROA
111.92.163.0/24NTTCOMNo ROA
111.92.164.0/23NTTCOMNo ROA
111.92.166.0/23NTTCOMNo ROA
111.92.168.0/21NTTCOMNo ROA
111.92.168.0/22NTTCOMNo ROA
111.92.168.0/23NTTCOMNo ROA
111.92.169.0/24NTTCOMNo ROA
111.92.170.0/23NTTCOMNo ROA
111.92.172.0/22NTTCOMNo ROA
111.92.172.0/23NTTCOMNo ROA
111.92.172.0/24NTTCOMNo 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.