Skip to main content
Zoho logo

Is Zoho Down?

No — Zoho is up

Reachable from all 8 checked regions

Average response time: 318ms

Last checked · checks run every 6 hours

Official status page: https://zohostatus.com

Zoho uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
374ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 76 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

76-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 31 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 39 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 38 checks
Sep 26: 100.00% uptime, 40 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 31 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 24 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
979ms
DNS 804ms TCP 2ms TLS 8ms TTFB 978ms
arn
148ms
DNS 61ms TCP 1ms TLS 8ms TTFB 148ms
cdg
198ms
DNS 36ms TCP 1ms TLS 8ms TTFB 198ms
dfw
330ms
DNS 244ms TCP 2ms TLS 6ms TTFB 329ms
sin
406ms
DNS 195ms TCP 1ms TLS 8ms TTFB 406ms
sjc
165ms
DNS 67ms TCP 10ms TLS 19ms TTFB 163ms
syd
242ms
DNS 32ms TCP 1ms TLS 6ms TTFB 242ms
yyz
82ms
DNS 34ms TCP 2ms TLS 9ms TTFB 82ms

What Zoho does

Zoho sells a wide suite of business applications, including CRM, Mail, Desk, Books, Campaigns, Analytics and Creator, all sharing one account and sign-in system. Companies frequently run sales, support and finance inside it, so a single component failing can interrupt an entire back office. Each account's data sits in a regional data centre chosen when it was created.

What an outage looks like

Sign-in fails across every Zoho application at once when the shared account service is affected, which presents as many separate outages rather than one. CRM records save without persisting, Desk tickets arrive late or duplicate, and Mail rejects sends with connection errors while already-delivered mail stays readable. Automations built in Flow or Creator stop firing, so downstream records are never created.

What to do about it

Check zohostatus.com and select your data centre, because Zoho reports availability separately for zoho.com, zoho.in, zoho.eu, zoho.uk, zoho.com.au, zohocloud.ca, zoho.jp, zoho.com.cn and zoho.sa, and an incident in one does not touch the others. The domain in your Zoho URLs tells you which you are on. Avoid re-saving records repeatedly, since duplicates are common once the backlog drains.

Is it down for everyone, or just you?

If this page says Zoho is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Zoho outage FAQ

Is Zoho down or is only my region affected?
Check the data centre your account lives in rather than the overall page. Zoho publishes a separate status view per region, and the domain you sign in at identifies yours: an account on zoho.eu is unaffected by an incident confined to the US data centre. Colleagues in another region can be working normally during an outage that has stopped you completely.
Why can I not log in to any Zoho app at once?
Every Zoho application authenticates against one shared account service, so when that is degraded the whole suite becomes inaccessible together. It looks like CRM, Mail and Desk failing independently, but there is a single cause. Sessions already established sometimes survive, which is why one browser keeps working while a fresh sign-in fails.
Is email lost when Zoho Mail is down?
Incoming mail is normally queued by the sending server and retried for a period measured in days, so messages arrive late rather than disappearing. Mail already in your mailbox is unaffected. Outbound messages that failed with a connection error were never sent, so check the sent folder before assuming a message went out, and expect some retried deliveries to arrive twice.
Do Zoho automations run once the outage ends?
Not reliably. Flow, Creator and CRM workflow rules fire on events, and events that occurred while the automation layer was degraded can be skipped rather than replayed. That leaves records created during the incident without the follow-up actions attached to them. Identify anything created in the outage window and check whether its automations actually ran.
How do I find which Zoho data centre I am on?
Look at the domain in the address bar of any Zoho application. Signing in at zoho.eu, zoho.in or zoho.com.au means the account is hosted in that region, and the matching view on zohostatus.com is the one that applies to you. The data centre is fixed when the account is created and is not something you switch between casually.

How we measure this

  • We request Zoho's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Zoho publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Zoho goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required