Störungsverlauf von Cisco Meraki

1. 28. Oktober 2026 um 11:29 UTCinvestigating

   Wir untersuchen ein Problem mit der SSO-Anmeldung am Meraki Dashboard, das sich auf die Benutzer auswirkt. Für Benutzer, die sich nicht direkt über SSO am Dashboard anmelden können, sollte die Änderung der URL durch Trimmen von /login/saml/email verification erfolgreiche Logins ermöglichen. Nächste Aktualisierung, sobald weitere Informationen verfügbar sind.

2. 28. Oktober 2026 um 11:55 UTCidentified

   Wir haben das Problem erkannt und arbeiten daran, es jetzt zu beheben. Wir werden weitere Updates bereitstellen, wenn der Vorfall fortschreitet. Für Benutzer, die sich nicht direkt über SSO am Dashboard anmelden können, sollte die Änderung der URL durch Trimmen von /login/saml/email verification erfolgreiche Logins ermöglichen. Nächste Aktualisierung, sobald weitere Informationen verfügbar sind.

3. 28. Oktober 2026 um 12:27 UTCmonitoring

   Unsere Teams haben die Ursache identifiziert und eine Milderung angewendet. Wir sehen ein verbessertes Verhalten und überwachen alle Systeme, um sicherzustellen, dass sie wie erwartet funktionieren.

4. 28. Oktober 2026 um 12:46 UTCresolved

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

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. Oktober 2026 um 13:58 UTCinvestigating

   Wir untersuchen ein Problem mit der Device to Cloud-Kommunikation, das einige Benutzer betrifft. Nächste Aktualisierung, sobald weitere Informationen verfügbar sind.

2. 14. Oktober 2026 um 14:15 UTCidentified

   Wir haben das Problem erkannt und arbeiten daran, es jetzt zu beheben. Wir werden weitere Updates bereitstellen, wenn der Vorfall fortschreitet.

3. 14. Oktober 2026 um 16:26 UTCmonitoring

   Wir haben eine Reparatur bereitgestellt und der reguläre Service ist jetzt wiederhergestellt. Wir werden die Situation weiterhin beobachten. Bitte wenden Sie sich an den Meraki Support, wenn Sie immer noch eine Serviceunterbrechung erleben.

4. 14. Oktober 2026 um 17:10 UTCresolved

   Dieser Vorfall ist nun gelöst. Es tut uns leid für jede Unterbrechung Ihres Dienstes.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 5. August 2026 um 23:44 UTCinvestigating

   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 as soon as we have more information.

2. 5. August 2026 um 23:58 UTCmonitoring

   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. 6. August 2026 um 00:24 UTCmonitoring

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

4. 6. August 2026 um 01:48 UTCresolved

   This incident has been resolved.

1. 15. Juli 2026 um 17:43 UTCidentified

   Wir sind uns bewusst, dass einige Kunden möglicherweise fehlgeschlagene Antworten vom generateSnapshot Camera API-Endpunkt erhalten (einen internen Auth-Fehler erhalten). Unsere Teams untersuchen aktiv und haben das Problem identifiziert.

2. 15. Juli 2026 um 19:11 UTCresolved

   Unsere Teams haben das Problem, das die Kunden betraf, erfolgreich gemildert. Es wurde bestätigt, dass der generateSnapshot Camera API-Endpunkt wie erwartet reagiert. Wenn Sie weiterhin Probleme haben, wenden Sie sich bitte an den Kundensupport.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 23. Juni 2026 um 23:44 UTCinvestigating

   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. 24. Juni 2026 um 00:24 UTCmonitoring

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

3. 24. Juni 2026 um 00:39 UTCresolved

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

1. 12. Juni 2026 um 03:20 UTCinvestigating

   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. 12. Juni 2026 um 04:03 UTCmonitoring

   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. 12. Juni 2026 um 06:01 UTCresolved

   This incident has been resolved.

1. 21. Mai 2026 um 11:42 UTCidentified

   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 dashboard based on the invalid characters shown in the error message received when attempting to save.

2. 21. Mai 2026 um 13:43 UTCmonitoring

   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. 21. Mai 2026 um 14:10 UTCresolved

   This incident has been resolved.

