starred/uptime-kuma

Fork 0

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

24h view counts only 12h #3804

New issue

Open

opened 2026-02-28 03:41:27 -05:00 by deekerman · 10 comments

deekerman commented

2026-02-28 03:41:27 -05:00

Owner

Originally created by @Chris-sentbe on GitHub (Dec 3, 2024).

🛡️ Security Policy

I agree to have read this project Security Policy

Description

No response

👟 Reproduction steps

all monitor item has same time table

👀 Expected behavior

it should show us 24 hours time table data

😓 Actual Behavior

only give us a 12hours data in 24h view

🐻 Uptime-Kuma Version

2.0.0-beta.0

💻 Operating System and Arch

aws linux 2023

🌐 Browser

chrome 131.0.6778.86

🖥️ Deployment Environment

Runtime:
Database:
Filesystem used to store the database on:
number of monitors:

📝 Relevant log output

No response

Originally created by @Chris-sentbe on GitHub (Dec 3, 2024). ### 📑 I have found these related issues/pull requests ![image](https://github.com/user-attachments/assets/71c44f3f-8d29-4632-ad26-14eab6a62472) ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description _No response_ ### 👟 Reproduction steps all monitor item has same time table ### 👀 Expected behavior it should show us 24 hours time table data ### 😓 Actual Behavior only give us a 12hours data in 24h view ### 🐻 Uptime-Kuma Version 2.0.0-beta.0 ### 💻 Operating System and Arch aws linux 2023 ### 🌐 Browser chrome 131.0.6778.86 ### 🖥️ Deployment Environment - Runtime: - Database: - Filesystem used to store the database on: - number of monitors: ### 📝 Relevant log output _No response_

deekerman added the

A:dashboard

bug

cannot-reproduce

labels

2026-02-28 03:41:27 -05:00

deekerman commented

2026-02-28 03:41:29 -05:00

Author

Owner

@Vipul-Vermaa commented on GitHub (Oct 24, 2025):

I’d like to work on this issue.

@Vipul-Vermaa commented on GitHub (Oct 24, 2025): I’d like to work on this issue.

deekerman commented

2026-02-28 03:41:29 -05:00

Author

Owner

@Vipul-Vermaa commented on GitHub (Oct 25, 2025):

This is not a bug - the system is working as designed.
The 24-hour view is correctly configured to display 24 hours of data, but it can only show the data that actually exists. If you've only been monitoring for a few hours, the chart will only display those few hours of available data.

@Vipul-Vermaa commented on GitHub (Oct 25, 2025): This is not a bug - the system is working as designed. The 24-hour view is correctly configured to display 24 hours of data, but it can only show the data that actually exists. If you've only been monitoring for a few hours, the chart will only display those few hours of available data.

deekerman commented

2026-02-28 03:41:29 -05:00

Author

Owner

@Vipul-Vermaa commented on GitHub (Oct 25, 2025):

The chart displays all available data within the selected time range. Since there's no historical data beyond when monitoring started, the chart can only show what's available.

@Vipul-Vermaa commented on GitHub (Oct 25, 2025): The chart displays all available data within the selected time range. Since there's no historical data beyond when monitoring started, the chart can only show what's available.

deekerman commented

2026-02-28 03:41:29 -05:00

Author

Owner

@louislam commented on GitHub (Oct 25, 2025):

@Vipul-Vermaa Thanks

I cannot reproduce too in the latest version, close the issue for now. If everyone is still experiencing it, feel free to open a new bug issue with reproduce steps.

@louislam commented on GitHub (Oct 25, 2025): @Vipul-Vermaa Thanks I cannot reproduce too in the latest version, close the issue for now. If everyone is still experiencing it, feel free to open a new bug issue with reproduce steps. <img width="1670" height="561" alt="Image" src="https://github.com/user-attachments/assets/6af8bcb8-db8f-461b-940d-a4ceca32cd65" />

deekerman commented

