Network · data from 2026-11-12
AS139006 ZCPL-AS-AP - Zoho Corporation PTY LTD
Registry name: ZCPL-AS-AP - Zoho Corporation PTY LTD, AU · not in PeeringDB
10IPv4 routes
80.0% RPKI valid · 100.0% with a route object
6IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
2No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
112Route objects not announced
registered with origin AS139006, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS139006, 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.
| 169.148.168.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 169.148.170.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
| 103.91.166.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 101.97.36.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 199.67.70.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.138.128.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.138.129.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 165.173.160.0/23 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 165.173.190.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 165.173.191.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 2400:5a20:4::/47 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:5a20:6::/47 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:5a20:a::/47 | Valid | RIR databaseAPNIC, RADB | 636 100% |
| 2602:801:c00a::/48 | Valid | RIR databaseARIN, NTTCOM, RADB | 75 12% |
| 2602:801:c00b::/48 | Valid | RIR databaseARIN, NTTCOM, RADB | 75 12% |
| 2602:801:c00c::/48 | Valid | RIR databaseARIN, NTTCOM, RADB | 75 12% |
AS-SET
AS139006 isn't in PeeringDB, where networks name their 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 118 are in fix.csv.
- ROA: none2
- Route object: RIR4
- Route object: not announced112
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 169.148.168.0/23 | No ROA covers it. Add a ROA for AS139006, maxLength 23. |
| Route object: RIR | 169.148.168.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 169.148.170.0/23 | No ROA covers it. Add a ROA for AS139006, maxLength 23. |
| Route object: RIR | 169.148.170.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.91.166.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 101.97.36.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS139006 whose prefix no peer sees AS139006 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.228.216.0/22 | NTTCOM | No ROA |
| 43.231.0.0/24 | NTTCOM | No ROA |
| 45.115.36.0/24 | NTTCOM | No ROA |
| 45.115.38.0/24 | NTTCOM | No ROA |
| 45.115.39.0/24 | NTTCOM | No ROA |
| 45.125.160.0/22 | NTTCOM | No ROA |
| 103.15.132.0/24 | NTTCOM | No ROA |
| 103.15.135.0/24 | NTTCOM | No ROA |
| 103.15.216.0/24 | NTTCOM | No ROA |
| 103.15.217.0/24 | NTTCOM | No ROA |
| 103.15.218.0/24 | NTTCOM | No ROA |
| 103.20.60.0/24 | NTTCOM | No ROA |
| 103.20.61.0/24 | NTTCOM | No ROA |
| 103.20.63.0/24 | NTTCOM | No ROA |
| 103.30.16.0/22 | NTTCOM | No ROA |
| 103.68.60.0/24 | NTTCOM | No ROA |
| 103.68.61.0/24 | NTTCOM | No ROA |
| 103.68.62.0/24 | NTTCOM | No ROA |
| 103.68.63.0/24 | NTTCOM | No ROA |
| 103.138.128.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.194.36.0/22 | NTTCOM | No ROA |
| 103.211.32.0/22 | NTTCOM | No ROA |
| 103.230.12.0/22 | NTTCOM | No ROA |
| 103.251.112.0/24 | NTTCOM | No ROA |
| 103.251.113.0/24 | NTTCOM | No ROA |
| 103.254.208.0/24 | NTTCOM | No ROA |
| 103.254.209.0/24 | NTTCOM | No ROA |
| 103.254.210.0/24 | NTTCOM | No ROA |
| 103.254.211.0/24 | NTTCOM | No ROA |
| 113.52.132.0/24 | NTTCOM | No ROA |
| 113.52.133.0/24 | NTTCOM | No ROA |
| 113.52.134.0/24 | NTTCOM | No ROA |
| 113.52.135.0/24 | NTTCOM | No ROA |
| 122.128.104.0/22 | NTTCOM | No ROA |
| 122.128.105.0/24 | NTTCOM | No ROA |
| 122.128.106.0/24 | NTTCOM | No ROA |
| 122.128.107.0/24 | NTTCOM | No ROA |
| 122.128.108.0/24 | NTTCOM | No ROA |
| 122.128.109.0/24 | NTTCOM | No ROA |
| 122.128.110.0/24 | NTTCOM | No ROA |
| 122.128.111.0/24 | NTTCOM | No ROA |
| 123.176.96.0/24 | NTTCOM | No ROA |
| 123.176.98.0/24 | NTTCOM | No ROA |
| 123.176.99.0/24 | NTTCOM | No ROA |
| 123.176.100.0/24 | NTTCOM | No ROA |
| 123.176.101.0/24 | NTTCOM | No ROA |
| 123.176.102.0/24 | NTTCOM | No ROA |
| 123.176.103.0/24 | NTTCOM | No ROA |
| 136.143.172.0/23 | RADB | No ROA |
| 136.143.172.0/24 | ARIN, NTTCOM, RADB | Valid |
| 136.143.173.0/24 | ARIN, NTTCOM, RADB | Valid |
| 146.196.52.0/24 | NTTCOM | No ROA |
| 146.196.53.0/24 | NTTCOM | No ROA |
| 146.196.54.0/24 | NTTCOM | No ROA |
| 146.196.55.0/24 | NTTCOM | No ROA |
| 165.173.160.0/22 | APNIC, NTTCOM, RADB | Valid |
| 165.173.160.0/24 | APNIC, NTTCOM | Valid |
| 165.173.161.0/24 | APNIC, NTTCOM | Valid |
| 165.173.162.0/23 | APNIC, NTTCOM | Valid |
| 165.173.162.0/24 | APNIC, NTTCOM | Valid |
| 165.173.163.0/24 | APNIC, NTTCOM | Valid |
| 169.148.151.0/24 | ARIN, NTTCOM, RADB | Valid |
| 169.148.152.0/23 | ARIN, NTTCOM, RADB | Valid |
| 169.148.152.0/24 | ARIN, NTTCOM, RADB | Valid |
| 169.148.153.0/24 | NTTCOM, RADB | Valid |
| 169.148.168.0/24 | RADB | No ROA |
| 169.148.169.0/24 | RADB | No ROA |
| 169.148.170.0/24 | RADB | No ROA |
| 169.148.171.0/24 | RADB | No ROA |
| 180.188.196.0/24 | NTTCOM | No ROA |
| 180.188.197.0/24 | NTTCOM | No ROA |
| 180.188.198.0/24 | NTTCOM | No ROA |
| 203.86.232.0/24 | NTTCOM | No ROA |
| 203.86.233.0/24 | NTTCOM | No ROA |
| 203.86.235.0/24 | NTTCOM | No ROA |
| 203.86.236.0/24 | NTTCOM | No ROA |
| 203.86.237.0/24 | NTTCOM | No ROA |
| 203.86.238.0/24 | NTTCOM | No ROA |
| 203.86.239.0/24 | NTTCOM | No ROA |
| 223.223.216.0/24 | NTTCOM | No ROA |
| 223.223.217.0/24 | NTTCOM | No ROA |
| 223.223.218.0/24 | NTTCOM | No ROA |
| 223.223.219.0/24 | NTTCOM | No ROA |
| 2001:df0:3c80::/48 | NTTCOM, RADB | No ROA |
| 2001:df0:3c80:1::/64 | NTTCOM | No ROA |
| 2400:5a20::/45 | APNIC, NTTCOM, RADB | Valid |
| 2400:5a20::/46 | APNIC | Valid |
| 2400:5a20::/47 | APNIC | Valid |
| 2400:5a20::/48 | APNIC | Valid |
| 2400:5a20:1::/48 | APNIC, RADB | Valid |
| 2400:5a20:2::/47 | APNIC | Valid |
| 2400:5a20:2::/48 | APNIC, RADB | Valid |
| 2400:5a20:3::/48 | APNIC | Valid |
| 2400:5a20:4::/46 | APNIC | Valid |
| 2400:5a20:4::/48 | APNIC | Valid |
| 2400:5a20:5::/48 | APNIC | Valid |
| 2400:5a20:6::/48 | APNIC | Valid |
| 2400:5a20:7::/48 | APNIC | Valid |
| 2400:5a20:8::/45 | APNIC, NTTCOM, RADB | Valid |
| 2400:5a20:8::/46 | APNIC | Valid |
| 2400:5a20:8::/47 | APNIC | Valid |
| 2400:5a20:8::/48 | APNIC | Valid |
| 2400:5a20:9::/48 | APNIC | Valid |
| 2400:5a20:a::/48 | APNIC | Valid |
| 2400:5a20:b::/48 | APNIC | Valid |
| 2400:5a20:c::/46 | APNIC | Valid |
| 2400:5a20:c::/47 | APNIC, RADB | Valid |
| 2400:5a20:c::/48 | APNIC | Valid |
| 2400:5a20:d::/48 | APNIC | Valid |
| 2400:5a20:e::/47 | APNIC, RADB | Valid |
| 2400:5a20:e::/48 | APNIC | Valid |
| 2400:5a20:f::/48 | APNIC | 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.