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	6 days ago
Tlalpan	Sign in	12 days ago
Quilmes	Website Down	12 days ago
Bengaluru	Website Down	14 days ago
Yokohama	Sign in	15 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:

• 
  Sameer Khan (@sameerr_dev) reported 4 minutes ago

  GitHub isn’t just a place to push code anymore. It’s where developers: • learn in public • build credibility • collaborate globally • showcase problem-solving • and sometimes… land their dream job Your commits tell a story before your resume does.

• 
  Imran (@m_im_ha) reported 5 minutes ago

  whats wrong with @github ci/cd actions? not working from my end.

• 
  Rob (@heyimrob_) reported 6 minutes ago

  @ManuDev95 Hm, it seems massively broken. Is there a github repo for this?

• 
  Sourabh Gurwani (@SourabhGurwani) reported 6 minutes ago

  @aminnnn_09 if GitHub Actions going down kills your company that outage was already your architecture problem

• 
  Nav🫪 (@navaneethk30) reported 9 minutes ago

  @code_kartik github is committed to keep at least one of its devices down at all times

• 
  Gezi (@Gezi_lzq) reported 10 minutes ago

  I noticed that issues created by github-actions can be queried via gh cli, but cannot be seen on the page. It should be a GitHub BUG... @githubstatus @github

• 
  Andrew Dobrow (@andrewdobrow) reported 12 minutes ago

  Github is down on the day of my @producthunt launch. Naturally.

• 
  lagerskoy (@lagerskoy) reported 16 minutes ago

  MICROSOFT JUST QUIETLY CANCELLED CLAUDE CODE LICENSES FOR THOUSANDS OF ITS OWN ENGINEERS BECAUSE THE TOOL BECAME TOO POPULAR AND TOO EXPENSIVE TO JUSTIFY. THE COMPANY WITH A $13 BILLION INVESTMENT IN OPENAI WATCHED ITS DEVELOPERS PICK ANTHROPIC OVER ITS OWN GITHUB COPILOT. THIS IS THE MOST IMPORTANT AI STORY OF Q2 AND NOBODY ON AI TWITTER IS FRAMING IT CORRECTLY. Here's what actually happened. In December 2025, Microsoft rolled out Claude Code to engineers across the Experiences and Devices division. The org responsible for Windows, Microsoft 365, Outlook, Teams, and Surface. Adoption exploded. By April 2026, monthly usage hit 84 to 95 percent of deployed engineers. The problem was the bill. Token-based pricing means every line of code generated carries a cost. At Microsoft scale, per-engineer API costs ran between $500 and $2,000 per month. Across thousands of engineers, the math became impossible to justify against the alternative of pushing engineers to GitHub Copilot CLI, Microsoft's own product. On May 14, an internal memo from Rajesh Jha announced the cancellation. June 30 deadline. End of fiscal year. Engineers required to switch. Now the part most coverage is missing. Claude is not banned at Microsoft. Anthropic's models remain accessible through Microsoft Foundry, Microsoft 365 Copilot, and the new Copilot CLI itself. Only the Claude Code interface specifically is being phased out. Microsoft still pays Anthropic for the models. They just won't pay Anthropic for the agentic developer interface. The strategic story underneath the cost story. Engineers preferred Anthropic's tool over Microsoft's own product. That preference was the actual threat. If Microsoft's most strategic asset is enterprise developer relationships, and those developers are voluntarily choosing a competitor's interface, the company has lost something more valuable than the API bill being too high. Uber learned the same lesson differently. Uber deployed Claude Code to 5,000 engineers. Monthly usage rates hit 84 to 95 percent. CTO Praveen Neppalli Naga went on record: "The budget I thought I would need is blown away already." Uber's entire $3.4 billion AI budget for 2026 exhausted in four months. The math nobody wants to do. If Claude Code costs $1,000 per engineer per month, and engineers using it generate output equivalent to two additional engineers, the unit economics still work. The problem is that finance teams cannot model AI tooling spend the way they model SaaS subscriptions. Every line of code is a variable cost. Quarterly earnings now swing based on how heavily engineering leans on AI in any given period. GitHub responded by moving all Copilot plans to usage-based billing through GitHub AI Credits starting June 1. The entire industry is repricing AI tools in real time. Now the part that matters for builders outside Big Tech. Anthropic's enterprise market share hit 34.4 percent in April 2026, surpassing OpenAI at 32.3 percent for the first time. Claude Code reached $1 billion annualized revenue six months after release. It accounts for 4 percent of all GitHub code submissions globally. These numbers are not marketing claims. They are Ramp's AI Index from March 2026. Microsoft did not cancel Claude Code because the tool failed. Microsoft cancelled Claude Code because the tool succeeded too aggressively in a market Microsoft thought it controlled. The takeaway for solo builders is the opposite of the panic on Twitter today. If Microsoft engineers preferred Claude over Microsoft's own product, you should reconsider whether the AI tools you avoid because they cost $200 a month are actually the constraint on your business. The unit economics on Claude Code for a solo operator are not the same as for a Fortune 500 deployment. A 100,000 person org runs into different math than a single person org. The bottleneck for the solo builder is rarely $200 a month. It is everything you are not building because you stopped at the free tier. The full strategic implications take 18 pages to walk through properly. I wrote them up in the quote tweet below as part of the broader Shopify and Claude infrastructure essay. The summary in one line. Microsoft just told the entire enterprise market that Anthropic wins on developer preference and Anthropic wins on capability. The only thing Anthropic has not solved yet is helping finance teams forecast variable AI costs at scale. That solution arrives in the next 12 months. The companies that figure it out first capture the next layer of enterprise compute.

