Interesting how outages like this seem to happen mostly on Monday^w Tuesday mornings.
If you have a risky commit, esp with a three day holiday weekend, you wait to land it until after the weekend.
GitHub Outage
21–30 of 87 posts
Re: GitHub Outage
#22Do we need to create a HN post for every outage? It happens every other week.
Re: GitHub Outage
#23Interesting how outages like this seem to happen mostly on Monday^w Tuesday mornings.
it is tuesday my dudes :P
Re: GitHub Outage
#24Time for some deep thumb-twiddling
Re: GitHub Outage
#25The service seems very flaky right now. Even the unicorn isn't loading properly.
Re: GitHub Outage
#26‘No server is currently available to service your request. Sorry about that. Please try refreshing and contact us if the problem persists.’
Re: GitHub Outage
#27Its back
Re: GitHub Outage
#28Github 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.
Not really. I'd rather be getting stuff done. ¯\_(ツ)_/¯ edit: oopsie I misread.
[deleted]
Re: GitHub Outage
#29Even 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.
In my experience its often the case the status site does not reflect reality -- until someone intervenes.
that's the whole point of a manually updated status page. you don't want automation to update it because that automation can fail. automation likely caused the outage you want to know more about.
you also don't want your automation guessing at what the problem is, or what the effects are. you want real info from a real person even if it isn't given to you the millisecond you look for it.
this is why status pages aren't updated by automation. if they're updated by a person, you know that people know about the problem, you know that people are working on the problem, and so on, which is good, but while they figure out what's going on, you see a "green" status page.
this is normal.
(this is for future readers, more than the person I am replying to.)
Re: GitHub Outage
#30Even 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.
In my experience its often the case the status site does not reflect reality -- until someone intervenes.
Exactly, status pages tend to be updated by the humans responding to the incident, they're not automatic (that'd be pretty useless, you already know it's down, you want to know when they know it's down). Coordinating what to put on the status page when an incident happens can take time, getting the correct scope of impact from responding engineers etc.