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 (58%)
• Errors (32%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Haarlem	Sign in	2 days ago
Villemomble	Website Down	2 days ago
Bordeaux	Website Down	6 days ago
Ingolstadt	Errors	10 days ago
Paris	Website Down	11 days ago
Berlin	Website Down	12 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:

• 
  Mihai Maruseac (@mihaimaruseac) reported 3 minutes ago

  I know a lot of great folks at GitHub and I'm saddened to see all these issues. But replying to this incident that impacted the integrity of repositories and broke the mental model of *** operations with a "roughly 0.07% were affected" is not right. I fear for GitHub's future.

• 
  Vitalii Khomenko (@VitaliiKhomenk1) reported 8 minutes ago

  @_rajathhr @NathanMcNulty You clearly don’t use Claude Sonnet in GitHub Copilot—it hasn’t been working there for over two years. You send a request, it starts thinking, and then you just get an error—that’s it, tokens wasted. I’ve written about this a thousand times.

• 
  Wassollichhier (@wassollichhier) reported 11 minutes ago

  @openclaw @cherry_mx_reds Pls fix the Confy UI integration. There are multiple issues already on github

• 
  Vulnerable U (@vuln_u) reported 14 minutes ago

  Unlike basic data theft, it encrypts and sends data to an external server, and if that fails, it pivots to GitHub creating repos, abusing tokens, and even pulling secrets from CI environments. If version 2026.4.0 is installed, assume everything on that machine is compromised.

• 
  Felix Allistar (@FelixAllistar) reported 16 minutes ago

  @kr0der subagents + github. OAI models already do a mini review at the end of large turns, and i've found a clean context window is less likely to say that its fine now, because it already said it was fine last turn. issue was really bad in -codex models, and 5.5 feels like a hybrid. subagents=new chat, it uses the same thing as /review but lets it stay pinned to your parent megathread.

• 
  Sarath 👨‍💻 (@sarat) reported 17 minutes ago

  @GergelyOrosz Moreover - they should cut down stuff like azure devops and integrate with GitHub. It’s redundant, substandard and none is building for ADO

• 
  junior85 (@junior85) reported 21 minutes ago

  @thsottiaux You need to take a look at the issues on Github. Windows app is fecked.

• 
  Rachel Blum (@groby) reported 23 minutes ago

  @hkarthik @satyanadella You mean after he fixed Windows? And their office apps? Snark aside, I don't think Github is a "Satya" shaped problem per se - the culture that leads to these things is, though. Except... it smells like the culture reverted to pre-Satya norms.

• 
  Riyaz Saiyad (@Rj_Saiyad) reported 25 minutes ago

  @github I’ve been overcharged for Copilot Pro (Ticket #4299654). You charged me $10 instead of the promised $5.11, counting free trial requests as paid! 😡 No response for 7-10 days while my money is gone and I have no access. Fix this ASAP! #GitHub #Copilot

• 
  24AIGlobal (@24AInor) reported 26 minutes ago

  Gas Town allegedly running inference on your own API credits without telling you. GitHub issue with 248 HN votes, still no official response. open source doesn't mean transparent. worth auditing what your tools actually send out.

• 
  Got Eem (@HaGoshem) reported 30 minutes ago

  @Longsword44 i also want to mention that this **** breaks constantly but the devs fix it like immediately. broke sometime this morning but the devs fixed it 3 hours ago on github

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 30 minutes ago

  There's a free open-source model that copies Anthropic's biggest secret. It is called OpenMythos. A guy named Kai Gomez built it from scratch on GitHub. Big AI models cost a fortune because they are massive. This new model is different. It loops its own brain to think deeper about hard problems. You get smarter answers without paying for a giant data center. This means you can run powerful AI right on your own machine. Your data stays private. Your API bills drop to zero. You can finally automate your emails and support tickets for free. If you want the exact steps to set this up for your business, join the AI Profit Boardroom.

• 
  Ronan Berder (@hunvreus) reported 30 minutes ago

  @badlogicgames What about greenfield work, or new features. I'm assuming you don't do that off of GitHub issues. Just talk back and forth with the AI to build a plan in a markdown file and then pull the trigger once aligned?

• 
  Atarus (@Atarussecurity) reported 32 minutes ago

  A critical SSRF vulnerability in LMDeploy, the open-source toolkit used to deploy large language models, was disclosed on GitHub last week. Twelve hours and thirty-one minutes later, an attacker was already in the honeypot. Eight-minute session. Ten requests across three phases. They confirmed the SSRF with an out-of-band DNS callback, enumerated the API surface, and ran a full internal port scan reaching AWS Instance Metadata Service, Redis, MySQL, and an admin interface behind the model server. No proof-of-concept code existed at the time of the attack. The attacker built theirs from the advisory text alone. This is the third major AI infrastructure exploitation we have analyzed in five days. The patch-to-exploit window is now measured in hours, regardless of install base size. Self-hosted AI infrastructure is a first-class attack surface. Treat it accordingly.

• 
  Filip (@filip_a__) reported 33 minutes ago

  @nbrempel @scaling01 terrible.. now u get 40 gpt 5.5 messages per month on 10$ plan and 200 on 40$ plan and thats if u dont get rate limited to hell, oai has about 450 requests per month on 20$ plan if u only do 15 requests per day with less rate limiting. idk what they are smoking at github recently

• 
  artee (@artee_49) reported 34 minutes ago

  Github has handled this quite poorly. We have not been given a list of affected commits so we can go and track them down and ensure all our automated flows are working as usual and that engineers are aware their changes got reverted. It's chaos.

• 
  bob (@blahblah8492) reported 37 minutes ago

  @kdaigle There is no way that .07% number is accurate, Why do I think that? Because 50% of our commits in that window was corrupted and we had to do ungodly things to fix it. 9 hours later we get an useless email from GitHub saying only 3 commits had this issue like it was no big deal

• 
  Micheale Hadera (@mike_enderta) reported 40 minutes ago

  Shipped @loret/sdk last week. Already at 389 weekly downloads + 66 GitHub clones with zero marketing. The weird part: almost zero stars, issues, or feedback so far. Indie devs who’ve launched devtools — how do you turn early curiosity into real engagement & adoption?

• 
  Vibe Code (@vcode_sh) reported 43 minutes ago

  @techjewel @FluentCartWP congrats! sadly you took down all PRs on github without any info - contributions approach needs revision

• 
  Ashutosh Tiwari (@beashutiwari) reported 43 minutes ago

  @agupta @garrytan I also built the same Polymarket dashboard even without AI. I was right on 19 out of 20 trades, and the one that went wrong was a cold error where the bot was not able to sell. These thing doesn’t fascinate me nowadays PS — check out my GitHub. I also have a very interesting open-source project there focused on an AI-powered arbitrage opportunity finder.

• 
  Santiago (@spersico) reported 44 minutes ago

  But it's becoming a problem, already. Isn't it? This is not a single incident. This yet another issue in a constant string of issues that have been occurring in GitHub for the last... Year?

• 
  L.vue (@eLkay0027) reported 44 minutes ago

  @github @acolombiadev copilot sdk now available for react native apps? honestly not sure what problem this solves that the chat interface doesn't already cover

• 
  Dred (comeback arc) (@0x_dred) reported 45 minutes ago

  ➤ Fix comms: Right now, the brand page feels like an announcement feed feed full of changelog updates that read like blocks of code (twitter has never looked so much like github ) Its clean and professional but lacks the fervor that makes you go “holy **** I need to try this right now.” Its more so optimizing for the available userbase who already know what Orgo is and read every changelog, not for the random dev doomscrolling at 2am who might discover them or the tokenholder trying to make sense of what’s being built The market already validated @nickvasiles-style content, I’d double down on that. ➛usecase pieces showing real-world potential and scale ➛story-driven breakdowns of what developers are building ➛ @claudeai-esque visual or demo-based “changelog” updates (where possible) instead of raw text dumps

• 
  dexploarer (@dEXploarer) reported 46 minutes ago

  ngl, the amount of projects that die, all because its holders dont have, or understand github sucks. solo founders/devs/small teams, they are building, not socializing....and if they are socializing they should prolly be building. im try and fix that soon fyi

• 
  codegraph 🇺🇸 (@codegraph) reported 49 minutes ago

  @lux this was already solved by github issues

• 
  Aryan vikash (@_aryanvikash) reported 50 minutes ago

  @AndrewPrifer @shadcn A few months ago i thought it was a bug . Then I go through that GitHub issue . Now i understand. That's a feature . Anyway i manually add it everytime

• 
  Robs (@rob_stemp) reported 52 minutes ago

  @John_Cappello_ @W0lf_Byt3 @theotherelliott Not really. While it does have some benefits, there's some clear shortcomings. We migrated from GitHub to Gitlab - It's UX is terrible compared to GitHub. Too much bloat, very old school. And some un intuitive features like copying a permalink from a line in a file. - it's web ide is lame compared to GitHubs codespaces which is a full Linux VM - duo isn't as good as GitHub copilot, especially considering GitHub copilot cli...

• 
  Son of Camp Nou (@clintonnzedimma) reported 54 minutes ago

  @Zyyon_ @Ayoolafelix Him being condescending was unnecessary and he doubled down on it with the GitHub nonsense

• 
  Louis Maddox (@permutans) reported 58 minutes ago

  Oh man this incident is a terrible moment for GitHub

• 
  Mari (@Tech_girlll) reported 60 minutes ago

  Hardcoding API keys is one of the fastest ways to get your system compromised. Once your code is pushed to a public repo like GitHub, those keys can be scraped within minutes by bots constantly scanning for exposed credentials. It also makes key rotation difficult. If a key gets leaked, you now have to hunt through your codebase, update it everywhere, and redeploy. That slows you down and increases risk. Another issue is environment separation. Production, staging, and development should all use different keys. Hardcoding ties your code to a single environment, which is bad practice and can lead to accidental misuse of production resources. Finally, it violates basic security principles like least privilege and secret management. Tools like AWS Secrets Manager, environment variables, or vault systems exist for a reason. They keep sensitive data out of your code and under controlled access.