Summary On the Server Monitoring chart, the vertical Deployment (…) annotations render several hours away from the actual deployment time. The metric series (CPU/RAM/…) are positioned correctly, but the deployment annotation lines are shifted by a constant offset (~6h in our case). The root cause looks like a time-reference mismatch: metric series x-values are local wall-clock strings, while deployment annotation x-values are UTC epoch milliseconds.

Affected page /panel/monitoring/{serverId} — ApexCharts instance id server-monitor-chart. Most visible on the 24h / 7d ranges.

Environment

Server ID 107056, server timezone Etc/UTC Ploi account timezone America/New_York (UTC−4, DST) Browser timezone America/Toronto (UTC−4) Expected The Deployment annotation line sits at the same x-position as the load bump it causes (a deploy always produces a CPU/load spike).

Actual The annotation renders ~6h before the real deployment / load spike.

Evidence (verified against server-side git reflog, which is in UTC — independent of the UI):

Real deployment (reset: moving to origin/master, UTC) Annotation x rendered on chart (UTC) Offset 2026-07-08 03:06:24 2026-07-07 21:07:32 −5.98 h 2026-07-06 17:56:07 2026-07-06 11:57:12 −5.98 h The CPU peak (58%, load 5.2) in the metric series sits at local 23:00 = 03:00 UTC, which matches the real deployment at 03:06 UTC. So the metrics are correct; only the annotation is misplaced, and the offset is constant across deployments.

Data-format mismatch (read from chart.w.config in the page):

Metric series points → x = local wall-clock string, no offset, e.g. "2026-07-07 23:00:00" Deployment annotations → x = absolute UTC epoch ms, e.g. 1783458452000 (= 2026-07-07 21:07:32 UTC) On a datetime axis these two conventions don't share the same reference. The naive local strings are parsed in the viewer's local timezone, while the annotation epochs are absolute UTC, so the annotation ends up shifted by a fixed timezone-related offset. (As a side effect, the naive local strings also make metric positioning depend on the viewer's browser timezone, which is fragile in its own right.)