Rewindex

CompaniesAsanaIncidents

Asana: Partial downtime for Asana's MCP server

No impact listedStatus: postmortemStarted Resolved (-644 min)2 updatesstspg.io (opens in new tab)
Part of an outage event

Cloudflare outage, Nov 18, 2025 · 77 vendors, 81 incidents

Asana’s incident blames Cloudflare as the cause. (hop 1, posted +10 h 44 min vs the first vendor naming Cloudflare)

“…Partial downtime for Asana's MCP server Incident: [Cloudflare experienced an outage](https://blog.cloudflare.com/18-november-2025-outage/) that impacted the Workers KV service, a storage infrastructur…”

Swipe sideways to see the whole diagram.

Cloudflareown incident not archivedWithin an hour13 vendors, 13 blamed CloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamed CloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, Maven Central +4Asana (this incident)posted +10 h 44 min
Cloudflareown incident not archivedWithin an hour13 vendors, 13 blamedCloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamedCloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, MavenCentral +4Asana (this incident)posted +10 h 44 min
Asana is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>13 vendors, 13 blamed Cloudflare<br/>Stytch, Zed, NordLayer +10"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>19 vendors, 19 blamed Cloudflare<br/>GitLab, Gorgias, Cursor +16"]:::blames
  root --> h4
  later["Later<br/>7 vendors, 7 blamed Cloudflare<br/>RudderStack, Brex, Maven Central +4"]:::blames
  root --> later
  me["Asana (this incident)<br/>posted +10 h 44 min"]:::me
  later --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    Asana's MCP server experienced partial unavailability for three hours due to an upstream provider outage. No data loss or security issues occurred during this outage. This resulted in an increased rate of errors from 3:20 - 5:00 AM PT and some failed requests from 5:04 - 6:26 AM PT. The service fully recovered after the upstream provider resolved the issue.

  2. postmortem

    Incident: [Cloudflare experienced an outage](https://blog.cloudflare.com/18-november-2025-outage/) that impacted the Workers KV service, a storage infrastructure service our MCP server relies on. This resulted in increased error rates and failed requests for a portion of our MCP traffic over the span of 3 hours. ‌ Impact:  Approximately 100 users making requests to the MCP server received error responses or were unable to reach the server from 2025-11-18 11:20 UTC through 14:20 UTC. ‌ Moving forward: We are investing in our MCP Server to improve its resilience to KV store outages, and are investigating ways to reduce the overall impact of Cloudflare outages. 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.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Asana profileRecent Asana incidentsMarkdownJSON