Home > Wireless LAN > Monitoring and Reporting > Wireless Health

Wireless Health

NOTE: Information included in this documentation is subject to change as the Wireless Health feature is currently under development. 


In today's enterprise, WiFi connectivity is seen as the pillar to workplace success. In many instances, enterprises are implementing the "wireless-only office" in which the only means of sending email, making a voice call, or starting a video conference are done via WiFi. Insights into the health of an organization's wireless network are a must and this article will outline how Meraki Wireless Health can be used to accomplish this. 

Wireless Health

Wireless Health helps IT teams verify that client devices can access the network as expected and that they have a fast, reliable experience. It does this by looking at all the steps necessary to provide a seamless experience, from associating to an AP, network authentication, DHCP, DNS, and displays metrics and anomaly data about each. This allows network administrators to rapidly identify where in this chain of events something is going wrong and to more preemptively remedy the issue.

NOTE:  Wireless Health will be rolled out as a free update for all wireless customers and a public beta should make its debut by end of April 2018.

Root Cause Identification

Wireless Health can assist by illuminating problematic locations in a client’s path to network connectivity.



There are many root causes of problematic connectivity. A few examples are:

  • Authentication failures
    • Client credentials aren’t accepted by a RADIUS server
    • Incorrect pre-shared key 
    • Device misconfiguration
    • Overloaded server prevents access requests from getting through
  • DHCP failures
    • Server fails to respond
    • No more available addresses in scope  
  • DNS failures
    • Server doesn’t respond to a client request for hostname resolution

Finally, success is measured not only by whether a client can successfully connect to a network but also by whether that client is able to pass traffic.

Traffic Latency Identification

Once a client has successfully connected, Wireless Health displays detailed metrics about network latency, identifying which types of traffic are showing performance problems at various thresholds of performance (measured in milliseconds).



Network administrators can drill down and get granular metrics on latency across their network at the AP level and at the device type level, helping them quickly identify the worst-performing APs and clients.


Latency at the AP level.


Latency by client device type.


These metrics and anomalies are synthesized into a holistic, network-level view that allows administrators to quickly identify networks with problems that require attention.


Wireless Health provides network-level statistics on latency and connectivity


Last modified



This page has no classifications.

Explore the Product

Click to Learn More

Article ID

ID: 6859

Explore Meraki

You can find out more about Cisco Meraki on our main site, including information on products, contacting sales and finding a vendor.

Explore Meraki

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case

Ask the Community

In the Meraki Community, you can keep track of the latest announcements, find answers provided by fellow Meraki users and ask questions of your own.

Visit the Community