bgpreport

Network · data from 2026-11-12

AS45710 CHOICENET-AS-ID - Yudhawira Khatulistiwa, PT

Registry name: CHOICENET-AS-ID - Yudhawira Khatulistiwa, PT, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45710, 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.75.96.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.75.97.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.75.98.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.75.99.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.75.100.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.75.101.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.75.102.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.75.103.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.75.104.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.75.105.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.75.106.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.75.107.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.75.108.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.75.109.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.75.110.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.75.111.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69

AS-SET

AS45710 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 41 are in fix.csv.

  • ROA: none16
  • Route object: not announced25
ChangePrefix or setDetailFull-table peers
ROA: none202.75.96.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673
ROA: none202.75.97.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673
ROA: none202.75.98.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673
ROA: none202.75.99.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673
ROA: none202.75.100.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673
ROA: none202.75.101.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673
ROA: none202.75.102.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673
ROA: none202.75.103.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673
ROA: none202.75.104.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673
ROA: none202.75.105.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673
ROA: none202.75.106.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673
ROA: none202.75.107.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673
ROA: none202.75.108.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673
ROA: none202.75.109.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673
ROA: none202.75.110.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673
ROA: none202.75.111.0/24No ROA covers it. Add a ROA for AS45710, maxLength 24.672 of 673

Route objects not announced

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

103.8.244.0/22NTTCOMNo ROA
103.8.244.0/23NTTCOMNo ROA
103.8.244.0/24NTTCOMNo ROA
103.8.245.0/24NTTCOMNo ROA
103.8.246.0/23NTTCOMNo ROA
103.8.246.0/24NTTCOMNo ROA
103.8.247.0/24NTTCOMNo ROA
103.195.158.0/23NTTCOM, RADBNo ROA
103.195.158.0/24NTTCOM, RADBNo ROA
103.195.159.0/24NTTCOM, RADBNo ROA
202.75.96.0/20APNIC, NTTCOM, RADBNo ROA
202.75.96.0/21NTTCOM, RADBNo ROA
202.75.96.0/22NTTCOMNo ROA
202.75.96.0/23NTTCOM, RADBNo ROA
202.75.98.0/23NTTCOM, RADBNo ROA
202.75.100.0/22NTTCOM, RADBNo ROA
202.75.100.0/23NTTCOM, RADBNo ROA
202.75.102.0/23NTTCOM, RADBNo ROA
202.75.104.0/21NTTCOM, RADBNo ROA
202.75.104.0/22NTTCOM, RADBNo ROA
202.75.104.0/23NTTCOM, RADBNo ROA
202.75.106.0/23NTTCOM, RADBNo ROA
202.75.108.0/22NTTCOM, RADBNo ROA
202.75.108.0/23NTTCOM, RADBNo ROA
202.75.110.0/23NTTCOM, 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.