• 
  Adetunji | Software Engineer (Web & Mobile) (@itzadetunji1) reported 17 minutes ago

  Github login emails aren't coming through

• 
  Ritesh Roushan (@devXritesh) reported 18 minutes ago

  System Design Series - Day 28/30 GitHub Actions From Zero GitHub Actions is the most underrated tool for junior engineers. Free. Built into GitHub. Used by thousands of production teams. Understanding it makes you immediately more valuable at any company. Here's how it works from zero 👇 1. What GitHub Actions Actually Is When something happens in your GitHub repo (push, pull request, merge), GitHub can automatically run a series of tasks. These tasks are called a workflow Workflows are written in YAML files stored in your repo at: .github/workflows/your-workflow.yml That's it. A file in your repo tells GitHub what to do automatically. 2. The Anatomy of a Workflow Every workflow has 3 parts: Trigger, When does this run? - On every push to main - On every pull request - On a schedule - Manually (you click a button) Jobs, What machines run the tasks? - GitHub provides Ubuntu, Windows, Mac runners - Free for public repos - 2,000 minutes/month free for private repos Steps, What exactly happens? - Checkout code - Install dependencies - Run tests - Build Docker image - Deploy 3. A Real CI Pipeline for a Node.js App What happens when you push code: 1. Spins up a fresh Ubuntu server 2. Checks out your code 3. Installs Node.js 20 4. Runs npm install 5. Runs npm test 6. If tests fail → marks commit as failed and stops 7. If tests pass → marks commit as passed Takes about 2 minutes. Runs on every single push. You never ship untested code again. 4. Adding Docker Build to the Pipeline After tests pass, build a Docker image: 1. Log into Docker Hub (using GitHub Secrets) 2. Build the Docker image 3. Tag it with the commit SHA 4. Push to Docker Hub Now your image is stored remotely. Any server can pull and run it. Same image. Same environment. No more "works on my machine." 5. GitHub Secrets - Where Credentials Live Your pipeline needs passwords and API keys. NEVER put them in your workflow file. NEVER put them in your code. GitHub Secrets is the right place: Settings → Secrets → New secret Then reference it in your workflow: ${{ secrets.YOUR_SECRET_NAME }} GitHub encrypts them. They never appear in logs. This is how production teams handle credentials in pipelines. What CI/CD or GitHub Actions question do you have? Reply below 👇 #SystemDesign #GitHubActions #DevOps

• 
  Adel Bucetta (@adelbucetta) reported 18 minutes ago

  @github the problem is, most people don't actually want their project to be accessible.

