Cisco Meraki Outage History

13 incidents recorded over the last 365 days, 13 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Cisco Meraki Incident

Cisco Meraki incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 5, 2026Dashboard pages not loadingThis incident has been resolved.2h 4mResolved
Jul 15, 2026Camera API errorOur 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…1h 27mResolved
Jun 23, 2026API OutageThe issue with API responses has been Resolved.  If you continue to see issues with failed API calls, please reach out to Customer Support.54 minResolved
Jun 12, 2026Dashboard Display IssueThis incident has been resolved.2h 41mResolved
May 21, 2026Dashboard Saving IssuesThis incident has been resolved.2h 27mResolved
May 1, 2026Dashboard issues with Live DataOur 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…4h 58mResolved
Apr 28, 2026Dashboard issues with Live dataOur 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…3h 8mResolved
Apr 14, 2026Meraki Support Email IssuesThis incident has been resolved.17 minResolved
Dec 15, 2025Cloud connectivityThis 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.3h 5mResolved
Oct 20, 2025Meraki Support Phone OutageThe issues connecting to the Support team via phone are now resolved. Thank you for your patience.9h 59mResolved
Oct 15, 2025Meraki Support Phone OutageThe 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…2h 44mResolved
Oct 8, 2025MX DDNS issuesThe 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…1h 19mResolved
Oct 1, 2025Load Times and Timeouts on Subscription Organization DashboardsThe 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…1h 48mResolved

How to Read This Cisco Meraki Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Cisco Meraki acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Cisco Meraki outage in this window ran 9h 59m, against a mean recovery of 2h 50m. If you depend on Cisco Meraki in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.