outages.live
Live
AsanaIncident · 2026-09-30 14:31 UTC

Partial API outage

ResolvedOfficial update

This incident has been resolved.

The latest update from Asana.

State

Resolved

Started

32 d ago

2026-09-30 14:31 UTC

Lasted

50 min

until 2026-09-30 15:21 UTC

Worst impact

Partial outage

Timeline

3 updates
14:3114:4314:5615:0815:21
Partial outageUpdate postedTimes in UTC

Investigating

38 min 76%

Identified

12 min 24%

Updates

Times in UTC

As posted by Asana

Resolved2026-09-30 15:21 UTC

This incident has been resolved.

Identified2026-09-30 15:09 UTC

We are currently seeing system recovery and are actively monitoring the situation to ensure a full recovery.

Investigating2026-09-30 14:31 UTC

We are currently investigating this issue.

Affected components

4
APIMobileUS - APIUS - Mobile

Asana in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

9

Days with an incident

10

Median duration

50 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 h 12 min
median 50 min
90 days agoToday

Other Asana incidents

All incidents

Asana·Background jobs partial outage

This incident has been resolved.

Resolvedresolved 9 d ago

Asana·Asana downtime

**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, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC. **Moving forward:** We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing. Our

Resolvedresolved 11 d ago

Asana·Partial API outage in EU

The incident has been resolved.

Resolvedresolved 33 d ago

Asana·Automations not running for EU users

This incident has been resolved.

Resolvedresolved 41 d ago

Asana·Slow performance for a subset of Asana users

This incident has been resolved.

Resolvedresolved 45 d ago

Follow Asana

Your coding agent knows when Asana is down, and tells you when a failure is theirs, not yours. You can also get Asana incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "asana" and tell me if Asana has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=asana
Slack
/feed subscribe https://outages.cc/feed.xml?providers=asana

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane