Network · data from 2026-11-12
AS138823 Trimitra Usaha Sejahtera
Registry name: TUSNETWORK-AS-ID - PT. Trimitra Usaha Sejahtera, ID · PeeringDB
16IPv4 routes
75.0% RPKI valid · 68.8% with a route object
14IPv6 routes
85.7% RPKI valid · 7.1% with a route object
3RPKI invalid
1 origin · 2 maxLength
3No ROA
18 with no route object for this origin
15Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS138823, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS138823, 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.
| 13.123.123.0/24 | Invalid: origin | None | 2 0%low visibility |
| 2405:c9c0:28:ffff::/64 | Invalid: maxLength | Nonecovered by 2405:c9c0::/32 | 7 1%low visibility |
| 2405:c9c0:29:ffff::/64 | Invalid: maxLength | Nonecovered by 2405:c9c0::/32 | 7 1%low visibility |
| 202.73.105.0/24 | No ROA | Other origin onlycovered by 202.73.104.0/22 | 672 100% |
| 138.82.3.0/24 | No ROA | None | 35 5%low visibility |
| 202.73.104.0/22 | No ROA | Other IRR onlyRADB | 37 5%low visibility |
| 203.161.26.0/23 | Valid | Nonecovered by 203.161.24.0/22 | 673 100% |
| 2405:c9c0:29::/48 | Valid | Nonecovered by 2405:c9c0::/32 | 636 100% |
| 2405:c9c0:290::/48 | Valid | Nonecovered by 2405:c9c0::/32 | 636 100% |
| 2405:c9c0:294::/48 | Valid | Nonecovered by 2405:c9c0::/32 | 636 100% |
| 2405:c9c0:2900::/40 | Valid | Nonecovered by 2405:c9c0::/32 | 636 100% |
| 2405:c9c0::/33 | Valid | Nonecovered by 2405:c9c0::/32 | 635 100% |
| 2405:c9c0:8000::/33 | Valid | Nonecovered by 2405:c9c0::/32 | 635 100% |
| 203.161.24.0/23 | Valid | Nonecovered by 203.161.24.0/22 | 35 5%low visibility |
| 2405:c9c0:138::/48 | Valid | Nonecovered by 2405:c9c0::/32 | 3 0%low visibility |
| 2405:c9c0:1388::/48 | Valid | Nonecovered by 2405:c9c0::/32 | 3 0%low visibility |
| 2405:c9c0:4000::/34 | Valid | Nonecovered by 2405:c9c0::/32 | 2 0%low visibility |
| 2405:c9c0:c000::/34 | Valid | Nonecovered by 2405:c9c0::/32 | 2 0%low visibility |
| 2405:c9c0:f000::/36 | Valid | Nonecovered by 2405:c9c0::/32 | 2 0%low visibility |
| 203.161.29.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.161.24.0/21 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.161.24.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 203.161.28.0/22 | Valid | RIR databaseAPNIC | 671 100% |
| 203.161.28.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 203.161.30.0/23 | Valid | RIR databaseAPNIC | 670 100% |
| 2405:c9c0::/32 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 203.161.24.0/24 | Valid | RIR databaseAPNIC | 35 5%low visibility |
| 203.161.25.0/24 | Valid | RIR databaseAPNIC | 35 5%low visibility |
| 203.161.26.0/24 | Valid | RIR databaseAPNIC | 35 5%low visibility |
| 203.161.27.0/24 | Valid | RIR databaseAPNIC | 35 5%low visibility |
AS-SET
PeeringDB's irr_as_set for AS138823: AS138823:AS-CLIENT. 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 (AS138823 isn't in the set, or no route object for AS138823 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.
| Name | Database | ASNs | Sets | AS138823 in it | Not covered |
|---|---|---|---|---|---|
| AS138823:AS-CLIENT | APNIC | 5 | 1 | Yes | 4 |
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 25 are in fix.csv.
- ROA: origin1
- ROA: maxLength2
- ROA: none3
- Route object: none18
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 13.123.123.0/24 | ROAs covering it name AS8075, not AS138823. If AS138823 should announce it, add a ROA for AS138823. |
| Route object: none | 13.123.123.0/24 | No route object for it. Add a route object with origin AS138823 in the RIR database for the space. |
| ROA: maxLength | 2405:c9c0:28:ffff::/64 | ROA 2405:c9c0::/32 AS138823 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2405:c9c0:28:ffff::/64. |
| Route object: none | 2405:c9c0:28:ffff::/64 | No route object for it. A route object for 2405:c9c0::/32 with origin AS138823 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS138823 in the RIR database for the space. |
| ROA: maxLength | 2405:c9c0:29:ffff::/64 | ROA 2405:c9c0::/32 AS138823 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2405:c9c0:29:ffff::/64. |
| Route object: none | 2405:c9c0:29:ffff::/64 | No route object for it. A route object for 2405:c9c0::/32 with origin AS138823 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS138823 in the RIR database for the space. |
| ROA: none | 202.73.105.0/24 | No ROA covers it. Add a ROA for AS138823, maxLength 24. |
| Route object: none | 202.73.105.0/24 | Route objects for it name AS9326, AS17884. A route object for 202.73.104.0/22 with origin AS138823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138823 in the RIR database for the space. |
| ROA: none | 138.82.3.0/24 | No ROA covers it. Add a ROA for AS138823, maxLength 24. |
| Route object: none | 138.82.3.0/24 | No route object for it. Add a route object with origin AS138823 in the RIR database for the space. |
| ROA: none | 202.73.104.0/22 | No ROA covers it. Add a ROA for AS138823, maxLength 22. |
| Route object: RIR | 202.73.104.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 203.161.26.0/23 | No route object for it. A route object for 203.161.24.0/22 with origin AS138823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138823 in the RIR database for the space. |
| Route object: none | 2405:c9c0:29::/48 | No route object for it. A route object for 2405:c9c0::/32 with origin AS138823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138823 in the RIR database for the space. |
| Route object: none | 2405:c9c0:290::/48 | No route object for it. A route object for 2405:c9c0::/32 with origin AS138823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138823 in the RIR database for the space. |
| Route object: none | 2405:c9c0:294::/48 | No route object for it. A route object for 2405:c9c0::/32 with origin AS138823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138823 in the RIR database for the space. |
| Route object: none | 2405:c9c0:2900::/40 | No route object for it. A route object for 2405:c9c0::/32 with origin AS138823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138823 in the RIR database for the space. |
| Route object: none | 2405:c9c0::/33 | No route object for it. A route object for 2405:c9c0::/32 with origin AS138823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138823 in the RIR database for the space. |
| Route object: none | 2405:c9c0:8000::/33 | No route object for it. A route object for 2405:c9c0::/32 with origin AS138823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138823 in the RIR database for the space. |
| Route object: none | 203.161.24.0/23 | No route object for it. A route object for 203.161.24.0/22 with origin AS138823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138823 in the RIR database for the space. |
| Route object: none | 2405:c9c0:138::/48 | No route object for it. A route object for 2405:c9c0::/32 with origin AS138823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138823 in the RIR database for the space. |
| Route object: none | 2405:c9c0:1388::/48 | No route object for it. A route object for 2405:c9c0::/32 with origin AS138823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138823 in the RIR database for the space. |
| Route object: none | 2405:c9c0:4000::/34 | No route object for it. A route object for 2405:c9c0::/32 with origin AS138823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138823 in the RIR database for the space. |
| Route object: none | 2405:c9c0:c000::/34 | No route object for it. A route object for 2405:c9c0::/32 with origin AS138823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138823 in the RIR database for the space. |
| Route object: none | 2405:c9c0:f000::/36 | No route object for it. A route object for 2405:c9c0::/32 with origin AS138823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138823 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS138823 is announced.
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.