Skip to main content
Clio logo

Is Clio Down?

No — Clio is up

Reachable from all 8 checked regions

Average response time: 412ms

Last checked · checks run every 6 hours

Official status page: https://status.clio.com

Clio uptime

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

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

30-day history

4-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: no data
Sep 2: no data
Sep 3: no data
Sep 4: no data
Sep 5: no data
Sep 6: no data
Sep 7: no data
Sep 8: no data
Sep 9: no data
Sep 10: no data
Sep 11: no data
Sep 12: no data
Sep 13: no data
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: 100.00% uptime, 8 checks
Sep 18: 100.00% uptime, 40 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 24 checks
Aug 22 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
360ms
DNS 78ms TCP 7ms TLS 166ms TTFB 359ms
arn
499ms
DNS 142ms TCP 1ms TLS 220ms TTFB 498ms
bom
782ms
DNS 205ms TCP 1ms TLS 369ms TTFB 780ms
cdg
315ms
DNS 29ms TCP 8ms TLS 166ms TTFB 314ms
dfw
159ms
DNS 47ms TCP 0ms TLS 62ms TTFB 158ms
ewr
73ms
DNS 28ms TCP 1ms TLS 14ms TTFB 71ms
fra
320ms
DNS 25ms TCP 1ms TLS 184ms TTFB 320ms
gru
791ms
DNS 430ms TCP 2ms TLS 225ms TTFB 789ms

What Clio does

Clio is legal practice management software. Clio Manage runs matters, calendars, documents, time tracking and billing, Clio Grow handles client intake, and Clio Payments collects fees, with Clio Draft, Clio Accounting and eFiling alongside. Law firms run their daily work in it, so an outage stops billing, intake and access to client files at once.

What an outage looks like

Sign-in fails or Clio Manage loads slowly or not at all, sometimes with a 502 error. Matters and documents will not open. Time entries and invoices cannot be saved. Intake forms from Clio Grow stop arriving. Payment links fail to process. Calendar rules and court deadlines may not calculate, and eFiling submissions do not go through.

What to do about it

Open status.clio.com and pick your region: Clio runs separate status pages for the United States, Canada, Europe and Australia. On the United States page each product has its own row, including Clio Manage, Clio Grow, Clio Payments, Clio Draft, Clio Accounting, Calendar Rules and Clio File - eFiling. If a court filing deadline is close and eFiling is affected, file through the court directly.

Is it down for everyone, or just you?

If this page says Clio 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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Clio outage FAQ

Why does Clio have four status pages?
Because Clio runs separate regional services. status.clio.com links to United States, Canada, Europe and Australia pages, and an incident in one region does not necessarily affect another. Open the page for the region your firm's account is in, since the all-clear on a different region's page says nothing about yours.
Is Clio Manage down or just one product?
Check the individual rows on your region's page. Clio lists Clio Manage, Clio Manage AI, Clio Grow, Clio Payments, Clio Draft, Clio Accounting, Clio Work, Calendar Rules and eFiling separately, so intake or payments can fail while Clio Manage works. That tells you whether to stop work entirely or only avoid one feature until it recovers.
What if an eFiling deadline falls during a Clio outage?
Do not wait for recovery if the deadline is close. Clio File - eFiling is its own component, and a court deadline is not extended because a vendor was unavailable. Use the court's own filing system or your usual fallback, keep a record of the outage from the status page, and update the matter in Clio afterwards.
Will time I entered during an outage be saved?
Only if it was saved before the failure. If Clio returned an error or the page hung, assume the entry did not save. Note your time somewhere else while Clio is down, then check the matter's activity once it recovers and add anything missing, so the invoice reflects the work actually done.
Is Clio down for everyone or just me?
Compare your region's status page with this page's measurements. If Clio reports all products operational and our probes reach the sign-in page from several regions, the problem is likely local: your office network, a VPN, or a browser session. If sign-in fails from several regions at once, it is Clio rather than your firm.

How we measure this

  • We request Clio'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 Clio 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 Clio goes down

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

Start Free Monitoring
Free plan available No credit card required