Live data from Hacker News

GitHub issue - resolved

githubstatus.com

71–80 of 169 posts

Re: GitHub issue - resolved

#71
post #64

Earlier quoted context omitted.

Google search is basically never down. AWS is basically never down. WhatsApp is basically never down. Time for GitHub to grow up?

RO system is generally probably easier to keep up than a RW system that is constantly innovating.

I Think he was referring to Google Search in general. I've never witness since Google went live in 1998 any Google Search downtime. Probably happened but I can not remember it.

Re: GitHub issue - resolved

#72
post #35

Earlier quoted context omitted.

Seems better done than a lot of status pages, runs on separate infra, updated, has a way to subscribe, etc. However, saying "degraded performance" when you know it's "down for everyone" is an industry phrasing thing that's irritating. AWS also has "elevated response times" when everyone is seeing 5xx errors, or infinite response times.

It's not down for everyone. I can browse just fine, but my pushes get rejected, so that qualifies as "degraded performance" for me.

It's got many named granular services marked as "degraded performance" or "degraded availability" that seemed to be down for everyone.

Re: GitHub issue - resolved

#73
post #48

Earlier quoted context omitted.

I'm sure your scale is similar.

Google search is basically never down. AWS is basically never down. WhatsApp is basically never down. Time for GitHub to grow up?

> Google homepage is basically never down.

The complexity difference between the Google search "app" (not counting the vast indexing infrastructure) and GitHub is also vastly different.

> AWS is basically never down.

Lol what? Have you used AWS?

> WhatsApp is basically never down.

Makes sense, Whatsapp always had a huge focus on reliable infrastructure, since day 0. Pays off I guess :)

Re: GitHub issue - resolved

#77

Yup. Tried pushing and got "remote: fatal error in commit_refs". Was trying to understand what I was doing wrong.

Same here haha. StackOverflow informed me that it means GitHub is down, and indeed it was. I have to wonder if Git could somehow report this better. I guess it depends on exactly how GitHub is down, but "fatal error in commit_refs" made me worry that my local repo was somehow hosed.

I think it can? whenever I can't connect to my company's git server I get a `failed to connect to git.company.com` message. or something like that

Re: GitHub issue - resolved

#78

Why GitHub is down so often? Why is it not possible to keep it up 100% of time (without counting physical failure)?. I haven't seen any down time for my system (it has hundreds of thousands of users online) in months since I have completed the setup.

Only GitHub truly knows. But everyone here knows that since Microsoft acquired it, it has degraded to the point where it goes down every month.

It is so frequent and unreliable, you just might as well self-host at this point. You would likely have better up time than GitHub over the past three years since this prediction. [0]

[0] https://news.ycombinator.com/item?id=22867803

Re: GitHub issue - resolved

#79
post #27

HN should really have a “Down HN” category, as this is the most reliable place to get this information.

Everytime something has degraded performance or is down for me: 1. check my internet connection 2. check HN 3. check official statuspage

I check HN first because that also checks my internet connection :-)

that said, HN is also down a lot lately, but that the kind of outage that makes more more productive actually!

Post reply on HN