Too bad federated GitLab still does not exist.
Tell HN: GitHub is down (Update: Back online now)
51–60 of 73 posts
Re: Tell HN: GitHub is down (Update: Back online now)
#52It's currently working in Switzerland.
Re: Tell HN: GitHub is down (Update: Back online now)
#53It's up and running now
Re: Tell HN: GitHub is down (Update: Back online now)
#54According to GH Status ( https://www.githubstatus.com/ ), everything is fine. Gotta love functional status pages. edit: Nevermind, they just reported "degraded performance" for GitHub Actions, Issues, and Pull Requests.
Quoted post unavailable.
It seemed like a good faith effort... Between when I was told about it (which seemed like it was very early on) to when I saw the status page change (saw it 'all clear' at first) was... 3 minutes? Yes, it's not 'real time' but they don't seem to be intentionally hiding something for hours on end. There may be some consequences for reporting on false positives too quickly as well.
Re: Tell HN: GitHub is down (Update: Back online now)
#55Earlier quoted context omitted.
Why manually update vs automatically?
I think it is so they can "hide" small outages that don't rise to the level of making the news sites so they can look better. A lot of sites do this sort of thing these days.
Ish? I wrote some stuff up here: https://news.ycombinator.com/item?id=30182591
When I worked at GCP it was all manually updated as well so we could add a sentence about what was actually affected. In any sufficiently large system it's hard to indicate exactly what's broken/how to work around it, so it was just easier to `/status `.
Re: Tell HN: GitHub is down (Update: Back online now)
#56No post body was provided.
Re: Tell HN: GitHub is down (Update: Back online now)
#57Works again for me here in Germany.
Re: Tell HN: GitHub is down (Update: Back online now)
#58github.com is having issues across the site, the API including git operations (and CLI) still work. Status page is manually updated, and we're working to get it updated. EDIT: it's updated now. EDIT EDIT: github.com is back up and running, apologies for the disruption :( Source: GitHub employee
Why manually update vs automatically?
Not many places I have worked for allowed for this to be automatic. A lot of it was so they could provide a coherent explanation as to what the current state of internal attention was directed at vs what everyone can plainly see.
Re: Tell HN: GitHub is down (Update: Back online now)
#59It looks like it's back up now, can anyone confirm?
Re: Tell HN: GitHub is down (Update: Back online now)
#60According to GH Status ( https://www.githubstatus.com/ ), everything is fine. Gotta love functional status pages. edit: Nevermind, they just reported "degraded performance" for GitHub Actions, Issues, and Pull Requests.
Quoted post unavailable.
I can't imagine the status page is mentioned anywhere in the contracts. I would think that the only language that is included is that it's the customers responsibility to track and notify the vendor (Github) about any downtime, and to do that within 48 hours of the downtime having occured. And only then will the customer be eligible for compensation, probably in the form of free service credits.
My personal take is that this wording is the reason you see so few public status pages in general, especially ones with automatic and minute-by-minute status history. Better to put it on the customer to have accurate monitoring in place, which most people simply won't have.