Autodesk Health Dashboard Incident History

1. resolvedSep 4 · 20:52 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. postmortemSep 4 · 15:55 UTC

   **AUTODESK EVENT ANALYSIS** **Incident Number:** # coe-inc151879-bimdata-p **Incident Date:** August 3, 2026 ‌ **Summary** Between 09:00 AM PDT and 07:30 PM PDT on August 24, 2026, Autodesk experienced a service disruption that resulted in customers being unable to view current data using Insight Builder in Forma Insight. ‌ **Impacted Services** * Forma Insight ‌ **Root Cause** * Long-running query timed out due to concurrent running data pipelines, combined with insufficient query performance. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Improvements to query performance * Remove unnecessary functions from the pipeline * Isolate Insight Builder pipeline to a dedicated reader for consistent performance ‌ Thank you for your patience and understanding.

Reported by Autodesk Health Dashboard on their status page.

1. postmortemSep 4 · 15:31 UTC

   **AUTODESK EVENT ANALYSIS** **Incident Number:** #COE-INC152917 **Incident Date:** August 15, 2026 ‌ **Summary** Between August 15, 2026, at 10:56 PM PDT and August 16, 2026, at 1:10 AM PDT, Autodesk experienced a service degradation impacting customers using Autodesk Platform Services. During the incident, some customer requests failed with service errors until the incident was resolved. ‌ **Impacted Services** * All Autodesk products using Autodesk Platform Services ‌ **Root Cause** * The incident was due to changes within a third part providers data storage infrastructure. * During routine infrastructure maintenance, this reduced the data capacity available to process requests causing some requests to fail. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Additional monitoring and alerts to detect similar underlying storage issues and improve response time. * Additional safeguards to prevent routine infrastructure maintenance from proceeding based on state of required components. ‌ Thank you for your patience and understanding.

Reported by Autodesk Health Dashboard on their status page.

1. postmortemSep 4 · 14:06 UTC

   **AUTODESK EVENT ANALYSIS** **Incident Number:** #COE-INC151602, #COE-INC151694 **Incident Date:** July 29, 2026, July 30, 2026 ‌ **Summary** On July 29, 2026, from 9:30 PM to 10:40 PM PDT and on July 30, 2026, from 11:12 PM to 11:45 PM PDT, Autodesk customers using Revit Cloud Worksharing / Cloud Models in the US region experienced issues accessing cloud model workflows, including Initiate Collaboration, Synchronize with Central, and Model Open. ‌ **Impacted Services** • Revit Cloud Worksharing / Cloud Models in the US region ‌ **Root Cause** • A routine database maintenance procedure triggered an expected failover event. • Though past events have not disrupted customer workflows, this one unexpectedly resulted in a reduction in service capacity, degrading its ability to handle customer requests. • As the service began to recover, customer demand exceeded available capacity, delaying a return to normal operation. • Autodesk temporarily limited demand and gradually lifted the limit as capacity recovered, restoring the service to normal operation. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken, including: • Update maintenance procedures to reduce the risk of disruption. • Improve service resilience to better tolerate brief disruptions to supporting systems. • Process improvements to operational response when demand exceeds capacity during recovery. ‌ Thank you for your patience and understanding.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedSep 4 · 11:16 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. postmortemSep 3 · 21:12 UTC

   **AUTODESK EVENT ANALYSIS** **Incident Number:** COE-INC153598 **Incident Date:** August 25, 2026 ‌ **Summary** On August 25, 2026, between 5:00 AM PDT and 6:00 AM PDT, Autodesk identified an issue where Autodesk Fusion customers were unable to load and view properties in the Property Panel. ‌ **Impacted Services** * Autodesk Fusion Property Panel ‌ **Root Cause** * One of Fusion’s eventing services was overloaded due to an increase in user activity. * Autodesk teams increased capacity for the underlying service to resolve the issue. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Increased capacity on the underlying eventing service and implemented more graceful handling of usage spikes. * Removed process dependencies such that when one downstream service is unavailable in the Properties Panel, access to the rest of the capabilities is still available. ‌ Thank you for your patience and understanding.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedSep 3 · 15:53 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedSep 3 · 05:29 UTC

   On 02-09-2026 at 11:30 AM PDT, Autodesk identified an issue where customers were unable to view newly generated activities in Forma Build as updates are not appearing in the Activity Log in US region. Once the issue was resolved on 02-09-2026 at 07:00 PM PDT, Forma Build returned to normal operation. This is a retroactive notification as this issue did not display on the Autodesk Health Dashboard at that time. Thank you for your patience and understanding.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedSep 2 · 11:20 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedSep 1 · 17:25 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedSep 1 · 16:39 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. postmortemAug 29 · 17:44 UTC

   **AUTODESK EVENT ANALYSIS** **Incident Number:** COE-INC151671 **Incident Date:** July 30, 2026 ‌ **Summary** On July 30, 2026, between 7:30 PM and 8:30 PM PDT, Autodesk experience an issue that prevented customers from accessing Forma Build Cost Management and BIM 360 Cost Management across all regions. ‌ **Impacted Services** * Forma Build Cost Management * BIM 360 Cost Management ‌ **Root Cause** * An outdated database schema caused database query failures and HTTP 500 API errors. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Add extra automated checks to ensure the DB Migration Pipeline is deployed along with the App Pipeline. * Add extra automated checks to ensure the Script Pipeline is deployed along with the App Pipeline for quicker recovery. ‌ Thank you for your patience and understanding.

