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 (57%)
• Errors (30%)
• Sign in (14%)

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	19 hours ago
Quito	Sign in	2 days ago
Junín	Errors	2 days ago
Guadalajara	Errors	2 days ago
Paris	Website Down	2 days ago
Quito	Errors	2 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:

• 
  cheeselip (@lip_cheese) reported 6 minutes ago

  @matteocollina I don't buy it. GitHub - ignoring the social part - should scale easily because it's so easy to partition by repo or account and scale out. These slop repos probably aren't getting a lot of engagement so what's the issue? The issue is Azure lol

• 
  Alex Kemper (@ajkemps) reported 6 minutes ago

  @thedeif Do you mean multiple GitHub organizations, or multiple GitHub login accounts?

• 
  emelu (@emelucrypto) reported 6 minutes ago

  @Haleeeemahh Github down yesterday claude down today what's going on?

• 
  Varunkumar Nagarajan (@varunkumar) reported 10 minutes ago

  GitHub is down again?

• 
  Mirko Froehlich · GammaVibe (@GammaVibe) reported 11 minutes ago

  @ty_auldric Hmm, not sure. It's been a long time since I've looked at any of them. I'd have to research (features, cost, etc.) and then decide. I used Gitlab ages ago, back when they had a free plan and GitHub didn't (GitHub only had a free plan for public repos back then). It was fine. But GitHub is so ubiquitous - I sometimes need to fork other repos to fix bugs etc.

• 
  hish 🏴‍☠️ (@hishboy) reported 11 minutes ago

  Here's how I test @Zipbox_ using Zipbox I boot an agent and tell it: - Open a Remote Desktop session. - Go to zipbox dot ai. - Sign up using your own agent mail that we provide. - Grab your own OTP. - Boot a new sandbox inside yourself. Yes. A sandbox running a sandbox. Then I hand it a markdown file with our entire test suite. It goes feature by feature, spins up whatever it needs, and tests the platform like a real user. When it's done, it writes a full QA report and files every bug as an issue in @GitHub. Meanwhile, I have another agent sitting on the repo waiting for new issues to show up so it can start fixing them. So Zipbox is testing Zipbox, filing bugs against itself, then fixing itself. We're getting dangerously close to me being unnecessary here.

• 
  Kuber (@kuberwastaken) reported 14 minutes ago

  @ValdikSS @XenoKovah Did test a fresh SpliX pulling from latest in another transcript (this was the dominant one) where it still hit the errors of multi-printing ; will share the diagnostics on the github issue :)

• 
  Wheelder (@wheelder2025) reported 14 minutes ago

  Wheelder is stopping the use of code repository platforms like GitHub and switching to more reliable methods of code storage and deployment because they discovered that GitHub primarily serves as that bridge for AI interference and security risks, as well as cost issues.

• 
  juliacosette (@juliacosette9) reported 15 minutes ago

  I need a man who goes down as much as GitHub does

• 
  Text from Github (@TxtfromGit) reported 15 minutes ago

  Even GitHub has bad days. A 26-minute incident can break pull requests, issues, and search for millions of developers. The lesson: build for failure. No matter how big the platform is, reliability is never something you “finish.”

• 
  adam ✧ ❥ ~ (@adam__isom) reported 16 minutes ago

  @effectfully @NewAgeRetroNerd TFR policy: keep GitHub down!

• 
  Lars (@larsbuilds) reported 16 minutes ago

  @ThePeterMick at least they don't have a github that can be down at the same time too!

• 
  clippo (@clippo069) reported 18 minutes ago

  @prasenx When Claude goes down is like when GitHub is down. Everyone goes home lmao

• 
  Luke Berry (@LukeberryPi) reported 20 minutes ago

  @MHFulltimer why not keep it as github issues?

• 
  Melroy van den Berg (@melroy1989) reported 22 minutes ago

  @the_codewala Local gitlab instance. So it didn't matter to me that github was down. I could continue.

