Autodesk Outage History

**AUTODESK EVENT ANALYSIS** **Incident Number:** COE-INC142187 **Incident Date:** April 30, 2026 ‌ **Summary** On April 30, 2026, between 08:00 AM PDT and 08:17 AM PDT, customers could not access Fusion Manage. ‌ **Impacted Services** * Fusion Manage ‌ **Root Cause** * The issue was caused by a production deployment. * Pre-deploy tests did not flag the issue. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * The production release was rolled back to get to previous state. * Additional tests were added to pre-deploy to prevent recurrence of this issue. ‌ Thank you for your patience and understanding.

**AUTODESK EVENT ANALYSIS** **Incident Number:** #coe-inc142006-pelican **Incident Date:** April 28, 2026 ‌ **Summary** On April 28, 2026, between 12:01 PM PDT and 01:30 PM PDT, Autodesk Customers attempting to place orders through the Autodesk Store were unable to complete the checkout process. ‌ **Impacted Services** * Autodesk Store ‌ **Root Cause** * It was determined that the issue was caused by an internal account consuming excessive database memory, which impacted database performance. * Database was locked with READLOCK to execute FLUSH command. Due to LOCK on database customer requests to the database were rejected. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Updates such that shared system accounts will no longer be used. ‌ Thank you for your patience and understanding.

**AUTODESK EVENT ANALYSIS** **Incident Date:** April 28, 2026 **Summary** On April 28, 2026, between 6:20 AM PDT and 7:33 AM PDT, Autodesk customers were unable to view thumbnails for newly created design data across Fusion, Fusion Online, Fusion Mobile, and Fusion Team in all regions. **Root Cause** * Thumbnail creation was delayed due to queuing issues which in turn led to thumbnail failures * We added more workers/solvers that could free up the queue quicker which resolved the problem ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * We have identified the root cause of what led to the back-up, and are working to correct the problem * Additional monitoring alerts for detecting similar issues in the future. ‌ Thank you for your patience and understanding.

**AUTODESK EVENT ANALYSIS** **Incident Number:** #coe-inc141903-pype-closeout **Incident Date:** April 27, 2026 ‌ **Summary** On April 27, 2026, between 01:57 PM PDT and 02:39 PM PDT, customers experienced issues logging in to Pype Closeout. ‌ **Impacted Services** * Pype Closeout ‌ **Root Cause** The issue was related to cache memory usage reaching capacity, which impacted system performance and resulted in login failures. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Optimizing cache management to ensure data is retained only as long as necessary and system resources are used efficiently * Enhancing monitoring and alerting to provide earlier visibility into rising memory usage * Reviewing and refining system configurations to reduce the risk of similar issues in the future ‌ Thank you for your patience and understanding.

**AUTODESK EVENT ANALYSIS** **Incident Number:** #COE-INC141103 **Incident Date:** April 20, 2026 ‌ **Summary** On April 20, 2026, between 12:30 PM PDT and 04:35 PM PDT, Autodesk experienced a service disruption that prevented BIM Collaborate Pro for Government users from loading projects. ‌ **Impacted Services** * BIM Collaborate Pro for Government ‌ **Root Cause** * A system configuration automatically limited the number of stored versions of a critical service component, which led to required versions becoming unavailable. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Additional alerting mechanisms to notify on-call engineers in real time. * Review of system configuration policies to prevent unintended removal of required service versions. ‌ Thank you for your patience and understanding.

**AUTODESK EVENT ANALYSIS** **Incident Number:** #coe-inc141074-acs-locations **Incident Date:** April 20, 2026 ‌ **Summary** On April 20, 2026, between 1:40 AM PDT 8:25 AM PDT, Autodesk Forma customers creating new projects experienced failures in location-dependent functionality. ‌ **Impacted Services** * Build * Data Management * Takeoff ‌ **Root Cause** * Locations service upgrade caused an error upon creating new projects, due to incorrect environment variable. * The issue was resolved by restoring a previous version. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Enhancements to the validation process within non-production environments. ‌ Thank you for your patience and understanding.

**AUTODESK EVENT ANALYSIS** **Incident Number:** #coe-inc140612-acc-autospecs **Incident Date:** April 14, 2026 ‌ **Summary** On April 14, 2026, between 12:15 PM PDT and 01:10 PM PDT, Autodesk experienced a service disruption impacting customers using Forma AutoSpecs within Forma Build and Forma for Construction Operations. ‌ **Impacted Services** * Forma AutoSpecs ‌ **Root Cause** The issue occurred when a large number of PDF files were uploaded at once, resulting in a high total file size. Processing these files required more system resources than were available at the time, which led to temporary service disruption. ‌ **Autodesk Actions** Autodesk has completed a review of the incident and is implementing the following improvements: * Increasing available system resources to better support large file processing * Introducing limits on the total size of files that can be uploaded at one time ‌ Thank you for your patience and understanding.

**AUTODESK EVENT ANALYSIS** **Incident Number:** coe-inc139594-shotgun **Incident Date:** April 1, 2026 ‌ **Summary** On April 1, 2026, between 7:00 AM PDT and 12:14 PM PDT, Autodesk experienced an issue that impacted customers using Flow Production Tracking \(FPTR\). During this time, customers were unable to create or modify webhooks. ‌ **Impacted Services** * Flow Production Tracking \(FPTR\): Customers were unable to create or update webhooks. ‌ **Root Cause** * The issue was caused by a change in DNS resolution behavior that affected webhook functionality. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Improvements to testing and validation processes to better identify similar issues before release. Enhancements to monitoring to detect webhook-related issues more quickly. ‌ Thank you for your patience and understanding.

**AUTODESK EVENT ANALYSIS** **Incident Number:** COE-INC139523 **Incident Date:** April 1, 2026 ‌ **Summary** On April 1, 2026, between 6:53 AM PDT and 5:45 PM PDT, Autodesk experienced an issue that impacted customers in the US region from using a specific feature in the Specifications tool of Autodesk Forma Build. ‌ **Impacted Services** * Autodesk Forma Specifications ‌ **Root Cause** * The issue was due to an issue with the component that detects and generates submittals, resulting in customers not being able to generate submittals from their project specifications ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Increase processing capacity, so queued tasks will be picked up and processed smoothly ‌ Thank you for your patience and understanding.