bgpreport

Network · data from 2026-11-12

AS7543 PT Reach Network Services Indonesia (Telstra International)

Registry name: PRNSI-AS-AP - PT Reach Network Services Indonesia, ID · PeeringDB

10IPv4 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
33Route objects not announced registered with origin AS7543, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS7543, 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.47.192.0/24 Valid RIR databaseAPNIC 673 100% 68
202.47.195.0/24 Valid RIR databaseAPNIC 673 100% 68
202.47.196.0/24 Valid RIR databaseAPNIC 673 100% 68
202.47.201.0/24 Valid RIR databaseAPNIC 673 100% 68
202.47.202.0/24 Valid RIR databaseAPNIC 673 100% 68
202.47.203.0/24 Valid RIR databaseAPNIC 673 100% 68
210.176.128.0/24 Valid RIR databaseAPNIC 672 100% 68
202.47.204.0/24 Valid RIR databaseAPNIC 156 23% 48
210.176.142.0/24 Valid RIR databaseAPNIC 156 23% 48
210.57.8.0/22 Valid RIR databaseAPNIC 151 22% 48

AS-SET

PeeringDB's irr_as_set for AS7543: APNIC::AS7543:AS-PTREACH. 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 (AS7543 isn't in the set, or no route object for AS7543 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 objectsAS7543 in itNot covered
APNIC::AS7543:AS-PTREACH APNIC 1243 Yes 0

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

  • Route object: not announced33

Route objects not announced

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

27.100.0.0/22RADBNo ROA
61.8.0.0/18RADBNo ROA
103.10.50.0/24RADBNo ROA
103.24.240.0/22RADBNo ROA
103.248.44.0/22RADBNo ROA
103.249.68.0/24RADBNo ROA
115.124.32.0/21RADBNo ROA
122.200.24.0/24RADBNo ROA
192.68.171.0/24RADBNo ROA
192.189.208.0/22RADBNo ROA
192.189.208.0/23RADBNo ROA
203.3.165.0/24RADBNo ROA
203.7.148.0/23RADBNo ROA
203.10.35.0/24RADBNo ROA
203.10.54.0/23RADBNo ROA
203.12.60.0/22RADBNo ROA
203.14.40.0/21RADBNo ROA
203.14.40.0/22RADBNo ROA
203.14.44.0/23RADBNo ROA
203.19.92.0/23RADBNo ROA
203.30.157.0/24RADBNo ROA
203.31.166.0/24RADBNo ROA
203.34.78.0/23RADBNo ROA
203.55.84.0/24RADBNo ROA
203.56.136.0/22RADBNo ROA
210.57.8.0/23APNICValid
210.57.8.0/24APNICValid
210.57.9.0/24APNICValid
210.57.10.0/23APNICValid
210.57.10.0/24APNICValid
210.57.11.0/24APNICValid
2001:e28::/32RADBNo ROA
2403:e800:b00::/40APNICValid

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.