Cisco Meraki Outage History

We are aware that some customers are having issues with Meraki cloud authentication, device to cloud connectivity and similar cloud services which rely on live network telemetry. Our engineers are actively working on remediating these issues.

Due to unforeseen congestion in communications proxies that serve the Campus Gateway and subset of Catalyst switches running in IOS-native mode, we are seeing a degradation in cloud connectivity. For Campus Gateway, connected Access Points previously configured and operating are unaffected. For some customers, this has resulted in issues connecting to their Campus Gateways or Catalyst switches to monitor or manage devices. Our engineers are aware of the problem, and are actively working towards a solution.

We have identified the problem and are working to remediate it now. We will provide further updates as the incident progresses.

We have identified the problem and are working to remediate it now. We will provide further updates as the incident progresses.

We have identified that a subset of devices running IPS/IDS are experiencing unexpected reboots. We are working on a remediation plan to restore device stability.

A mitigation is being deployed to our systems and we are continuing to monitor the results. Your MX device may experience a further onetime reboot now during this remediation.

We have identified the problem and are working to remediate it now. We will provide further updates as the incident progresses.

We have identified the cause of the issue, and our teams are actively working on putting mitigation in place.

We have identified the cause of the issue, and our teams are actively working on putting mitigation in place.

We are continuing to work on a fix for this issue.

We have identified the cause of the issue, and our teams are actively working on putting mitigation in place.

We understand that many customers cannot access the Client Details page in Meraki Dashboard. Our teams are aware of the issue, and are actively working to mitigate it.

We have identified the cause of the issue, and our teams are actively working on putting mitigation in place.

We have identified the cause of the issue, and our teams are actively working on putting a mitigation in place.

Our teams have identified the underlying cause of the issue, and are actively working on implementing a solution. Our teams have also determined that MT webhook alerts and related SMS messaging are also impacted.

We have identified a proximate cause for the Meraki Auto VPN issues and are working on a remediation plan to restore normal service. A fix will be deployed to that effect shortly.

Meraki engineering identified an issue with MX and vMX devices operating in Passthrough or VPN Concentrator mode and are working to test and deploy a fix. In the meantime, customers can reboot MX and vMX devices operating in those modes to restore service. For steps to reboot your device please follow the below knowledge base article: https://documentation.meraki.com/MX/Monitoring_and_Reporting/Using_the_MX_Live_tools#Reboot_Appliance

Customers potentially affected can restore service by rebooting MX and vMX appliances operating in Passthrough or VPN Concentrator mode. Meraki Engineering has tested a fix and are in the process of deploying it. Once deployed, we anticipate that MX and vMX appliances that have not already been rebooted will experience up to two minutes of disruption to the following services: AnyConnect, eBGP, Connection Monitoring, and IPSEC VPN Tunnels. For steps to reboot your device please follow the below knowledge base article: https://documentation.meraki.com/MX/Monitoring_and_Reporting/Using_the_MX_Live_tools#Reboot_Appliance

We are aware that some customers are having issues when trying to load the Video Wall page from the Meraki Dashboard. Engineers have identified a cause for this, and are actively working to remediate the issue. Video Walls viewed within the Meraki Vision Portal are unaffected. Please utilize the Vision Portal as a valid workaround until this issue is resolved.

We are aware of an issue that my be blocking customers' ability to update switch port configurations. Our teams are actively working on remediating the issue at this time. As a workaround, use of our API can be used to apply configuration updates to switch ports.

We are aware that some customers have reported issues saving changes on different dashboard pages. We believe this includes Site-to-site VPN, Group policies, MX Firewall, Traffic Shaping and Access Control. Our engineers believe they have identified the cause for this, and are actively working to remediate this issue.

Our teams have confirmed that the APIs that support updates to these pages are not affected by the current issues. As such, it is possible for customers to use the following API endpoints to update their configurations until these issues are resolved: https://developer.cisco.com/meraki/api-v1/update-network-group-policy/ https://developer.cisco.com/meraki/api-v1/update-network-appliance-vpn-site-to-site-vpn/ https://developer.cisco.com/meraki/api-v1/update-network-appliance-firewall-l-3-firewall-rules/ https://developer.cisco.com/meraki/api-v1/get-network-wireless-ssid-firewall-l-3-firewall-rules/ https://developer.cisco.com/meraki/api-v1/get-network-wireless-ssid-firewall-l-7-firewall-rules/