bgpreport

Network · data from 2026-11-12

AS24210 Angkasa Sarana Teknik Komunikasi PT

Registry name: ANGKASAWAVE-AS-ID - Angkasa Sarana Teknik Komunikasi PT, ID · PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
23Route objects not announced registered with origin AS24210, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS24210, 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.

180.150.233.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
202.173.16.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
202.173.17.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.173.18.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
202.173.19.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
202.173.20.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.173.21.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.173.22.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69

AS-SET

AS24210'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 23 are in fix.csv.

  • Route object: not announced23

Route objects not announced

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

180.150.232.0/21NTTCOMValid
180.150.232.0/22NTTCOMValid
180.150.232.0/23NTTCOMValid
180.150.232.0/24APNIC, NTTCOM, RADBValid
180.150.234.0/23NTTCOMValid
180.150.234.0/24APNIC, NTTCOMValid
180.150.235.0/24APNIC, NTTCOMValid
180.150.236.0/22NTTCOMValid
180.150.236.0/23NTTCOMValid
180.150.236.0/24APNIC, NTTCOMValid
180.150.237.0/24APNIC, NTTCOMValid
180.150.238.0/23NTTCOMValid
180.150.238.0/24APNICValid
180.150.239.0/24APNIC, NTTCOMValid
202.173.16.0/20NTTCOMNo ROA
202.173.16.0/21NTTCOM, RADBValid
202.173.16.0/22NTTCOMValid
202.173.16.0/23NTTCOMValid
202.173.18.0/23NTTCOMValid
202.173.20.0/22NTTCOMValid
202.173.20.0/23NTTCOMValid
202.173.22.0/23NTTCOMValid
202.173.23.0/24APNIC, NTTCOM, 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.