Is Cisco Meraki Down?

No — Cisco Meraki is up

Reachable from all 8 checked regions

Average response time: 1046ms

Last checked 6 hours ago · checks run every 6 hours

Official status page: https://status.meraki.net

Cisco Meraki uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

901ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

21-day clean streak

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

fra

424ms

DNS 1ms TCP 4ms TLS 18ms TTFB 424ms

gru

1545ms

DNS 0ms TCP 2ms TLS 8ms TTFB 1545ms

iad

678ms

DNS 0ms TCP 2ms TLS 12ms TTFB 678ms

jnb

1963ms

DNS 0ms TCP 1ms TLS 7ms TTFB 1963ms

lax

692ms

DNS 0ms TCP 1ms TLS 12ms TTFB 692ms

lhr

411ms

DNS 0ms TCP 2ms TLS 13ms TTFB 411ms

nrt

1778ms

DNS 0ms TCP 1ms TLS 11ms TTFB 1777ms

ord

879ms

DNS 0ms TCP 2ms TLS 15ms TTFB 878ms

What Cisco Meraki does

Cisco Meraki sells access points, switches, security appliances and cameras that are configured and monitored from a cloud dashboard instead of on-box consoles. IT teams and managed service providers use it to run networks for offices, schools and retail sites from one place, so the dashboard is the single control plane for every site they manage.

What an outage looks like

The dashboard at dashboard.meraki.com does not load or signs you out. API calls from automation return errors. Devices show as offline or unreachable in the dashboard while their sites keep working. Configuration changes do not save or do not reach devices. Alerts and reports stop updating, so a real site outage can go unnoticed during a cloud incident.

What to do about it

Check status.meraki.net, which splits every row by region: North and South America, Europe, Asia-Pacific, Canada, China and India, each with Dashboard, API, device connectivity, access point, switch, WAN appliance and camera rows. Find your region first. Hold configuration changes until Dashboard recovers, and confirm site health from a user on the network rather than the dashboard.

Is it down for everyone, or just you?

If this page says Cisco Meraki is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Cisco Meraki outage FAQ

Does my network go down if the Meraki dashboard is down?

No. Meraki's documentation says traffic between devices and the cloud is management data only, so if that connection is interrupted the network keeps passing traffic and users do not notice. Wireless clients stay connected and switches keep forwarding. What stops is the ability to change configuration and see reports until the connection returns.

Why do my devices show offline in the dashboard?

During a cloud incident, the dashboard can lose contact with devices that are working normally. The status page reports Network Device Connectivity separately from Dashboard for each region, and that row is the one to check. Confirm with a user at the site before dispatching anyone; a device shown offline may be serving traffic fine.

Is Meraki down in my region only?

Often, yes. Every component is listed separately for North and South America, Europe, Asia-Pacific, Canada, China and India, so an incident in one region can leave the others fully healthy. A colleague in a different region signing in proves nothing about your organization's dashboard. Check the rows for the region your organization is hosted in.

Do Meraki cameras keep recording during a cloud outage?

Yes, according to Meraki's documentation: MV cameras keep recording to local storage when they lose contact with the cloud. Viewing footage remotely through the dashboard depends on the cloud, so it may be unavailable until the connection returns. The Camera row on the status page shows whether the camera service itself is affected.

Should I make changes during a Meraki incident?

Avoid it. Changes submitted while Dashboard or API is degraded may not save, or may save and not reach devices, leaving you unsure which configuration is live. Wait for the region's rows to recover, then make the change and confirm it on a device. Scripts that push configuration through the API should be paused for the same reason.

How we measure this

We request Cisco Meraki's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Cisco Meraki publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Cisco Meraki goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required