Cisco Meraki

Affected: Dashboard, End User Device Connectivity

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-14 13:58 UTC

   We are investigating an issue with the Device to Cloud Communication that is impacting some users. Next update as soon as more information becomes available.

2. identified 2026-10-14 14:15 UTC

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

3. monitoring 2026-10-14 16:26 UTC

   We have deployed a fix and regular service is now restored. We will continue to monitor the situation. Please reach out to Meraki Support if you a re still experiencing a service interruption.

4. resolved 2026-10-14 17:10 UTC

   This incident is now resolved. We are sorry for any interruption to your service.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Affected: Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-05 23:44 UTC

   We are aware of an issue affecting Dashboard that may be causing pages not to load for some customers. At this time, device connectivity and user data remain unaffected. Our team is actively investigating the issue and working toward a resolution. We will provide another update...

2. monitoring 2026-08-05 23:58 UTC

   Our teams have identified the root cause and applied a mitigation. We are seeing improved behavior and are monitoring all systems to ensure they are operating as expected.

3. monitoring 2026-08-06 00:24 UTC

   We are continuing to monitor for any further issues. All systems are operating as expected right now.

4. resolved 2026-08-06 01:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Affected: API, API, API, API, Camera, Camera, Camera, Camera

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-15 17:43 UTC

   We are aware that some customers may be receiving failed responses from the generateSnapshot Camera API endpoint (receive an internal auth error). Our teams are actively investigating and have identified the issue.

2. resolved 2026-07-15 19:11 UTC

   Our teams have successfully mitigated the issue that was affecting customers. It has been confirmed that the the generateSnapshot Camera API endpoint is responding as expected. If you continue to have issues, please contact Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Affected: API, API, API, API, API, API

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-23 23:44 UTC

   We are aware that API requests are failing for many customers. Our teams are investigating the issue now, and we'll provide an update as soon as we know more.

2. monitoring 2026-06-24 00:24 UTC

   The issue was determined to be a routine infrastructure version upgrade that had an unexpected side-effect. Teams are in the process of rolling back the infrastructure to the last known-good version. We continue to monitor systems to confirm API calls are being responded to as...

3. resolved 2026-06-24 00:39 UTC

   The issue with API responses has been Resolved. If you continue to see issues with failed API calls, please reach out to Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Affected: Dashboard, Dashboard, Dashboard, Dashboard, Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-12 03:20 UTC

   We are aware of an issue affecting Dashboard that may be causing some pages to display incorrectly for some customers. Our team is actively investigating the issue and working toward a resolution. We will provide another update as soon as we have more information.

2. monitoring 2026-06-12 04:03 UTC

   Our teams have identified the root cause and applied a mitigation. We are seeing improved behavior and are monitoring all systems to ensure they are operating as expected.

3. resolved 2026-06-12 06:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Affected: Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, API, API, API, API, API, API, Network Device Connectivity, Network Device Connectivity, Network Device Connectivity, Network Device Connectivity, Network Device Connectivity, Network Device Connectivity, End User Device Connectivity, End User Device Connectivity, End User Device Connectivity, End User Device Connectivity, End User Device Connectivity, End User Device Connectivity, Access Point, Access Point, Access Point, Access Point, Access Point, Access Point, Switch, Switch, Switch, Switch, Switch, Switch, WAN appliance, WAN appliance, WAN appliance, WAN appliance, WAN appliance, WAN appliance, Camera, Camera, Camera, Camera

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-21 11:42 UTC

   We have identified an issue currently whereby some customers are unable to make changes in the Cisco Meraki dashboard. Our teams are currently actively working to resolve this issue. As a workaround to avoid this issue please review addresses populated on devices in your...

2. monitoring 2026-05-21 13:43 UTC

   Our teams have identified a root cause, and applied a mitigation. We are seeing improved behavior, and are monitoring for correct expected behavior across all systems.

3. resolved 2026-05-21 14:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Affected: Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-01 18:15 UTC

   We are aware of an issue with Dashboard where some customers may be having issues using the Live Tools and/or viewing live data regarding their network devices. We are actively triaging the issue, and will post an update when we know more.

2. monitoring 2026-05-01 18:34 UTC

   Our teams have identified a root cause, and applied a mitigation. We are seeing improved behavior, and are monitoring for correct expected behavior across all systems.

