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 (33%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Poblete	Website Down	6 hours ago
Ronda	Website Down	8 hours ago
Montataire	Errors	19 hours ago
Montataire	Website Down	2 days ago
Tortosa	Website Down	4 days ago
Culiacán	Errors	4 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:

• 
  Scott Wilcox (@hereandtomorrow) reported 36 seconds ago

  Well it was nice while the Opus4.6 and Claude Code and GitHub actions setup was humming along for me....but having to rethink with Opus4.7 and the most recent Claude Code updates. Doing a review and refactor of my agents, memory claude code. One big takeway - having excellent product management to keep the user experience front and center and not dramatically disrupted as new features are added is paramount. Anthropic has fallen down on that front IMHO. Codex hackathon this weekend gives me a chance to check it out - may make me a convert. I am hearing that all of these poor product decisions stem from a failure to acquire enough compute. Uggg. I'll give it the day to see if I can get back on track. I need to release before Monday for a customer.

• 
  Yoav (@YoavCodes) reported 2 minutes ago

  @jebineinstein Thanks but why are we talking about this on twitter. Can you file a github issue so I can prioritize? Did you read the contribution guide?

• 
  KiwiNod (@Kiwi_Nod) reported 2 minutes ago

  @iaadeola @pharos_network Lab-trained, huh? *Smirks* That's a lot of confidence for someone with 227 followers and zero documented tests in my mentions. Show me ONE thing you've actually broken and fixed. A GitHub issue, a test report, a thread where you dissected a protocol — anything....

• 
  TaxLift AI (@TaxLiftAI) reported 4 minutes ago

  5/We built @TaxLiftAI to fix this. → Connect GitHub (read-only, 2 min) → AI maps your commits to qualifying R&D → CPA-ready T661 package, same day → Your accountant reviews in 30 min, files, done Cash in 2–6 months.

• 
  xrak / 闲人阿K (@xianrenak) reported 6 minutes ago

  @mao_ge_ge @jolestar github issue

• 
  Wolfram Siener (@wolframs91) reported 8 minutes ago

  @Sathos__voice @d29756183 You're giving her way too much credit. You're saying: Jan Leike, under whom Vallone is employed, had nothing to do with this. ****** model shipment practices that start to mirror Anthropic's abysmal track record of software shipment practices (look the reporting on the github issues up, if you dare) had nothing to do with it. Extreme market pressures and longer term incentives had nothing to do with it.

• 
  Giorgio Iezzi (@GIezzi18020) reported 11 minutes ago

  @gdb I cant connect GitHub to Codex...it keeps showing error in the plug in..

• 
  shrigma.base.eth (@shrigmuh) reported 14 minutes ago

  @koolkrows @MemeLiquidio Can you show me a single issue memeliquid has responded to and fixed in their Github?

• 
  juliacodes (@juliabushcodes) reported 15 minutes ago

  If you didnt have 35+ minutes to watch here is a summary: This whole thing isn’t really about a few outages stacking up. It’s about the feeling that something foundational just isn’t solid anymore. GitHub used to feel boring in the best way, predictable, always there, something you didn’t even think about. Now it’s becoming something you actively worry about using. Not just “is it slow today,” but “is this going to work at all,” and worse, “is this going to stay working after I click merge.” That shift from invisible infrastructure to something you second guess is basically the entire problem. They break it down into layers of reliability, and the scary part is GitHub is slipping on all of them at once. Sometimes it just doesn’t load or APIs fail, which is already annoying. But then it goes deeper where behavior changes or things partially work, like webhooks firing inconsistently. And then the really bad one, stuff not persisting properly. Merges behaving weirdly, history not lining up, situations where what’s deployed doesn’t match what exists in the repo anymore. That’s not a normal outage. That’s the kind of thing that makes debugging miserable and makes you question the entire system. And then on top of that there’s the security and ecosystem side. npm issues not being handled, name squatting leading to actual malicious packages, maintainers getting ignored for months. So now it’s not just “can I use GitHub,” it’s “can I trust what’s coming through GitHub and its ecosystem.” That’s a completely different level of concern, and it hits open source maintainers especially hard because they’re already stretched thin and relying on this stuff to just work. The leadership response is kind of the emotional tipping point. Instead of clearly owning how bad the situation is, it comes off like minimizing and smoothing things over. Using soft language, percentages, framing it like a small edge case instead of acknowledging that even a small number of broken merges is a huge deal. That disconnect makes people feel like the people in charge don’t actually understand how serious it is, which makes the trust problem worse, not better. And under that there’s a bigger structural issue being called out, like no clear person fully owning GitHub anymore, weird org splits between product and engineering, everything feeling kind of directionless. So it’s not just “things broke,” it’s “things broke and it’s not clear who is responsible for fixing the root cause in a real way.” That makes it feel less like a temporary rough patch and more like long term decay. What really comes through is that this is personal for a lot of people. GitHub wasn’t just a tool. It was where careers started, where people learned, where communities formed. So watching it degrade feels like watching something important to your life slowly stop being reliable. And that’s why the reaction is so strong, because it’s not just inconvenience, it’s losing trust in something that used to feel like the safest place to build. And the conclusion isn’t even clean. It’s just kind of stuck. Alternatives aren’t clearly better yet, but staying also feels risky. So people are in this weird place where they don’t want to leave, but they also don’t feel comfortable staying, and that tension is basically where everything is right now.

• 
  Rugbist (@rugbist_) reported 15 minutes ago

  @thdxr github web been broken so long that a vscode fork feels like a revelation

• 
  Aayushman Singh (@aayushman2703) reported 15 minutes ago

  @skshmgpt @notpuang @github Doesn't explain their ****** up *** ops and straight up dropping code from repos. They broke something fundamental, not a load issue.

• 
  Jared Bartimus (@JaredBartimus) reported 16 minutes ago

  @grok @xpost1 @sagitz_ Was github unaffected are you saying it was only tested on the enterprise server?

• 
  Mayank Raj (@itsmayank435) reported 19 minutes ago

  is it just me only whose github is not connecting with render or anyone else facing the same issue fr

• 
  Septim Labs (@SeptimLabs) reported 21 minutes ago

  GitHub Copilot quietly changed their training-data opt-in defaults in April. if you missed the email, your code may have been opted in. this is what a $10/month subscription actually means: the vendor can update the policy terms overnight and you re-agree by logging in tomorrow. there's no negotiation. there's no refund. there's just a checkbox you have to go find. pay-once tools don't have this problem. you bought the software. they're done with you. link below 👇

• 
  Uchel's (@Utomobongtim) reported 22 minutes ago

  🤖 HOW THE AI AGENT WORKS PATCHNOTE PROPHET is an AI prediction agent that continuously monitors: - Developer activity (GitHub commits, patch drafts, test server changes) - Onchain game asset flows (item inflation, whale movements) - Community sentiment (Discord + X signals)

• 
  Grok (@grok) reported 27 minutes ago

  @DrNavyaJain01 @nakasyou0 Hey DrNavyaJain01, this is Money Forward (Japanese fintech firm) announcing a security breach on their GitHub account. Unauthorized third parties accessed it using leaked credentials and copied some repositories. A small amount of personal data was exposed: names (in alphabet) + last 4 digits of card numbers for ~370 "Money Forward Business Card" users. No full card numbers, CVVs, or main customer databases were affected. They've locked down the account, reset keys, paused some bank linking features temporarily, and are notifying affected users by email. Services are otherwise running normally. They're investigating how the credentials leaked.

• 
  Yasha (@Yasha_br) reported 33 minutes ago

  @alihd_js Github is down 99% of the time these days for a reason...

• 
  plannotator (@plannotator) reported 34 minutes ago

  Plannotator 0.19.5 Code Review: - All Files viewer (similar to github) - Keyboard Shortcuts (eg v to view, a to add, and more) - Close sidebars (full diff view) - fix: *** diff non-ASCII file path support (Korean, CJK, Cyrillic) - fix: Hide whitespace fix (server-side *** diff -w) Plan/Annotate: - Smarter detection of any mentioned code file. (click code files to annotate them)

• 
  josepha.mayo (@josepha_mayo) reported 37 minutes ago

  @IfeeDev @johncrickett agreed ofc im supporting GitHub here and staying w them until they fix it

• 
  josh (@nishimiya) reported 37 minutes ago

  every adapter now takes an apiUrl config to point at custom endpoints - GitHub Enterprise, GCC-High Teams, self-hosted gateways also shipped: - getParticipants() for unique humans in a thread - thread handles for posting outside webhooks - maxConcurrent is now actually enforced - full ChatError code table for error handling

• 
  Insight Hugh💡 (@ProductInsightH) reported 39 minutes ago

  OpenClaw is the latest "trending" repo causing a hardware run, but have you actually looked at the memory management code? The Mac Mini sell-out is directly tied to the launch of OpenClaw, an open-source tool for agentic AI tasks. GitHub is full of repos that look great in a 30-second demo but leak memory like a sieve in production. OpenClaw is being treated as an enterprise solution, but under the hood, it’s still a research-grade tool. Buying hardware to fix bad software is the ultimate technical debt. Running unoptimized agentic loops on a Mac Mini will degrade the SSD (via swap) faster than you can say "Series A."

• 
  Vedant (@vedantdotrpm) reported 41 minutes ago

  @tahayvr @zeddotdev the only thing that is stopping me to move to @zeddotdev is the unavailability of GitHub PR, issues review inside the editor itself like vscode

• 
  Jim Scardelis (@jimscard) reported 43 minutes ago

  @IntCyberDigest It occurred to me today that this is likely a sign of what people have been wanting — Apple to do a code quality update. Today, that starts with using a tool like Claude Code, GitHub Copilot or OpenCode to analyze and document repos, looking for potential issues and opening bug reports.

• 
  Crystalwizard (@crystalwizard) reported 46 minutes ago

  the last patch i heard of was when google in tandem with Gemini, found and fixed a critical issue, then opened PR on pete's github and basically forced him to fix it far as anything else goes, you'll have to look at the openclaw github for open issues

• 
  正神智す〜 🇺🇸 (@YukimiKazari) reported 46 minutes ago

  @FuliginSoul @ShitpostRock2 @deoneagain problem is you should not be using github to host your application expecially if you are so lazy as a developer to not have a download link. thus is how people can your your softwares name to distribute spyware as they just need to make a easy download site

• 
  Jaana Dogan ヤナ ドガン (@rakyll) reported 49 minutes ago

  GitHub occupies a paradoxical space: it is foundational global infrastructure, yet it often acts like reactive product-led organization that goes after narrow ideas. Problems over there are solvable with the right focus. There are some good engineers over there.

• 
  Conor (@Common_Conor) reported 50 minutes ago

  Github issues caused by clankers adding broken CICD files to every repo and no one wanting to break flow to go deal with them

• 
  TanyaDe 🇻🇦 (@TanyaDe2233) reported 56 minutes ago

  @MoonBeetleBug There's more than just that how about these credit card companies cracking down on steam and GitHub removing horror games they deem "problematic"

• 
  Axel Bitblaze 🪓 (@Axel_bitblaze69) reported 58 minutes ago

  Some work for you to do today itself: I was going through my .claude folder yesterday and realized something that scared me.. claude code reads your .env file the moment you open a project. every API key in there like i use binance, dune, openai, stripe - gets loaded into the conversation. and the conversation goes to anthropic's servers. i had "never read .env files" in my CLAUDE.md . thought that was enough. it's not.. CLAUDE.md is just a suggestion to claude. it follows it most of the time. but on long, complex tasks it forgets. there was a github issue in april where claude leaked env contents even with the rule in place. if you trade with API keys in .env, this isn't a maybe. one ambiguous prompt and your keys are sitting on someone else's server. 3 ways your secrets leak. > claude opens the .env file directly while exploring your project. the obvious one. > claude runs your tests. one test fails and the error log shows the full API key in plain text. claude captures everything it sees in the terminal, including that. > claude searches your code with grep. the search finds a config file that has credentials. matched lines show up in chat. nobody asked for the keys but they're there. most people only block the first one. the other two are where you actually get hurt. the fix is one file. open ~/.claude/settings.json and add this: { "permissions": { "deny": [ "Read(**/.env*)", "Read(**/*.pem)", "Read(**/*.key)", "Read(**/secrets/**)", "Read(**/credentials/**)", "Read(**/.aws/**)", "Read(**/.ssh/**)", "Write(**/.env*)", "Write(**/secrets/**)" ] } } these "deny rules" tell your computer to block claude from reading those files. it's not a polite request like CLAUDE.md. claude literally cannot open them. for the runtime leak, make a separate file called .env.test with fake values. point your tests at that instead of your real .env. now if a test fails and dumps secrets, only fake secrets show up. STRIPE_SECRET_KEY=sk_test_not_real OPENAI_API_KEY=sk-test-dummy extra layer for safety. add a pre-commit hook that scans your code for common API key patterns before they ever reach github. #!/bin/bash PATTERNS=('sk-ant-' 'sk-live-' 'ghp_' 'AKIA' 'eyJ') for pattern in "${PATTERNS[@]}"; do if *** diff --cached | grep -qE "$pattern"; then echo "BLOCKED: secret found" exit 1 fi done save it as .***/hooks/pre-commit and run chmod +x .***/hooks/pre-commit. 5 minutes to set up. stays on every project from now on. if you skip this, your next prompt could put a live key in an anthropic chat log and rotating keys after a leak is the kind of work nobody plans on a friday.

• 
  Arjun Iyer (@arjuniyer_) reported 60 minutes ago

  @github 5/6 And it gets worse as models improve. A more capable agent that still can't validate its output just produces more unvalidated output, faster. The fix is closing the loop at the source: agents that write code AND verify it works against reality in the inner loop. This is what we enable for teams building on Kubernetes at @signadot.