Reported by Autodesk Health Dashboard on their status page.

1. postmortemAug 29 · 17:35 UTC

   **AUTODESK EVENT ANALYSIS** **Incident Number:** COE-INC151562 **Incident Date:** July 29, 2026 ‌ **Summary** From July 28, 2026, at 9:44 AM PDT to July 29, 2026, at 7:53 AM PDT, Autodesk Forma experienced an issue that prevented customers from creating and accessing new projects in the Australia \(AUS\) region. The incident impacted customers using Forma Build, Forma Data Management, and Forma Takeoff. Existing projects remained available and continued to function normally throughout the incident. ‌ **Impacted Services** * Forma Build * Forma Data Management * Forma Takeoff ‌ **Root Cause** * A recent infrastructure deployment recreated a messaging component with an incorrect configuration, preventing project initialization events from being processed for newly created projects in the Australia region. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Corrected the messaging configuration, restoring normal processing of project initialization events. Autodesk also initiated recovery of the projects affected during the incident. * Strengthen deployment validation to verify that messaging components are created and configured correctly before infrastructure changes are promoted to production. * Improve end-to-end monitoring of project initialization workflows, so messaging failures are detected more quickly. ‌ Thank you for your patience and understanding.

Reported by Autodesk Health Dashboard on their status page.

1. postmortemAug 29 · 17:27 UTC

   **AUTODESK EVENT ANALYSIS** **Incident Number:** #COE-INC151656 **Incident Date:** July 30, 2026 ‌ **Summary** On July 30, 2026, between 8:50 AM PDT and 12:46 PM PDT, Autodesk experienced a service disruption that impacted customers using TradeTapp Qualifications in BuildingConnected. Impacted users were unable to add or update contacts in their qualification applications. ‌ **Impacted Services** * BuildingConnected \(Qualifications module\) * TradeTapp by BuildingConnected ‌ **Root Cause** * The service disruption was caused by a faulty deployment which contained a regression that blocked this workflow. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Implement new workflow testing requirements before deployments. * Improvements to automated testing infrastructure. ‌ Thank you for your patience and understanding.

Reported by Autodesk Health Dashboard on their status page.

1. postmortemAug 29 · 17:20 UTC

   **AUTODESK EVENT ANALYSIS** **Incident Number:** COE-INC151439 **Incident Date:** July 28, 2026 ‌ **Summary** From July 24, 2026, at 1:00 PM PDT to July 28, 2026, at 4:25 PM PDT, Autodesk experienced a service disruption impacting hub creation requests by customers using BIM360 across US, AUS, EMEA, India, Japan, and Canada regions. ‌ **Impacted Services** * Autodesk Business Systems \(Autodesk Support\). ‌ **Root Cause** * The internal tool used by Autodesk Support to provision new customer hubs had a bug in the system. Autodesk proactively disabled the tool to prevent any further impact while a fix was developed and validated. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Safely restored the tool in read-only mode. * Strengthened access controls on the provisioning tool. * Validated the fix in all regions before returning the tool to full service. ‌ Thank you for your patience and understanding.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 28 · 17:01 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. postmortemAug 27 · 22:26 UTC

   **AUTODESK EVENT ANALYSIS** **Incident Number:** #COE-INC153353 **Incident Date:** August 20, 2026 ‌ **Summary** From August 20, 2026, at 1:00 PM PST to August 21, 2026, at 3:35 PM PST, Autodesk experienced an issue that prevented some customers from accessing User Management tab within Autodesk Account Portal. Affected customers may also have been unable to manage newly purchased or renewed subscriptions. This issue affected a subset of customers globally. ‌ **Impacted Services** * Autodesk Account ‌ **Root Cause** * A compatibility issue in a backend service caused some scheduled entitlement updates to fail, preventing customer account information from updating as expected. * Autodesk corrected the affected service configuration and refreshed account information for potentially affected customers to restore access. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Improve monitoring and alerting to identify failed entitlement updates earlier. * Add safeguards to capture and recover failed entitlement updates more quickly. * Add automated checks to identify missing or incomplete entitlement updates. * Improve recovery procedures to restore affected access more quickly. ‌ Thank you for your patience and understanding

Reported by Autodesk Health Dashboard on their status page.

