Cisco Meraki Outage History

Cisco Meraki API requests across Asia-Pacific, India, North and South America, Europe, Canada and China experienced an outage starting at 11:46 PM UTC. The disruption blocked programmatic access to Meraki dashboards and management APIs, impacting customers relying on integrations, automation, and portal workflows. The API endpoints in all listed regions were affected, causing API responses to fail and delaying connected tools. The incident began at 11:46 PM UTC and was resolved by 12:41 AM UTC.

The Cisco Meraki dashboard experienced sign-in and loading problems that prevented access to the Meraki Dashboard for administrators. The outage began on 6:53 PM UTC and was resolved by 7:11 PM UTC, lasting about 18 minutes. User reports indicated the dashboard would not load after signing in, with activity observed across multiple regions, suggesting a broad but brief disruption to dashboard access.

StatusGator recorded an Early Warning Signal at Jan 28, 2026 6:53 PM UTC for this incident, while Cisco Meraki’s status page did not publish official updates during the event. Reports described sign-in failures and dashboards getting stuck on the login or loading page from locations including North America, Europe, and Asia, indicating a global reach of the issue.

Meraki reported a cloud connectivity incident affecting cloud authentication, device-to-cloud connectivity, and telemetry-dependent features. The outage began at 6:11 PM UTC and persisted for about 3 hours and 5 minutes, with services returning to normal by 9:16 PM UTC. During the incident, cloud access and telemetry may have been intermittently impaired for affected customers.

Meraki posted two official updates: an initial acknowledgment of identified cloud connectivity and authentication issues and progress on remediation, followed by confirmation that services had returned to normal as the incident resolved at 9:16 PM UTC.

Cisco Meraki dashboards and login pages became inaccessible due to DNS resolution issues, affecting users across Europe, parts of Asia, and other regions. Reports described blank dashboards, DNS not resolving messages, and sign-in failures, preventing admins from accessing the Meraki dashboard to manage networks. The incident started around 09:45 UTC and was resolved by 10:37 UTC, lasting roughly 52 minutes.

The Cisco Meraki status page reported a global issue affecting Meraki Support phone access, tied to a broader AWS outage. The incident began when the status moved to a warning at Oct 20, 2025 3:11 PM UTC. For new cases, customers were asked to open a case and choose the Call In option with “Outage Oct/20” in the subject, and for existing cases to include the word “Outage” in the comment. The provider issued two status updates during the incident to communicate the ongoing investigation.

On Oct 15, 2025 7:46 PM UTC Meraki reported a problem with connecting to the Support line, listing a phone outage and ongoing investigation. Customers could not reach Meraki Support by phone during the incident, with a workaround to open a case and select the Call In option for new cases. The outage lasted approximately 2 hours and 45 minutes and was resolved by Oct 15, 2025 10:31 PM UTC. Meraki posted two status updates during the incident to communicate ongoing efforts and the eventual restoration.

Cisco Meraki reported Dynamic DNS (DDNS) issues affecting MX firewall devices. Users began reporting problems around 6:00 PM UTC, with a small number of reports indicating degraded connectivity or hostname resolution tied to DDNS. The Meraki status page flagged the issue at Oct 8, 2025 7:01 PM UTC, noting that the source had been identified and a mitigation was being rolled out. The incident affected the MX DDNS component and prompted two official status updates as mitigation progressed. The issue was resolved by Oct 8, 2025 8:21 PM UTC, with service restored.

Cisco Meraki reported slower load times and intermittent timeout errors on the Dashboard pages for organizations using subscription-based licensing. Users attempting to load subscription organization dashboards may have encountered delays or timeout messages, while organizations using other licensing models were not affected.

Cisco Meraki reported a brief outage affecting Campus Gateway and cloud-managed Catalyst connectivity due to congestion in communications proxies. For Campus Gateway, already-connected Access Points remained unaffected, but some customers experienced difficulties connecting to Campus Gateways or Catalyst switches to monitor or manage devices. The outage began at 4:52 PM UTC and was resolved by 6:11 PM UTC, lasting about 1 hour and 19 minutes. Meraki posted two status updates during the incident describing the identified issue and ongoing mitigation.

The root cause was congestion in the communications proxies serving Campus Gateway and a subset of Catalyst switches running in IOS-native mode, leading to degraded cloud connectivity. Engineers were actively working on resolution, and connectivity returned as the status was restored to normal by 18:11 UTC. The incident represents a targeted, short-lived disruption affecting a portion of Meraki devices rather than a full service outage across all regions.

Cisco Meraki reported a partial outage affecting newly added devices trying to connect to the Cisco Meraki Dashboard. Devices already online and connected were not impacted. The incident began at 11:31 PM UTC and the service was restored by 3:16 AM UTC, lasting about 3 hours and 45 minutes. The status page described Device-to-Cloud Connectivity Issues and noted an ongoing investigation.

The status page updates indicated the issue was investigated and eventually resolved as services returned to normal. The outage affected a subset of devices rather than the entire platform, with Dashboard access for the affected devices restored as connectivity stabilized.