Autodesk incident

Multiple Autodesk Products

Minor Resolved View vendor source →

Autodesk experienced a minor incident on June 25, 2026 affecting Autodesk account and AutoCAD Web and 1 more component, lasting 3h 25m. The incident has been resolved; the full update timeline is below.

Started
Jun 25, 2026, 03:15 PM UTC
Resolved
Jun 25, 2026, 06:41 PM UTC
Duration
3h 25m
Detected by Pingoru
Jun 25, 2026, 03:15 PM UTC

Affected components

Autodesk accountAutoCAD WebAutodesk.comBIM 360 Glue [EOL]Forma - Admin Console (Canada)Forma - Admin Console (Germany)Forma - Admin Console (India)Forma - Admin Console (Japan)Forma - Admin Console (UK)Forma Mobile App

Update timeline

  1. investigating Jun 25, 2026, 03:15 PM UTC

    We are investigating an issue where customers are experiencing latency during authentication while accessing Admin/Project Admin within user profile and the ACC platform. We are actively looking into this and we will provide an update within 60 minutes or sooner if we have more information to share.

  2. investigating Jun 25, 2026, 03:32 PM UTC

    We are continuing to investigate this issue where customers are experiencing latency while accessing multiple Autodesk products. We are actively looking into this and we will provide an update within 60 minutes or sooner if we have more information to share.

  3. investigating Jun 25, 2026, 03:53 PM UTC

    We are continuing to investigate where customers are experiencing latency while accessing multiple Autodesk products. We subsequently determined that the cause of this issue was also affecting Autodesk account, Forma Mobile App, AutoCAD Web, BIM 360 Glue, Revit Cloud Worksharing / Cloud Models. We will provide an update within 60 minutes or sooner if we have more information to share.

  4. investigating Jun 25, 2026, 04:52 PM UTC

    We are continuing to investigate where customers are experiencing latency while accessing multiple Autodesk products. We subsequently determined that the cause of this issue was also affecting Autodesk.com and TradeTapp. We will provide an update within 60 minutes or sooner if we have more information to share.

  5. identified Jun 25, 2026, 05:53 PM UTC

    We have identified the cause of the issue where customers are experiencing latency while accessing multiple Autodesk products. Our team is actively working on resolving this as quickly as possible. We will provide an update within 60 minutes or sooner if we have more information to share.

  6. resolved Jun 25, 2026, 06:41 PM UTC

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

  7. postmortem Jul 07, 2026, 01:22 PM UTC

    **AUTODESK EVENT ANALYSIS** **Incident Number:** coe-inc147370 **Incident Date:** June 25, 2026 ‌ **Summary** On June 25,2026 between 07:17 AM PDT and 11:22 AM PDT, Autodesk experienced a service disruption that impacted customers using ACC Login, Forma Mobile, AutoCAD Web, BIM 360 Glue, Revit Cloud Worksharing, Autodesk account, TradeTapp, the Autodesk Store and Forma Carbon Insights in the US, EU, UK, Japan, Canada, Germany, India, and Australia regions. During the incident, some users were unable to sign in, while others experienced slower-than-normal application performance. ‌ **Impacted Services** * ACC Login * Forma Mobile * AutoCAD Web * BIM 360 Glue * Revit Cloud Worksharing * Autodesk account * TradeTapp * [Autodesk.com](http://Autodesk.com) purchase flow * Forma Carbon Insights. ‌ **Root Cause** * On June 25, 2026, a deployment of a new service inadvertently modified the access permissions used by the User Profile service. As a result, the User Profile service was unable to access a required internal messaging component, causing the service disruption. * Resolution was achieved by rerunning the previous production deployment pipeline to restore the correct IAM policies. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Implement new monitoring and alerting to quickly detect service startup failures and access permission issues, enabling faster identification and response to similar incidents. * Update deployment process to isolate service configurations, preventing changes to one service from inadvertently affecting another. ‌ Thank you for your patience and understanding.