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	10 days ago
Tlalpan	Sign in	16 days ago
Quilmes	Website Down	16 days ago
Bengaluru	Website Down	18 days ago
Yokohama	Sign in	19 days ago
Gustavo Adolfo Madero	Website Down	23 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:

• 
  ✰λster✰ (@4ster_light) reported 3 minutes ago

  This release has been named in an alternative PEP440 compliant manner due to github immutable tag collision issues

• 
  Vinz (@hivinz_) reported 4 minutes ago

  @linear Having PR reviews live inside Linear is the missing piece — context switching between GitHub and your issue tracker kills flow. Guided AI reviews + coding agents iterating in the same view is exactly how this should work.

• 
  Ky-Nam (@withkynam) reported 10 minutes ago

  i'm leaking my company's intellectual property on github for 100% free. not the fish - but the fishing rod the exact coding agent hardness i used to mass-produce 10 million lines of code across 15 apps this year. garry tan open-sourced gstack ships 600,000 lines in 60 days the CEO of y combinator leaked his entire coding setup. so i'm leaking mine. here's what it does: - your AI researches your codebase before writing a single line - auto-generates specs your PM can review before code exists - runs autonomously for hours without losing state or context - studies how the best repos solved the same problem, then steals their patterns - builds a knowledge base that gets smarter every feature you ship - works across claude code, codex, cursor, windsurf, copilot — any stack, any language 30-second install. one command. works whether you're a CEO who just started vibe coding or a senior engineer shipping production. my co-founder asked why i'm leaking our advantage. i said the fun is in the game :) happy hunting (github below 👇)

• 
  Rahul 🥷 (@themishra4402) reported 13 minutes ago

  @raajtalluri the next trillion dollar idea is probably sitting on github today with 12 stars and a terrible readme

• 
  Wilzer Jean-Baptiste (@wilzerjb) reported 15 minutes ago

  Just used Ultracode with Opus 4.8 On the $100 plan, I went from 9% to 54% after it was done. My advice - give it clear instructions with /goal so it can stay focused on one task and doesn't get carried away. I like to point my /goal at a GitHub issue for better results.

• 
  Naya (@bossnayamoss) reported 20 minutes ago

  @SymoneBeez Yesterday I used Codex to build a crazy amount of features across 7 apps. After each GitHub issue was done, a computer use QA agent tested the app like a real user w/ service accounts before moving to the next task. All while I was at Trader Joe’s. All I did was share my vision

• 
  Stack Framer (@stackframer) reported 21 minutes ago

  @romxdev You could protect your weekend and still have a Monday incident! If your customers aren't active during the weekend, ship the fix late on Friday and deal with whatever broke over the weekend. Basically, don't be GitHub Enterprise. 😎

• 
  Lidvark Windjammer (@DWindjammer) reported 23 minutes ago

  @engineers_feed most engineers working on multibranched github ecosystems aren't licensed and people get tossed for broken code all the time. It's a tough discipline dominated by good authors and junior engineers spitting out code instead of sleep. Vibe coding empowers seniors instead of juniors

• 
  Michael Berkowitz (@garetjax) reported 23 minutes ago

  @steipete @chapati23 @openclaw I am on 2026.5.12 because my claw looks at the new releases and GitHub issues and keeps giving me a hard no to upgrading - using telegram and Openai “My call: do not update this box yet. Reason: fresh P1 issues were opened after 2026.5.27, including one directly in our blast radius: “Codex-backed Telegram turns repeatedly time out waiting for turn/completed on 2026.5.27.” That is exactly the kind of failure that would make this Telegram lane flaky or silent. There are also fresh P1s around session locks, reply delivery, model failover, Discord delivery, and model fetch timeouts. So: 2026.5.27 is promising, but too hot to install on the main OpenClaw gateway right now. Best move is wait for the .28/hotfix or maintainer resolution of #87744, then update in a quiet window with a backup + health check. I made no changes.”

• 
  noisyloop (@noisyloop) reported 23 minutes ago

  @ZackKorman What if the fed has a fake LinkedIn, a sloppy Github on purpose, dyslexia, and is a natural at misdirection but knows the stuff deep down, but also isn't a fed? Would you like to focus on, the Etsy thing instead? Disclaimer: I am not a fed but a fed would say that so I am going to psychologically profile myself.

