Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub was down again

githubstatus.com

Post reply on HN
Print view View original

31–40 of 125 posts

Re: GitHub was down again

#31

Post by malux85 »

KingOfCoders wrote: post #26
malux85 wrote: post #17

Earlier quoted context omitted.

At large bureaucratic organisations there's often political implications of changing the official status, so often it lags behind reality until it cannot be swept under the rug anymore Not saying it's right, just an observation

As a CTO responsible for an often failing eCommerce website that lost millions when down and which I took over, I fell in the same trap of trying to sweep things under the rug. Until I decided to no longer do that and my life improved considerably.

Yeah it's very frustrating - especially if your customers are technical, they are seeing the errors and the status page says everything is fine.

I've seen status pages and error counts tied to bonuses, which only caused a giant mess of bad incentive alignment and internal lies, customers are unhappy, developers are unhappy, management are lying to upper management, it's so much easier to focus efforts on real problems and just be honest and improve. Thank goodness I dont work there anymore (cough cough Google)

Re: GitHub was down again

#32

Post by miguelmota »

Where does github publish post-moderms of downtime? I only see things like "We have deployed a fix and are monitoring recovery." in the github status history which doesn't provide details.

Re: GitHub was down again

#33

Post by atraac »

carstenhag wrote: post #10
silasdavis wrote: post #7

GitHub actions downtime is becoming painful for us. Having been lured on there with 10,000 included minutes which they shortly thereafter dropped to 3,000 I feel aggrieved paying for overages incurred from actions regularly shitting the bed.

Also having outages at Azure DevOps Pipelines every other month or so it seems. And that's paying - for hours there's no mention on the status page and we are stuck there, not being able to merge PRs or release our app in the standard way.

This is weird because we haven't encountered any real issues with agents in Azure DevOps pipelines. I think we maybe had a single downtime in last 6 months. They recently removed .NET Core 2.2 SDK without any notice and broke our builds but that's another thing.

Re: GitHub was down again

#35

Post by gourmetennui »

wizzwizz4 wrote: post #28
iso947 wrote: post #24

Don’t host yourself, it’s impossible to meet the reliability of the professionals

No, it's not. Apart from scheduled downtime when nobody's using it (e.g. restarts in the morning to update the kernel), it's not that hard to beat GitHub's uptime for a small Gitea instance. My power's on more than GitHub is up. A UPS and a tethered smartphone would get me three nines uptime-while-anyone-needs-it, which is well in excess of what I need.

I think the OP was being sarcastic.

Re: GitHub was down again

#36

Post by s_dev »

marcinzm wrote: post #19

How is GitLab like in terms of downtime? I looked at their status history page and I'm seeing a lot of incidents but it's hard to figure out what it actually means.

Thats why the self hosted options are there -- and why GitLab has a competitive advantage in this sense.

Cloud solutions are great -- however they have a golden rule, don't go down ever. This is seriously damaging to GitHubs reputation.

Re: GitHub was down again

#38

Post by tpetry »

luckylion wrote: post #11
rollulus wrote: post #8

Earlier quoted context omitted.

Currently it does, indeed. From my Slack logs, at 15:00 UTC I noticed problems. I'm pretty sure that message is manually created, at least 41 minutes after the fact.

That's the most annoying thing. Usually when I get notifications from monitoring about some issue, the first thing I do is check the vendor or provider's status page to see whether it's an issue on their end. If there's nothing, I go and investigate. Recently, more and more of them take 10-15 minutes until they mention a service outage. I don't work in super HA, I don't want to get an alarm because a single ping fail…

Idea for an startup: Paying a service to do independent health checks to popular services with the ability to select the services i would like to be notified of their health status.

Re: GitHub was down again

#39

Post by ocdtrekkie »

marcinzm wrote: post #19

How is GitLab like in terms of downtime? I looked at their status history page and I'm seeing a lot of incidents but it's hard to figure out what it actually means.

IIRC GitLab is super transparent about service outages, so it may not be that they're less reliable, but that they're more honest about it.
Post reply on HN