Incorrectly Connected Response Time Graph #173

New issue

Closed

opened 2026-02-28 01:37:31 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 01:37:31 -05:00

Owner

Originally created by @quexten on GitHub (Aug 28, 2021).

Is it a duplicate question?
I haven't found this in the issues.

Describe the bug
The response time graph connects points in the wrong order, leading to a weird overlap.

To Reproduce
I'm not sure what happened to reproduce this, but the incorrectly connected graph starts when I turned off uptime kuma for a while.

Expected behavior
The graph should be connected in the correct order.

Info

Uptime Kuma Version: 1.3.2
Using Docker: Yes
OS: Linux
Browser: Google Chrome

Screenshots
https://i.imgur.com/dExShzf.png

Error Log
Not relevant.

Originally created by @quexten on GitHub (Aug 28, 2021). **Is it a duplicate question?** I haven't found this in the issues. **Describe the bug** The response time graph connects points in the wrong order, leading to a weird overlap. **To Reproduce** I'm not sure what happened to reproduce this, but the incorrectly connected graph starts when I turned off uptime kuma for a while. **Expected behavior** The graph should be connected in the correct order. **Info** - Uptime Kuma Version: 1.3.2 - Using Docker: Yes - OS: Linux - Browser: Google Chrome **Screenshots** [https://i.imgur.com/dExShzf.png](https://i.imgur.com/dExShzf.png) **Error Log** Not relevant.

deekerman

2026-02-28 01:37:31 -05:00

closed this issue
added the
bug
label

deekerman commented

2026-02-28 01:37:38 -05:00

Author

Owner

@chakflying commented on GitHub (Aug 29, 2021):

Will investigate when I have time, I have seen it once or twice, but nothing in my code should affect how the dots connect chronologically, so it might be a chart.js bug.

@chakflying commented on GitHub (Aug 29, 2021): Will investigate when I have time, I have seen it once or twice, but nothing in my code should affect how the dots connect chronologically, so it might be a chart.js bug.

deekerman commented

2026-02-28 01:37:38 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jul 26, 2023):

@quexten could you close this issue? It seems that https://github.com/louislam/uptime-kuma/issues/843 is a better description of the underlying issue
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

@CommanderStorm commented on GitHub (Jul 26, 2023): @quexten could you close this issue? It seems that https://github.com/louislam/uptime-kuma/issues/843 is a better description of the underlying issue If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage? If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

deekerman commented

2026-02-28 01:37:38 -05:00

Author

Owner

@quexten commented on GitHub (Jul 28, 2023):

I don't know whether it's actually the same bug as I have multiple overlaps (visible on the right on the screenshot) which doesn't speak for a time zone issue. Regardless, I haven't encountered the bug again in the last 2 years so I'm closing for now.

@quexten commented on GitHub (Jul 28, 2023): I don't know whether it's actually the same bug as I have multiple overlaps (visible on the right on the screenshot) which doesn't speak for a time zone issue. Regardless, I haven't encountered the bug again in the last 2 years so I'm closing for now.