1. postmortemAug 27 · 21:30 UTC

   **AUTODESK EVENT ANALYSIS** **Incident Number:** # COE-INC151406 **Incident Date:** July 28, 2026 ‌ **Summary** On July 28, 2026, between 3:30 AM PDT and 5:20 AM PDT, Autodesk experienced an issue affecting the Search service due to capacity constraints in the Amazon MSK \(Kafka\) cluster supporting the service. The issue impacted the service’s ability to maintain the required number of Kafka consumer connections. ‌ **Impacted Services** * Flow Platform ‌ **Root Cause** * Autodesk completed a root cause analysis and determined that the issue was caused by a capacity limitation in the Amazon MSK \(Kafka\) cluster. * The cluster was configured with a default maximum client connection limit per broker. As the number of consumer connections increased, the service reached this limit, resulting in the incident. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified and implemented actions to improve capacity and prevent recurrence. These include the following: * Increased the maximum client connection limit to accommodate additional consumer connections. * Removed unused partner consumers from the configuration to reduce unnecessary Kafka connections. * Began development to split the ingestion service to reduce unused consumer connections and improve connection management. * Added monitoring and alerts to provide early notification when connection metrics approach configured limits. * Planned additional improvements to increase consumer utilization efficiency and further reduce the number of connections required to the Kafka brokers. ‌ Thank you for your patience and understanding.

Reported by Autodesk Health Dashboard on their status page.

1. postmortemAug 27 · 21:22 UTC

   **AUTODESK EVENT ANALYSIS** **Incident Number:** #coe-inc153351-tnkrcad-p **Incident Date:** August 21, 2026 ‌ **Summary** Between August 19, 2026, at 08:07 PM PST and August 21, 2026, at 12:36 PM PST, Autodesk updated a sign-in workflow that impacted some customers using Tinkercad globally. Users who used “Sign on with Google” \(or similar third-party sign-on\) with a federated SSO were given new accounts. Predominantly, those affected were accounts who use Google to sign in for educational accounts. ‌ **Impacted Services** * Tinkercad ‌ **Root Cause** * The sign-in workflow for Tinkercad was switched to a more modern industry standard sign-on protocol. * Tinkercad rolled back the sign-on protocol change, allowing federated SSO users to access their previous account and data. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Additional testing to ensure any federated SSO accounts will have uninterrupted access to their data on future authentication protocol updates. ‌ Thank you for your patience and understanding.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 27 · 16:58 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 24 · 10:32 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 24 · 07:16 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 21 · 23:43 UTC

   After further review, no customer impact has been identified for Autodesk.com. We apologize for any confusion caused by our previous notification and appreciate your patience and understanding

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 20 · 16:50 UTC

   All services have returned to normal operation. The service disruption affecting multiple Autodesk products was limited to customers in the US region, while other regions remained unaffected. We sincerely apologize for any inconvenience this may have caused and thank you for your patience and understanding as we worked to resolve the issue.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 17 · 23:00 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. monitoringAug 6 · 12:35 UTC

   On August 4, 2026, BIM 360 Glue reached end of life (EOL). Questions? Please see the FAQ link below or contact Autodesk Support for assistance. https://help.autodesk.com/view/BIM360/ENU/?guid=GUID-5277DEB0-74F7-4314-84D7-3EF51BDC35D2

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 16 · 03:41 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 14 · 06:08 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 13 · 14:31 UTC

   On August 13, 2026, at 04:35 AM PDT, Autodesk identified an issue where customers were experiencing delays viewing uploaded files in Autodesk Viewer. Once the issue was resolved on August 13, 2026, at 06:56 AM PDT, Autodesk Viewer returned to normal operation. This is a retroactive notification as this issue did not display on the Autodesk Health Dashboard at that time. Thank you for your patience and understanding.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 13 · 14:12 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 13 · 12:10 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. postmortemAug 13 · 08:56 UTC

   **AUTODESK EVENT ANALYSIS** **Incident Number:** # COE-INC151641 **Incident Date:** July 29, 2026 ‌ ‌ **Summary** On July 29, 2026, between 10:14 AM PST and July 31, 2026, at 6:00 AM PST, Autodesk experienced an issue that prevented some customers with sufficient capacity from using APS Data Management, Autodesk Tandem, and Design Automation API for AutoCAD. Affected customers may have received 403 errors with an “API request capacity exceeded” message, and some capacity-related notifications were delayed by up to 14 hours. The issue affected a subset of customers globally. ‌ ‌ **Impacted Services** * Capacity Balance Service * APS - Automation API * APS – Data Management ‌ ‌ **Root Cause** * On July 23, 2026, a service update unintentionally caused duplicate capacity events to be processed, creating a backlog that delayed customer capacity updates. * Autodesk corrected the event processing issue and increased processing capacity to clear the backlog and restore normal service. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Add monitoring and alerts to identify unusual increases in capacity events and processing delays earlier. * Improve safeguards to prevent unnecessary capacity events from creating processing delays. * Add additional testing for changes that affect capacity processing. * Improve deployment and recovery procedures to support faster restoration of service. ‌ ‌ Thank you for your patience and understanding.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 12 · 18:06 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 12 · 00:56 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 11 · 23:53 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 10 · 15:24 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.

1. resolvedAug 10 · 11:44 UTC

   The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

Reported by Autodesk Health Dashboard on their status page.