Skip to main content
Cisco Meraki Documentation

Meraki Status Page

This page describes the Meraki Status page, the value it represents, and how to use it.

Link: Meraki Status Page


To understand the purpose and benefits of the Meraki Status Page, and how to use it.

After reading this article you will:

  1. Understand the purpose and benefits of the Meraki Status Page.
  2. Understand when and what to expect to be published on the Meraki Status Page.
  3. Understand how to Subscribe to the Meraki Status Page for updates.


Simply stated, the Meraki Status Page is intended to keep customers informed of severe outages within the Meraki Cloud.  The intent is to share a high-level description of incidents that Meraki is aware of, and how we are addressing them. 


  • Customers can quickly grasp the scope of critical incidents that are in-flight at Meraki
  • Customers need not contact Meraki Support to stay abreast of critical in-flight incidents
  • Customers can subscribe to updates, if they desire
    • Updates are available in the following formats:
      • Email
      • RSS feed
      • ATOM feed

Scope of Incidents

At this time, Meraki Status Page is scoped to communicate critical, global customer outages only.  What this means is that only outages which affect most customers will be visible on Meraki Status Page.  This implies an outage of a large number of Meraki servers, or a critical supporting service that affects most customers.  If a particular Meraki server that your Meraki devices use is down, but most servers are operating normally, you should not expect to see a posting on Meraki Status page.

Here is a non-exhaustive list of some examples of conditions that are specifically excluded from being posting in Meraki Status Page:

  1. Maintenance notifications
  2. Issues that affect only a single Meraki server, or a small group of servers (anything less than a cluster/region)
  3. Any non-critical services that are down (even if they affect all customers)
  4. General Dashboard latency, unless attributed to a global outage
  5. Latency of specific operations (e.g. processing new device claims, auto-VPN updates, etc.), unless attributed to a global outage

What you can expect to see

Perhaps the best way to explain what you can expect to see is by way of some fictitious examples.  Please note: the images below are not taken from actual Meraki incidents, and therefore won't be visible on the actual Meraki Status Page.  The images below are for illustrative purposes only.  The exact look and feel of actual incident posts on the Meraki Status Page my vary somewhat from what is shown below.

Example screen captures

New Incident published

As part of the incident triage process, each new incident will be evaluated to see if it meets the Scope of Incidents defined above.  Once an incident is determined to be in-scope for that criteria, then our teams will post a preliminary message to share the fact that an investigation is underway:


Update to Incident published

As the investigation unfolds, and the incident remediation team has information to share, there will be posts similar to the one below.  Some things to keep in mind:

  • Updates are not posted on a fixed schedule, but rather as deemed necessary to convey useful information
  • Its quite possible that more than one update may be posted for an incident
  • The level of detail is kept intentionally low, for the sake of sending a clear, comprehensible message 

Here is an example update that shows progress in a fictitious investigation:


Incident Resolved

Once an incident has been investigated and remediated, and normal service levels restored, the incident will be Resolved in the Meraki Status page.  Even once Resolved, the incident is still visible in the Past Incidents section.  Here is a fictitious example:


Meraki Status Page Incident Color Legend

You may have noticed in the example screen captures above that the color of the frame around the incident text is different colors.  For the fictitious examples above, it begins as black, and then shows yellow.  These colors are generally meant to convey the relative severity of the incident.  Here is a color legend that describes these various severity ratings:

  • None (black)
    • When incidents are newly created, they default to this, as the severity may not be clear from the outset
  • Minor (yellow)
  • Major (orange)
  • Critical (red)



Accessing Meraki Status Page

The Meraki Status Page can be accessed via this URL:  Not login nor authentication is required to view the page.

Note: the Meraki Status Page is not incorporated into the Meraki Dashboard; this is intentional.  By keeping the Meraki Status Page independent, its utility is maximized in the event that the Meraki Dashboard is experiencing an issue.

Subscribing to Email Updates

1. Navigate to


3. Click the "Email address:" field.

4. Type in the email address you wish to receive updates

5. Click the "Subscribe Via Email" button.

6. You will receive a confirmation email from Meraki Status Page. You must click the "Confirm subscription" link in the email in order to finalize your email subscription.


Canceling your Email Subscription

Want to stop your email subscription?  Simple.

Just click the "Unsubscribe" link which is at the bottom of every email you receive from Meraki Status Page (including your subscription confirmation email):


Subscribing to RSS feed

1. Navigate to


3. From the pop-up window, select the tab with the "feed icon" (looks like a wifi icon).

4. Click the link for "RSS Feed"

5. The browser will refresh to show the RSS feed URL. Copy that URL, and inject it into any tool that supports RSS feeds.



Subscribing to Atom feed


1. Navigate to


3. From the pop-up window, select the tab with the "feed icon" (looks like a wifi icon).

4. Click the link for "Atom Feed"

5. The browser will refresh to show the Atom feed URL. Copy that URL, and inject it into any tool that supports Atom feeds.


Still need help?

If this documentation article did not answer your questions, or give you what you need, please feel free to reach out to Meraki Support.

  • Was this article helpful?