GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (65%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Itapema	Website Down	7 days ago
Tlalpan	Sign in	13 days ago
Quilmes	Website Down	13 days ago
Bengaluru	Website Down	15 days ago
Yokohama	Sign in	16 days ago
Gustavo Adolfo Madero	Website Down	19 days ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  eu (@ieuyowatashiwa) reported 4 minutes ago

  is github down?

• 
  Njuguna Mureithi (@mureithi_me) reported 5 minutes ago

  The problem here is marketing. I bet such platforms exist on Github and Gitlab. In marketing you will be competing with Uber which is willing to take a $5bn loss per year.

• 
  qualk 🌲🪓 (@qualk37) reported 7 minutes ago

  @threepointone @github made a 3CV and now your issues are gone

• 
  CryptoCloaks™ 🤘 (@CryptoCloaks) reported 7 minutes ago

  @AmericanFoolBTC @ProofofInk GitHub theres a posted a fix

• 
  Patrick Marsceill (@pmarsceill) reported 8 minutes ago

  me (trying to flex): Hey, check out this native Mac (SwiftUI) that caches all my PRs and Issues locally so I can still work on stuff even if GitHub goes down... @_clem : oh i should show you the one i have haha i did the same thing. How many other people have built this?

• 
  Shaurs (@Shaursbtw) reported 10 minutes ago

  Paid scraping tools are basically obsolete. A free open-source AI just hit #1 on GitHub. Paste a url, describe what you want in plain English, get LinkedIn profiles, emails, pricing in 60 seconds. No code, no captchas, no bans. Tested on 500 profiles. Zero issues. Comment 'SCRAPE' for the link.

• 
  0x4143 (@calebawani) reported 10 minutes ago

  @IntCyberDigest GitHub and GitLab both have clear policies against hosting active weaponized exploits that could get exploited in the wild before patches land but hey, what's life without trouble ig

• 
  Chris Kearney (@SiliconForested) reported 13 minutes ago

  I started ChonkBlocker as a free-time puzzle game back in Dec 2018. The old demo.gif I’m attaching was from the scrappy “can I even make this work?” era. Fast-forward to today: 731 commits, 168k LOC, 112 PRs, 517 GitHub issues, and roughly 240 active commit-session hours later, it’s becoming a real shipping game. Linux, macOS, Windows. Steam + Mac App Store paths. Online head-to-head multiplayer, matchmaking, Steam-friendly stats, broad SDL2/Steam Deck/controller support, native installers, CI release builds, and a lot of late-night “why is this one frame wrong?” energy. It started as a toy. Somehow it became a game.

• 
  Valtteri (@vvaltterisa) reported 16 minutes ago

  @github are you down again

• 
  Faison (@glenn_faison) reported 20 minutes ago

  We assumed it was a one-off issue and pushed an empty commit on top of it, and it's still stuck processing. It's nearing a half-hour, and GitHub Status dot com is all green🤔

• 
  Somi AI (@somi_ai) reported 23 minutes ago

  Two compounding failure modes Datacurve's team surfaced. The tasks come from real GitHub issues, small and well-specified, built on data every coding model since 2024 has trained on. DeepSWE tasks edit 7 files and 668 lines on average. SWE-Bench Verified: 1 file, 10 lines. One is engineering. The other is recall.

• 
  João Capinha (@joaopcapinha) reported 24 minutes ago

  I'm using Claude Code more than any other tool in my stack right now, and not just for writing code. Here's how I'm running a DeFi project with agentic AI orchestration at its core. I'm coordinating across ClickUp, Google Drive, Slack, GitHub, and call transcripts. And the problem isn't that the information doesn't exist. It's that finding it, connecting it, and moving it between tools quietly becomes the job. Nobody puts "context archaeology" in the job description. It just eats your day. The shift: instead of jumping between apps, I talk to Claude about the project. Pull the latest task status. Cross-reference a spec. Update a ticket. Draft a message. One thread. No rebuilding context from scratch every time. It also makes you faster at being wrong (worth saying out loud!) Feed it a messy problem, you'll get back a very confident-sounding mess. The judgment still has to be yours. But the coordination overhead? The invisible tax that was never really the job? Most of it has disappeared. Huge productivity unlock.

• 
  Ivan Lim (@IvanLim7613) reported 26 minutes ago

  Core idea: - Create a new issue with a template (title, topic, keywords, target audience, tone, sources/context) - GitHub Actions triggers on issue creation - Uses OpenAI API to generate outline + full draft - Commits the Markdown file back to the repo All free-tier friendly (GitHub Actions minutes + affordable API calls). YAML is surprisingly simple.

• 
  Emil Privér (@emil_priver) reported 29 minutes ago

  i am so used to github having issues so it's just another wednesday

• 
  search founder (@n0riskn0r3ward) reported 31 minutes ago

  @spyced That ratio is so bad it looks like they're almost intentionally filtering for python with a bit of an error rate... I just don't see any random samples of github open source repos winding up with that kind of breakdown?

• 
  JimBobSquarePants 🇺🇦 (@James_M_South) reported 32 minutes ago

  How does anyone get anything done with GitHub Copilot? It's so dumbed down compared to Codex.

• 
  John Solly (@_jsolly) reported 33 minutes ago

  It's a good day for GitHub 5xx errors.

• 
  Jozef Izso (@jozefizso) reported 34 minutes ago

  Another day, another @github outage during work hours.

• 
  mbetts (@mbetts) reported 35 minutes ago

  @threepointone @github It is fallout from the issue a few weeks back. I still see it on repositories from time to time. Seems to impact those which have a lot of commits/PRs.

• 
  Satoshi Club (@esatoshiclub) reported 35 minutes ago

  From January to March, it felt like every single day there was another AI announcement. Two months later, Microsoft has told its engineers to drop Claude Code and switch back to GitHub Copilot by June 30. Uber burned through its entire 2026 AI coding budget in four months, with per-engineer token costs running between $500 and $2,000 per month. And yet, where are the major products built fully by vibe coding? Most of what we’ve seen so far is demos, wrappers, landing pages, and internal tools. AI is useful. It speeds up work. But writing code was never the hard part. Shipping, maintaining, securing, scaling, and building something people actually use still requires real engineering. The AI boom may not be over. But the “AI replaces software teams” narrative is starting to calm down.

• 
  Govind Tiwari (@Govind_tiwari_) reported 37 minutes ago

  Is GitHub down?

• 
  Live Out Loud and on Purpose (@LoveItAndLiveIt) reported 37 minutes ago

  @TheLouieCo @MikeNellis So, you’re blaming AI because you don’t want to pay a premium to bypass that problem? The moment I came across limits in GitHub Copilot — I upgraded to the first tier. And when I ran into limits after that — I upgraded again. I’ve never had a problem since.

• 
  Linux Handbook (@LinuxHandbook) reported 38 minutes ago

  GitHub Actions went down again today. For about two and a half hours, CI/CD pipelines stalled worldwide. Builds failed. Deployments stopped. Teams waited. It was the third significant Actions outage in May alone. But here's the part that doesn't get talked about enough. GitHub's own CTO admitted the platform "wasn't built for the scale it's now being asked to handle." They planned for 10x growth. The actual number turned out to be 30x. What changed? AI agents. Agentic development workflows took off in late 2025. Code agents don't just commit once and open a pull request. They iterate. They trigger workflows dozens of times per session. They run tests, check results, push fixes, trigger more runs. One agent doing what a human developer does in a week might generate 10x the Actions traffic in an hour. Multiply that across thousands of teams adopting agentic workflows simultaneously, and you have a platform being hammered by a use case it was never designed for. 257 incidents in the past year. 48 major outages. GitHub Actions alone failed 57 times. We gave the agents the keys to the CI/CD pipeline before the infrastructure was ready for them. The irony is hard to miss. The same AI momentum that made GitHub more valuable as a platform is now the thing stressing it to breaking point. The question worth asking is whether GitHub can catch up fast enough, or whether this quietly accelerates the case for self-hosted alternatives like Forgejo and Gitea. Because reliability is not a nice-to-have. For teams running production deployments through Actions, every outage is a real cost.

• 
  Serena Ge (@serenaa_ge) reported 38 minutes ago

  We wanted tasks that reflect realistic, novel engineering work. The SWE-Bench family scrapes existing GitHub issues and PRs, which creates two problems: memorization (models have already seen the solution) and triviality (most tasks are small). DeepSWE tasks are built from scratch, keeping prompts intentionally short and natural while requiring significantly more code to solve.

• 
  Avinash Kumar (@AvinashAK_) reported 42 minutes ago

  Day 12/100 📥 Wrote the logic to download GitHub Action workflow logs programmatically.  If a pipeline fails, the bot immediately grabs the error stack trace.  Data collection is the first step to automated problem-solving! 📊 #DevOpsEngineer

• 
  Avish Hakani (@AvishJH) reported 42 minutes ago

  Microsoft is reportedly winding down many internal Claude Code licenses after heavy internal adoption and shifting teams toward GitHub Copilot CLI. Interestingly, the issue wasn't that employees disliked it. Employees loved it.

• 
  Asmit (@coolcoder56) reported 47 minutes ago

  GitHub down Leetcode down TUF down Some intern deployed AI code to production

• 
  Satoshi Talks (@Satoshi_Talks) reported 56 minutes ago

  From January to March, it felt like every single day there was another AI announcement. Two months later, Microsoft has told its engineers to drop Claude Code and switch back to GitHub Copilot by June 30. Uber burned through its entire 2026 AI coding budget in four months, with per-engineer token costs running between $500 and $2,000 per month. And yet, where are the major products built fully by vibe coding? Most of what we’ve seen so far is demos, wrappers, landing pages, and internal tools. AI is useful. It speeds up work. But writing code was never the hard part. Shipping, maintaining, securing, scaling, and building something people actually use still requires real engineering. The AI boom may not be over. But the “AI replaces software teams” narrative is starting to calm down.

• 
  Techificial.ai (@techificial) reported 58 minutes ago

  @godofprompt You install a package because the GitHub repo looks clean. And then, you add an extension because everyone else is using it. You connect to an MCP server because a random post said it saves time. A few clicks later, your machine becomes an open door and you never even notice it happened. Tools like this look more like locking your front door before going to sleep.

• 
  Bryce (@blobdell) reported 58 minutes ago

  @github you guys suck. Can I not get one goddamned day when I don't have some strange wonky bullshit interrupting my workflow on your website. My firm pays real money for this and it is not good. Start fixing things. Also, your status page does not reflect the frequency of random error messages or 404 pages loading a repository/file page.