3. resolved 2026-05-01 23:14 UTC

   Our teams have confirmed that the prior issues regarding Live Tools and/or viewing live data for network devices have been resolved. All systems are now operating normally. If you continue to see issues, please contact Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Affected: Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-28 16:10 UTC

   We are aware of an issue with Dashboard where some customers may be having issues using the Live Tools and/or viewing live data regarding their network devices. We are actively triaging the issue, and will post an update when we know more.

2. monitoring 2026-04-28 17:41 UTC

   Our teams have identified a root cause, and applied a mitigation. We are seeing improved behavior, and are monitoring for correct expected behavior across all systems

3. resolved 2026-04-28 19:19 UTC

   Our teams have confirmed that the prior issues regarding Live Tools and/or viewing live data for network devices have been resolved. All systems are now operating normally. If you continue to see issues, please contact Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-14 19:11 UTC

   We are aware of an issue where emails sent to Meraki support are bouncing. If you need to contact Meraki support, please call in to any of our hotlines or provide case updates through the Support Center of the Meraki Dashboard For information on our different regional hotlines,...

2. monitoring 2026-04-14 19:22 UTC

   A fix has been implemented and we are monitoring the results

3. resolved 2026-04-14 19:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-12-15 18:09 UTC

   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.

2. monitoring 2025-12-15 19:24 UTC

   A mitigation is in place that has restored normal functionality. Our engineering teams continue to monitor this solution to confirm correct behavior.

3. resolved 2025-12-15 21:15 UTC

   This incident is now resolved. All systems should be operating normally at this time. If you continue to experience issues, please feel free to contact Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-20 15:08 UTC

   We are currently experiencing issues connecting to the Support team via phones. Our team is actively working on this. For new cases, please open a case and choose the "Call In" option including "Outage Oct/20" in the subject. For existing cases, please provide a case comment...

2. monitoring 2025-10-20 16:45 UTC

   We are actively monitoring the situation related to issues connecting to the Support team via phone. If you continue to experience issues attempting to contact us via our Support Hotline please follow these steps. For new cases, please open a case and choose the "Call In" option...

3. monitoring 2025-10-20 21:38 UTC

   We are continuing to monitor the situation related to issues connecting to the Support team via phone, with indications that the service is recovering. If you continue to experience issues attempting to contact us via our Support Hotline please follow these steps. For new cases,...

4. resolved 2025-10-21 01:07 UTC

   The issues connecting to the Support team via phone are now resolved. Thank you for your patience.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-15 19:46 UTC

   We are currently experiencing issues connecting to the Support team via phone. Our team is actively working to resolve this as quickly as possible. For new cases please open a case and choose the "Call In" option, for existing cases please provide a case comment with the phrase...

2. monitoring 2025-10-15 21:49 UTC

   The issue involving customers being unable to reach our support team via phone has been resolved. We are actively monitoring the situation but if you continue to experience issues attempting to contact us via our Support Hotline please follow these steps. For new cases please...

3. resolved 2025-10-15 22:31 UTC

   The issue involving customers being unable to reach our support team via phone has been resolved. If you continue to experience issues attempting to contact us via our Support Hotline please follow these steps. For new cases please open a case and choose the "Call In" option,...

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-10-08 18:57 UTC

   We are aware that some customers using MX (firewall) devices may be experiencing issues with DDNS. We have pinpointed the source of the issue, and are in the process of rolling out a mitigation.

2. resolved 2025-10-08 20:17 UTC

   The mitigation for the earlier MX (firewall) DDNS issues has been fully propagated and verified. Normal DDNS functionality has been restored to all MX (firewall) devices. If you continue to have issues, please contact Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-01 20:52 UTC

   We are currently investigating an issue causing slower load times and intermittent timeout errors when accessing dashboard pages for organizations with subscription-based licensing. Affected users may encounter delays or receive timeout messages when loading these pages....

2. monitoring 2025-10-01 21:41 UTC

   The underlying cause of increased load times and intermittent timeouts for dashboard pages in subscription-based organizations has been identified. We have implemented changes to improve system performance, and impacted users should now see normal load times. We are closely...

3. resolved 2025-10-01 22:41 UTC

   The recent issue causing slow load times and intermittent timeouts for dashboard pages in subscription-based organizations has been resolved. System performance has returned to normal, and all affected services are operating as expected. If you continue to experience any issues,...

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-07-15 16:47 UTC

   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...

