Mist Outage History

Started Sep 11, 2026, 02:01 PM UTC· resolved Sep 11, 2026, 02:11 PM UTC

1. investigating Sep 11, 2026, 02:01 PM UTC

   We are aware of a login issue with Global 03 (manage.ac2.mist.com). We are currently investigating. Networks are operational.

2. resolved Sep 11, 2026, 02:11 PM UTC

   We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Started Aug 03, 2026, 03:31 PM UTC· resolved Aug 03, 2026, 03:57 PM UTC

1. investigating Aug 03, 2026, 03:31 PM UTC

   We are currently experiencing an issue with login to Global 03 (manage.ac2.mist.com). We are actively investigating the issue. Devices remain connected to the cloud.

2. resolved Aug 03, 2026, 03:57 PM UTC

   The login issue on Global 03 is resolved. Thank you for your patience.

Read the full incident report →

Started Mar 02, 2026, 10:48 AM UTC· resolved Mar 12, 2026, 08:53 AM UTC

1. investigating Mar 02, 2026, 10:48 AM UTC

   The EMEA-03 (manage.ac6.mist.com) cloud environment is unavailable due to an upstream provider issue. We are monitoring the issue closely. All networks are operational. If you utilize the Mist Guest portal or External Guest portal options, those SSIDs would fail open by default, or fail closed if configured. Mist access assurance is operational.

2. identified Mar 02, 2026, 11:15 AM UTC

   We've confirmed the loss of availability is due to an issue with the upstream hosting provider in the region. We are monitoring closely and evaluating recovery options.

3. identified Mar 03, 2026, 01:31 PM UTC

   EMEA 03 ( manage.ac6.mist.com) cloud environment is still in the process of recovery. We are working with our hosting provider to resolve the issue. While the cloud visibility is still being recovered, your network should still be operational with client connectivity maintained.

4. identified Mar 04, 2026, 07:08 AM UTC

   We have been working continually to recover all services for our Global 03 instances, and are working with our hosting provider. We have partial recovery for some services- but full service restoration is still in process. We will provide another update by 6am PST, March 4th if not earlier.

5. identified Mar 04, 2026, 03:27 PM UTC

   Thank you for your continued patience. We are in the final phase of recovery, and expect to be enabling all services as part of our disaster recover process between 8pm -10pm UAE local time, March 4th. We willl provide an around 8:30pm UAE local time today on the services recovered.

6. monitoring Mar 04, 2026, 05:07 PM UTC

   We are in the process configuration recovery for wired and wireless. Once complete, we will begin bringing the Access Points online so that wireless visibility is restored. We request you to not make any configuration changes at this time. Wired devices connectivity will follow as well as we continue with recovery. We will update every hour to report on progress.

7. monitoring Mar 04, 2026, 06:40 PM UTC

   Access Points and Wireless Assurance Services are recovering with respect to full visibility for wireless services - AP and Client insights, SLEs, Events are all available for clients and APs as they come online. Some issues still being resolved: 1. Claiming new devices - this is in the process of resolution. Please do not claim any new APs to this environment at this time. 2. Guest Portal Config - please validate. 3. Firmware Upgrade for Wireless Access Points - currently still being resolved. Please do not upgrade APs at this time. Thank you again for your patience. We will update on progress on items above as well as when we begin wired assurance recovery.

8. monitoring Mar 04, 2026, 09:33 PM UTC

   **Update:** Access Points continue to be recovered on manage.ac6.mist.com. For customers using local DNS in your networks - please do refresh the DNS cache as that may cause APs to not come online in your organization. Firmware Upgrade service for APs which was previously in progress been recovered. Wired Assurance recovery is in progress - your switches in your inventory will start connecting back to cloud and show connected status. Wired Client telemetry per port will also begin to populate in the cloud instance for your organization. Please do not currently make any changes to configurations for your wired devices. There should be no connectivity disruption for end users - wired /wireless devices , nor is any disruption expected as we continue to recover all the services for manage.ac6.mist.com. Known issues still being resolved: 1. Claiming devices 2. NAC services 3.WAN Assurance for SSR and SRX 4. Premium Analytics 5. Location services ( BLE engagement and asset visibility) We will continue to provide updates as we progress on the above.

9. monitoring Mar 05, 2026, 06:40 AM UTC

   Majority of APs, Switches , WAN edges with Wireless, Wired & WAN Assurance have been recovered and should be showing as connected to your organization with telemetry coming through for wireless and wired clients. If you are not seeing them online, and there is a local DNS configured for your networks, please refresh the cache. Known issues still in the process of resolution: 1. Claiming devices 2. NAC services 3. Premium Analytics for wireless/wired/wan 4. Location services ( BLE engagement and asset visibility) 5. Guest Access Portal issues - if you are experiencing any issues post recovery your network- please do review the guest portal configuration, and make changes in case there is any aspect missing. Thank you again for your patience as we progress towards full recovery.

