Ping graph stopped drawing #4557

New issue

Open

opened 2026-02-28 04:07:15 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 04:07:15 -05:00

Owner

Originally created by @zeshinsei on GitHub (Dec 30, 2025).

I did not find an issue relating to this.

🛡️ Security Policy

I have read and agree to Uptime Kuma's Security Policy.

📝 Description

For one monitor, the ping graph stopped drawing even though it's up and still has a ping:

I've checked other monitors and they didn't encounter this issue.

👟 Reproduction steps

Unable to reproduce on other monitors. Refreshing the page etc does not resolve this issue, as I had assumed this was a browser issue and it does not appear to be. If I change this to "Recent", it graphs just fine which indicates there are ping numbers.

👀 Expected behavior

The ping numbers are graphed as expected in the 24-hour range.

Another monitor that looks just fine with 24-hour:

😓 Actual Behavior

The majority of the 24-hour range graph is empty.

🐻 Uptime-Kuma Version

2.0.2

💻 Operating System and Arch

Synology NAS, DSM 7.2.2-72806 Update 5

🌐 Browser

Firefox 146.0.1 (64-bit)

🖥️ Deployment Environment

Embedded SQL database

Container Manager v24.0.2-1543

Number of monitors: 6

📝 Relevant log output

Originally created by @zeshinsei on GitHub (Dec 30, 2025). ### 📑 I have found these related issues/pull requests I did not find an issue relating to this. ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Description For one monitor, the ping graph stopped drawing even though it's up and still has a ping: <img width="1665" height="332" alt="Image" src="https://github.com/user-attachments/assets/36e00bb2-8e4f-40c2-9863-d00bad137ba7" /> I've checked other monitors and they didn't encounter this issue. ### 👟 Reproduction steps Unable to reproduce on other monitors. Refreshing the page etc does not resolve this issue, as I had assumed this was a browser issue and it does not appear to be. If I change this to "Recent", it graphs just fine which indicates there are ping numbers. ### 👀 Expected behavior The ping numbers are graphed as expected in the 24-hour range. Another monitor that looks just fine with 24-hour: <img width="1619" height="284" alt="Image" src="https://github.com/user-attachments/assets/bc189753-6812-48d9-a3bc-abb89a27cc88" /> ### 😓 Actual Behavior The majority of the 24-hour range graph is empty. ### 🐻 Uptime-Kuma Version 2.0.2 ### 💻 Operating System and Arch Synology NAS, DSM 7.2.2-72806 Update 5 ### 🌐 Browser Firefox 146.0.1 (64-bit) ### 🖥️ Deployment Environment Embedded SQL database Container Manager v24.0.2-1543 Number of monitors: 6 ### 📝 Relevant log output ```bash session ```

deekerman added the

A:dashboard

bug

cannot-reproduce

labels

2026-02-28 04:07:15 -05:00

deekerman commented

2026-02-28 04:07:18 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 30, 2025):

Maybe related to

#6294

Just as in that isssue, I don't know what is happening (-> as you said, not reproducible).
A sql backup of the db would help, but would be a lot of work for you to prepare (+ensure that it does not include any secrets).
Currently, this issue is not very actionable as I don't have a testcase/ state to start debugging from.

@CommanderStorm commented on GitHub (Dec 30, 2025): Maybe related to - #6294 Just as in that isssue, I don't know what is happening (-> as you said, not reproducible). A sql backup of the db would help, but would be a lot of work for you to prepare (+ensure that it does not include any secrets). Currently, this issue is not very actionable as I don't have a testcase/ state to start debugging from.