This is reaching an unacceptable level of performance. There isn't a week that work isn't interrupted by GH.
I would say we are way past unacceptable.
Incident with Issues and Webhooks – Resolved
11–20 of 275 posts
Re: Incident with Issues and Webhooks – Resolved
#12This is reaching an unacceptable level of performance. There isn't a week that work isn't interrupted by GH.
It's been unacceptable for months, but now it's at the level of "we should actively look for alternatives".
Re: Incident with Issues and Webhooks – Resolved
#13Hilariously, it looks like basically everything except Copilot is degraded. The jokes write themselves sometimes.
Re: Incident with Issues and Webhooks – Resolved
#14I keep wondering what causing such a bad service from GH lately, is it the overuse of AI generated code? Are they trying to cut costs with the infrastructure?
Re: Incident with Issues and Webhooks – Resolved
#15Github has published some incredible usage rate increase numbers, which they ascribe to the rise of agentic coding. At some point, they are going to have to change rate limits, cut free-tier usage, or find some other path to reducing load. It's clear that their infrastructure can't keep up with this significant increase, and it's unlikely that they're going to just absorb the increased costs themselves.
Very curious to see what the future holds for Github.
Re: Incident with Issues and Webhooks – Resolved
#16Hilariously, it looks like basically everything except Copilot is degraded. The jokes write themselves sometimes.
Copilot's full functionality is only fractionally useful compared to what's currently degraded.
Re: Incident with Issues and Webhooks – Resolved
#17If this was a business running on its own, without Microsoft’s capital and anti competitive practices, they would have been out of business by now.
Re: Incident with Issues and Webhooks – Resolved
#18oh no, anyway...
Re: Incident with Issues and Webhooks – Resolved
#19Github has published some incredible usage rate increase numbers, which they ascribe to the rise of agentic coding. At some point, they are going to have to change rate limits, cut free-tier usage, or find some other path to reducing load. It's clear that their infrastructure can't keep up with this significant increase, and it's unlikely that they're going to just absorb the increased costs themselves. Very curious…
They can't really cite the situation as a problem given their hand in creating and continuing it.
Re: Incident with Issues and Webhooks – Resolved
#20This is genuinely pathetic. I wish I could do my job this poorly and still be employed.