1. 1. Mai 2026 um 18:15 UTCinvestigating

   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. 1. Mai 2026 um 18:34 UTCmonitoring

   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. 1. Mai 2026 um 23:14 UTCresolved

   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.

1. 28. April 2026 um 16:10 UTCinvestigating

   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. 28. April 2026 um 17:41 UTCmonitoring

   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. 28. April 2026 um 19:19 UTCresolved

   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.

1. 14. April 2026 um 19:11 UTCinvestigating

   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, please visit meraki.cisco.com/meraki-support/overview/

2. 14. April 2026 um 19:22 UTCmonitoring

   A fix has been implemented and we are monitoring the results

3. 14. April 2026 um 19:28 UTCresolved

   This incident has been resolved.

1. 15. Dezember 2025 um 18:09 UTCidentified

   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. 15. Dezember 2025 um 19:24 UTCmonitoring

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

3. 15. Dezember 2025 um 21:15 UTCresolved

   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.

1. 20. Oktober 2025 um 15:08 UTCinvestigating

   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 with the phrase "Outage".

2. 20. Oktober 2025 um 16:45 UTCmonitoring

   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 including "Outage Oct/20" in the subject. For existing cases, please provide a case comment with the phrase "Outage. We appreciate your patience and understanding as we work to restore full service.

3. 20. Oktober 2025 um 21:38 UTCmonitoring

   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, 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 with the phrase "Outage. We appreciate your patience and understanding as we work to restore full service.

4. 21. Oktober 2025 um 01:07 UTCresolved

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

1. 15. Oktober 2025 um 19:46 UTCinvestigating

   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 "10-15-Outage" and we will reach out to you as soon as possible. We appreciate your patience and understanding as we work to restore full service.

2. 15. Oktober 2025 um 21:49 UTCmonitoring

   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 open a case and choose the "Call In" option, for existing cases please provide a case comment with the phrase "10-15-Outage" and we will reach out to you as soon as possible. We appreciate your patience and understanding as we work to restore full service.

3. 15. Oktober 2025 um 22:31 UTCresolved

   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, for existing cases please provide a case comment with the phrase "10-15-Outage" and we will reach out to you as soon as possible.

1. 8. Oktober 2025 um 18:57 UTCmonitoring

   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. 8. Oktober 2025 um 20:17 UTCresolved

   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.

1. 1. Oktober 2025 um 20:52 UTCinvestigating

   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. Organizations using other licensing models are not impacted. We are actively working to resolve the issue and will provide updates as more information becomes available.

2. 1. Oktober 2025 um 21:41 UTCmonitoring

   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 monitoring the system to ensure stability. Further updates will be provided as we work toward a permanent resolution.

3. 1. Oktober 2025 um 22:41 UTCresolved

   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, please contact our support team for further assistance.

1. 15. Juli 2025 um 16:47 UTCidentified

   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.

2. 15. Juli 2025 um 18:11 UTCresolved

   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.

1. 21. April 2025 um 23:29 UTCinvestigating

   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. 22. April 2025 um 01:27 UTCidentified

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

3. 22. April 2025 um 02:11 UTCmonitoring

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

4. 22. April 2025 um 03:15 UTCresolved

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

1. 17. April 2025 um 09:30 UTCinvestigating

   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. 17. April 2025 um 12:50 UTCinvestigating

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

3. 17. April 2025 um 13:08 UTCidentified

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

4. 17. April 2025 um 16:24 UTCmonitoring

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

5. 17. April 2025 um 16:50 UTCresolved

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

1. 16. April 2025 um 11:27 UTCinvestigating

   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. 16. April 2025 um 12:45 UTCidentified

   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. 16. April 2025 um 13:54 UTCidentified

   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. 16. April 2025 um 14:44 UTCmonitoring

   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. 16. April 2025 um 17:16 UTCresolved

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

1. 1. April 2025 um 03:12 UTCinvestigating

   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. 1. April 2025 um 07:58 UTCidentified

   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.

3. 1. April 2025 um 11:54 UTCidentified

   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.

4. 1. April 2025 um 12:19 UTCmonitoring

   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.

5. 1. April 2025 um 13:25 UTCinvestigating

   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.

6. 1. April 2025 um 14:18 UTCidentified

   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.

7. 1. April 2025 um 16:34 UTCmonitoring

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

8. 1. April 2025 um 20:24 UTCresolved

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