[GH-ISSUE #76] Outage #47

Closed
opened 2026-02-25 23:40:57 +03:00 by kerem · 14 comments
Owner

Originally created by @szepeviktor on GitHub (Aug 19, 2016).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/76

Was there an outage?
I've got only "red exclamation marks".

Originally created by @szepeviktor on GitHub (Aug 19, 2016). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/76 Was there an outage? I've got only "red exclamation marks".
kerem closed this issue 2026-02-25 23:40:57 +03:00
Author
Owner

@CameronBanga commented on GitHub (Aug 19, 2016):

Seeing similar, have two checks that are down, and don't seem to be working. Seeing following when I try manually:

wget https://hchk.io/xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx -O /dev/null
--2016-08-19 16:29:29--  https://hchk.io/xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx
Resolving hchk.io... 2604:a880:800:10::170d:6001, 104.236.126.203
Connecting to hchk.io|2604:a880:800:10::170d:6001|:443... connected.
HTTP request sent, awaiting response... 400 Bad Request
2016-08-19 16:29:29 ERROR 400: Bad Request.
<!-- gh-comment-id:241140561 --> @CameronBanga commented on GitHub (Aug 19, 2016): Seeing similar, have two checks that are down, and don't seem to be working. Seeing following when I try manually: ``` wget https://hchk.io/xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx -O /dev/null --2016-08-19 16:29:29-- https://hchk.io/xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx Resolving hchk.io... 2604:a880:800:10::170d:6001, 104.236.126.203 Connecting to hchk.io|2604:a880:800:10::170d:6001|:443... connected. HTTP request sent, awaiting response... 400 Bad Request 2016-08-19 16:29:29 ERROR 400: Bad Request. ```
Author
Owner

@hakanw commented on GitHub (Aug 19, 2016):

+1

<!-- gh-comment-id:241142087 --> @hakanw commented on GitHub (Aug 19, 2016): +1
Author
Owner

@hakanw commented on GitHub (Aug 19, 2016):

error 400 on the healthchecks

<!-- gh-comment-id:241142126 --> @hakanw commented on GitHub (Aug 19, 2016): error 400 on the healthchecks
Author
Owner

@pahud commented on GitHub (Aug 20, 2016):

I also got 400 here

<!-- gh-comment-id:241171206 --> @pahud commented on GitHub (Aug 20, 2016): I also got 400 here
Author
Owner

@Saxtus commented on GitHub (Aug 20, 2016):

Confirming outage.
It began just after 19-Aug-2016 20:35 UTC

<!-- gh-comment-id:241194777 --> @Saxtus commented on GitHub (Aug 20, 2016): Confirming outage. It began just after [19-Aug-2016 20:35 UTC](http://www.timeanddate.com/countdown/to?iso=20160819T2035&p0=1440)
Author
Owner

@barryrowlingson commented on GitHub (Aug 20, 2016):

400 Bad Requests all over here too. On the plus side, I've now discovered the code is on github and I can host my own healthchecks site...

<!-- gh-comment-id:241198985 --> @barryrowlingson commented on GitHub (Aug 20, 2016): 400 Bad Requests all over here too. On the plus side, I've now discovered the code is on github and I can host my own healthchecks site...
Author
Owner

@pzelnip commented on GitHub (Aug 20, 2016):

Ditto here.

<!-- gh-comment-id:241209184 --> @pzelnip commented on GitHub (Aug 20, 2016): Ditto here.
Author
Owner

@szepeviktor commented on GitHub (Aug 20, 2016):

Email sent to contact@

<!-- gh-comment-id:241209422 --> @szepeviktor commented on GitHub (Aug 20, 2016): Email sent to `contact@`
Author
Owner

@foozmeat commented on GitHub (Aug 20, 2016):

contacted via twitter

<!-- gh-comment-id:241210546 --> @foozmeat commented on GitHub (Aug 20, 2016): contacted via twitter
Author
Owner

@cuu508 commented on GitHub (Aug 20, 2016):

Hello, hchk.io server was having a database connectivity issue, and I was out of the country with roaming data off (bad idea!). Fixed for now. Will look into preventing this kind of issue in future, and will write a postmortem. Sorry about this.

<!-- gh-comment-id:241221792 --> @cuu508 commented on GitHub (Aug 20, 2016): Hello, hchk.io server was having a database connectivity issue, and I was out of the country with roaming data off (bad idea!). Fixed for now. Will look into preventing this kind of issue in future, and will write a postmortem. Sorry about this.
Author
Owner

@szepeviktor commented on GitHub (Aug 20, 2016):

Thank you for your free service!

<!-- gh-comment-id:241224508 --> @szepeviktor commented on GitHub (Aug 20, 2016): Thank you for your free service!
Author
Owner

@cuu508 commented on GitHub (Aug 22, 2016):

post-mortem of this outage: https://medium.com/@healthchecks/outage-postmortem-20-august-2016-204297b9d3dd#.58n9g8tnj

<!-- gh-comment-id:241509364 --> @cuu508 commented on GitHub (Aug 22, 2016): post-mortem of this outage: https://medium.com/@healthchecks/outage-postmortem-20-august-2016-204297b9d3dd#.58n9g8tnj
Author
Owner

@vmalloc commented on GitHub (Aug 23, 2016):

@cuu508 thanks for the post mortem, and many thanks for this awesome service!

<!-- gh-comment-id:241622167 --> @vmalloc commented on GitHub (Aug 23, 2016): @cuu508 thanks for the post mortem, and many thanks for this awesome service!
Author
Owner

@hakanw commented on GitHub (Aug 23, 2016):

Agree with everyone else. Thanks for a great service!!

2016-08-23 6:14 GMT+02:00 Rotem Yaari notifications@github.com:

@cuu508 https://github.com/cuu508 thanks for the post mortem, and many
thanks for this awesome service!


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/healthchecks/healthchecks/issues/76#issuecomment-241622167,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGJ2GmiZRWNFwLk1HgjkqBWXR0NhGRTks5qinPBgaJpZM4Jo2-N
.

<!-- gh-comment-id:241652834 --> @hakanw commented on GitHub (Aug 23, 2016): Agree with everyone else. Thanks for a great service!! 2016-08-23 6:14 GMT+02:00 Rotem Yaari notifications@github.com: > @cuu508 https://github.com/cuu508 thanks for the post mortem, and many > thanks for this awesome service! > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > https://github.com/healthchecks/healthchecks/issues/76#issuecomment-241622167, > or mute the thread > https://github.com/notifications/unsubscribe-auth/AAGJ2GmiZRWNFwLk1HgjkqBWXR0NhGRTks5qinPBgaJpZM4Jo2-N > .
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/healthchecks#47
No description provided.