2026-02-28 03:41:29 -05:00

Author

Owner

@villivateur commented on GitHub (Dec 18, 2025):

I can exactly reproduce this.

I am using V2.0.2

Please reopen this issue. @louislam

@villivateur commented on GitHub (Dec 18, 2025): I can exactly reproduce this. <img width="1609" height="385" alt="Image" src="https://github.com/user-attachments/assets/0c86aae0-cd91-4eb7-b4f8-ff8c7afd1c99" /> I am using V2.0.2 Please reopen this issue. @louislam

deekerman commented

2026-02-28 03:41:29 -05:00

Author

Owner

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

Could you explain more? The screenshot you are showing shows a downtime for ~12h and then being up with one downtime in between.

@CommanderStorm commented on GitHub (Dec 18, 2025): Could you explain more? The screenshot you are showing shows a downtime for ~12h and then being up with one downtime in between.

deekerman commented

2026-02-28 03:41:29 -05:00

Author

Owner

@villivateur commented on GitHub (Dec 21, 2025):

@CommanderStorm I mean, I selected 24h view, but it only show from 12-18 07:00 to 12-18 18:00, which means, 12h.

@villivateur commented on GitHub (Dec 21, 2025): @CommanderStorm I mean, I selected 24h view, but it only show from 12-18 07:00 to 12-18 18:00, which means, 12h.

deekerman commented

2026-02-28 03:41:29 -05:00

Author

Owner

@GunterKramp commented on GitHub (Feb 3, 2026):

I can confirm the Issue, even if there is data for much longer the 24 hour view shows only the last 12 hours.
The one week view seems also dubious in a similar way but I don't have a full week of data jet.
Here is a screenshot of the 24h view clearly showing only 12 hour even if there is no downtime:

@GunterKramp commented on GitHub (Feb 3, 2026): I can confirm the Issue, even if there is data for much longer the 24 hour view shows only the last 12 hours. The one week view seems also dubious in a similar way but I don't have a full week of data jet. Here is a screenshot of the 24h view clearly showing only 12 hour even if there is no downtime: <img width="1038" height="326" alt="Image" src="https://github.com/user-attachments/assets/c95f1d3e-8c35-4f24-9d0a-c228f5f80db2" />

deekerman commented

2026-02-28 03:41:29 -05:00

Author

Owner

@GunterKramp commented on GitHub (Feb 3, 2026):

Timestamps on the axis could be also improved, but still its clear. Screenshot was taken at around 8:57 in the morning, Data goes back to 21:00 = 9 o clock in the evening so 12 hours definitly. Please reopen the issue.

@GunterKramp commented on GitHub (Feb 3, 2026): Timestamps on the axis could be also improved, but still its clear. Screenshot was taken at around 8:57 in the morning, Data goes back to 21:00 = 9 o clock in the evening so 12 hours definitly. Please reopen the issue.

deekerman commented

2026-02-28 03:41:29 -05:00

Author

Owner

@sausa28 commented on GitHub (Feb 3, 2026):

I am also seeing the same issue. I believe it is also effecting the 24h uptime % stat. I had a service go down for 10 hours in the last 24, but the uptime is only showing as ~25%, which matches what it would be if it only checked the last 12h. The correct value should be ~55%.

The below screenshots were taken around 15:30 for reference.

@sausa28 commented on GitHub (Feb 3, 2026): I am also seeing the same issue. I believe it is also effecting the 24h uptime % stat. I had a service go down for 10 hours in the last 24, but the uptime is only showing as ~25%, which matches what it would be if it only checked the last 12h. The correct value should be ~55%. The below screenshots were taken around 15:30 for reference. <img src="https://github.com/user-attachments/assets/6c6056ec-6d17-4244-84ba-6bb7cbb9bc8a" width="200" /> <img src="https://github.com/user-attachments/assets/4c90d28c-e24c-4519-9442-758e5ab56fe1" width="200" />