Is ClickUp Down?

No — ClickUp is up

Reachable from all 8 checked regions

Average response time: 162ms

Last checked 4 hours ago · checks run every 6 hours

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

ClickUp uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

196ms

Avg response, 30 days

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

30-day history

72-day clean streak

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

303ms

DNS 126ms TCP 2ms TLS 93ms TTFB 281ms

lhr

69ms

DNS 25ms TCP 1ms TLS 4ms TTFB 40ms

nrt

335ms

DNS 122ms TCP 2ms TLS 4ms TTFB 308ms

ord

102ms

DNS 77ms TCP 2ms TLS 3ms TTFB 86ms

sin

209ms

DNS 179ms TCP 1ms TLS 3ms TTFB 189ms

sjc

110ms

DNS 72ms TCP 2ms TLS 4ms TTFB 86ms

syd

44ms

DNS 12ms TCP 1ms TLS 5ms TTFB 23ms

yyz

125ms

DNS 31ms TCP 8ms TLS 11ms TTFB 63ms

What ClickUp does

ClickUp is a work management platform where teams run tasks, docs, chat, dashboards and goals inside one hierarchy of spaces, folders and lists. It is often the system of record for an entire department's process, with automations and integrations wired through it, so an outage stops coordination rather than a single feature.

What an outage looks like

Lists and boards load empty or hang on a spinner. Task edits appear to save and then revert on refresh. Automations stop firing, leaving tasks in a status that should have triggered a move or a notification. Docs fail to open or open read-only, chat messages do not send, and integrations with other tools fail without showing an error.

What to do about it

Check status.clickup.com, which reports Tasks, Docs, Chat, Automations, Dashboards, Search, Notifications, Integrations, Brain and the Public API separately, and marks each as affecting a single region, multiple regions or all regions. Read that regional marker first, because a single-region incident can leave your workspace healthy while a colleague's is broken. Afterwards, review anything time-sensitive that an automation should have moved.

Is it down for everyone, or just you?

If this page says ClickUp 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

ClickUp outage FAQ

Is ClickUp down for everyone, or only my region?

ClickUp marks every component as affecting a single region, multiple regions or all regions, which is unusual and useful. Workspaces are hosted regionally, so an incident can stop one office entirely while another sees nothing wrong. Read the regional marker on status.clickup.com before telling your team ClickUp is down, because the answer often differs by desk.

Do automations run after the outage ends?

Not reliably. Automations fire on events, and an event that happened while the automation engine was degraded may never be replayed once it recovers. Automations is a separate status component precisely because it fails independently of the tasks themselves. Treat anything with a deadline attached as needing a manual check rather than assuming the backlog caught up on its own.

Will edits I made during the outage be saved?

Edits the browser accepted but could not send are often held and sync when the connection returns. Anything typed into a tab you then refreshed or closed is usually gone. Keep the tab open until status.clickup.com clears. For a long comment or doc section, copying the text somewhere else first costs a few seconds and removes the question entirely.

Why can I see my tasks but not save changes?

Reads and writes fail separately in most incidents. Serving a cached list is far cheaper than accepting a change that has to trigger automations, notifications and integrations, so the read path frequently survives while the write path is already failing. A board that loads normally is not evidence that ClickUp is healthy; try one small edit to find out.

How we measure this

We request ClickUp'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 ClickUp 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 ClickUp 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