[GH-ISSUE #1088] Unexpected "down" after sending ping #754

New issue

Closed

opened 2026-02-25 23:43:28 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 23:43:28 +03:00

Owner

Originally created by @haideralipunjabi on GitHub (Nov 20, 2024).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/1088

My config:

Events
Screenshot 2024-11-21 at 1 55 51 AM

I was not expecting the grace period to trigger just 1.5 hours after the ping.

Originally created by @haideralipunjabi on GitHub (Nov 20, 2024). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/1088 My config: <img width="568" alt="Screenshot 2024-11-21 at 1 55 58 AM" src="https://github.com/user-attachments/assets/8a6ef0a0-e6f2-4139-9c1d-8057ebd25725"> Events <img width="771" alt="Screenshot 2024-11-21 at 1 55 51 AM" src="https://github.com/user-attachments/assets/0595587e-31b9-4ad4-8aea-96ec59d578cd"> I was not expecting the grace period to trigger just 1.5 hours after the ping.

kerem closed this issue

2026-02-25 23:43:28 +03:00

kerem commented

2026-02-25 23:43:29 +03:00

Author

Owner

@cuu508 commented on GitHub (Nov 21, 2024):

I suspect there's an issue with timezone mismatch between the client and your Healthchecks instance.

In the events section, switch the time zone to Asia/Kolkata and check the timestamps then.

@cuu508 commented on GitHub (Nov 21, 2024): I suspect there's an issue with timezone mismatch between the client and your Healthchecks instance. In the events section, switch the time zone to Asia/Kolkata and check the timestamps then. ![image](https://github.com/user-attachments/assets/8b2e4948-c825-409f-a306-0f98e905f374)

kerem commented

2026-02-25 23:43:29 +03:00

Author

Owner

@haideralipunjabi commented on GitHub (Nov 22, 2024):

I suspect there's an issue with timezone mismatch between the client and your Healthchecks instance.

In the events section, switch the time zone to Asia/Kolkata and check the timestamps then.

Yeah this was it. The CRON was executing in UTC.

@haideralipunjabi commented on GitHub (Nov 22, 2024): > I suspect there's an issue with timezone mismatch between the client and your Healthchecks instance. > > > > In the events section, switch the time zone to Asia/Kolkata and check the timestamps then. > > > > ![image](https://github.com/user-attachments/assets/8b2e4948-c825-409f-a306-0f98e905f374) > > Yeah this was it. The CRON was executing in UTC.