Observability

Unmanage window shows incorrect time when SolarWinds Platform Web Console is accessed from different time zone

This article provides information about an issue where the planned unmanage interval is displayed one hour earlier than expected on the Node Details page when the SolarWinds Platform server is configured in one time zone (for example, Eastern Time) and the web console is accessed from a browser running in a different time zone (for example, India Standard Time).

First published date

2/4/2026 11:41 PM

Last published date

5/29/2026 3:30 PM

Overview

In SolarWinds Platform versions 2025.4.x and 2026.x, users may observe incorrect time values displayed for a node’s planned unmanage window when viewing the web console from a machine in a different time zone than the SolarWinds Platform server.

 

This issue is most commonly observed when:

  • The SolarWinds Platform server (and SQL server) are configured in Eastern Time (ET)
  • The unmanage window is scheduled for a date during standard time (non-DST)
  • The SolarWinds web console is accessed remotely from a browser in another time zone (for example, IST)

 

In this scenario, the Node Details page may display the unmanage start and end times one hour earlier than expected. The displayed time appears to treat Eastern Time as if it were in daylight saving time (UTC-4) even though the date falls in February, when Eastern Time should be UTC-5.

 

Example

Scheduled on the SolarWinds server:

  • Start: February 7, 2026, 3:00 AM ET
  • End: February 7, 2026, 8:00 AM ET

 

Expected display when viewed from an IST browser:

Node will be unmanaged from 2/7/2026 1:30 PM to 2/7/2026 6:30 PM

Actual display:

Node will be unmanaged from 2/7/2026 12:30 PM to 2/7/2026 5:30 PM

This behavior only affects how the time is rendered in the UI. The issue is reproducible when browsing the web console remotely from a machine in a different time zone than the SolarWinds Platform server.

Product section

Hybrid Cloud Observability

Cause

This behavior is due to a known product defect in the way the SolarWinds Platform handles time zone and DST conversion for unmanage/maintenance intervals when:

  • The SolarWinds server is in one time zone (for example, a North American time zone), and
  • The web console is accessed from a different time zone (for example, a remote workstation in another region), and
  • The unmanage schedule is created and/or viewed from that remote browser.

In this scenario:

  • The unmanage window is stored in the database using UTC (as expected).
  • However, the logic that converts these values for display in certain UI paths (for example, the Node Details “will be unmanaged from…” text) can incorrectly apply timezone and/or DST offsets when the browser is not in the same time zone as the SolarWinds server.
  • This leads to the displayed times being shifted by one hour, even though the underlying UTC values are correct.

Resolution

This issue will be addressed in a future release of the SolarWinds Platform. As of May 29, 2026, use the workaround provided below.

 

Workaround

  • Perform unmanage scheduling and validation directly from the SolarWinds Platform server, or from a machine configured with the same time zone as the SolarWinds server.
  • Avoid relying on the Node Details page time display when accessing the web console from a remote browser in a different time zone.

 

Monitor this KB article and the SolarWinds Platform release notes for future updates and product fixes.