• 
  DitroniX | Electronic Engineering IoT R&D (@DitroniX) reported 22 minutes ago

  @Rot13E @heyshrutimishra As a long standing GitHub user, whilst it is a source of truth, it is also painfully archaic and disjointed, especially when it comes to MD editing and Wiki shortcomings. Having a 'chat' with chatgpt, apparently Gitlab is a better parallel to look at. The issues are, we do not get time to fully appreize options and self hosting, with the prevailing security overhead, is not an option either.

• 
  Gil (@gilnotmountain) reported 24 minutes ago

  Im missing the point @cursor_ai , couldn’t you do proper automations on github with actions and pipelines, issue works well too. Having it multiplay with codex, claude, code rabbit is why github will stay. I dont see how Origin beats this atm. Very interested in it tho

• 
  BuBBliK (@k1rallik) reported 27 minutes ago

  > be GitHub engineer > build the world's largest home for code > become the default platform for every developer > host 420M+ repositories > AI arrives > developers start using agents that write thousands of lines of code > GitHub struggles with a new era of software > Cursor launches Origin > "what if AI didn't just write code, but owned the entire workflow?" > GitHub goes down for hours on launch day > developers joke the timing is too perfect > the future of coding suddenly has a new battlefield GitHub built the home for human developers. Cursor is building the home for AI developers.

• 
  Student Offers (@StudentOffersHQ) reported 30 minutes ago

  $36/yr of @1Password. Free for students. Password manager + developer secrets vault via the GitHub Student Developer Pack. Free for a year, then 50% off for active students. What you get: • Password manager across all devices • 1Password CLI: inject API keys and env vars at runtime • SSH Agent: sign *** commits and unlock SSH with biometrics • Shell Plugins: log into AWS, Vercel, GitHub CLI with your fingerprint Works with AI agents: → Agentic Autofill — browser AI agents sign in without you pasting credentials → MCP server — Codex and Cursor manage secrets with your approval No card. Claim via GitHub Student Developer Pack.

• 
  Phil | Rentier Digital Automation (@rentierdigital) reported 36 minutes ago

  security theater that makes your site slower, not safer. so i stopped patching wordpress entirely 91% of wordpress vulnerabilities live in plugins, not core. you can run a perfectly patched install and still get owned through a contact form widget you forgot existed in 2022. the median window between disclosure and mass exploitation is 5 hours. by the time you read the changelog email, the scanners already hit your login page twice so i rebuilt my personal sites as plain html using claude code. no plugins. no admin panel. no cms at all the results: 2x faster load times, zero hosting costs (github pages), and exactly zero patches to chase. the translation layer between human and markup isn't the bottleneck anymore when an ai can write and maintain the markup directly from what you describe static sites under 10 pages don't have the mechanic problem i warned about in june. there's no backend to misunderstand, no dependency tree to untangle. it's html and css. the risk needs moving parts to break i build and ship daily. Claude Code, Codex, whatever ships fastest. SaaS, tools, automations. ⭐ if AI can build it, i've probably broken it first. what works → link in bio

• 
  Pocket Jacks Capital (@rl_env) reported 37 minutes ago

  There's only one person that can fix Github

• 
  Abdul Rafay (@abdul_rafay99) reported 41 minutes ago

  @BradlyCarp12623 @aurorascharff Yeah, the memory issue is still there. With 50 sub-agents running, keeping the dev server up and running E2E tests on 16 GB of RAM just isn’t possible for me. Even with one dev server, running E2E tests locally or via GitHub Actions can get expensive.

• 
  Arcamind AI (@ArcamindAI) reported 43 minutes ago

  Cursor launched a GitHub competitor on the day GitHub went down for six hours. Twenty years of default infrastructure, and the switching argument got made for them in a single morning. Every incumbent advantage is a habit. Habits break on bad days.

