Skip to main content
Asana logo

Is Asana Down?

No — Asana is up

Reachable from all 8 checked regions

Average response time: 244ms

Last checked · checks run every 6 hours

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

Asana uptime

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

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

30-day history

77-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 31 checks
Sep 17: 100.00% uptime, 32 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, 32 checks
Sep 23: 100.00% uptime, 31 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 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, 1 incident
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, 32 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, 32 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
289ms
DNS 112ms TCP 8ms TLS 21ms TTFB 214ms
arn
376ms
DNS 73ms TCP 1ms TLS 54ms TTFB 233ms
cdg
185ms
DNS 36ms TCP 9ms TLS 24ms TTFB 133ms
dfw
355ms
DNS 78ms TCP 0ms TLS 52ms TTFB 194ms
ewr
209ms
DNS 69ms TCP 1ms TLS 22ms TTFB 152ms
fra
148ms
DNS 41ms TCP 1ms TLS 12ms TTFB 125ms
gru
165ms
DNS 12ms TCP 2ms TLS 10ms TTFB 124ms
iad
228ms
DNS 105ms TCP 1ms TLS 8ms TTFB 182ms

What Asana does

Asana is a work management platform where teams plan projects, assign tasks and track them through to completion. It sits between a shared to-do list and a full project management tool, and companies run roadmaps, campaign calendars and onboarding checklists inside it. Rules and integrations push work into other systems, which makes it a dependency rather than just a place to write things down.

What an outage looks like

Tasks fail to save, or revert to their earlier state after a refresh, and project and portfolio views load empty or spin without finishing. The mobile app often keeps working from cached data while the web app fails, which makes the outage look local. Rules stop firing so tasks are never moved or reassigned, and notifications arrive late or not at all.

What to do about it

Check status.asana.com, which reports App, API, Mobile, Automations and Background Actions, Webhooks and Event Streams, and Notifications separately for the US, EU, Japan, Australia and Middle East regions, so trouble in one region need not affect yours. Resist re-entering work that appeared to fail, because duplicate tasks are common once the backlog drains.

Is it down for everyone, or just you?

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

Jira
Jira
Monday.com
Monday.com
Notion
Notion
Slack
Slack

Asana outage FAQ

Is Asana down for everyone or just my workspace?
Asana hosts workspaces in separate regions and its status page reports the US, EU, Japan, Australia and Middle East independently, so start with the region your organisation is on. If every region is green and colleagues elsewhere are unaffected, the problem is more likely your network or browser session. Signing out and back in clears a surprising number of single-user cases.
Will I lose work I entered while Asana was down?
Usually not, but do not assume it saved. Asana's web app writes changes to the server as you make them, so an edit made during an outage may never have left the browser. When service returns, reload the project and confirm what actually persisted before retyping anything, since re-entering work that did save is the most common way people end up with duplicates.
Do Asana rules and automations run after the outage ends?
Automations and Background Actions is a separate component on Asana's status page, and it can lag behind the main app. Rules that should have fired during the incident may run late once the queue drains rather than being skipped, so give it time before triggering them by hand. Check the affected tasks afterwards, because a rule that ran twice is easier to spot than one that never ran.
Does the Asana mobile app work when the website is down?
Sometimes, and that is misleading rather than reassuring. Mobile is tracked as its own component, and the app can show cached tasks and projects that look current while writes silently fail. Treat anything you can only see on mobile as unconfirmed until the web app agrees, and avoid making bulk changes from the phone during an incident.
Does an Asana outage affect Slack and other connected tools?
It affects the connection, not the other tool. Webhooks and Event Streams is the component that pushes Asana activity outward, so Slack notifications, calendar sync and anything built on the API can stop while Slack itself is perfectly healthy. Work created in the other direction may queue rather than fail outright, so check both sides before assuming a message was lost.

How we measure this

  • We request Asana'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 Asana 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 Asana 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