Live data from Hacker News

GitHub was having issues

githubstatus.com

141–150 of 231 posts

Re: GitHub was having issues

#141
post #128

Earlier quoted context omitted.

Had to buy an IPv4 address for a VPS the other day in order to clone some git repositories. Couldn't believe it. Costing their customers money when they should be able to support v6 by now.

What VPS are you using that doesn't come with both IPv4 and IPv6?

There are plenty of low end providers that support IPv6 only.

At that scale price of IPv4 is the highest cost of the VPS.

Here is a list of providers I created back in 2022.

https://blog.miyuru.lk/ipv6-hosting-2022/

Re: GitHub was having issues

#142
post #128

Earlier quoted context omitted.

Had to buy an IPv4 address for a VPS the other day in order to clone some git repositories. Couldn't believe it. Costing their customers money when they should be able to support v6 by now.

What VPS are you using that doesn't come with both IPv4 and IPv6?

Hetzner charges extra for IPv4 address, as I believe most of them do. I know because I went through the same crap.

Re: GitHub was having issues

#143

Earlier quoted context omitted.

Companies should automate this. Write their own outage monitoring, feed the results, plus the cumbersome format you have to send to the provider, into an LLM, have it spit out an email requesting SLA credits or whatever the contract specifies. Probably not worth it for low cost services, but if you’re paying GitHub $x millions per year, maybe it is.

Some customers of my product, StatusGator, do this with our API. They can extract the outage data -- including the time when we detect the outage before its acknowledged. And then use that to get SLA credits.

Why would I trust you to report

Its great that your specific product does this, but as a whole I have to monitor the service separately to keep you honest (well not you specifically, I'm sure you are honest and do as much as you can to be honest, but not every company is), and of course to monitor the problems I have which you don't detect.

Re: GitHub was having issues

#144
post #130
post #70

Earlier quoted context omitted.

> GitHub is _easily_ the most unreliable SaaS product. Some of us are stuck using Atlassian and BitBucket and it is by far worse in every way.

I used GitHub for years in the tech industry, then went into the games industry and used BitBucket and hated it, thought it was such a downgrade. Now I'm back in the tech industry and using GitHub, and I miss BitBucket.

I liked the UI of BitBucket more. Stuff I accessed frequently like commits and branches were tabs across the top, easy to reach from any page. Branch dropdown sort order was by most recently updated unlike GitHub where I have to search for it. Easy to diff files. This was like 4 or 5 years ago though, maybe it has gone through modernization/enshittification. GitHub feels a bit fragmented and it tries to be more performant by virtualizing some things but while BitBucket in some sense was more rudimentary and showed it all (bogging my machine down some), it allowed me to CTRL + F easily with more confidence whereas with virtualization I've had issues with it finding things and I couldn't 100% trust it.

Re: GitHub was having issues

#145
post #128

Earlier quoted context omitted.

Had to buy an IPv4 address for a VPS the other day in order to clone some git repositories. Couldn't believe it. Costing their customers money when they should be able to support v6 by now.

What VPS are you using that doesn't come with both IPv4 and IPv6?

AWS charges for ipv4 doesn't it?

Re: GitHub was having issues

#146

Earlier quoted context omitted.

I think it's just a simple reality that most projects don't actually need or want a decentralized development process. In my experience, most projects are looking for a single, high-reliability canonical source that is in control of project leadership. Most projects are only developed by a small group, maybe even only one person.

Yeah, I think what people really liked about git (vs many other VCSs at the time) was cheap and easy local branching, not the distributed nature.

I think the distributed support is pretty nice for easy-ish mirroring. Even to a relatively bare git+ssh target on a self-hosted server. No specialized services required. I mean, just for VCS.

Re: GitHub was having issues

#147
post #130
post #70

Earlier quoted context omitted.

> GitHub is _easily_ the most unreliable SaaS product. Some of us are stuck using Atlassian and BitBucket and it is by far worse in every way.

I used GitHub for years in the tech industry, then went into the games industry and used BitBucket and hated it, thought it was such a downgrade. Now I'm back in the tech industry and using GitHub, and I miss BitBucket.

> then went into the games industry and used BitBucket and hated it

At least it wasn't Perforce?

Re: GitHub was having issues

#148

Enterprise customers, remember to email your sales rep and ask for them to report on their contracted uptime with you that you are allowed to do as per contract. They wont do this unless you ask hoping you don't notice the outages. It creates lots of internal pain - they have no automation internally for reporting on this. This is the only way anything will ever change. GitHub is _easily_ the most unreliable SaaS pro…

The way you change this is not by pressuring Microsoft to be better or less of a shitty company.

The way that you change this is by switching to a different forge host, or by self-hosting Gitea.

I do so, and it’s simple and painless and cheap, and this quarter my uptime is better than this multinational’s.

Re: GitHub was having issues

#149
post #34

I am surprised at how much github is willing to let themselves go for being a product that can nowadays be replaced by someone over the weekend. This is the second major outage within like 2 weeks.

Depends how much customization you've done to your cicd and how heavily you use custom GHA, and other plugins. No way my org could move off in a weekend.

Agreed... you could probably move a single project over pretty easily on a weekend, or several depending on how integrated you are.

Re: GitHub was having issues

#150
post #70

Enterprise customers, remember to email your sales rep and ask for them to report on their contracted uptime with you that you are allowed to do as per contract. They wont do this unless you ask hoping you don't notice the outages. It creates lots of internal pain - they have no automation internally for reporting on this. This is the only way anything will ever change. GitHub is _easily_ the most unreliable SaaS pro…

> GitHub is _easily_ the most unreliable SaaS product. Some of us are stuck using Atlassian and BitBucket and it is by far worse in every way.

Isn't Sourcetree an Atlassian product? I used that for a while when my company outlawed Github and it seemed to do a good job.
Post reply on HN