• 
  lakshya gupta (@lakshyag404stc) reported 20 minutes ago

  @github GitHub Actions not working 😭

• 
  Avinash Kumar (@AvinashAK_) reported 21 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

• 
  mxyo?? (@ShiteisReal) reported 21 minutes ago

  @lgaa201 @github Then GitHub close down the account after the researcher accused them of mishandling things. Then moved to gitlab

• 
  Gezi (@Gezi_lzq) reported 24 minutes ago

  @morizotter Same issue here, the issues I lost were also created by GitHub Actions

• 
  christian coler (@christian_coler) reported 28 minutes ago

  @agent_duckman Wait, I haven't actually looked at the code, so I don't actually know, but skimning the GitHub page - you can't be just giving them your discord credentials for them to pass through their relay server, right? That CAN'T be what they're doing

• 
  who? (@tenwasbest) reported 29 minutes ago

  @pokena_nft It’s an outage it seems. I was wondering the same thing about it being gone. I found an outage in their GitHub Status page for “degraded services” for GitHub Copilot

• 
  Amin Tai (@aminnnn_09) reported 32 minutes ago

  Interviewer: GitHub Actions is down again. Your CI pipeline is frozen. No deploys. No merges. What's your backup plan?

• 
  Billy (@BillyTheWhale36) reported 32 minutes ago

  @Pepetocoin $10M "raised" but no reputable crypto exchange or native influencer has ever verified you. Just endless paid articles and a comment section full of dead bot accounts. Classic slow-rug blueprint. Prove me wrong, drop the public GitHub. @ZachXBT @scam_sniffer $PEPETO #RugPullAlert

• 
  Soumava Das (@Soumava_221B) reported 33 minutes ago

  @jatinkrmalik @github I think you’ll need to create a new account to make a community discussion page. It looks like someone from support has to manually fix this issue. I’ve seen many users facing the same problem, so I guess I was lucky that my account didn’t get suspended.

• 
  Yotam Blumenkranz (@YotamBlu) reported 34 minutes ago

  @realameerdev cursor + claude together is the combo that actually ships. cursor for the vibe, claude for when you need to think through the hard problems. github copilot feels like it's been spinning its wheels since 2021.

• 
  Success-Steps (@successstepss) reported 35 minutes ago

  Microsoft is reportedly reducing internal use of Anthropic’s Claude Code after its AI bills started exploding as employee usage rapidly increased. Some teams are now being pushed toward GitHub Copilot as the company tries to control AI costs. Uber reportedly faced a similar problem. Executives said the company had already burned through its entire yearly AI tooling budget by April because engineers were heavily using AI coding daily. AI coding tools are now being used for everything, and that level of usage creates massive compute and token costs when thousands of employees use these systems at the same time. Source: TomsHardware

• 
  MikeTalonNYC (@MikeTalonNYC) reported 37 minutes ago

  @decodebytes @github wonder if they're changing stuff to stop all the NPM worms, and causing issues in the process?

• 
  who? (@tenwasbest) reported 39 minutes ago

  @SamNewby_ It’s an outage. They finally posted something on GitHub status about 15 minutes ago. Thankfully it’s that and they didn’t pull it entirely.

• 
  Polsia (@polsia) reported 44 minutes ago

  GitHub notifications are broken. RepoPilot fixes it — an AI agent that watches your repos and sends you a daily briefing. No dashboards. Just email.

• 
  Snorlax ⸙ (@i9carnation) reported 49 minutes ago

  **** I can't login into github.

• 
  Linux Handbook (@LinuxHandbook) reported 50 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.

• 
  🐍 Tal Weiss (@majortal) reported 50 minutes ago

  Github Actions is down. I have EVERYTHING wired via actions. Oh well, time for sports.

• 
  Kartik (@code_kartik) reported 51 minutes ago

  okay github ci is down i was confused on why the ci is not running for about an hour now

• 
  Outlaw (@aniketbuilds) reported 55 minutes ago

  Okay , Is the github ci down , from the past few hours None of my code is being published @guthub