5 ms·
Sincere apologies to all GitHub users for the downtime this morning, and the brief outages last week as well. We take reliability very seriously, and will publi
by natfriedman 7y ago
Sincere apologies to all GitHub users for the downtime this morning, and the brief outages last week as well. We take reliability very seriously, and will publish a full RCA in the near future.
- latchkey 7y agoThanks Nat! Keep up the good work and thanks for contributing here. Github is still my favorite. =)
- MuffinFlavored 7y agoWhat did you guys deploy/what scale tipping point did you guys hit that caused the past 3 days of problems? At my job, if something we go wrong... management just tells us roll it back. That always fixes the problem, right? :P
- uniformlyrandom 7y agoYep, it is Dunning-Kruger effect. If rolling back works for a simple system, why wouldn't it work for a complex one? Because one cannot step into the same river twice. Heraclitus would probably make a good engineering manager.
- tcbasche 7y agoThis is 100% not the Dunning-Kruger effect. How on Earth would it be? edit - from wikipedia: In the field of psychology, the Dunning–Kruger effect is a cognitive bias in which people assess their cognitive ability as greater than it is.
- behindsight 7y agoMaybe not directly but it could still apply. I interpreted GP as saying the aforementioned management has just enough cursory knowledge to want to apply the same hammer that worked on a simple system to that on a complex system, but not enough knowledge to realize the unknown-unknowns that they aren't even aware of.
- tcbasche 7y agoI wouldn't say that's a psychological phenomenon though, just ignorance, arrogance or over-confidence.
- zeta0x10 7y agoAt least your main competitor's uptime metrics are also pretty bad, so fingers crossed.
- guessmyname 7y ago> […] downtime this morning, and the brief outages last week as well. For context, there were four (public) incidents this week: • Incident on Feb 27, 14:31 until 18:54 UTC - https://www.githubstatus.com/incidents/q07bfjh7jf1t https://www.githubstatus.com/incidents/q07bfjh7jf1t • Incident on Feb 25, 16:36 until 18:48 UTC - https://www.githubstatus.com/incidents/xp2qc958g4wt https://www.githubstatus.com/incidents/xp2qc958g4wt • Incident on Feb 20, 21:31 until 22:16 UTC - https://www.githubstatus.com/incidents/bd29l6zgr43g https://www.githubstatus.com/incidents/bd29l6zgr43g • Incident on Feb 19, 15:17 until 16:09 UTC - https://www.githubstatus.com/incidents/fxbbtd7mhz1c https://www.githubstatus.com/incidents/fxbbtd7mhz1c
- _bxg1 7y agoWell Bitbucket lost all of my repositories this morning so you've got a long way to fall
- 101404 7y agoWhat do you mean they "lost your repositories"?
- _bxg1 7y agoWhen I tried to log in I was prompted to "upgrade my account" to a "Bitbucket Cloud" account. After doing so, all of my repositories were gone. It seems that my repositories remained on my "Bitbucket ""Regular""" account but that my email address was no longer associated with it, giving me no way of logging in to it. I emailed support 6 hours ago and have yet to get a response.
- MyelinatedT 7y agoWow Atlassian... That is quite horrifying! Glad I stuck with GitHub through the MS acquisition. Bitbucket was probably my main alternative.
- _bxg1 7y agoYep. Luckily I was able to recover the most important one - a website I'd built a couple years ago for a paying client - from Heroku, of all places.
- zenexer 7y agoFor the record, Azure DevOps did the same thing to me when we switched over to Azure AD. My account and repositories ended up in an entirely corrupt state. Support was eventually able to resolve most of it, but I’m still discovering problems.
- _bxg1 7y agoI shudder at the thought of GitHub one day trying to integrate with people's Microsoft accounts.
- pnako 7y agoDo you guys ever miss meritocracy?