bgpreport

Network · data from 2026-11-12

AS56241 Telkom Satelit Indonesia

Registry name: TELKOMSAT-AS-ID - PT Telkom Satelit Indonesia, ID · PeeringDB

17IPv4 routes 88.2% RPKI valid · 82.4% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
2No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
48Route objects not announced registered with origin AS56241, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS56241, 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.99.98.0/24 No ROA Other origin only 670 100% 68
203.99.99.0/24 No ROA Other origin only 670 100% 68
203.99.96.0/24 Valid None 671 100% 67
45.126.155.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 69
103.10.56.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 69
103.10.145.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 69
103.37.226.0/24 Valid Other IRR onlyNTTCOM 671 100% 69
103.37.227.0/24 Valid Other IRR onlyNTTCOM 671 100% 70
103.85.221.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 69
103.85.222.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 69
103.85.223.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 69
103.86.144.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 69
103.86.145.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 69
103.255.52.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 69
103.255.53.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 69
203.99.103.0/24 Valid Other IRR onlyRADB 671 100% 67
203.99.112.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 67

AS-SET

PeeringDB's irr_as_set for AS56241: AS56241:AS-TELKOMSAT56241. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS56241 isn't in the set, or no route object for AS56241 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS56241 in itNot covered
AS56241:AS-TELKOMSAT56241 In no IRR database read today.

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

  • ROA: none2
  • Route object: none3
  • Route object: RIR14
  • AS-SET: not found1
  • Route object: not announced48
ChangePrefix or setDetailFull-table peers
ROA: none203.99.98.0/24No ROA covers it. Add a ROA for AS56241, maxLength 24.670 of 673
Route object: none203.99.98.0/24Route objects for it name AS10137, AS46031. Add a route object with origin AS56241 in the RIR database for the space.670 of 673
ROA: none203.99.99.0/24No ROA covers it. Add a ROA for AS56241, maxLength 24.670 of 673
Route object: none203.99.99.0/24Route objects for it name AS10137, AS46031. Add a route object with origin AS56241 in the RIR database for the space.670 of 673
Route object: none203.99.96.0/24No route object for it. Add a route object with origin AS56241 in the RIR database for the space.671 of 673
Route object: RIR45.126.155.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.10.56.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.10.145.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.37.226.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR103.37.227.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR103.85.221.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.85.222.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.85.223.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.86.144.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.86.145.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.255.52.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.255.53.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR203.99.103.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR203.99.112.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
AS-SET: not foundAS56241:AS-TELKOMSAT56241PeeringDB names AS56241:AS-TELKOMSAT56241; no IRR database read has it.

Route objects not announced

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

45.126.152.0/24NTTCOM, RADBValid
45.126.153.0/24NTTCOM, RADBValid
103.37.224.0/22NTTCOMNo ROA
103.37.224.0/24NTTCOM, RADBValid
103.37.225.0/24NTTCOM, RADBValid
103.85.220.0/24NTTCOM, RADBNo ROA
103.86.146.0/24RADBNo ROA
103.86.147.0/24RADBNo ROA
103.92.36.0/24RADBNo ROA
103.92.37.0/24RADBNo ROA
103.92.38.0/24RADBNo ROA
103.92.39.0/24RADBNo ROA
103.93.184.0/24RADBNo ROA
103.93.185.0/24RADBNo ROA
103.93.186.0/24RADBNo ROA
103.93.187.0/24RADBNo ROA
103.147.64.0/24RADBNo ROA
103.147.65.0/24RADBNo ROA
103.147.66.0/24RADBNo ROA
103.147.67.0/24RADBNo ROA
103.163.82.0/24RADBNo ROA
103.163.83.0/24RADBNo ROA
103.163.84.0/24RADBNo ROA
103.163.85.0/24RADBNo ROA
103.163.86.0/24RADBNo ROA
103.163.87.0/24RADBNo ROA
103.163.88.0/24RADBNo ROA
103.163.89.0/24RADBNo ROA
123.253.128.0/23RADBNo ROA
202.125.100.0/24NTTCOM, RADBNo ROA
202.125.101.0/24NTTCOM, RADBNo ROA
203.99.101.0/24RADBValid
203.99.105.0/24RADBNo ROA
203.99.106.0/24RADBNo ROA
203.99.107.0/24RADBNo ROA
203.99.112.0/23RADBNo ROA
203.99.113.0/24RADBNo ROA
203.99.114.0/24RADBNo ROA
203.99.115.0/24RADBNo ROA
203.99.116.0/24NTTCOM, RADBNo ROA
203.99.117.0/24NTTCOM, RADBNo ROA
203.99.118.0/24NTTCOM, RADBNo ROA
203.99.119.0/24RADBNo ROA
203.99.120.0/24RADBNo ROA
203.99.121.0/24NTTCOM, RADBNo ROA
203.99.122.0/24RADBNo ROA
203.99.124.0/24RADBNo ROA
203.99.127.0/24RADBNo 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.