bgpreport

Network · data from 2026-11-12

AS17769 PT Indopratama Teleglobal

Registry name: CITYNET-AP - PT Indopratama Teleglobal (ISP)Wisma BSG Floor 6, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17769, 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.159.20.0/24 No ROA Other IRR onlyRADB 673 100% 69
202.55.169.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
202.55.175.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69

AS-SET

AS17769'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 58 are in fix.csv.

  • ROA: none1
  • Route object: RIR3
  • Route object: not announced54
ChangePrefix or setDetailFull-table peers
ROA: none103.159.20.0/24No ROA covers it. Add a ROA for AS17769, maxLength 24.673 of 673
Route object: RIR103.159.20.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.55.169.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.55.175.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 AS17769 whose prefix no peer sees AS17769 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.147.74.0/24APNICValid
103.147.75.0/24APNICValid
103.147.116.0/24APNICValid
103.147.117.0/24APNICValid
103.147.140.0/24APNICValid
103.147.141.0/24APNICValid
103.147.142.0/24APNICValid
103.147.143.0/24APNICValid
103.147.144.0/24APNICValid
103.147.145.0/24APNICValid
103.147.146.0/24APNICValid
103.147.147.0/24APNICValid
103.147.148.0/24APNICValid
103.147.164.0/24APNICValid
103.147.165.0/24APNICValid
103.158.164.0/24RADBValid
103.159.12.0/24RADBNo ROA
103.159.13.0/24RADBNo ROA
103.159.14.0/24RADBNo ROA
103.159.15.0/24RADBNo ROA
103.159.16.0/24RADBNo ROA
103.159.17.0/24RADBNo ROA
103.159.18.0/24RADBNo ROA
103.159.19.0/24RADBNo ROA
103.159.21.0/24RADBNo ROA
202.55.160.0/20NTTCOM, RADBNo ROA
202.55.160.0/21NTTCOM, RADBNo ROA
202.55.160.0/22NTTCOM, RADBNo ROA
202.55.160.0/23NTTCOM, RADBNo ROA
202.55.160.0/24NTTCOMValid
202.55.161.0/24NTTCOM, RADBValid
202.55.162.0/23NTTCOM, RADBNo ROA
202.55.162.0/24NTTCOM, RADBValid
202.55.163.0/24NTTCOMValid
202.55.164.0/22NTTCOM, RADBNo ROA
202.55.164.0/23NTTCOM, RADBNo ROA
202.55.164.0/24NTTCOM, RADBValid
202.55.165.0/24NTTCOM, RADBValid
202.55.166.0/23NTTCOMNo ROA
202.55.166.0/24NTTCOMValid
202.55.167.0/24NTTCOM, RADBValid
202.55.168.0/21NTTCOM, RADBNo ROA
202.55.168.0/22NTTCOM, RADBNo ROA
202.55.168.0/23NTTCOM, RADBNo ROA
202.55.168.0/24NTTCOM, RADBValid
202.55.170.0/23NTTCOM, RADBNo ROA
202.55.170.0/24NTTCOM, RADBValid
202.55.171.0/24NTTCOMValid
202.55.172.0/22NTTCOM, RADBNo ROA
202.55.172.0/23NTTCOM, RADBNo ROA
202.55.172.0/24NTTCOMValid
202.55.173.0/24NTTCOM, RADBValid
202.55.174.0/23NTTCOM, RADBNo ROA
202.55.174.0/24NTTCOM, RADBValid

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.