Home > Meraki Insight > MI WAN Health

MI WAN Health

WAN Health Overview

The WAN Health feature is specifically designed to monitor ISP connections, and it will help with troubleshooting and reporting for these connections. In addition to active/primary ISP uplinks, WAN Health will also monitor secondary/failover connections (such as WAN2 and LTE connections). WAN Health will help in troubleshooting network outages to determine if the issue is caused by a LAN-side issue or if the outage is a WAN-side/ISP issue. The WAN connection information is presented in a simple, easy to read table format.

WAN Health Use Case

The WAN Health feature will be very useful in cases where:


  • Multiple MX devices are being used in the organization

  • The network is relying on an SD-WAN Architecture

  • Networks are using LTE as a failover link


If you are looking to monitor all of your network uplinks, including WAN2 and LTE connections (even when they are not active), WAN Health is designed to solve for this. WAN Health will also help in the planning of ISP capacity and LTE deployments. Additionally, WAN Health will differentiate between issues due to external factors (such as ISP issues), and internal factors (such as high usage on the LAN).

Activating WAN Health

WAN Health is a part of Meraki Insight, and any Insight deployment will have access to WAN Health without additional configuration/licensing. The WAN Health feature requires a Meraki Insight license enabled in the organization and activated for the network’s MX. The MX must be running on firmware version MX14.20 or greater. For more information on Meraki Insight licenses, please refer to Meraki Insight article.

WAN Health Page




Explanation of Terms



  • The Down number defines the number of uplinks that are down in the dashboard organization. This could be either multiple links in one network, or links across several networks, showing a “down” status for Primary WAN, Secondary WAN or LTE.


Poor Performance

  • Poor Performance defines the number of uplinks that are performing poorly in the organization due to an issue related to ISP. Poor performance can be noted due to either packet loss or high latency.

High Usage

  • High Usage defines the number of network that are saturated due to high usage on the LAN side. If the bandwidth limit is reaching 80% or greater of the set value under Security Appliance > Traffic Shaping > Uplink Configuration for a particular WAN uplink, it will be considered High Usage. For more information on Traffic Shaping page, please refer to this article.

The Search Option




You can search your organization’s uplinks by 4 different attributes:


  • Network Name: You can type a network name and any matching networks will appear with all the configured uplinks.

  • Network Tags: This will allow you to filter the uplinks by applied Network Tags.

  • ISP: This filter will allow you to search uplinks by ISP name.

  • Uplink: This will allow you to filter the list by primary, secondary, or LTE uplink types.

Uplink Status Colors


  • Green: Uplink is healthy without any issues

  • Yellow: Either Poor Performance (WAN issue) or High Usage (LAN issue)

  • Red: Uplink is down. No connectivity or L1 issue

  • Grey: Uplink is either not configured or has not been connected for a long time

Uplink Type

  • Primary: The primary uplink is detected based on the uplink set on Traffic shaping page.

  • Secondary: The secondary uplink is detected based on which uplink is in a Ready state (Not selected as a primary uplink under Traffic Shaping page).

  • LTE: Either a USB 3G/4G modem or built-in LTE (For MX67C/MX68CW only) will be detected as Secondary, Cellular.


Note: In the event that Load Balancing is enabled, the selected primary uplink under Traffic Shaping will be labeled as primary and remaining uplinks will show as secondary.


Some MX models (such as the MX67C/MX68CW/Z3C) have integrated LTE. WAN Health will be able to detect the following from those devices:

  • Uplink Status: If the SIM card is inserted and the device is trying to connect to its service provider but is not successful, WAN Health will show the LTE status in the Uplink Status column with a Red status indicator in Connecting mode. Fully connected LTE uplinks will show the Green status indicator.

  • Uplink Type: If the uplink listed is an LTE connection, the uplink will be listed with the tag cellular under the Uplink Type column

  • ISP: If the WAN connection is a cellular connection, the ISP field will have the LTE provider name.

  • Signal (dBm): WAN Health will report the LTE uplink's signal strength in dBm.





How is the ISP Detected?

We do reverse look up to the next hop IP address which will give us which ISP the uplink belongs to. Alternatively, the Security Appliance > Appliance Status > Uplink tab status page would show the ISP. If the lookup is failing, it will show “unknown”.


How is Current Bandwidth measured?

Current Bandwidth is measured from the Current Uplink Traffic displayed on the Security Appliance > Appliance Status > Uplink tab status page.


How is Current Loss and Latency measured?

Current Loss and Latency statistics are measured based on the responses we receive on the connectivity testing IP address configured on the Security Appliance > Traffic Shaping > Uplink Statistics page. By default, the IP address set is For changing it to different destination, you can set addresses on the Traffic Shaping page. For more information on configuring uplink statistics, please check our Traffic Shaping Settings document.


How are Affected Apps detected?

If there are tracked web applications set to be monitored on the Insight > Web Application Performance > Monitor tab, this data will be used to determine if the Application is performing poorly due to poor performance on the WAN uplink.


If the performance score is less than 80% of its threshold, Insight will flag the application as “Affected.” From the WAN Health page, it will be easy to determine if the application performance is degraded due to a WAN uplink with Poor Performance or not. A Poor Performance indication could be caused by packet loss or high latency.


If the WAN shows no sign of issues, we can then check on the Web Application Performance page for that particular Application. This will give more detail as to whether any issues are reported on the LAN side or the Server side. For more information on web application performance, check our our main Meraki Insight document.

Last modified



This page has no classifications.

Explore the Product

Click to Learn More

Article ID

ID: 7556

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