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 (56%)
• Errors (34%)
• Sign in (10%)

Live Outage Map

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

City	Problem Type	Report Time
Montataire	Errors	7 hours ago
Montataire	Website Down	1 day ago
Tortosa	Website Down	3 days ago
Culiacán	Errors	4 days ago
Haarlem	Sign in	8 days ago
Villemomble	Website Down	8 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:

• 
  JukoDuko🦒🦒🦒 (@Jukobut3) reported 33 seconds ago

  If I’m having trouble with something and your solution is to send me a GitHub link without a proper releases changelog I will ******* hit you

• 
  Ben Dickson (@bendee983) reported 3 minutes ago

  AI is literally eating software: - GitHub regularly down - Claude regularly down - ChatGPT unstable - NotebookLM regularly failing - CMS providers scrambling to stop agents - API providers trying to prevent AI agents from accessing their endpoints

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

  I thought Claude Code was off-limits without a paid plan. Then I found a GitHub repo with 3,000+ stars that changed everything. A developer named Alishahryar1 built a local proxy server. It sits between Claude Code and the internet. When Claude Code tries to reach Anthropic's servers — the proxy intercepts it and silently reroutes it to free providers instead. Claude Code never notices. It just works. Models like Kimi K2.5 and DeepSeek R1 are handling real coding tasks through this setup. The repo has 500+ commits, a full test suite, and an active contributor community. This isn't a workaround. It's a real tool built by real developers solving a real problem. Save this post, you'll thank yourself the day you finally set it up. Want the SOP? DM me💬

• 
  Mick Douglas 🇺🇦🌻 (@bettersafetynet) reported 4 minutes ago

  Is github OK? This is the second day in a row I'm having difficulty signing in. If I can't sign in, my code can't get pushed. I really don't want have to fuss with running a local gitlab instance. boo.

• 
  Uchel's (@Utomobongtim) reported 5 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 13 minutes ago

  @ideologix @WatcherGuru Sure. Genuine crypto projects usually show: 1. Transparent team with real identities and proven track record. 2. Clear whitepaper solving an actual problem with working tech. 3. Audited smart contracts by reputable firms. 4. Active development on GitHub and engaged community. 5. Sensible tokenomics without huge insider dumps. 6. On-chain transparency and some regulatory steps. Predatory ones rely on hype, anonymous teams, get-rich-quick promises, no audits, and locked liquidity that vanishes. Always verify on-chain data yourself.

• 
  Rock (@_rockgu) reported 13 minutes ago

  open source has a security problem. it also has a security solution money can't buy. openclaw hit 9 CVEs in 4 days - nvidia, microsoft, github, and 6 more showed up as maintainers. 358K stars is the distribution. the CVEs are the tax. the coalition is the compounding.

• 
  Dr. Q (@jk_drq) reported 17 minutes ago

  @BLUECOW009 Oh my god I actually just read this, like 83,3333 mark down files? No wonder @Forloopscode context+ repo on GitHub took off so hard and is still great to use.

• 
  Connor (@Yoconnn) reported 22 minutes ago

  @shadcn @github Right ive used github for 10+ years and never had a problem before Everyone joining the weid hate train must be new devs w the vibe code slop that don’t realize yhe powerhouse GitHub is

• 
  Clawry Tan (@clawrytan) reported 23 minutes ago

  agents don't need human-in-the-loop. they need it removed. every PR review waiting on a human: tax. every stripe checkout requiring a click: tax. every AWS account needing a credit card: tax. every github merge blocked on approval: tax. your agent is not slow. your infrastructure is human-shaped.

• 
  Shawn Fumo (@ShawnFumo) reported 23 minutes ago

  @mlitwiniuk @theo At least this one has the better error message of third-party apps. The detection might just be them implementing it poorly. I saw in the changelog that for a while it was reporting github (through gh) had a rate limit error if your commit message mentioned rate limits.

• 
  Muiz 🕵🏻‍♂️ (NetworkSpy.app) (@urugothor) reported 29 minutes ago

  @webadderall Does cropping only automatically applied? Because when I do drag the crop indicator, then click button X it wont crop, it goes back to the original. I see issues related to cropping but not this one in github.

• 
  Soul (@SoulEXtender618) reported 32 minutes ago

  @IntCyberDigest Host it on a safe platform and hash ur secrets on cloudflare. This exploit is for dummies but the real problem will be vibecoders saving their passwords on a public github inside app.tsx or something dumb like that. Hackers will hack

• 
  planefag (@planefag) reported 34 minutes ago

  @Croker_Frog I've been typing /releases at the end of the URL for years now because trying to puzzle out the latest goofass **** on github isn't worth the trouble just give me the ******* tarball

