If Zoho is loading slowly or feeling unresponsive, the cause is not always straightforward. Performance can be affected by the application itself, your network infrastructure, your browser, or local device settings. This guide walks you through the checks and diagnostic steps that will help identify the root cause and get the issue resolved as quickly as possible.

Step 1: Check Zoho's System Status

Before investigating your own setup, confirm whether Zoho itself is experiencing any known issues. Visit www.zohostatus.com to see the live status of all Zoho services. If a service is listed as degraded or under maintenance, no local action is needed — the issue is on Zoho's side and will be resolved by their team.

Step 2: Gather Information About the Problem

Before contacting support, work through the following questions. Having clear answers to all of these makes it significantly faster to diagnose and resolve a performance problem.

• Does the slowness affect all Zoho pages, or only specific modules or sections?
• Is the problem tied to a particular action — for example, loading a page, submitting a form, or running a report — or does everything feel slow?
• Is the issue constant, or does it happen only at certain times of day (such as during peak business hours)?
• Is the problem consistent every time it occurs, or does it come and go?
• What is the name of your Internet Service Provider (ISP)?
• What is your public IP address? You can find this by visiting whatsmyip.org.

Step 3: Run a TraceRoute Test

A TraceRoute maps the path your connection takes to reach Zoho's servers and shows where delays are occurring along that route. Run tests against at least two affected Zoho services and save the complete output of each.

On Windows

Open the Command Prompt (search for cmd in the Start menu) and run the following commands one at a time, saving the full output from each:

1. tracert zoho.com
2. tracert zoho.eu (for accounts hosted in the EU data centre)
3. tracert [your Zoho service URL] — replace this with the specific Zoho URL you are experiencing trouble with
4. tracert js.zohocdn.com
5. nslookup zoho.com

On Mac

You have two options:

• Network Utility: Open Network Utility, select the Traceroute tab, enter the Zoho service URL, and run the test.
• Terminal: Run traceroute zoho.com, traceroute zoho.eu, or traceroute [your Zoho service URL] as appropriate.

Step 4: Check Firewall and Proxy Settings

If your organisation uses a firewall or proxy server, verify that Zoho's domains are not being blocked or throttled. Zoho services require their domains to be whitelisted in your firewall and proxy configuration. If you are unsure how to check this, speak to your IT team or network administrator.

What Happens When You Raise a Support Request

When a performance issue is raised with the diagnostic information above, the investigation follows the pattern below based on what the TraceRoute results reveal:

• Route does not reach Zoho's network: logs are reviewed with Zoho's Network Operations Centre and upstream providers are engaged to investigate.
• Latency appears mid-route: Zoho's Network Operations Centre and upstream providers are involved to investigate the affected network hop.
• Latency at the final hop or border: the issue is investigated with the relevant ISP or addressed through DDoS mitigation measures if applicable.
• Route reaches Zoho's border but not the service: a remote session via Zoho Assist may be requested to review your local firewall and antivirus configuration.
• API or webhook performance issues: the accessibility of the destination endpoint is verified and alternative approaches are explored where needed.