2. resolved 2025-07-15 18:11 UTC

   Our engineering teams have implemented changes to mitigate the impact of the previously-reported communications issues. Our teams consider this issue resolved at this time. If you continue to have issues, please reach out to Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-21 23:29 UTC

   We are aware that a subset of newly added devices are having issues connecting to the Cisco Meraki Dashboard. Devices already online and connected should not be experiencing any impact. Our teams are actively investigating the issue.

2. identified 2025-04-22 01:27 UTC

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

3. monitoring 2025-04-22 02:11 UTC

   Our teams have deployed a fix and all services should be restored now. We are continuing to monitor the situation.

4. resolved 2025-04-22 03:15 UTC

   This incident is now resolved. All systems are performing as expected. If you continue to experience issues, please contact Cisco Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-17 09:30 UTC

   We are aware that some customers in EMEA are experiencing Cloud Monitored Catalyst Switches appearing offline in the Dashboard and we are actively investigating this issue. We will provide the next update as soon as more information becomes available.

2. investigating 2025-04-17 12:50 UTC

   We are continuing to investigate this issue. We will provide the next update as soon as more information becomes available.

3. identified 2025-04-17 13:08 UTC

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

4. monitoring 2025-04-17 16:24 UTC

   Our teams have deployed a fix and regular service is now restored. We are continuing to monitor the situation.

5. resolved 2025-04-17 16:50 UTC

   This incident is now resolved. All systems are performing as expected. If you continue to experience issues, please contact Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-16 11:27 UTC

   We are aware that some customers are experiencing Meraki MX reboots, and we are actively investigating this issue. We will provide the next update as soon as more information becomes available.

2. identified 2025-04-16 12:45 UTC

   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.

3. identified 2025-04-16 13:54 UTC

   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.

4. monitoring 2025-04-16 14:44 UTC

   We have deployed a fix and services are restored. We will continue to monitor the situation. Please reach out to Meraki Support if you continue to experience unexpected MX reboots.

5. resolved 2025-04-16 17:16 UTC

   This incident is now resolved. All systems are performing as expected. If you continue to experience issues, please contact Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-04-01 03:12 UTC

   We are investigating an issue with the Client Details Page that is impacting some users. Switching to the old version of the page should allow the page to load and can be used as a workaround in the meantime.

2. identified 2025-04-01 03:20 UTC

   We have identified the problem and are working to remediate it now. We will provide further updates as the incident progresses. Please continue using the old version of the page as a workaround in the meantime.

3. identified 2025-04-01 07:58 UTC

   We have identified the cause of the issue, and our teams are actively working on putting mitigation in place. Please continue using the old version of the page as a workaround in the meantime.

4. identified 2025-04-01 11:54 UTC

   We have identified a fix for this issue. It is currently going through vigorous testing before being deployed to our systems. Please continue using the old version of the page as a workaround in the meantime.

5. monitoring 2025-04-01 12:19 UTC

   Our teams are in the process of rolling out a mitigation to the Meraki Cloud. Some customers may have already regained access to the Clients Details page. These efforts are active, and ongoing.

6. investigating 2025-04-01 13:25 UTC

   We are investigating further performance issues with the Client Details Page since a fix was deployed that is impacting some users. Switching to the old version of the page should avoid these issues and can be used as a workaround in the meantime.

7. identified 2025-04-01 14:18 UTC

   We have identified the problem and are working to remediate it now. We will provide further updates as the incident progresses. Please continue using the old version of the page as a workaround in the meantime.

8. monitoring 2025-04-01 16:34 UTC

   Our teams are in the process of rolling out a mitigation to the Meraki Cloud. These efforts are active and ongoing.

9. resolved 2025-04-01 20:24 UTC

   This incident is now resolved. All systems are performing as expected. If you continue to experience issues, please contact Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-01-03 22:30 UTC

   We are investigating an issue with the Meraki Dashboard that is impacting some users. Next update as soon as more information becomes available.

2. identified 2025-01-03 22:36 UTC

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

3. monitoring 2025-01-03 22:40 UTC

   We have deployed a fix and regular service is now restored. We will continue to monitor the situation. Please reach out to Meraki Support if you are still experiencing a service interruption.

4. resolved 2025-01-03 22:52 UTC

   This incident is now resolved. We are sorry for any interruption to your service.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-11-19 10:50 UTC

   We are aware that creating video exports for MV camera deployments is currently failing for some customers. Our teams are actively investigating the issue.