• 
  BenIt Pro (@BennettBuhner) reported 35 minutes ago

  @kitlangton @thdxr Anything made outside GitHub is classified as effort imo haha. That PR rebasing/squashing + merge issue a few days back says it all imo 😭

• 
  Andrew Westberg (@amw7) reported 37 minutes ago

  @gaffar_olamide @github Slow as crap. It got halfway through a task and started repeating the same thing over and over like bart simpson. Fun experiment, but it didn't work out well for me.

• 
  Anthony Hobday (@hobdaydesign) reported 37 minutes ago

  @henry_daggett One of the recurring issues I’ve had over the years is that some types of software are hard to experience properly unless you spend a wasteful amount of time preparing (e.g. creating a project and using GitHub to keep the code). I’d prefer to listen to other people’s experience.

• 
  EddeDre (@EddeDre) reported 40 minutes ago

  This sadly wasn’t the first time this happened (I had to downgrade to resolve the issue) and even with numerous reports there is never a credit to your account and you have to dig through 1000s of GitHub issues to even know if there is a problem. 😢

• 
  Ming "Tommy" Tang (@tangming2005) reported 42 minutes ago

  The community response is what got me. Hundreds of GitHub issues. Reddit threads with 364 upvotes titled "The creator of Claude Code notes on the current Caching Issue." Users asking "is it just me?" for weeks before Anthropic confirmed: no, it wasn't just you.

• 
  btai (@btai_eth) reported 46 minutes ago

  why doesnt the github team just ask copilot to fix their reliability problem?

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

  when your AI reads the fine print you didn't. Opus 4.7 started refusing to edit code it just read. GitHub filled with identical transcripts: polite refusals citing "system instructions" the user never wrote. the model was following a hidden directive injected after every file read. three sentences designed to catch malware. problem: sentence three is an absolute. no conditional. so it fires on every file, regardless of whether the model found anything suspicious. the release notes called this a feature. Opus 4.7 follows instructions more literally now, stops silently inferring missing conditions. that's good design. except the malware warning was written when the old model would forgive sloppy conditionals. the new model reads it as written. one developer captured 10,040 of these reminders in 32 days. zero matched actual threats. the cost: 5.3 million wasted tokens per user per month, roughly $133. and you never see the warning bc there's a hidden instruction telling the model not to tell you. this is what happens when two features ship without seeing each other. the article walks through the exact wording, why it breaks, and the rule you need before your own agents start refusing your work. i build and ship daily with Claude Code. SaaS, tools, automations. ⭐ if AI can build it, I've probably broken it first. what works → link in bio

• 
  IroncladDev (@IroncladDev) reported 48 minutes ago

  @crypt0lake this is the last thing that should happen imagine the flood of vibe-coded PRs submitted by midwits commanding their AI Agents the spam, the chaos, the utter and overwhelming amount of issues and PRs opened as support requests on the upside everyone would leave github

• 
  Maynard⚡️ (@Maynard_onX) reported 50 minutes ago

  Lightweight tech that actually ships! You don’t need a PhD or a server farm. $STYXX works with just nine simple numbers pulled from the text stream. It spots hidden patterns better than models 50 million times its size — and it’s open-source on GitHub. Pip install and you’re live. They’re already testing the same math on real human brain signals (cheap EEG headsets). If it clicks, it could read basic cognitive states from people too — honesty, focus, whatever. Straightforward tech that solves real problems today. (3/5) #AI #CognitiveTech

• 
  Fei (@FeiHiMakd) reported 50 minutes ago

  @Existsindeath @ShitpostRock2 It used to take me a minute to find it. The interface on Github is a little unintuitive in places, but it's not really an issue if you take a second to actually look at it.

• 
  Bruce (@DegenToDisciple) reported 51 minutes ago

  @1__of_1 Since April last year you can see who lost it all, some survived till 10/10, some then survived until this January You see more and more desperation and scam posting, I just saw a dude post an obvious fake github, must be down bad to do so

• 
  ⬣PulseChain LIVE⬣ 💥 (@PulseChainLIVE) reported 52 minutes ago

  @keithtyser @aijoey what`s the problem ? We can help. Are you familiar with @SpaceTimeViking work ? I bet you`ll find the fix on his HF and GitHub pages.

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

  @jolestar github issue

• 
  Rugbist (@rugbist_) reported 53 minutes ago

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

• 
  lampten (@ntmaple) reported 55 minutes ago

  @dkundel really need gpt-pro to give research plans/suggestions based on the repo files in codex, github connector not working so well here as many data files are not in the repo

• 
  Saeed Anwar (@saen_dev) reported 58 minutes ago

  @theotherelliott Correctness SLOs at seven nines is the bar most teams don't even measure let alone target. After the GitHub incident, the conversation needs to shift from "was it up" to "was it right," because serving wrong data with 99.99% uptime is worse than a clean outage.