bgpreport

Network · data from 2026-11-12

AS24204 Satnetcom Balikpapan

Registry name: SATNETCOM-AS-ID - Satnetcom Balikpapan PT., ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24204, 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.
203.80.8.0/24 Valid Nonecovered by 203.80.8.0/23 673 100% 69
203.80.9.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
203.80.10.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
203.80.11.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
203.80.12.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
203.80.13.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
203.80.14.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
203.80.15.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
2405:8e00::/32 Valid Other IRR onlyRADB 635 100% 67

AS-SET

AS24204'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 16 are in fix.csv.

  • Route object: none1
  • Route object: RIR8
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: none203.80.8.0/24No route object for it. A route object for 203.80.8.0/23 with origin AS24204 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24204 in the RIR database for the space.673 of 673
Route object: RIR203.80.9.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR203.80.10.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR203.80.11.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR203.80.12.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR203.80.13.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR203.80.14.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR203.80.15.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2405:8e00::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

203.80.8.0/21APNIC, NTTCOM, RADBNo ROA
203.80.8.0/22NTTCOM, RADBNo ROA
203.80.8.0/23NTTCOM, RADBNo ROA
203.80.10.0/23NTTCOM, RADBNo ROA
203.80.12.0/22NTTCOM, RADBNo ROA
203.80.12.0/23NTTCOM, RADBNo ROA
203.80.14.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.