Is Clio Down?

No — Clio is up

Clio's status page: Not available · we could not read it
FlareWarden checks: Website reachable · 8 of 8 regions · 500 ms

Right now

We could not read Clio's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

account.clio.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 500 ms
Checked: 5 hours ago

By region

Amsterdam reachable, 403 ms
Chicago reachable, 116 ms
San Jose reachable, 400 ms
Singapore reachable, 756 ms
Stockholm reachable, 410 ms
Sydney reachable, 1054 ms
Tokyo reachable, 780 ms
Toronto reachable, 88 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	61 ms	4 ms	189 ms	383 ms
Chicago	22 ms	7 ms	43 ms	116 ms
San Jose	110 ms	2 ms	133 ms	399 ms
Singapore	79 ms	1 ms	437 ms	755 ms
Stockholm	49 ms	1 ms	219 ms	409 ms
Sydney	165 ms	2 ms	435 ms	1053 ms
Tokyo	162 ms	1 ms	299 ms	780 ms
Toronto	23 ms	11 ms	19 ms	88 ms

We check that account.clio.com loads, not every feature behind it. Test it yourself

History

Incidents Clio reported

Since Oct 22, 15 days · from status.clio.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Clio website availability

Measured by FlareWarden · account.clio.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 447ms

Last 30 days

50-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of account.clio.com from multiple regions every 6 hours. Clio's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 50 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Clio itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Clio goes down

We check Clio every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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