If you go to www.githubstatus.com, the downtime is not showing in the chart. I was annoyed enough yesterday when I visited this page to figure out why my Actions had failed and was greeted with big green ticks and only a tiny red rectangle halfway down the page to indicate the problem. This time they've just scrubbed the evidence outright?
Incident with Pull Requests, Issues, Git Operations and API Requests
81–90 of 221 posts
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#82It's the same issue as the other day - display message at the top admitting that cache needs to be refreshed (or whatever the wording was)
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#83Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#84https://mrshu.github.io/github-statuses/
Seems more accurate with my experience of GitHub.
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#85Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#86Earlier quoted context omitted.
Self-hosting forgejo under tailscale + mirroring public repos through GitHub Has worked wonders for me :)
It's fascinating how fast the Forgejo I host at my university's laboratory loads from my home network. Every page load is <100ms. I think it goes to show how much bloat we don't realise exists in modern webapps.
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#87Earlier quoted context omitted.
GH was acquired by microsoft some eight years ago. It has been working quite well until recently. People may have had complaints about functionality, features, commercial issues, but the thing used to at least have a decent uptime until recently.
Has nothing to do with Microsoft acquisition... AI usage has increased demand and load. More PRs, more Action runners, more of everything firing. GitHub just wasn't ready for the scale and are now having issues catching up with it as it continues to increase exponentially.
The more surpassing part is that Microsoft hasn't figured out a way to manage/contain the AI-sourced traffic better so it doesn't create all this noisy neighbor problems for non-AI usage/users.
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#88is it me or ever since AI coding became the norm, there have been way more outages with otherwise reliable services? I get downtime on Supabase every few weeks. Even Cloudflare. And now Github
Yes, because that caused the usage of the services to skyrocket, GitHub runs on Azure and Azure is experiencing capacity strain due to AI, so GitHub's services are struggling to auto-scale
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#89Earlier quoted context omitted.
> The UI of that page is so nice Is it? Seems a text description of "Make a website outlining 'How cooked GitHub' is with a modern style" to basically any LLM would produce exactly that UI and design, literally nothing of that design a human had any influence on, besides the ones selecting what training data the used LLMs was trained with. I think most of us who've tried using LLMs for web-design can recognize that s…
What really grinds my gears is how easy it is to get better designs out of LLMs. But if you don't ask, you get the default.
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#90Earlier quoted context omitted.
> The UI of that page is so nice Is it? Seems a text description of "Make a website outlining 'How cooked GitHub' is with a modern style" to basically any LLM would produce exactly that UI and design, literally nothing of that design a human had any influence on, besides the ones selecting what training data the used LLMs was trained with. I think most of us who've tried using LLMs for web-design can recognize that s…
What really grinds my gears is how easy it is to get better designs out of LLMs. But if you don't ask, you get the default.