Live data from Hacker News

Has GitHub been down more since its acquisition by Microsoft?

nimbleindustries.io

21–30 of 149 posts

Re: Has GitHub been down more since its acquisition by Microsoft?

#23
post #14

It's easy to see from the uptime history [1] that there have been many more incidents in April-June than in January-April. Don't know if that has anything to do with the Microsoft acquisition, but it is concerning. [1] https://www.githubstatus.com/uptime?page=1

They're still averaging 99.81% up-time over the last three months. This means they have been down for a total of 4 hours out of 90 days. I don't think it's all that concerning.

Re: Has GitHub been down more since its acquisition by Microsoft?

#24
post #7

It could also mean that they are more active and creating more chaos due to more changes. shameless and useless advertising.

Personally, I'd prefer some availability over sparkly features.

Not counting the redesign, there haven't been "sparkly" features. Sparkly features are the kinds of things the old management used to let engineers have free reign to implement.

Github pre-Microsoft was rudderless. They were more prone to implementing silly 3d model diff tools and things instead of supporting enterprise features or building powerful CI/CD tools and automation.

New Github is on the right track.

Re: Has GitHub been down more since its acquisition by Microsoft?

#25
What I don't get is how they can be down for hours on end. If I make a deploy that turns out to be buggy, I'll roll my site back to a stable previous version within minutes. Sure, that's not always possible if I've made incompatible database schema changes, but in my experience those are very, very rare (i.e. I almost always add db columns, and only rarely delete or rename columns - and when I do, I do so after those columns haven't been in use for a while).

Re: Has GitHub been down more since its acquisition by Microsoft?

#26
I really wish there was an option to decouple the core git functionality from the 'fancy' stuff (PRs, actions, issues) etc. When your CI pipeline runs directly from your git repository, not being able to commit/merge means you cannot release to production.

For binary artifacts, you can get around dependencies on a single provider by mirroring, but because git is mutable, you can't just mirror the repo and allow changes there, because you need the same permissions, ssh keys etc. for the repositories and because changes will need to be synced back to the source repository. You might as well not use Github in the first place and self-host (with all the problems that entails).

As far as I know, none of the major git providers offer this - I've experienced outages with GitLab, Bitbucket and GitHub that all affected the production environment (luckily, it's never been critical so far).

Re: Has GitHub been down more since its acquisition by Microsoft?

#27
post #14

It's easy to see from the uptime history [1] that there have been many more incidents in April-June than in January-April. Don't know if that has anything to do with the Microsoft acquisition, but it is concerning. [1] https://www.githubstatus.com/uptime?page=1

They're still averaging 99.81% up-time over the last three months. This means they have been down for a total of 4 hours out of 90 days. I don't think it's all that concerning.

This kind of depends whether you have something urgent work to handle through Github. Been waiting for over an hour so I could continue my work but Github PR-functionality hasn't shown latest changes because of the currently happening outage so I cannot. Really, really annoying and wastes partially my planned work for the day.

(of course I'm working on other stuff in the meantime but splices focus unnecessarily)

Re: Has GitHub been down more since its acquisition by Microsoft?

#29

Has nimbleindustries.io been down more since Github's acquisition by Microsoft?

Sorry... we probably should have put a CDN in front of our humble Linode box earlier. Here's a cache link:

https://web.archive.org/web/20200629103627/https://nimbleind...

Edit: Cloudflare seems to be working now. Wow, that was really easy to setup.

Post reply on HN