2. identified 2024-11-19 11:46 UTC

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

3. monitoring 2024-11-19 13:49 UTC

   A mitigation has been deployed to our systems and we are continuing to monitor the results.

4. resolved 2024-11-19 14:55 UTC

   This incident is now resolved. All systems are performing as expected. If you continue to experience issues, please contact Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-11-18 16:21 UTC

   We are aware that creating video exports for MV camera deployments is currently failing. Our teams are actively investigating the issue

2. resolved 2024-11-18 17:05 UTC

   This incident is now resolved. All systems are performing as expected. If you continue to experience issues, please contact Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-11-15 07:13 UTC

   We are aware that some customers are having difficulty either logging into or accessing pages on Cisco Meraki Dashboard. Our teams are actively working on remediating this issue.

2. investigating 2024-11-15 07:14 UTC

   We are continuing to investigate this issue.

3. identified 2024-11-15 08:17 UTC

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

4. identified 2024-11-15 08:19 UTC

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

5. monitoring 2024-11-15 10:28 UTC

   A mitigation has been deployed to our systems and we are continuing to monitor the results.

6. monitoring 2024-11-15 12:45 UTC

   We are continuing to monitor our systems for correct behaviour.

7. resolved 2024-11-15 14:50 UTC

   This incident is now resolved. All systems are performing as expected. If you continue to experience issues, please contact Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-11-08 05:04 UTC

   We are aware that a subset of devices are having issues connecting to the Cisco Meraki Dashboard in China (dashboard.meraki.cn). Devices currently showing offline should still be able to operate and pass client traffic using its last known configuration. Our teams are actively...

2. identified 2024-11-08 05:16 UTC

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

3. monitoring 2024-11-08 05:30 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2024-11-08 07:36 UTC

   This incident is now resolved. All systems are performing as expected. If you continue to experience issues, please contact Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-10-28 17:46 UTC

   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.

2. monitoring 2024-10-28 18:39 UTC

   Our teams are in the process of rolling out a mitigation to the Meraki Cloud. Some customers may have already regained access to the Clients Details page. These efforts are active, and ongoing.

3. resolved 2024-10-28 19:33 UTC

   This incident is now resolved. All systems are performing as expected. If you continue to experience issues, please contact Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-10-14 22:32 UTC

   We are aware that video backup with MV Cloud Archive is currently degraded. We have a team actively investigating.

2. resolved 2024-10-14 23:29 UTC

   This incident is now resolved. Cloud Archive storage and retrieval is working as expected for all MV cameras. If you continue to experience issues, please contact Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-10-10 07:11 UTC

   We are aware that customers are having issues connecting to the Meraki Dashboard in China (dashboard.meraki.cn). Our teams are actively investigating the issue.

2. identified 2024-10-10 07:31 UTC

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

3. monitoring 2024-10-10 08:09 UTC

   Our teams are deploying a mitigation to our systems, and are continuing to monitor them for normal function.

4. resolved 2024-10-10 08:30 UTC

   This incident is now resolved. All services are performing as expected. If you continue to have issues, please contact Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-10-09 23:26 UTC

   We are aware that a significant number of customers may be having challenges connecting to the Meraki Dashboard, as well as associated tools such as Vision Portal. We have a team actively investigating.

2. identified 2024-10-09 23:43 UTC

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

3. monitoring 2024-10-10 00:43 UTC

   Our teams are deploying a mitigation to our systems, and are continuing to monitor them for normal function.

4. resolved 2024-10-10 03:28 UTC

   This incident is now resolved. All services are performing as expected. If you continue to have issues, please contact Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-10-01 20:05 UTC

   We are aware that some customers may not be receiving alerts via webhooks as expected. Our teams are actively investigating this.

2. identified 2024-10-01 20:39 UTC

   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.

3. resolved 2024-10-02 00:55 UTC

   This incident is now resolved. All webhook and SMS alerts are being issued as expected. If you experience any issues with alert delivery, please contact Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-20 16:30 UTC

   We are aware that some customers are experiencing intermittent issues accessing the Meraki Dashboard. An elevated level of intermittent failures for API calls or requests to Meraki Authentication services may also be possible. These issues are actively being investigated.

