URLs not showing in uptime dashboard #3626

Closed
opened 2026-02-28 03:35:47 -05:00 by deekerman · 2 comments
Owner

Originally created by @renugamanimegalai on GitHub (Sep 26, 2024).

We have 90+ URLs in uptime , when we open the dashboard it is taking more than 45 minutes to list all the
urls .

image

🛡️ Security Policy

Description

No response

👟 Reproduction steps

Add 40+ URLs

👀 Expected behavior

home page should load

😓 Actual Behavior

home page taking more time load

🐻 Uptime-Kuma Version

1.23.11

💻 Operating System and Arch

ubuntu 24

🌐 Browser

chrome

🖥️ Deployment Environment

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

📝 Relevant log output

No response

Originally created by @renugamanimegalai on GitHub (Sep 26, 2024). ### 📑 I have found these related issues/pull requests We have 90+ URLs in uptime , when we open the dashboard it is taking more than 45 minutes to list all the urls . ![image](https://github.com/user-attachments/assets/aea579c0-c765-4e23-b837-f38a1018d684) ### 🛡️ 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 Add 40+ URLs ### 👀 Expected behavior home page should load ### 😓 Actual Behavior home page taking more time load ### 🐻 Uptime-Kuma Version 1.23.11 ### 💻 Operating System and Arch ubuntu 24 ### 🌐 Browser chrome ### 🖥️ Deployment Environment - Runtime: - Database: - Filesystem used to store the database on: - number of monitors: ### 📝 Relevant log output _No response_
deekerman 2026-02-28 03:35:47 -05:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@tifirifi commented on GitHub (Sep 26, 2024):

Hi,

The issue you mentioned is known and will be addressed in the upcoming 2.0 release of Uptime Kuma. Version 2.0 is focused on improving performance, especially for larger numbers of monitors. You can track the progress or contribute here: GitHub Issue #4500.

For now, try reducing monitor history retention, increasing check intervals, or pausing less essential monitors to mitigate performance issues.

@tifirifi commented on GitHub (Sep 26, 2024): Hi, The issue you mentioned is known and will be addressed in the upcoming 2.0 release of Uptime Kuma. Version 2.0 is focused on improving performance, especially for larger numbers of monitors. You can track the progress or contribute here: [GitHub Issue #4500](https://github.com/louislam/uptime-kuma/issues/4500). For now, try reducing monitor history retention, increasing check intervals, or pausing less essential monitors to mitigate performance issues.
Author
Owner

@CommanderStorm commented on GitHub (Sep 26, 2024):

My bet would be that https://github.com/louislam/uptime-kuma/pull/5025 resolved this issue and have marked said PR as such.
Said PR needs a review though

@CommanderStorm commented on GitHub (Sep 26, 2024): My bet would be that https://github.com/louislam/uptime-kuma/pull/5025 resolved this issue and have marked said PR as such. Said PR needs a review though
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#3626
No description provided.