Just noticed issues with Github handling requests and overall flakiness.
Getting a lot of status code 500 errors and decided to open this thread for status updates.
Even though the status page (https://www.githubstatus.com/) shows no issues, I'm still getting the occasional 500. It seems to be happening quite irregularly. They are possibly facing a lot of load.
Been running into many unicorns for the last few minutes, had a moment where it came back but seems to be down again. Even the unicorn image won't load on the unicorn page.
In the beginning of status pages, most of them were automatic one way or another, or engineers quickly threw up "We know of the problem, stay tuned" messages there.
But soon after, legal/executive team got ownership of them apparently, and the status pages are no longer automatically showing downtime/response time and notice about when things are actually down can take a while.
So I think it's nice that there is at least one place where I can see if it's a problem on my end, or if it's global. It helps to remove some frustration at least.
Yep, noticed it with comments on an issue (had timeouts while submitting but it eventually went through).
Now 30 mins later, i've refreshed the issue and see that my reply and the comment I was replying too (by another user) are both gone. Hopefully, it's eventually consistent and these comments will re-appear later.
According to Metrist monitoring (disclosure: I work there), the errors were very rare, and didn't happen enough for us to call the product "down." Looks like around 1% of requests.
How reliable are Github cron action workflows? I set one up to run every 15 minutes recently, but it seems to actually be running closer to once an hour.
Github outages are the bored engineer's equivalent of getting a surprise snow day when you were in school, full of unbridled joy.
For engaged, happy engineers its the equivalent of getting a surprise snow day when you are grown up and have to go dig your car out of the snow and its a normal day just with extra steps.
omn1|3 years ago
adamscybot|3 years ago
rozenmd|3 years ago
Seems like a huge spike in load.
unknown|3 years ago
[deleted]
bowsamic|3 years ago
MattIPv4|3 years ago
omn1|3 years ago
qwertox|3 years ago
Those GitHub badges... they are as ugly as it gets.
naikrovek|3 years ago
irajdeep|3 years ago
Bingo. Not everything in this world needs to be gamified.
blueflow|3 years ago
capableweb|3 years ago
But soon after, legal/executive team got ownership of them apparently, and the status pages are no longer automatically showing downtime/response time and notice about when things are actually down can take a while.
So I think it's nice that there is at least one place where I can see if it's a problem on my end, or if it's global. It helps to remove some frustration at least.
RcouF1uZ4gsC|3 years ago
corford|3 years ago
Now 30 mins later, i've refreshed the issue and see that my reply and the comment I was replying too (by another user) are both gone. Hopefully, it's eventually consistent and these comments will re-appear later.
kid64|3 years ago
fredrikaverpil|3 years ago
sivapil|3 years ago
{ "code": 500, "message": "internal server error" }
Does anyone have luck? Any workaround to fix it?
jmartens|3 years ago
WFHRenaissance|3 years ago
unknown|3 years ago
[deleted]
bilalq|3 years ago
view|3 years ago
EDIT: Seems to be a routing issue. I've enabled a UK VPN and it's working fine now.
cherryblossom00|3 years ago
bityard|3 years ago
HJain13|3 years ago
kleinsch|3 years ago
planxty|3 years ago
max23_|3 years ago
azeemh|3 years ago
dave4420|3 years ago
adamscybot|3 years ago
alexandremonjol|3 years ago
isusmelj|3 years ago
tambourine_man|3 years ago
jmartens|3 years ago
unknown|3 years ago
[deleted]
ohmahjong|3 years ago
JSDevOps|3 years ago
planxty|3 years ago
maxcan|3 years ago
For engaged, happy engineers its the equivalent of getting a surprise snow day when you are grown up and have to go dig your car out of the snow and its a normal day just with extra steps.
ramigb|3 years ago
lysergia|3 years ago
Not if you self-host Git
unknown|3 years ago
[deleted]
naikrovek|3 years ago
edit: oopsie I misread.
rcnewrefcellnew|3 years ago
[deleted]
wheelerof4te|3 years ago
Not a huge problem, unless it lasts for hours or gasp, days.