top | item 32735734

GitHub Outage

140 points| mre | 3 years ago

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.

80 comments

order

omn1|3 years ago

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.

adamscybot|3 years ago

In my experience its often the case the status site does not reflect reality -- until someone intervenes.

bowsamic|3 years ago

Status pages are absolutely useless. I've never seen them accurately reflect an outage

MattIPv4|3 years ago

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.

omn1|3 years ago

Which is weird because the unicorn is an inlined image (png), encoded in base64. Seems like they broke it.

qwertox|3 years ago

I haven't pushed to GitHub in over a year. Now I'm setting up a new page on github.io with a new repo and GitHub goes 500 just when I try to push.

Those GitHub badges... they are as ugly as it gets.

naikrovek|3 years ago

well, I for one would like more unrequested critique of artwork on a code sharing website. ಠ_ಠ

irajdeep|3 years ago

> Those GitHub badges... they are as ugly as it gets.

Bingo. Not everything in this world needs to be gamified.

blueflow|3 years ago

Do we need to create a HN post for every outage? It happens every other week.

capableweb|3 years ago

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.

RcouF1uZ4gsC|3 years ago

What else are you supposed to do when you can’t work because you don’t have access to your source code.

corford|3 years ago

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.

kid64|3 years ago

It's completely down for me. Status page says "all systems operational".

fredrikaverpil|3 years ago

The service seems very flaky right now. Even the unicorn isn't loading properly.

sivapil|3 years ago

Still getting this same error for past 10-12 hours. Tried in different times.

{ "code": 500, "message": "internal server error" }

Does anyone have luck? Any workaround to fix it?

jmartens|3 years ago

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.

bilalq|3 years ago

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.

view|3 years ago

I'm trying to clone a repo at a whopping 6KB/s from Kenya.

EDIT: Seems to be a routing issue. I've enabled a UK VPN and it's working fine now.

cherryblossom00|3 years ago

‘No server is currently available to service your request. Sorry about that. Please try refreshing and contact us if the problem persists.’

bityard|3 years ago

Interesting how outages like this seem to happen mostly on Monday^w Tuesday mornings.

HJain13|3 years ago

Its Tuesday my man :)

kleinsch|3 years ago

If you have a risky commit, esp with a three day holiday weekend, you wait to land it until after the weekend.

planxty|3 years ago

it is tuesday my dudes :P

max23_|3 years ago

I get an error saying the action can't be performed when trying to star a repo.

azeemh|3 years ago

this is what happens when you sell important community infrastructure to M$FT

dave4420|3 years ago

This predates them getting bought by MS. GitHub was notoriously flaky from the very beginning.

isusmelj|3 years ago

Same issue. Site is also very non-responsive.

tambourine_man|3 years ago

They’ve been having issues since yesterday.

jmartens|3 years ago

I'd say since Friday night Pacific time.

ohmahjong|3 years ago

Time for some deep thumb-twiddling

JSDevOps|3 years ago

Yeah I noticed it earlier.

planxty|3 years ago

Seeing the same.

maxcan|3 years ago

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.

ramigb|3 years ago

I can be both bored and engaged, don't test me buddy /s

lysergia|3 years ago

> equivalent of getting a surprise snow day

Not if you self-host Git

naikrovek|3 years ago

Not really. I'd rather be getting stuff done. ¯\_(ツ)_/¯

edit: oopsie I misread.

wheelerof4te|3 years ago

You still can use git, you just can't push the code.

Not a huge problem, unless it lasts for hours or gasp, days.