down
Is Asana down?
Asana provides work and project management tools for coordinating organizational tasks and workflows.
https://asana.com/ ↗Mapped components are operational in the latest status update; individual experiences can vary.
Service disruption activity for Asana
Last 24 hoursObserved disruption signals combine available incidents, recorded reports, website checks, and emerging problem patterns. A low score does not guarantee that every feature is working.
Latest observation: 2026-11-08 15:54:28 UTC. Refreshes automatically while this page is visible.
No user-submitted outage reports in the last 24 hours.
Asana outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
Select a square for daily details. Scroll sideways to explore earlier months.
How to read this calendar
Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.
Asana website uptime and response time
Website responded successfully HTTP 200. Last checked 2026-11-08 15:35:29 UTC.
Checked address: https://asana.com/
DNS lookup: 2 ms · TCP connection: 2 ms · TLS handshake: 8 ms. Certificate expires 2027-01-10; trusted connection: yes.
100%
Successful website checks (24h)
22 successful / 22 measurable checks
90 ms
Median response time
631 ms
95th percentile response time
0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.
Evidence behind the status
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.
Website checks and estimated activity have independent update times. Refer to each section for its latest observation.
These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.
Official component status
Asana official status · fetched 2026-11-08 15:54:28 UTC
40 mapped components · 0 reporting problems
| Component | Provider status |
|---|---|
| App | operational |
| US | operational |
| App | operational |
| App | operational |
| App | operational |
| App | operational |
| API | operational |
| EU | operational |
| API | operational |
| API | operational |
| API | operational |
| API | operational |
| Mobile | operational |
| Mobile | operational |
| Japan | operational |
| Mobile | operational |
| Mobile | operational |
| Mobile | operational |
| Automations and Background Actions | operational |
| Automations and Background Actions | operational |
| Automations and Background Actions | operational |
| Australia | operational |
| Automations and Background Actions | operational |
| Automations and Background Actions | operational |
| Webhooks and Event Streams | operational |
| Webhooks and Event Streams | operational |
| Webhooks and Event Streams | operational |
| Webhooks and Event Streams | operational |
| Middle East | operational |
| Webhooks and Event Streams | operational |
| Notifications | operational |
| Notifications | operational |
| Notifications | operational |
| Notifications | operational |
| Notifications | operational |
| AI Meetings | operational |
| AI Meetings | operational |
| AI Meetings | operational |
| AI Meetings | operational |
| AI Meetings | operational |
Official incident timeline
Background jobs partial outage · resolved · 2026-10-24T02:35:28.599Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
We've paused some problematic workloads, and we think we're seeing recovery.
- · investigating
We have a significant degradation in our system for processing asynchronous work. We previously had some crashes from web application users, but that appears to have resolved. We're monitoring the asynchronous work.
Asana downtime · postmortem · 2026-10-24T00:23:45.858Z
Product match: components.
Read the provider’s incident report
- · postmortem
**Incident:** An infrastructure update targeting security caused DynamoDB to become inaccessible across Asana's production environment. This change was related to a production isolation initiative, and was applied in a way that left all of our production services unable to use DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. **Impact:** Asana services were completely unavailable for approximately 30 minutes,
- · resolved
The fix has been applied. We have observed recovery of error rates and traffic, and believe this incident is now resolved. We will post a postmortem/RCA within 72 hours.
- · identified
We are continuing to work on a fix for this issue.
- · identified
We have identified the cause of this outage and have initiated changes to address this. We are seeing some signs of recovery, and will post an update once we've confirmed recovery.
- · identified
Asana services are currently experiencing a major service disruption. We have identified a likely cause and are working on applying a fix. This affects all services and all regions.
Partial API outage · resolved · 2026-09-30T15:21:10.793Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · identified
We are currently seeing system recovery and are actively monitoring the situation to ensure a full recovery.
- · investigating
We are currently investigating this issue.
Partial API outage in EU · resolved · 2026-09-29T15:25:57.485Z
Product match: components.
Read the provider’s incident report
- · resolved
The incident has been resolved.
- · investigating
We are currently investigating the issue.
Automations not running for EU users · resolved · 2026-09-21T16:10:01.319Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
We're currently working our way through the backlog of automations that did not run.
- · identified
We are continuing to work on a fix for this issue.
- · identified
We've heard reports of rules and automations not running in the EU region. We've identified the source of the issue and fixed it for new automations triggers going forward. Our engineers are currently working on the backlog of automations that triggered and did not run during the incident.
Slow performance for a subset of Asana users · resolved · 2026-09-17T15:13:16.424Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · investigating
We are continuing to investigate this issue.
- · investigating
We received an alert for unusual slow performance in several regions. We're investigating.
We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment. · postmortem · 2026-09-04T19:53:15.949Z
Product match: components.
Read the provider’s incident report
- · postmortem
Incident: An internal system responsible for automatically scaling backend server capacity in one of our compute clusters stopped replacing capacity that had been cycled out during routine maintenance. This caused a gradual reduction in available capacity over several hours. A subsequent deployment was activated with insufficient capacity, causing all new requests for that compute cluster to fail. To mitigate the impact, we reverted to a previous release revision, which still had sufficient capa
- · resolved
This incident has been resolved.
- · monitoring
A fix has been implemented and we are monitoring the results.
- · investigating
The rollback seems to have completely resolved errors. We're monitoring closely, but users should be able to access Asana again.
- · investigating
We are continuing to investigate this issue.
- · investigating
We are currently investigating this issue.
Asana full outage for some users (2 hours, 25% outage) · postmortem · 2026-09-02T21:38:00.116Z
Product match: components.
Read the provider’s incident report
- · postmortem
We’ve been working to add a caching layer to our update pipeline, tuning it carefully and rolling it out gradually. On Wednesday, August 26 we enabled it for most use cases, and it initially performed well. On Monday, August 31, a combination of unrelated infrastructure changes and peak traffic pushed the cache past its scaling limits. Once that threshold was crossed, the cache became unusable, and many pods serving read traffic for the Asana application could no longer serve it. We mitigated
- · resolved
User-facing symptoms have recovered. We'll continue to monitor, and will prioritize a retrospective to understand and prevent similar incidents in the future.
- · monitoring
We've applied a fix are seeing signs of recovery.
- · investigating
We have made configuration changes and see partial recovery, but we continue to see some elevated errors.
- · investigating
We are continuing to investigate the issue; we have reverted recent changes, and are working to identify the source of the errors.
- · investigating
We are investigating alerts for slow performance and application errors.
Recovery tracker
No recent recovery can be established from available evidence.
1 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
No sustained slowdown has been established against the earlier baseline.
Recent median: 631 ms · Earlier median: 90 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.
Emerging down-report signals
No recent emerging problem patterns are available for this service.
Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.
Is it down in your region?
Run one public website check from a community probe. Results describe that probe, not every user in a country.
Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.
Infrastructure incident context
Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Asana.
No active incidents recorded.
- Spectrum Availability Issue in Phoenix · monitoring
- Fedramp Customers have Delayed Purges · identified
About Asana status on Iszdown
Asana provides work and project management tools for coordinating organizational tasks and workflows.
This page combines the available Asana report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.
40 product-matched official components are listed above. Latest public website measurement: 2026-11-08T15:35:29.000Z.
Visit the official Asana website · Official provider status · How it works
What to check when Asana is not working
These are troubleshooting suggestions, not a list of currently reported problems.
Check your tenant and affected workflow
Note the product, account region or instance, and whether the issue affects sign-in, a specific workflow, or an integration. A public website response does not test your organization’s account.
Separate access problems from application errors
Check your organization’s sign-in service and whether colleagues see the same error. Keep private customer data, employee information, credentials, and access tokens out of public reports.
Website troubleshooting guide · Sign-in problems · API errors and timeouts
Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.
Recent Asana outage history
Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.
| Incident | Started (UTC) | Recorded duration | Last collected status |
|---|---|---|---|
| Background jobs partial outage | 158 min | resolved | |
| Asana downtime | 37 min | postmortem | |
| Asana Down | No resolution recorded | investigating | |
| Partial API outage | 50 min | resolved | |
| Partial API outage in EU | 192 min | resolved | |
| Automations not running for EU users | 70 min | resolved | |
| Slow performance for a subset of Asana users | 36 min | resolved | |
| We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment. | 42 min | postmortem |
Frequently asked questions about Asana
Is Asana down right now?
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-11-08T16:02:21.000Z.
How many Asana outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-07T16:00:00.000Z to 2026-11-08T16:00:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.
Why does Asana show operational when it is not working for me?
An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Asana feature.
When was Asana status last updated?
The latest status observation was 2026-11-08T15:54:28.000Z. Only matched product components and incidents are shown. The assessment is recent.
Has Asana had outages before?
The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.
How do I follow Asana or report a problem?
Use “Watch this service” to save Asana in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.
Related services to Asana
Check a related product separately; its status can differ from Asana.