starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

uptime value exceeds 100% #1793

New issue

Closed

opened 2026-02-28 02:32:44 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-28 02:32:44 -05:00

Owner

Originally created by @spac3monkey on GitHub (Jan 17, 2023).

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

Description

👟 Reproduction steps

I don't know.

👀 Expected behavior

The max. uptime value should be 100%.

😓 Actual Behavior

The max. uptime value is over 100%.

🐻 Uptime-Kuma Version

1.19.3

💻 Operating System and Arch

Raspbian bullseye

🌐 Browser

Google Chrome, Safari, Mozilla Firefox

🐋 Docker Version

2.14.1

🟩 NodeJS Version

No response

📝 Relevant log output

No response

Originally created by @spac3monkey on GitHub (Jan 17, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description ![image](https://user-images.githubusercontent.com/97247944/213014602-4fa2c5a5-a30a-4da2-a085-c0dbfbc6a052.png) ### 👟 Reproduction steps I don't know. ### 👀 Expected behavior The max. uptime value should be 100%. ### 😓 Actual Behavior The max. uptime value is over 100%. ### 🐻 Uptime-Kuma Version 1.19.3 ### 💻 Operating System and Arch Raspbian bullseye ### 🌐 Browser Google Chrome, Safari, Mozilla Firefox ### 🐋 Docker Version 2.14.1 ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output _No response_

deekerman

2026-02-28 02:32:44 -05:00

closed this issue
added the
wontfix

bug
labels

deekerman commented

2026-02-28 02:32:51 -05:00

Author

Owner

@Computroniks commented on GitHub (Jan 17, 2023):

I think we just need a sanity check when displaying the uptime. I will look into implementing this tomorrow.

@Computroniks commented on GitHub (Jan 17, 2023): I think we just need a sanity check when displaying the uptime. I will look into implementing this tomorrow.

deekerman commented

2026-02-28 02:32:51 -05:00

Author

Owner

@chakflying commented on GitHub (Jan 17, 2023):

I think this most likely is because of inaccurate system clock (common for raspberry pis), and the time went backwards. The question is, is hiding the real problem by e.g. clamping the value to 100% a better solution?

@chakflying commented on GitHub (Jan 17, 2023): I think this most likely is because of inaccurate system clock (common for raspberry pis), and the time went backwards. The question is, is hiding the real problem by e.g. clamping the value to 100% a better solution?

deekerman commented

2026-02-28 02:32:51 -05:00

Author

Owner

@louislam commented on GitHub (Jan 17, 2023):

I cant find the old issue, but as @chakflying said, it is common issue for pi users.

Capping at 100% visually is good, but it will be hard to identify issues if we have make the calculation wrong in the future. I prefer to keep it as is for now.

@louislam commented on GitHub (Jan 17, 2023): I cant find the old issue, but as @chakflying said, it is common issue for pi users. Capping at 100% visually is good, but it will be hard to identify issues if we have make the calculation wrong in the future. I prefer to keep it as is for now.

deekerman commented

2026-02-28 02:32:51 -05:00

Author

Owner

@Computroniks commented on GitHub (Jan 18, 2023):

Not sure if this affects both the status page and the dashboard, I assume it would. I would suggest only capping it on the status page, the thing that is shown to the public. This way we don't have obvious public facing errors whilst still having the ability to check if we broke the calculations but the bug isn't visible to the public.

@Computroniks commented on GitHub (Jan 18, 2023): Not sure if this affects both the status page and the dashboard, I assume it would. I would suggest only capping it on the status page, the thing that is shown to the public. This way we don't have obvious public facing errors whilst still having the ability to check if we broke the calculations but the bug isn't visible to the public.

deekerman commented

2026-02-28 02:32:51 -05:00

Author

Owner

@louislam commented on GitHub (Jan 18, 2023):

@Computroniks good idea.

@louislam commented on GitHub (Jan 18, 2023): @Computroniks good idea.

deekerman commented

2026-02-28 02:32:51 -05:00

Author

Owner

@Computroniks commented on GitHub (Jan 18, 2023):