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

GitHub issue - resolved

githubstatus.com

Post reply on HN
Print view View original

111–120 of 169 posts

Re: GitHub issue - resolved

#111

Post by smcl »

gibspaulding wrote: post #92
smcl wrote: post #82

Earlier quoted context omitted.

Step #3 is unfortunately often pointless given that often either: 1. the status page is unavailable too 2. the status page reports the service as green/available even though it's red/down (maybe it's still accessible to the service pinging its health status, maybe it's "accessible" but not actually functional, maybe the engineers were too busy fixing the problem to click the button to update the status page, maybe no…

I suppose a static html page saying everything is fine hosted on the same infrastructure as your service would be an accurate indicator a good chunk of the time.

Yeah it gives you a bit of confidence that the problem may not be something on your end. I don't think there's a perfect way to handle this, though.

Re: GitHub issue - resolved

#112

Post by efficax »

tyingq wrote: post #35
MattIPv4 wrote: post #5

https://www.githubstatus.com/incidents/52z0j6phhnjs

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.

having been on the other side a number of times at a site with huge amounts of traffic, very often things can be down for a huge percentage but our logs will still show thousands of requests succeeding a minute. so it might be working well but slowly for some while not at all for many

Re: GitHub issue - resolved

#115

Post by vrosas »

sveeeeeene wrote: post #97
mpsprd wrote: post #55

Earlier quoted context omitted.

HN is de facto the fastest secondary source for any current event related to tech.

I also use it for connectivity check. Most other sites have so much ads and cookies it creates long lags with adblock in some older systems I use. So I point to HN and get a really fast response that the web is working

One time HN was itself down and that was a confusing experience

Re: GitHub issue - resolved

#118

Post by tiffanyh »

Only code with Github is replicated locally, not everything else like wiki, issues, etc.

That's something I love about Fossil.

Everything with Fossil (wiki, issues, code) is replicated as well.

Re: GitHub issue - resolved

#119

Post by williamvds »

belter wrote: post #102

Git Docs... - https://git-scm.com/book/en/v2/Getting-Started-About-Version... "...The next major issue that people encounter is that they need to collaborate with developers on other systems. To deal with this problem, Centralized Version Control Systems (CVCSs) were developed. These systems (such as CVS, Subversion, and Perforce) have a single server that contains all the versioned files, and a number of clients tha…

Git avoids the problem where the central service being down gets in the way of local development. Even in Git, that central service going down means degraded collaboration.

Normally a Git remote is just an ssh-accessible machine, and so pretty resilient. But GitHub is a lot more complex, so apparently that simple service went down, along with all the features they built on top of it

Re: GitHub issue - resolved

#120

Post by rozab »

jonas-w wrote: post #27
larsnystrom wrote: post #19

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

And if HN is down, you know it's a biggie
Post reply on HN