Partial API outage
降级This incident has been resolved.
Asana 是不是挂了？
Asana 运行正常。 Asana 用于跟踪团队项目与任务。
近 90 天
99.80%
估算可用率
估算可用率
90 天前今天
根据 Asana 公布的事件推算，属于估算，不是实测值。
Asana 近 90 天稳定性
7报告事件数
0完全中断
50 min典型时长
3 h 12 min最长事件
最近一次事件：“Partial API outage”，19 天前。
组件
App正常
App正常
App正常
App正常
App正常
API正常
API正常
API正常
API正常
API正常
Mobile正常
Mobile正常
Mobile正常
Mobile正常
Mobile正常
Automations and Background Actions正常
Automations and Background Actions正常
Automations and Background Actions正常
Automations and Background Actions正常
Automations and Background Actions正常
Webhooks and Event Streams正常
Webhooks and Event Streams正常
Webhooks and Event Streams正常
Webhooks and Event Streams正常
Webhooks and Event Streams正常
Notifications正常
Notifications正常
Notifications正常
Notifications正常
Notifications正常
近期事件
Partial API outage in EU
降级The incident has been resolved.
Automations not running for EU users
降级This incident has been resolved.
Slow performance for a subset of Asana users
降级This incident has been resolved.
We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.
降级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 capacity. Impact: For approximately 30 minutes, customers whose traffic was handled by this compute cluster saw full downtime; other customers were unaffected. No customer data was lost. Moving forward: We have added additional monitoring to detect this type of capacity-scaling failure much earlier, and have added safeguards to prevent deployments from shifting traffic before sufficient healthy capacity is confirmed. _Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average._
常见问题
Asana 现在是不是挂了？
Asana 官方状态页显示：All Systems Operational。本页每次打开时会重新读取，最多每 5 分钟一次。
Asana 上一次故障是什么时候？
Asana 最近一次报告的事件是“Partial API outage”，发生在19 天前（2026-09-30 14:31 UTC）。近 90 天的事件中没有完全中断。
这里跟踪了 Asana 的哪些部分？
Asana 的状态页列出 30 个组件，包括 App, App, App, App, App。每次页面刷新都会重新读取。
Asana 挂了我该怎么办？
尽量用本地或离线副本继续工作，等恢复后再做大批量导入或同步。
Asana 状态页按 US/EU/Japan 分行，是什么意思？
Asana 提供区域数据驻留，状态页按区域分别跟踪 App、API、Mobile、Automations、Webhooks。只有托管在点名区域的组织才受影响。
任务能打开但自动化和 webhook 没跑？
Automations and Background Actions 与 Webhooks and Event Streams 是按区域单列的组件——应用正常时规则也可能暂停。
怎么判断 Asana 是所有人都打不开，还是只有我这边有问题？
如果上面显示运行正常但 Asana 对你仍然不可用，问题多半在你这边：换个网络、清除缓存，或检查自己的网络连接。如果显示降级或故障，说明其他人也受到影响。
我自己的网站挂了，怎么第一时间收到通知？
OpenUptime 每分钟检查一次你的网站，一旦无响应就通过 Slack、Telegram、邮件或 Webhook 告警。它是开源的，可以免费开始使用。