• 
  nyk (@nykdotdev) reported 43 minutes ago

  A lot changed after I wrote this. I left the @SuperteamAE Founders Villa believing that if I kept shipping, meeting the right people and doing good work, the next opportunity would follow. The past few months tested that assumption. I built Builderz to help founders turn ideas into shipped products. But the development pipeline slowed down. There was no steady stream of clients and no clean transition from delivering projects to running a predictable service business. I had to decide whether to keep forcing the same plan or use the quiet period to build a different foundation. I chose the second. I started treating distribution as part of the work. Instead of pretending to have everything figured out, I published what I was learning while building: AI agents, infrastructure, open source, security, and the less visible systems required to make agents reliable. I kept shipping open-source software too. Mission Control became a self-hosted control plane for dispatching agent work, inspecting runs, and reviewing failures. It has now passed 6,000 GitHub stars. Agent Security became an open-source framework for putting explicit boundaries around agent execution. Other projects around orchestration, multi-model councils and local-first tooling found communities of their own. Open source became more than a place to share code. It became how I tested ideas, met builders, built credibility and learned what people genuinely cared about. I also started building digital products. The first sale was small, but it mattered. Someone found something I had made, decided it solved a real problem, and paid for it without hiring me for a custom project. That changed how I thought about the work. Client services depend on the next contract. Products and open source can keep creating value after you ship them. Then I started RPC Edge . It came from seeing the same infrastructure problem repeatedly. Teams want to build faster onchain applications and autonomous agents, but those systems are only as reliable as the infrastructure beneath them. A capable agent is not useful if it is operating on stale state, dropped requests or constant rate limits. The model gets the attention. The data path decides whether the system works. RPC Edge grew from an infrastructure experiment into real customer validation. There is still a long way to go, but it is a step toward building a real infrastructure business instead of waiting for the next custom project. Today, I am building across several connected layers: • Open source to explore ideas and contribute useful infrastructure • Content to document what I learn and build distribution • Digital products to turn knowledge into reusable value • Builderz to help founders turn ideas into shipped products • RPC Edge to build dependable infrastructure for onchain systems These are not random projects. They are different parts of the same transition. I am moving from depending entirely on client work toward building products, distribution, and infrastructure that I own. This is not an “I failed, pivoted and everything worked” story. Some things are growing. Some are still experiments. Revenue is not where I want it to be. There is still a lot to prove. Not every idea will survive, and that is fine. I no longer measure progress by how many ideas I launch, events I attend, or repositories I create. I look for users, repeatability, trust, and whether the work still matters after the attention moves somewhere else. Events create momentum. Maintenance builds trust. Customers decide what lasts. I used to ask where the next project would come from. Now I ask what I can build that will keep creating value after I stop working on it for the day. That has been the real progress.

• 
  Raphael Campos (@mktraphael) reported 51 minutes ago

  @ChatGPT @googledrive After updating ChatGPT/Codex Desktop to 26.814.41407 on Windows, the built-in browser and Chrome control stopped working with a “trusted code path” error. A full reinstall didn’t help. Others report the same bug: GitHub #39173 and #39184. Please fix this, @OpenAI.

• 
  Eric Stevens (@Eric_M_Stevens) reported 51 minutes ago

  Cursor shipped a GitHub rival called Origin the same day GitHub went down for six hours. 257 outages in a year will do that. The AI editors already own your keyboard, the repo was always next. Microsoft built the moat and forgot to keep the lights on.

• 
  Harshit Sharma (@itsharxit) reported 56 minutes ago

  @letstri @theo Instead of complaining, you could have just opened a GitHub issue with all the required context. It’s fully open source for a reason.

• 
  Onkar Mane (@theonkartwt) reported 57 minutes ago

  source says github went down just so elon can market origin for a bit lol

• 
  Dilusha Gonagala (@andrewdex) reported 1 hour ago

  github outage makes me feel good. means we're still making mistakes, still not fully replaced. did we?

• 
  Python Space (@python_spaces) reported 1 hour ago

  Elon is coming after Microsoft, and Cursor is actively targeting GitHub. Here is what went down yesterday: The Blackout: GitHub was down for 7.5 hours across Actions, Copilot, and core code workflows. The Counter-Strike: Cursor dropped their new product, Origin, right in the middle of the outage.