Network · data from 2026-11-12
AS45839 Shinjiru Technology
Registry name: SHINJIRU-MY-AS-AP - Shinjiru Technology Sdn Bhd, MY · PeeringDB
99IPv4 routes
96.0% RPKI valid · 99.0% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
1RPKI invalid
0 origin · 1 maxLength
3No ROA
1 with no route object for this origin
62Low visibility
seen by under 10% of full-table peers
18Route objects not announced
registered with origin AS45839, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS45839, 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.
| 111.90.151.16/32 | Invalid: maxLength | Nonecovered by 111.90.151.0/24 | 1 0%low visibility |
| 38.134.3.0/24 | No ROA | RIR databaseARIN | 669 99% |
| 38.133.213.0/24 | No ROA | RIR databaseARIN | 668 99% |
| 78.40.143.0/24 | No ROA | RIR databaseRIPE | 666 99% |
| 101.99.64.0/21 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 101.99.72.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 101.99.74.0/24 | Valid | RIR databaseAPNIC, REACH | 673 100% |
| 101.99.77.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 101.99.78.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 101.99.79.0/24 | Valid | RIR databaseAPNIC, REACH | 673 100% |
| 101.99.80.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.90.128.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 111.90.136.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 111.90.138.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 111.90.144.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 124.217.224.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 124.217.233.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 124.217.234.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 124.217.235.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 124.217.236.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 124.217.238.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 124.217.240.0/20 | Valid | RIR databaseAPNIC | 673 100% |
| 101.99.76.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 101.99.88.0/23 | Valid | RIR databaseAPNIC | 670 100% |
| 101.99.90.0/23 | Valid | RIR databaseAPNIC | 670 100% |
| 101.99.95.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 111.90.152.0/22 | Valid | RIR databaseAPNIC | 670 100% |
| 111.90.158.0/23 | Valid | RIR databaseAPNIC | 670 100% |
| 101.99.92.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 103.155.92.0/24 | Valid | RIR databaseAPNIC | 667 99% |
| 103.155.93.0/24 | Valid | RIR databaseAPNIC | 667 99% |
| 101.99.75.0/24 | Valid | RIR databaseAPNIC, REACH | 666 99% |
| 101.99.93.0/24 | Valid | RIR databaseAPNIC | 666 99% |
| 101.99.94.0/24 | Valid | RIR databaseAPNIC | 666 99% |
| 111.90.140.0/23 | Valid | RIR databaseAPNIC | 666 99% |
| 111.90.142.0/23 | Valid | RIR databaseAPNIC | 666 99% |
| 111.90.156.0/24 | Valid | RIR databaseAPNIC | 666 99% |
| 111.90.140.0/24 | Valid | RIR databaseAPNIC | 665 99% |
| 2407:6c00:18::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 101.99.64.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 101.99.65.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 101.99.66.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 101.99.67.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 101.99.68.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 101.99.69.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 101.99.70.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 101.99.71.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 101.99.72.0/24 | Valid | RIR databaseAPNIC, REACH | 35 5%low visibility |
| 101.99.73.0/24 | Valid | RIR databaseAPNIC, RADB, REACH | 35 5%low visibility |
| 101.99.80.0/24 | Valid | RIR databaseAPNIC, REACH | 35 5%low visibility |
| 101.99.81.0/24 | Valid | RIR databaseAPNIC | 35 5%low visibility |
| 101.99.84.0/24 | Valid | RIR databaseAPNIC | 35 5%low visibility |
| 101.99.86.0/24 | Valid | RIR databaseAPNIC, REACH | 35 5%low visibility |
| 101.99.87.0/24 | Valid | RIR databaseAPNIC, REACH | 35 5%low visibility |
| 111.90.129.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 111.90.130.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 111.90.131.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 111.90.132.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 111.90.133.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 111.90.134.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 111.90.135.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 111.90.138.0/24 | Valid | RIR databaseAPNIC | 35 5%low visibility |
| 111.90.139.0/24 | Valid | RIR databaseAPNIC | 35 5%low visibility |
| 124.217.224.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.225.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.226.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.227.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.228.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.229.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.230.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.231.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.236.0/24 | Valid | RIR databaseAPNIC | 35 5%low visibility |
| 124.217.237.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 35 5%low visibility |
| 124.217.240.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.241.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.242.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.243.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.244.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.245.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.246.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.247.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.248.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.249.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.250.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.251.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.252.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.253.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.254.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 124.217.255.0/24 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 101.99.82.0/24 | Valid | RIR databaseAPNIC | 34 5%low visibility |
| 101.99.85.0/24 | Valid | RIR databaseAPNIC, REACH | 34 5%low visibility |
| 101.99.88.0/24 | Valid | RIR databaseAPNIC | 34 5%low visibility |
| 111.90.152.0/24 | Valid | RIR databaseAPNIC, RADB | 34 5%low visibility |
| 111.90.153.0/24 | Valid | RIR databaseAPNIC, RADB | 34 5%low visibility |
| 111.90.154.0/24 | Valid | RIR databaseAPNIC, RADB | 34 5%low visibility |
| 111.90.155.0/24 | Valid | RIR databaseAPNIC, RADB | 34 5%low visibility |
| 111.90.158.0/24 | Valid | RIR databaseAPNIC | 34 5%low visibility |
| 111.90.159.0/24 | Valid | RIR databaseAPNIC | 34 5%low visibility |
| 111.90.151.0/24 | Valid | RIR databaseAPNIC, RADB | 2 0%low visibility |
| 111.90.150.0/24 | Valid | RIR databaseAPNIC, RADB | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS45839: AS45839:AS-SHINJIRU. 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 (AS45839 isn't in the set, or no route object for AS45839 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 | AS45839 in it | Not covered |
|---|---|---|---|---|---|
| AS45839:AS-SHINJIRU | APNIC | 1 | 1 | Yes | 1 |
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.
- ROA: maxLength1
- ROA: none3
- Route object: none1
- Route object: not announced18
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 111.90.151.16/32 | ROA 111.90.144.0/21 AS45839 has maxLength 21; ROA 111.90.151.0/24 AS45839 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 111.90.151.16/32. |
| Route object: none | 111.90.151.16/32 | No route object for it. A route object for 111.90.151.0/24 with origin AS45839 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45839 in the RIR database for the space. |
| ROA: none | 38.134.3.0/24 | No ROA covers it. Add a ROA for AS45839, maxLength 24. |
| ROA: none | 38.133.213.0/24 | No ROA covers it. Add a ROA for AS45839, maxLength 24. |
| ROA: none | 78.40.143.0/24 | No ROA covers it. Add a ROA for AS45839, maxLength 24. |
Route objects not announced
Route objects with origin AS45839 whose prefix no peer sees AS45839 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 101.99.83.0/24 | APNIC | Valid |
| 101.99.89.0/24 | APNIC | Valid |
| 101.99.90.0/24 | APNIC | Valid |
| 101.99.91.0/24 | APNIC | Valid |
| 111.90.128.0/24 | APNIC, RADB | Valid |
| 111.90.136.0/24 | APNIC | Valid |
| 111.90.137.0/24 | APNIC | Valid |
| 111.90.141.0/24 | APNIC | Valid |
| 111.90.142.0/24 | APNIC | Valid |
| 111.90.143.0/24 | APNIC | Valid |
| 111.90.144.0/24 | APNIC, RADB | Valid |
| 111.90.145.0/24 | APNIC, RADB | Valid |
| 111.90.146.0/24 | APNIC, RADB | Valid |
| 111.90.147.0/24 | APNIC, RADB | Valid |
| 111.90.148.0/24 | APNIC, RADB | Valid |
| 111.90.149.0/24 | APNIC, RADB | Valid |
| 124.217.232.0/24 | APNIC, NTTCOM, RADB | Valid |
| 124.217.239.0/24 | APNIC, NTTCOM | Valid |
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.