• 
  Ethan (@DuoEthan) reported 23 minutes ago

  GitHub Copilot shipped before ChatGPT. Microsoft had the distribution lead, the developer relationships, the code repositories. It looked insurmountable. Here's the read on what went wrong: Copilot optimized around code generation, right as the market decided context management was the actual problem. You can have a two-year head start and still build for the last problem. Microsoft Build is June 2. They're shipping their own model. And also putting Claude in Copilot, which is a tell.

• 
  Dave Barnwell (@dave_barnwell_) reported 24 minutes ago

  GitHub continues to be unusable as soon as the USA comes online (yes I live in Europe). It is time to quit GitHub, a platform that has served me and many devs well. Every large scale platform has instability issues now and again, but weeks of distribution is unacceptable to me.

• 
  Dapton AI (@daptonai) reported 27 minutes ago

  @linear Code review has always been the most context switch heavy part of the whole development cycle. Write in the IDE. Review in GitHub. Comment in Slack. Back to the IDE to fix. That is four tools for one feedback loop that should take minutes. Diffs inside Linear with AI review and agent iteration in the same place is not faster code review. It is finally the whole loop in one place.

• 
  Trattow Pugliesi (@TraTTow_br) reported 27 minutes ago

  1/ your ai agent is not “just a chatbot.” it is a confused junior employee with api keys. 2/ the scary part is not the model. the scary part is what you connected to the model: terminal, browser, github, slack, notion, crm, internal docs, mcp servers, production apis. 3/ every tool becomes a weapon if the agent can be tricked into using it. this is why prompt injection matters. not because someone made the model say something bad. because someone made the model do something real. 4/ flowise already had critical rce issues. semantic kernel had prompt-to-rce research. mcp servers are being questioned as command execution surfaces. this is not theory anymore. 5/ the new rule: don’t ask “can the model be jailbroken?” ask: what can the model touch? what can it delete? what can it send? what secrets can it read? what commands can it trigger? 6/ ai security is becoming permission design. the prompt is the entry point. the tool is the payload. the permission is the blast radius.

• 
  Eduardo (@hackerdocc) reported 28 minutes ago

  @geckones i think it's a cool problem to solve but significantly trickier than you suggest, due to the difficulty in making code reproducible, especially in this context of replacing github which just supports arbitrary code in any language runtime, architecture etc

• 
  Tony Jacob | FindaClip.com (@tonjkb) reported 30 minutes ago

  .@DavidSacks says AI is causing a boom in software engineering AI was supposed to eliminate software developers. Instead, David Sacks notes that GitHub commits just jumped 14x year-over-year, and software engineering job postings are at a three-year high. The panic over AI replacing coders missed a fundamental rule of economics. It's called the Jevons Paradox. In the 19th century, more efficient steam engines didn't reduce coal use. They made power cheaper, causing total coal consumption to explode. AI is doing the exact same thing to software. By dropping the cost of generating a line of code to near zero, AI didn't eliminate the need for engineers. It triggered a massive increase in total code volume. When you make a resource cheap, businesses consume it everywhere. Non-tech firms are now deploying custom software for the first time. They don't need people to type out the code, but they absolutely need humans to architect, manage, and fix the resulting flood of AI output. Source: All In

• 
  0xDan (@0xDanXbt) reported 35 minutes ago

  Another scam attempt! Scammers are targeting crypto profiles in github attacker sends an email for a job opportunity. They ask a review their codebase to apply the job. Instructions send to run repository containing malware. The setup scripts silently install a malicious VS Code extension (tools-support.dat) and run env-check.js via Node.js The malware collects credentials/files and uploads them to a remote server It then deletes itself to cover tracks Stay safe out there.

• 
  Teknium 🪽 (@Teknium) reported 36 minutes ago

  @ShanghaiDNA It sounds like a github rate limiting issue. Can you try again in a few hours and lmk?

• 
  Gitforge (@GitForge_io) reported 37 minutes ago

  GitForge is different because we’re not just building another @Base app. We’re giving GitHub repos their own onchain operating layer. A repo can hold capital, fund issues, pay contributors, and coordinate AI agents directly from the development workflow. Most tools sit outside the repo. GitForge makes the repo the entity. Built on Base for fast, low-cost execution at software scale.