2. investigating 2024-09-20 19:00 UTC

   We are aware that some customers are experiencing intermittent access issues with the Meraki dashboard and may receive alerts about device connectivity. These devices will continue to function normally and pass network traffic. We are also aware of reports of intermittent API...

3. identified 2024-09-20 20:00 UTC

   Meraki Engineering identified a problem causing intermittent access issues with the Meraki dashboard as well as alerts about device connectivity. These devices will continue to function normally and pass network traffic. We are also aware of reports of intermittent API call and...

4. identified 2024-09-20 21:00 UTC

   Meraki Engineering continues to work towards identified remediation steps to restore full service. As mentioned in previous updates, customers may experience intermittent access issues with the Meraki dashboard as well as alerts about device connectivity. These devices will...

5. identified 2024-09-20 22:02 UTC

   Meraki Engineering continues to validate and implement remediation efforts to restore full service across the Meraki platform. As mentioned in previous updates, customers may experience intermittent access issues with the Meraki dashboard as well as alerts about device...

6. monitoring 2024-09-21 02:00 UTC

   Meraki Engineering has successfully normalized connectivity and is currently monitoring to ensure the stability of all Meraki services.

7. resolved 2024-09-24 18:00 UTC

   This incident is now resolved. If you are still experiencing any issues, please contact Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-09-18 06:25 UTC

   We are aware that some customers are experiencing Meraki Auto VPN issues, and we are actively investigating. Rebooting MX/vMX devices operating in passthrough mode can be used as a workaround in the meantime.

2. identified 2024-09-18 08:38 UTC

   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.

3. investigating 2024-09-18 11:20 UTC

   We continue to investigate the root cause of Meraki Auto VPN connectivity issues in MX and vMX appliances running in passthrough mode and are working to remediate them. Customers can restore service by rebooting the appliance in Passthrough Mode via the Meraki dashboard. For...

4. identified 2024-09-18 14:21 UTC

   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...

5. identified 2024-09-18 15:46 UTC

   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...

6. monitoring 2024-09-18 17:30 UTC

   Meraki Engineering has begun to deploy the fix to this issue. It is expected to be complete by approximately 18:30 UTC. 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...

7. resolved 2024-09-18 19:02 UTC

   This incident is now resolved. If you are still experiencing any issues, please contact Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-09-17 23:48 UTC

   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....

2. resolved 2024-09-18 00:18 UTC

   This incident is now resolved. Video Wall within Meraki Dashboard should now operate as expected. If you continue to have issues, please contact Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-09-03 19:00 UTC

   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.

2. monitoring 2024-09-03 20:06 UTC

   Our engineering teams have deployed a fix which mitigates impact to customers. Customers should once again be able to successfully update switch port configurations via the Meraki Dashboard. We will continue to monitor systems to verify correct behavior.

3. resolved 2024-09-04 00:24 UTC

   This incident is now Resolved. All systems are operating as expected. If you continue to have issues, please reach out to Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-08-26 21:16 UTC

   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...

2. identified 2024-08-26 21:51 UTC

   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:...

3. monitoring 2024-08-26 23:55 UTC

   Our teams are in the process of deploying a fix which will mitigate impact for customers. We will continue to monitor systems for correct behavior as the fix is rolled out.

4. resolved 2024-08-27 00:27 UTC

   This incident is now Resolved. All systems are performing as expected. If you are still experiencing any issues, please contact Meraki Customers Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-08-23 21:08 UTC

   We are aware that some customers are having difficulty either logging into or accessing pages on Meraki Dashboard. Further, some of the functionality in Dashboard page footers and utilities may not behave as expected. Our engineering teams have identified a likely cause, and are...

2. monitoring 2024-08-23 21:53 UTC

   Our engineering teams have deployed a fix to mitigate impact to customers. To ensure you can take advantage of this fix, you will need to perform a cache-less refresh of your web browser. On a Mac, shift-clicking the Reload button should work, or on Windows, Ctrl-clicking the...

3. resolved 2024-08-23 23:16 UTC

   This incident is now resolved. All systems are operating normally. If you continue to see issues, please feel free to contact Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-08-15 20:01 UTC

   We are aware that some customers are experiencing issues when attempting to authenticate to the Meraki Dashboard via an Service Provider-initiated SAML connection. Our teams are actively working to mitigate this issue.

