Earlier quoted context omitted.
Just your casual $3.8T company. There were so many severe Github Actions outages (10+ ?) in the past year. Cause: Migration to the disaster zone also known as Azure, I assume. Most of them happened during (morning) CET working hours, as to not inconvenience the americans and/or make headlines. Money doesn't buy competency. It's a long-term culture thing. You can never let go on maintaining competency in your organiza…
“guess Microsoft did let go” - are we thinking of the same Microsoft here?
GitHub partial outage
41–50 of 88 posts
Re: GitHub partial outage
#42It's possible that Microsoft buying GitHub was a large-scale psyop intended to reduce the productivity of the competition. Any time their startup competitors are making too much progress they can just push the "GitHub incident" button and slow everyone down.
I'm not sure the new school cares nearly as much. But then again this is how companies change as they mature. I saw this with StubHub as well.. The people who care the most are the initial employees, employee #7291 usually dgaf
Re: GitHub partial outage
#43Anyone using GitLab have any insight on how well their operations are running these days? We originally left GitLab for GitHub after being bit by a major outage that resulted in data loss. Our code was saved, but we lost everything else. But that was almost 10 years ago at this point.
We use GitLab on the daily. Roughly 200 repos pushing to ~20 on any given day. There have been a few small, unpublished outages that we determined were server side since we have a geo-distributed team, but as a platform seems far more stable than 5-6 years ago. My only real current complaint is that the webhooks that are supposed to fire in repo activity have been a little flaky for us over the past 6-8 months. We ha…
They are pretty good, in my experience, at *eventually* delivering all updates. The outages take the form of a "pause" in delivery, every so often... maybe once every 5 weeks?
Usually the outages are pretty brief but sometimes it can be up to a few hours. Basically I'm unaware of any provider whose webhooks are as reliable as their primary API. If you're obsessive about maintaining SLAs around timely state, you can't really get around maintaining some sort of fall-back poll.
Re: GitHub partial outage
#44Github is owned by Microsoft, so this is a pretty small time indie operation, you need to give them a break.
PS: None of our 40+ engineers felt anything, our self hosted Forgejo is as snappy as ever.
Re: GitHub partial outage
#45Re: GitHub partial outage
#46Re: GitHub partial outage
#47Anyone using GitLab have any insight on how well their operations are running these days? We originally left GitLab for GitHub after being bit by a major outage that resulted in data loss. Our code was saved, but we lost everything else. But that was almost 10 years ago at this point.
No issues on GitLab. Haven't seen any outage from GitLab in like, ever.
Re: GitHub partial outage
#48Earlier quoted context omitted.
We use GitLab on the daily. Roughly 200 repos pushing to ~20 on any given day. There have been a few small, unpublished outages that we determined were server side since we have a geo-distributed team, but as a platform seems far more stable than 5-6 years ago. My only real current complaint is that the webhooks that are supposed to fire in repo activity have been a little flaky for us over the past 6-8 months. We ha…
FWIW, GitHub is also unreliable with webhooks. Many recent GH outages have affected webhooks. They are pretty good, in my experience, at *eventually* delivering all updates. The outages take the form of a "pause" in delivery, every so often... maybe once every 5 weeks? Usually the outages are pretty brief but sometimes it can be up to a few hours. Basically I'm unaware of any provider whose webhooks are as reliable a…
Re: GitHub partial outage
#49Github is owned by Microsoft, so this is a pretty small time indie operation, you need to give them a break.