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

GitHub appears to be struggling with measly three nines availability

theregister.com

Post reply on HN
Print view View original

61–70 of 255 posts

Re: GitHub appears to be struggling with measly three nines availability

#62

Post by throw10920 »

neonihil wrote: post #54

Nothing unexpected. Microsoft has a remarkable talent for turning good products into useless ones. Skype is another good showcase of such talent.

Windows (including Notepad and Explorer), too. I think ~Office~ ~Office 365~ ~Microsoft 365~ Copilot 365 is still technically useful despite the insane branding and licensing and AI slop features, but I doubt it'll last much longer.

Re: GitHub appears to be struggling with measly three nines availability

#63

Post by Anon1096 »

Anyone who used the phrase "measly" in relation to three nines is inadvertently admitting their lack of knowledge in massive systems. 99.9 and 99.95 is the target for some of the most common systems you use all day and is by no means easy to achieve. Even just relying on a couple regional AWS services will put your CEILING at three nines. It's even more embarrassing when people post that one GH uptime tracker that combines many services into 1 single number as if that means anything useful.

Re: GitHub appears to be struggling with measly three nines availability

#64

Post by eterm »

sixeyes wrote: post #33
eterm wrote: post #10

Earlier quoted context omitted.

If this were a place for memes, then I'd share that swimming pool meme with Microsoft holding up copilot while GitHub is drowning. Then Azure Dev Ops (formerly known as Visual Studio Team System) dead o n the ocean floor. Although given how badly GitHub seems to be doing, perhaps it's better to be ignored.

why is az devops on the floor? i am having to choose between the clients existing az dops and our internal gitlab for where to host a pipeline, and i don't know what would be good at all

It works fine,it just feels like it has been under a kind of maintenance mode for a while.

There's clearly one small team that works on it. There are pros and cons to that.

It hasn't even got an obnoxious Copilot button yet for example, but on the other hand it was only relatively recently you could properly edit comments in markdown.

If the client has existing AzDo Pipelines then I'd suggest keeping them there.

Re: GitHub appears to be struggling with measly three nines availability

#65

Post by dathinab »

wait they still have 3 ninth, it really doesn't feel like that

but then their status center isn't really trust-able anymore and a lot of temporary issues I have been running into seem to be temporary, partial, localized failures which sometimes fall under temp. slow to a point of usability. Temporary served outdated (by >30min) main/head. etc.

so that won't even show up in this statistics

Re: GitHub appears to be struggling with measly three nines availability

#68

Post by CodingJeebus »

ajhenrydev wrote: post #60
CodingJeebus wrote: post #55

Earlier quoted context omitted.

Did react render better than turbo or the opposite? I assume a well-optimized turbo page would perform better

React destroyed perf and used more resources than turbo

That's what I figured and has been my experience as well.

Re: GitHub appears to be struggling with measly three nines availability

#69

Post by bombcar »

apetresc wrote: post #51
Alifatisk wrote: post #45

Have anyone checked out the status page? It's actually way worse than I thought, I believe this is the first time I am actually witnessing a status page with truly horrible results. https://mrshu.github.io/github-statuses

Well then clearly you haven't taken a look at https://status.claude.com .

This is ... surprisingly honest? The one above is "missing" status page; and most status pages would legally have to be filed in the "fiction" section of the library.
Post reply on HN