10. monitoring Mar 05, 2026, 07:35 PM UTC

    **Update** : We have full recovery for Wired and Wan assurance with switching and wan edges. On Wireless Assurance, we have full recovery except for a few issues reported on Guest portal- please validate the configuration and reconfigure if any inconsistencies are seen. We are continuing to progress on recovering the following: 1. Access Assurance 2. Location Services 3. Premium Analytics 4. Claiming devices Thank you for being patient and working with us as we continue our efforts towards full recovery.

11. monitoring Mar 06, 2026, 02:26 AM UTC

    **Update:** : In addition to full recovery for Wired and Wan assurance with switching and wan edges, we also have **_Access Assurance Services fully recovered_**. On Wireless Assurance, we have full recovery except for a few issues reported on Guest portal- please validate the configuration and reconfigure if any inconsistencies are seen. We are continuing to progress on recovering the following: 1. Location Services 2. Premium Analytics 3. Claiming devices Thank you for being patient and working with us as we continue our efforts towards full recovery.

12. monitoring Mar 06, 2026, 10:41 PM UTC

    **Update**:**Premium Analytics** service is also now fully recovered. Some telemetry/insight gaps may be seen for the time period during the outage with our cloud provider, but the network is now feeding telemetry to premium analytics service and updating dashboards. We are still working on the following two services: 1. Claiming Devices 2. Location Services Thank you for your patience as we continue towards full recovery in our disaster recovery operations.

13. monitoring Mar 12, 2026, 12:12 AM UTC

    **Update**: All services are now operational in the new disaster recovery environment that we set up to recover from the UAE instance. The only remaining issue is EX device claiming, which is actively being addressed. Thank you for your continued patience as we work to fully restore this capability

14. resolved Mar 12, 2026, 08:53 AM UTC

    **Final Update:** All services including claiming of devices have been fully restored in the new environment as part of disaster recovery of UAE instance.Thank you for your patience during this time.

Read the full incident report →

Started Oct 20, 2025, 08:09 PM UTC· resolved Oct 20, 2025, 11:21 PM UTC

1. monitoring Oct 20, 2025, 08:09 PM UTC

   Due to the ongoing AWS East service disruption, you may see sporadic impact on our Service Level expectation metrics and Insights telemetry not being rendered in the Mist portal UI. This is being observed on Global 03 environment only, and there is no disruption to the network devices ( AP/Switches/ WAN Edges) connecting to cloud, as well as no impact to end user/ end device client connections ( including Access Assurance) to the Mist environment for Global 03 despite the AWS East service degradation. We are sorry for this inconvenience and will keep you updated as we continue recovery.

2. resolved Oct 20, 2025, 11:21 PM UTC

   The telemetry is now being rendered for the Service Level Expectation Metrics and Insights in the Mist portal UI for the last hour in the Global 03 environment. Thank you again for your patience.

Read the full incident report →

Started Jun 12, 2025, 07:30 PM UTC· resolved Jun 12, 2025, 10:42 PM UTC

1. investigating Jun 12, 2025, 07:30 PM UTC

   We are aware of an issue where APIs and the UI have intermittent timeouts in the Global 02 (manage.gc1.mist.com), Global 04 (manage.gc2.mist.com), and EMEA 02 (manage.gc3.mist.com) environments. This is due to a global degradation in the cloud provider infrastructure. Network connectivity is not impacted, however the Mist captive portal may experience intermittent issues. We are recommending to avoid configuration changes until further notice as they may not get saved. We will update as we have more details. More information https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW#2c2sBHWU84yPDJ8y1ar4

2. identified Jun 12, 2025, 08:15 PM UTC

   The provider has identified the issue. Global 04 and EMEA 02 have recovered and are back to normal. Global 02 is still experiencing intermittent timeouts.

3. resolved Jun 12, 2025, 10:42 PM UTC

   We've now resolved the incident. All functions have returned to normal.

Read the full incident report →

Started Apr 30, 2025, 08:33 PM UTC· resolved Apr 30, 2025, 09:23 PM UTC

1. investigating Apr 30, 2025, 08:33 PM UTC

   We are aware of an issue with logging into Global 02 (manage.gc1.mist.com) and accessing the API. Please note networks remain functional. We are investigating the issue and will provide updates as we have them.

2. identified Apr 30, 2025, 09:10 PM UTC

   We have identified the issue and working on recovery.

3. monitoring Apr 30, 2025, 09:18 PM UTC

   We've fixed the core issue, and things are recovering.

4. resolved Apr 30, 2025, 09:23 PM UTC

   We've now resolved the incident. Thanks for your patience.

Read the full incident report →