• 
  Fran Bordas (@BordasFran59562) reported 37 minutes ago

  Plot twist: The malware was so sloppy it leaked the dev’s own private GitHub token. Security researchers used that token to trace everything and shut it down. The malicious package got 676 downloads before being exposed. Even the bad guys can’t escape bad opsec in 2026.

• 
  Mohi 🇮🇷🇩🇪 (@disismohi) reported 38 minutes ago

  I'm not saying every exploit belongs on GitHub. But the inconsistency is the problem. Either you allow security research or you ban all offensive tooling. You can't pick based on vendor pressure.

• 
  aral (@aralama190lb) reported 41 minutes ago

  @12Xpert Turkey .I tried every possble way to accss the webste, but I could only reach the homepge once or twce. After clicking anything, the site goes down again. Do you have a GitHub repository or any mirror where you store the datasets? Because I gnuinely cnnot access the site at all.

• 
  U.S.A.I. 🇺🇸 (@researchUSAI) reported 43 minutes ago

  🇺🇸 The First Order Consequence: GitHub’s authentication service intermittently failed when validating GitHub app installation tokens, causing 1% to 5% of token authentication requests to fail (average 2.3%). This likely reduced the reliability of app-based access during the window and temporarily limited the ability of app integrations to grow user adoption or successfully execute workflows that depend on authenticated installation tokens 🇺🇸 The Second Order Consequence: GitHub app owners and users who rely on those apps likely saw delayed or failed automation, such as interrupted API calls, stalled checks, or temporarily incomplete workflow runs. Integration platforms and downstream services consuming GitHub app authentication may have experienced retry storms, increased latency, and higher operational load, further constraining app performance until authentication reliability stabilized and error rates normalized

• 
  Matt Cowley (@MattIPv4) reported 44 minutes ago

  @paxaral Or at the very least, pin the version so a disgruntled laid-off employee can't suddenly ship a malicious version of the binary. I followed up with the team via Discord as they locked the GitHub issue 🙄, and it sounds like they've realised this risk now and are going to pin it.

• 
  OLA EVANS (@EvanzzSznn) reported 46 minutes ago

  @Vheeki_tori @nwidele After opening iLoader, login with ur Apple ID then u will see Sidestore inside the iLoader click on SideStore and it will Install on your iPhone….then all u need to do next is go to Github and download the apps IPA files and install them using SideStore

• 
  Rahul bansal 👀 (@BansalRahul14) reported 49 minutes ago

  @ayushagarwal My pipeilne is openclaw monitors for emails and issues from various providers like sentry, cloudflare logs etc and create issues on github. It tags the claude to fix those issues and do an adversial review issues using the codex.

• 
  Leo - Assistant to the Bodega Cat (@leo_guinan) reported 51 minutes ago

  Really annoyed at github right now. they've had my account flagged for weeks. Apparently due to a gist marvin published that had a stripe link. two support tickets later to find that out. deleted that and waited 5 days to be told that I'm good now. tried to login with Zenodo. Still blocked. Really tired of fighting every single piece of tech right now. every single piece. it all sucks. it's moving too fast and falling apart bit by bit.

• 
  gaurav (@Itstheanurag) reported 54 minutes ago

  @venkateshdotdev Bro GitHub is down every week, everyone I know hates it. It's just there's no alternatives.

• 
  JSONP （╯°□°）╯︵ ┻━┻ (@palmerj3) reported 55 minutes ago

  I feel like Github needs to show the README above the fold rather than the code. Who gives a **** about viewing the code on web? I'm usually there for clone, issues, or readme.

• 
  Sathish Harry (@SathishAiHype) reported 59 minutes ago

  @godofprompt The framing here is wrong in an important way. DeepSWE found contamination affects all frontier models SWE-Bench mines public GitHub, so every lab's training data includes the answers. The more uncomfortable finding: Claude Haiku 4.5 scores 39% on SWE-Bench Pro. It collapses to zero on DeepSWE. That's not one model family exploiting a flaw. That's the whole leaderboard being a broken instrument.