2. resolved 2024-08-15 21:00 UTC

   Our teams have implemented a mitigation for these SAML login issues. All systems are performing normally. If you continue to have issues, please reach out to Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-07 18:24 UTC

   We are aware that some customers may be having issues with viewing video from cameras that are not in their local network. Our teams are actively investigating.

2. resolved 2024-08-07 20:50 UTC

   Our teams have addressed the issue that was preventing playback of video from cameras not in a local network. Normal functionality has been fully restored. If you continue to experience issues, please reach out to Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-08-07 00:10 UTC

   We are aware that some customers may be having issues with Dashboard Live Tools and the display of live data (uplink traffic, port listings, etc.) regarding Meraki devices in Dashboard. Our teams are actively working on remediating this issue.

2. resolved 2024-08-07 01:43 UTC

   The issue with Live Tools has been addressed. This issue is now Resolved. If you continue to experience difficulties, please don't hesitate to contact Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-07-30 18:19 UTC

   Cisco is aware of an issue with one of our third party certificate authority providers. We are currently reviewing our certificate inventory to understand impact and updating certificates as needed. We will continue to actively monitor this issue. Any customers needing...

2. identified 2024-07-31 05:33 UTC

   One of our third-party vendors identified an issue requiring some of their customers, including Cisco Meraki, to rotate certain certificates. As a result, we are rotating the RADIUS certificate for Meraki Cloud Authentication on Friday, August 2, 2024, 21:00 UTC. If you do not...

3. identified 2024-08-01 21:36 UTC

   The RADIUS certificate rotation timeline has been expedited and will take place starting at 01:30 UTC on Friday, August 2, 2024. Please follow the steps outlined in our documentation to ensure continuous service. If you need assistance or have additional questions, please reach...

4. resolved 2024-08-05 19:06 UTC

   All impacted certificates have been rotated. This issue is now Resolved. If you are experiencing any issues, please consult this KB article, or reach out to Meraki Technical Support .

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-07-23 23:29 UTC

   We are aware that some customers may be experiencing failures for SMS and webhook alerts for MT devices. Our remediation teams are actively investigating this.

2. identified 2024-07-24 02:28 UTC

   While our remediation team continues working towards a mitigation of this issue, we wanted to clarify the impact: all webhook-based alerting, as well as MT SMS based alerting is currently in-scope for impact.

3. resolved 2024-07-24 03:40 UTC

   Our remediation team has deployed a fix, and verified all alerts are being dispatched as expected. This incident is now resolved. If you continue to encounter any issues, please feel free to reach out to Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-07-12 23:30 UTC

   We are aware of issues with email communications from Meraki Dashboard to customers. This may be affecting One Time Password (OTP) email logins, as well as password reset, and other types of emails such as alert emails and sponsor requests. Our teams are actively working on...

2. resolved 2024-07-13 00:48 UTC

   Our teams have deployed a mitigation that addresses the earlier issues with email. Emails are being successfully sent at this time. This incident is now Resolved. Please retry the workflow for any failed emails, if desired. If you continue to have issues, please feel free to...

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-07-11 15:53 UTC

   We are aware that customers may be having issues streaming stored video from the Vision Portal. Teams have identified the cause of this, and are actively working on deploying a fix. Customers can continue to stream stored video directly from the Meraki Dashboard.

2. identified 2024-07-11 15:58 UTC

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

3. monitoring 2024-07-11 16:31 UTC

   Our teams have deployed a fix to mitigate the issue with Vision Portal streaming stored video content. In order for customers to take advantage of this fix, they will need to either refresh the page or click the Update button is in the upper right-hand corner of the Vision...

4. resolved 2024-07-11 19:12 UTC

   This incident is now resolved. All systems are operating as expected. If you continue to have issues, please don't hesitate to reach out to Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-14 10:06 UTC

   We are investigating an issue with the Meraki Dashboard that is impacting some users. Next update as soon as more information becomes available.

2. identified 2024-06-14 10:22 UTC

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

3. monitoring 2024-06-14 11:35 UTC

   We have deployed a fix and regular service is now restored. We will continue to monitor the situation. Please reach out to Meraki Support if you are still experiencing a service interruption.

4. resolved 2024-06-14 11:47 UTC

   This incident is now resolved. We are sorry for any interruption to your service.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-13 23:19 UTC

   We are aware that some customers are experiencing issues accessing the Meraki dashboard. We have teams actively investigating this now.

