7 ms·
GitHub incident: ongoing issues with Actions, Issues and other Git operations
- joennlae 3y agoYou will probably notice it also when trying to push a new branch: `error: failed to push some refs to ` when using --set-upstream
- jaitsu 3y agoIndeed, I notice it when trying to push also: remote: Resolving deltas: 100% (3/3), completed with 3 local objects. remote: fatal error in commit_refs To github.com:acme/foo.git ! [remote rejected] HEAD -> acme/foo (failure) error: failed to push some refs to 'github.com:acme/foo.git'
- yurishimo 3y agoHaving issues with `git push` from The Netherlands. :(
- perryizgr8 3y agoThis is a monthly incident at this point. Maybe they have a rogue cron job??
- jonas-w 3y agomore like weekly when you look at the past incidents https://www.githubstatus.com/#past-incidents https://www.githubstatus.com/#past-incidents
- malka 3y agoAgain?
- rvz 3y agoYes. Once again. [0] Due to GitHub's chronic unreliability, it is guaranteed to continue happening every month. Looks like avoiding to 'centralize everything to GitHub' has aged very well [1] and at this point you would get better uptime with self-hosting instead of using GitHub. Just ask many open source organizations like RedoxOS, ReactOS, wireguard, GNOME, KDE, etc. [0] https://news.ycombinator.com/item?id=35817662 https://news.ycombinator.com/item?id=35817662 [1] https://news.ycombinator.com/item?id=22867803 https://news.ycombinator.com/item?id=22867803
- wun0ne 3y agoDoes GitHub provide uptime stats? Seems very unreliable recently.
- steelaz 3y agohttps://www.githubstatus.com/history https://www.githubstatus.com/history seems to show incidents in the last 3 months: * March - 20 incidents * April - 12 incidents * May - 4 incidents (so far)
- deleted 3y ago[deleted]
- voytec 3y agoIt's since M$FT took over, not so recently.
- deleted 3y ago[deleted]
- bobmaxup 3y agoThey used to, some screenshots of it existing here: https://interface.lt/github-uptime-and-microsoft https://interface.lt/github-uptime-and-microsoft
- capableweb 3y ago> Let’s hope it’s temporary and GitHub error 500 won’t become their own version of Blue Screen of Death. In this case it would be Green Screen of Death (GSoD or GhSoD). Heh, if anything it has gotten worse.
- that_guy_iain 3y agoAbout 10 years ago someone said we should move to self hosting because bitbucket who we used were unreliable. I looked at the status page and say 2 hours of downtime over 3-months, while we have 3-4 days of downtime on our self hosted jenkins during the same time. I always think of that when I see people complain about services being unreliable. Often we see one or two problems in short span and forget about the months were we didn't see any issues. GitHub is probably as reliable now as it has been for the past 10 years. It's always had downtime.
- Kelteseth 3y agoWhy don't we all collectively mirror our repos to gitlab and switch development to there during the monthly outage?
- geraldwhen 3y agoEnterprise says I have to use this unreliable garbage.
- bombolo 3y agoYep. We could self host. But it's forbidden.
- geraldwhen 3y agoWe migrated recently. On prem was never down, but since moving to GitHub were more down than up.
- lol768 3y agoIt's definitely no less reliable than GitLab, where a good 300GB of database data got deleted in production by accident...
- 8organicbits 3y agogitlab.com or self-hosted?
- hnarn 3y agogitlab.com is implied since it happening on a self-hosted instance would have nothing to do with gitlab as a service (they can't be responsible for your on-site backups). > Trying to restore the replication process, an engineer proceeds to wipe the PostgreSQL database directory, errantly thinking they were doing so on the secondary. Unfortunately this process was executed on the primary instead. The engineer terminated the process a second or two after noticing their mistake, but at this point around 300 GB of data had already been removed. https://about.gitlab.com/blog/2017/02/10/postmortem-of-database-outage-of-january-31/ https://about.gitlab.com/blog/2017/02/10/postmortem-of-datab...
- vermilingua 3y agoNow pages too
- JestUM 3y agoWas unable to merge PRs. Earlier, I also got GitHub PR comment emails about 6 hours late. Whatever it is, it’s been happening for more than 6 hours.
- toastal 3y agoCould you apply the patch from the URL? Pull requests aren't really needed.
- NikxDa 3y agoThe GitHub Status shows 14 incidents affecting Git Operations this year alone [1]. That's quite a lot, considering it's only May. I wonder if the outages were always this frequent and just get more publicity on here now, or whether there was a significant increase in outages fairly recently. [1] https://www.githubstatus.com/history https://www.githubstatus.com/history
- capableweb 3y agoMany outages happen because something changed, and someone/something missed one of the effects of said change, bringing the platform down immediately, or after a while. There was a period of time when GitHub basically didn't change, for years. And the platform was relatively stable (although "unicorns" (downtime)) still happened from time to time. But nowhere near as often as now, but then again, there is a lot of more moving pieces now compared to before.
- dinvlad 3y agoI wonder if it has anything to do with layoffs, if crucial Ops people left
- vb-8448 3y agoi wonder if all these incidents are related to azure devops integration
- deleted 3y ago[deleted]
- voytec 3y agoThey are adding affected services to the status entry title (started with Issues, Actions, Operations). Can't even do a simple push due to this so-called "degraded performance".
- meindnoch 3y agoThankfully git is a distributed version control system, so such outages are not of major concern.
- ninepoints 3y agoI mean, you joke but that's actually fairly true. P4 users always notice when the central server goes down because you can't reliably look at changelist history, draft CLs, and do a host of other operations that are possible on git locally. (using a central VCS confers other advantages of course).
- capableweb 3y agoIgnoring the fact that what people actually do with GitHub, git is such a small part. Issues, PRs, CI/CD and basically everything that isn't git, doesn't happen over git (besides the wiki, which somehow miraculously actually is via git). Some people have their entire roadmap in GitHub, and every single bug report / feature request, without any offline backup. Don't ask me why, I don't get it. Especially since they have proven for the last few years that they cannot keep the platform up in a stable manner.
- smcleod 3y agoYou're kidding right? People / companies rely on git being available for deployments, builds, config changes, developer workflow etc
- theobr 3y agoI haven't been able to push for a bit now
- xmdx 3y agoBeen off work for a month-ish. Everything is as it was I see.
- candiddevmike 3y agoReally looking forward to kicking the tires on Gitea next month.
- dindresto 3y agoWe've switched to selfhosted Gitea last month, no regrets. Only the CI story could be a bit better. We're currently using Woodpecker but need macOS runners, and Woodpecker's "local" agent implementation is still unstable. I'm watching Gitea Actions' progress with great interest.
- capableweb 3y agoDid you try the macOS runners? Been using Linux, Windows and macOS runners without any issues for quite some time.
- hnarn 3y agoAny reason to use Gitea over the Forgejo fork? Based on the drama I'd rather use Forgejo if they're functionally equal.[1] [1]: https://forgejo.org/faq/#why-was-forgejo-created https://forgejo.org/faq/#why-was-forgejo-created
- justinclift 3y ago"We gave ChatGPT root access to our infrastructure servers, and unexpectedly it crashed everything." That's almost believable at this point. ;)
- indeyets 3y ago"Actions, Issues" are not "Git operations". would sound better without "other" in title
- jaitsu 3y agogood catch
- pavo-etc 3y agoWondered why I couldn't push my notes, appears that pushing commits is also impacted.
- arkitaip 3y agoGoddamn and here I thought I was getting errors because the files i pushed were to large or something.
- linhns 3y agoCannot create a new repo
- jelling 3y agoCivitAI.com is down and Hugging Face is having 502s for some operations. Perhaps there is a larger issue?
- scottmf 3y agoWow huggingface is down completely
- idk1 3y agoI debugged for one min at 11:59 trying to push, and then my eat-lunch notification came in at 12:00 and I opened hackernews with a tuna sandwich and this is super helpful because it means I wont need to debug it locally for 10 mins before figuring out Github is down. Edit - Just want to clarify when I say "opened hackernews with a tuna sandwich" I want to clear up that I did indeed full on mash the keyboard letters with my sandwich. It's costing me a fortune in keyboards every day and it's ruining my sandwich most days as well, I think I have an issue.
- koolba 3y agoIdeally both GitHub and HN would be down at the same time. With nowhere to discuss the former, people might actually get something done.
- candiddevmike 3y agoThis is why I don't touch other people's keyboards.
- idk1 3y agoWell from another perspective, a bootstrapping perspective, and hackernews does like a bootstrapping perspective, I could make a case that a good meal could pick licked out of most keyboards, saving money on lunch once a week.
- capableweb 3y agoLittle bit of bacteria helps build up your immune system for when you really need it :)
- Sohcahtoa82 3y agoYou jest, but it's actually a legit hypothesis. https://en.wikipedia.org/wiki/Hygiene_hypothesis https://en.wikipedia.org/wiki/Hygiene_hypothesis
- brookst 3y agoYeah, this is a good argument for licking them instead.
- vienzo 3y agoInterested to hear whether anyone actually managed getting some Client Credits as per their SLA [1]? Over the last quarter they probably went sub 99.9% in some services. [1] https://github.com/customer-terms/github-online-services-sla https://github.com/customer-terms/github-online-services-sla
- papito 3y agoPerhaps everyone should stop complaining and be thankful for a chill morning. You can't create a PR right now - go get a pastry and some fresh air. Be in the moment for once. It's beautiful outside* * Where I am
- Vasniktel 3y agoGreat to be here. Next week same time?
- michaelmure 3y agoIf that makes you mad, I still need help with https://github.com/MichaelMure/git-bug https://github.com/MichaelMure/git-bug ;-) Coming at some point, kanban and pull-request support, offline-first!
- deleted 3y ago[deleted]
- shibel 3y agoRumor has it Microsoft is pushing them to move their infrastructure to Azure, which explains much of the frequent downtimes lately.
- maccard 3y agoWhere'd you get this from?
- shibel 3y ago1) A friend in DevOps who supposedly has contacts there. 2) It's not like this push is a big secret: https://www.cnbc.com/2022/10/12/microsoft-github-relying-more-on-azure-cloud-services-scott-guthrie.html#:~:text=Microsoft%20has%20been%20making%20its,company's%20own%20Azure%20public%20cloud https://www.cnbc.com/2022/10/12/microsoft-github-relying-mor...
- p-o 3y agoMaybe it's the case, but Github has always had issues with uptime and stability.
- hnarn 3y ago"Always"? I don't remember it being nearly as frequent before they were bought by Microsoft, some data to back this up would be nice.
- KomoD 3y agoWhere is their infra right now?
- everfrustrated 3y agoFrom the outside, it appears GitHub doesn't have any internal sharding going on. Outages always affect _all_ repos. Architecturally this seems rather sub optimal? EG AWS doesn't roll out changes globally - they start with an internal shard within a region and progressively roll out to more shards and more regions. Why do GitHub not do the same?
- kjuulh 3y agolast I heard they've sharded some stuff, but some of the core tables/databases are still using a monolithic architecture. And I guess you're only as strong as your weakest link, which can be not that bad, that is, if it isn't your core tables. Though take this with a grain of salt, this is mostly hearsay =D
- RamblingCTO 3y agoHm, we had this last week as well. Guess who had a demo yesterday, needed to deploy things on Thursday/Friday and couldn't :(
- capableweb 3y agoIf this is your first time being affected, I guess you have a good reason to adjust your deployment structure so you can deploy manually if needed. If this is not the first time, hopefully at least it will be the last one :)
- RamblingCTO 3y agoNo worries, we can. But I like to rely on automation to spend my time on other stuff. Worked out good in the end though ;)
- hnarn 3y agoMaybe a good time to investigate whether it's possible to hold those demos without relying on third party services.
- RamblingCTO 3y agoYou're always relying on third parties. Always. Except if you run it locally. We're way beyond that. I deployed to production just fine. It's just a helper. It adds to the stress tho.
- kwyjibo_hunter 3y agoThey’ve convinced me to shut off the GitHub status alerts I get on slack (or at least move them to their own channel that I can ignore).
- Vasniktel 3y ago2 hours going strong!
- rvz 3y agoOnce again another GitHub incident and 4 days later before the last one [0], GitHub Actions goes down. You are better off self-hosting at this point, rather than centralizing everything to GitHub [1] as it is just chronically unreliable for years ever since the Microsoft acquisition. [0] https://news.ycombinator.com/item?id=35817998 https://news.ycombinator.com/item?id=35817998 [1] https://news.ycombinator.com/item?id=22867803 https://news.ycombinator.com/item?id=22867803
- hnarn 3y ago> You are better off self-hosting at this point For medium/large companies, I fully agree. For smaller projects, specifically open source projects, I'd look at something like https://codeberg.org/ https://codeberg.org/
- hospitalJail 3y agoI'm the lone person at my team that still believes in keeping most of our stuff local, with online versions as primarily backup. Every time some global service goes down, or internal internet/intranet goes down, there is a security breach, or a WFH person has a power outage I'm reminded I'm right. I'm no luddite, these services make you dependent on them. The worst thing I'm dependent on here is a bad computer. We have backups and keep our files on our network, so it seems fine. We are slowly moving to an online system, and I'm constantly reminded all the problems shifting online. Meanwhile, if I had a linux server, we would be in control of our own destiny.
- goodoldneon 3y agoI don't know about you, but the stuff I self-manage usually has worse uptime than SaaS products
- sofixa 3y agoReally depends on the "stuff". GitLab pretty much manages itself through their Helm and Omnibus installs.
- hospitalJail 3y agoDepends. Having our programs offline mean I can run them, even if the internet isnt working. Instead of getting 0 data from downtime, I can still get the data, run the programs, and give it to the person who needs it. If we are fully online, if the servers are down, we basically lose the entire time. Not to mention, I think 'uptime' is a pretty optimistic number, unusable slow service doesnt seem to hit any metrics I'm aware of.
- dijit 3y agoDoesn't matter if your uptime is 80% as long as that 20% of downtime is happening when nobody is working Additionally an 80% uptime architecture is really simple to maintain and restore and so on. Complexity increases exponentially the more 9's you add.
- solotronics 3y ago
- KomoD 3y agoThis happens constantly, what is the Github team doing?
- voynich 3y agoI've started working on a Forgejo instance for myself (Gitea fork). It's honestly disappointing how bad GitHub has gotten, just in terms of uptime anymore. I hope they get their stuff together.
- yuuta 3y agoEver since Microsoft acquisition
- dclowd9901 3y agoCan anyone from GH weigh in on this? We've had several major outages from GH over the last month or two, and the company has been completely silent on the causes, as well as any sort of remediation steps to fix stability. As a somewhat large size org, we're now exploring other options for code hosting.