Live / Asana / Incident
Asana: Background jobs partial outage
Asana · asana.comMajor incidentResolved2026-10-24 02:35 UTC
Public — what happened
Summary
Asana reported a major partial outage affecting its background jobs, meaning the system that handles work running behind the scenes was significantly degraded. The company said it began at 23:57 UTC on 2026-10-23, and that some web application users had earlier experienced crashes that seemed to have stopped. By 00:03 UTC Asana said it had paused certain problematic workloads and believed recovery was underway, and the incident was marked resolved at 02:35 UTC on 2026-10-24.
Affected
Automations and Background Actions, Webhooks and Event Streams, Notifications
Timeline
- Started — 2026-10-23 23:57 UTC
- Investigating — 2026-10-23 23:57 UTC
- Monitoring — 2026-10-24 00:03 UTC
- Resolved — 2026-10-24 02:35 UTC · 2h 38m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Asana against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Asana: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Asana report →
More from Asana
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.