2. identified 2024-06-13 23:38 UTC

   We have identified a cause for the current customer issues and are actively working on deploying a mitigation.

3. monitoring 2024-06-14 00:30 UTC

   Our teams have deployed a fix that has mitigated impact to customers. Our teams will continue to monitor systems to confirm correct behavior.

4. resolved 2024-06-14 01:03 UTC

   This incident is now resolved. All systems are operating as expected. If you continue to experience issues, please reach out to Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-07 07:50 UTC

   We are aware that a number of customers have reported issues claiming devices into organizations after the scheduled maintenance concluded earlier today. Engineers are actively investigating the root cause of the issue.

2. identified 2024-06-07 08:31 UTC

   While the resolution is still in progress, claiming devices via API can be used as a workaround using this endpoint: https://developer.cisco.com/meraki/api-v1/claim-into-organization-inventory/. For more information about the API, please refer to this Knowledge Base Article:...

3. monitoring 2024-06-07 13:46 UTC

   Our teams have deployed a fix which has mitigated impact for customers. We will continue to monitoring systems for correct behavior.

4. resolved 2024-06-07 20:08 UTC

   This incident is now Resolved. All systems are performing as expected. If you are still experiencing any issues, please contact Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-06-03 21:33 UTC

   We are aware that a number of customers have reported issues logging into the Meraki Dashboard. Engineers are actively working to mitigate the impact to customers.

2. monitoring 2024-06-03 22:31 UTC

   Our incident remediation team has put a fix in place to mitigate impact to customers. You should now be able to access the Meraki Dashboard as usual. Our teams will continue to monitor systems to confirm correct behavior.

3. monitoring 2024-06-03 23:52 UTC

   While the majority of systems have been fully recovered for some time, there is a small handful of machines that are continuing to exhibit issues, which may affect a small subset of customers. We are continuing our investigation and remediation of these remaining systems.

4. resolved 2024-06-04 00:34 UTC

   This incident is now Resolved. If you continue to experience any issues accessing the Meraki Dashboard, please feel free to contact Meraki Customer Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-05-29 19:26 UTC

   We are aware that customers may be having challenges with sentry wifi authentication. Our remediation teams have identified the issue, and are actively working to mitigate impact to customers.

2. resolved 2024-05-29 19:54 UTC

   Our teams have deployed a fix that has mitigated impact to customers. Normal sentry wifi authentication functionality has been restored, and systems are operating as expected. If you continue to have issues, please feel free to contact Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-05-23 03:27 UTC

   We are aware that Meraki Dashboard customers using the China Dashboard may be encountering issues when trying to load Splash Pages. Our engineers have identified what they believe to be the source of the issue, and are actively working on applying a fix.

2. monitoring 2024-05-23 03:45 UTC

   A fix for the issue loading splash pages in the China dashboard has been rolled out and verified. If you experience further issues, please don't hesitate to contact Meraki Support.

3. resolved 2024-05-23 04:45 UTC

   After monitoring, this issue is believed to be fully resolved. If you experience further issues, please don't hesitate to contact Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-05-21 21:11 UTC

   We are aware of Meraki Dashboard customers may be encountering issues with the left-hand navigation in the Meraki Dashboard. Engineers have identified what they believe to be the source of the issue, and are actively working on applying a fix.

2. identified 2024-05-21 21:18 UTC

   We are aware that Meraki Dashboard customers may be encountering issues with how the Meraki Dashboard is rendered, as well as navigation within the Dashboard. Engineers have identified the issue and are actively working on applying a fix.

3. resolved 2024-05-21 23:38 UTC

   A fix for the rendering and navigation issues with Meraki Dashboard has been rolled out and verified. Meraki Dashboard is now operating as expected. If you experience further issues, please don't hesitate to contact Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-05-06 19:25 UTC

   We are investigating an issue with the Meraki Dashboard that is impacting some users. Next update as soon as more information becomes available.

2. identified 2024-05-06 19:57 UTC

   Our teams have isolated what we believe to be the root of the performance issues that some customers may be experiencing, and have implemented mitigative measures. Customers should begin to see a return to normal performance soon.

3. resolved 2024-05-06 20:50 UTC

   This incident is now Resolved. All systems are operating normally. If you are still having issues, please don't hesitate to reach out to Meraki Support.

Excerpts are shortened. Read the full incident on Cisco Meraki's status page.