Network · data from 2026-11-12
AS205111 ZOHO-EU ZOHO Corporation B.V
Registry name: ZOHO-EU ZOHO Corporation B.V, NL · not in PeeringDB
41IPv4 routes
85.4% RPKI valid · 85.4% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
6No ROA
6 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
22Route objects not announced
registered with origin AS205111, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS205111, 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.
| 199.67.80.0/23 | No ROA | Other origin only | 672 100% |
| 199.67.82.0/23 | No ROA | Other origin only | 672 100% |
| 199.67.80.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 199.67.81.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 199.67.82.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 199.67.83.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.230.212.0/23 | Valid | Other origin only | 673 100% |
| 185.230.214.0/23 | Valid | Other origin only | 673 100% |
| 199.67.72.0/23 | Valid | None | 673 100% |
| 199.67.74.0/23 | Valid | None | 673 100% |
| 91.103.153.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.103.155.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.31.54.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 136.143.170.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 136.143.171.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 144.89.64.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 144.89.66.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 144.89.68.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 144.89.69.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 144.89.70.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 144.89.78.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 169.148.130.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 169.148.131.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.230.213.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.230.215.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 199.67.74.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 199.67.75.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 199.67.88.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 199.67.90.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 213.161.74.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 91.103.152.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.103.154.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 136.143.168.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 136.143.169.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 169.148.188.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 169.148.189.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 169.148.128.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 169.148.129.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 199.67.90.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 144.89.68.0/23 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 185.230.214.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS205111 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 34 are in fix.csv.
- ROA: none6
- Route object: none6
- Route object: not announced22
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.67.80.0/23 | No ROA covers it. Add a ROA for AS205111, maxLength 23. |
| Route object: none | 199.67.80.0/23 | Route objects for it name AS2639. Add a route object with origin AS205111 in the RIR database for the space. |
| ROA: none | 199.67.82.0/23 | No ROA covers it. Add a ROA for AS205111, maxLength 23. |
| Route object: none | 199.67.82.0/23 | Route objects for it name AS2639. Add a route object with origin AS205111 in the RIR database for the space. |
| ROA: none | 199.67.80.0/24 | No ROA covers it. Add a ROA for AS205111, maxLength 24. |
| ROA: none | 199.67.81.0/24 | No ROA covers it. Add a ROA for AS205111, maxLength 24. |
| ROA: none | 199.67.82.0/24 | No ROA covers it. Add a ROA for AS205111, maxLength 24. |
| ROA: none | 199.67.83.0/24 | No ROA covers it. Add a ROA for AS205111, maxLength 24. |
| Route object: none | 185.230.212.0/23 | Route objects for it name AS41913. Add a route object with origin AS205111 in the RIR database for the space. |
| Route object: none | 185.230.214.0/23 | Route objects for it name AS41913. Add a route object with origin AS205111 in the RIR database for the space. |
| Route object: none | 199.67.72.0/23 | No route object for it. Add a route object with origin AS205111 in the RIR database for the space. |
| Route object: none | 199.67.74.0/23 | No route object for it. Add a route object with origin AS205111 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS205111 whose prefix no peer sees AS205111 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.103.152.0/21 | RIPE | No ROA |
| 94.31.62.0/24 | RIPE | Invalid: origin |
| 136.143.172.0/24 | ARIN, RADB | Valid |
| 136.143.173.0/24 | ARIN, RADB | Valid |
| 144.89.74.0/23 | RIPE | No ROA |
| 144.89.76.0/23 | RIPE | No ROA |
| 169.148.151.0/24 | ARIN, RADB | Valid |
| 169.148.152.0/23 | ARIN | Valid |
| 169.148.152.0/24 | ARIN | Valid |
| 169.148.153.0/24 | RADB | Valid |
| 169.148.162.0/24 | ARIN | Valid |
| 169.148.188.0/23 | RADB, RIPE | No ROA |
| 185.230.212.0/24 | RIPE | Valid |
| 199.67.72.0/24 | RIPE | Invalid: maxLength |
| 199.67.73.0/24 | RIPE | Invalid: maxLength |
| 199.67.88.0/24 | RIPE | Valid |
| 199.67.89.0/24 | RIPE | Valid |
| 199.67.91.0/24 | RIPE | Valid |
| 2602:801:c00a::/48 | ARIN, RADB | Valid |
| 2602:801:c00b::/48 | ARIN, RADB | Valid |
| 2602:801:c00c::/48 | ARIN, RADB | Valid |
| 2602:801:c00d::/48 | ARIN, RADB | No 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.