Earlier quoted context omitted.
possibly Azure?
Doesn't look like it, unless the status-page update is also affected :) https://status.azure.com/en-us/status
GitHub was having issues
11–20 of 96 posts
Re: GitHub was having issues
#12Here we go again [0] and again [1] and again [2] and again [3]. Time to reset the counter once again. Now everything there is degraded performance. Oh dear. Consider a self-hosted alternative or have one as a backup like I have said before. [0] https://news.ycombinator.com/item?id=27192869 [1] https://news.ycombinator.com/item?id=27172443 [2] https://news.ycombinator.com/item?id=26666843 [3] https://news.ycombinator.…
I’m tired of them now, anyone using hosted solutions should know this by now and they’ve made that choice.
Personally I believe people underestimate how easy it is to host your own services.
But I’m sick of having the conversation over and over, if people aren’t willing to investigate then, what’s the saying: “you can lead a horse to water but you can’t make them drink”
Re: GitHub was having issues
#13Here we go again [0] and again [1] and again [2] and again [3]. Time to reset the counter once again. Now everything there is degraded performance. Oh dear. Consider a self-hosted alternative or have one as a backup like I have said before. [0] https://news.ycombinator.com/item?id=27192869 [1] https://news.ycombinator.com/item?id=27172443 [2] https://news.ycombinator.com/item?id=26666843 [3] https://news.ycombinator.…
Re: GitHub was having issues
#14Re: GitHub was having issues
#15Maybe these are just a bunch of coincidences, but I have a feeling that GitHub is being poorly run recently. Apart from quite frequent uptime issues, it seems that Github Actions is pretty half-baked and they completely botched the migration of Dependabot (for example, take a look at this issue and especially, how it was handled: https://github.com/dependabot/dependabot-core/issues/3253 )
However, scrolling back through the status page's history for the last year shows that there between 6 and 12 incidents every month, and it often hovers at the high end of that range.
That has to be an utter misery for anyone who's on call.
Re: GitHub was having issues
#16OT but why did it capitalize the title like that? I submitted "GitHub is having issues". I don't see that for other submissions (unless people manually edit them afterwards). EDIT: Before the change to "GitHub was having issues" it had converted my original submission from "GitHub is having issues" to "GitHub Is Having Issues".
Re: GitHub was having issues
#17For people using GitHub Actions how often do these types of incidents impact your CI/CD?
Re: GitHub was having issues
#18Earlier quoted context omitted.
Doesn't look like it, unless the status-page update is also affected :) https://status.azure.com/en-us/status
It seems that status pages never work properly in those kind of situations. The only reliable source of information seems to be twitter and HN
Re: GitHub was having issues
#19Here we go again [0] and again [1] and again [2] and again [3]. Time to reset the counter once again. Now everything there is degraded performance. Oh dear. Consider a self-hosted alternative or have one as a backup like I have said before. [0] https://news.ycombinator.com/item?id=27192869 [1] https://news.ycombinator.com/item?id=27172443 [2] https://news.ycombinator.com/item?id=26666843 [3] https://news.ycombinator.…
Cue the age old argument chain about outsourcing responsibility vs having control of downtimes. I’m tired of them now, anyone using hosted solutions should know this by now and they’ve made that choice. Personally I believe people underestimate how easy it is to host your own services. But I’m sick of having the conversation over and over, if people aren’t willing to investigate then, what’s the saying: “you can lead…
Security risk isn't a one-and-done decision. It's a changing landscape and, arguably, there are far too many eggs in the GitHub basket for this not to be something people might want to think twice about now.
Re: GitHub was having issues
#20What's the reason these Git services have so many issues all the time?
A ton of companies are using these tools literally 24/7, at most of my jobs Github/Gitlab being down meant most of us would just be spending half of our time faking working (rare are the people who could just do "offline" dev for half a day without any external input/output)
Slack could be down it had less impact overall.