SolarWinds Platform Maps Showing Node as UP While Node Status and Alerts Show DOWN in Large‑Scale Environments

This behavior is caused by the way SolarWinds Platform Maps consumes and refreshes status information in comparison to the core polling and alerting engine, especially in large, heavily loaded environments.

To address the immediate inconsistency in status reporting for the affected component, re‑enable the component monitor as follows:

1. Navigate to the Application Details – Summary page for the affected application.

2. Click Edit Application Monitor.

3. Locate and check the TCP Port Monitor (or the relevant component monitor).

4. Click Disable for this component.

5. After it is disabled, click Enable to re‑enable the component.

This forces the component monitor to reset and can help ensure that the status pipeline from component → node → map is refreshed correctly.

This behavior can be expected in certain large-scale environments.

SolarWinds Platform Maps display status based on cached or periodically refreshed data that may lag behind the real-time node status seen in Node Details or Alerts. The node status you see in SolarWinds Platform Maps is derived from the platform’s status rollup and map-specific refresh cycles, which do not always update instantaneously with the core polling engine’s detection of node status changes. This can lead to temporary inconsistencies where a node is correctly marked DOWN in Node Details but still appears as UP on the map until the map refreshes its data.

A transient inconsistency where maps lag behind core node status is by design possible and is expected to be more visible in large or stressed environments. It is not a separate polling defect; it is a refresh/propagation delay between the core status pipeline and the map visual layer.