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

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	11 days ago
Ahmedabad	Errors	17 days ago
Delme	Sign in	18 days ago
Lyaud	Website Down	18 days ago
Catania	Errors	20 days ago
Inverness	Website Down	1 month 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:

• 
  Abdallah Shaban (@AbdallahSh07) reported 57 seconds ago

  @rashed_sahaji @FlutterDev Got it - did you perhaps submit a GitHub issue to help us triage this? It would be tremendously helpful if you can please do that!

• 
  Rusty Williams McMurray (@1RustyMac) reported 1 minute ago

  Persistent AI doesn’t have a supply chain problem at the model. It has a supply chain problem at the moment it changes its mind. Personality drifts. Tools get installed. Memory accumulates. The thing you shipped on Monday is not the thing answering on Friday. We can attest who built the weights. We still cannot attest who authorized what the agent became on Tuesday. That is the hole. Who is allowed to let it change? We built Living Supply-Chain Security for Persistent AI Organisms around one law: The organism may propose evolution. It may not authorize it. No trace, no drift. If an agent wants a new personality, a new tool, a new maturity, or a rollback — that change does not happen because it felt confident. Confidence is not a key. Self-narration is not evidence. Evidence is not interpretation. Interpretation is not authorization. Authorization has to come from outside the organism, bound to the exact change, used once, and written into an append-only history. Even a rollback cannot erase the record. You can restore a prior state. You cannot pretend the detour never happened. Default-deny. Hash-chained. Externally signed. We froze battery v1 on July 5 and ran it against the paper’s own claims. It held. That is executable evidence. Not a proof. Not a production blessing. Not “alignment, solved.” If it can’t be attacked, it isn’t finished. GitHub later this week. Come try to break it.

• 
  Fox (@0xMfox) reported 5 minutes ago

  Gave an AI agent a month and GitHub access. Wanted to see if it could make money. The plan was simple. Point it at bounty-labeled issues, let it write the fix, submit the pull request, collect the payout. > Day 1 12 PRs submitted. 0 merged. 2 rejected. 8 just sat there ignored. Somewhere in that first week it also passed its own tests for a file that didn't exist. Wrote 25 tests for notification_service.py. The real file in that branch was called NotificationRoutingMiddleware. Confidently reported clean anyway. > Day 30 Looked completely different. 84 PRs submitted, 59 merged, $500-800 earned. Ran the agent for about $45 in API calls that whole month. Net somewhere around $455-755. Here's the part that stuck with me. Out of those 59 merges, 3 repos accounted for 90%+ of them. Every other repo it touched, zero merges, despite 30+ PRs going out across dozens of projects. Open source bounties follow a power law. Almost nobody merges your first PR. A few maintainers will merge your tenth without even reviewing it closely. That's what actually fixed the acceptance rate, from 24% up to around 70%. Not a smarter model, a scoring function that runs before the agent touches anything. Repos where it already has 10+ merged PRs score +40. Zero competing PRs on the same issue, +20. Five or more competitors already in, -20, skip it. Repos that closed PRs without merging before, instant -100, not even worth reading the issue. The fastest way to build the credibility that makes this work isn't code at all. Documentation translations sit at a 95% merge rate, barely reviewed, always needed somewhere. A handful of clean translations got the agent enough trust that maintainers started assigning it harder issues directly, no competition, no review queue. Spam version of this, submitting to every repo with a bounty label, burned through 30+ repos for 3 that ever paid out. Worse, it reads like exactly what it is to a maintainer watching the same account flood a dozen projects with mediocre PRs. Paid out by the hour, week 1 was rough, close to $5/hour, mostly setup and failed attempts. By week 3-4, once the scoring system was tuned and a few repos trusted it on sight, that climbed to $30-50/hour on the same kind of work. Bookmark this, scoring logic is worth stealing.

• 
  Kun Chen (@kunchenguid) reported 7 minutes ago

  @petergyang yo @myfirstmate peter just told me his skills are all at user level. backpass currently only runs things at project level i want a proposal for making backpass support a user level run. put that into a github issue use fable for peter

• 
  Pranavvv👾 (@pranvv27) reported 12 minutes ago

  honestly, i’m not even mad at this. commit messages are a small thing, but they say a lot about how you work. “fix”, “update”, “changes” might get the job done, but meaningful commits show professionalism, attention to detail, and that you actually care about maintainability. your GitHub is part of your resume. might as well make it look like you know how software is built in a team.

• 
  AINotes (@ainotesus) reported 12 minutes ago

  🔥 Trending on GitHub: Ponytail Ponytail helps Claude Code avoid writing code that does not need to exist. That means less clutter, fewer unnecessary dependencies, and simpler changes to maintain. Before custom code, it checks whether the feature is needed and whether the codebase, platform, standard library, or an existing dependency already solves it. It also reviews work, audits implementation complexity, and tracks unnecessary token use without dropping validation, error handling, security, or accessibility requirements. In reported Claude Code sessions on a FastAPI and React repository, Ponytail used about 54% less code, 20% less cost, and 27% less time than the no-skill baseline. Those measurements came from 12 feature tasks, so results vary with the work. Full analysis in the first reply ↓

• 
  Åsa-Nietzsche (@AsaNietsche) reported 17 minutes ago

  @peterb0yd @burkeholland @github It's every ******* model. I'm getting whiplash from all of this everything changing forever society being turned upside down every two weeks.

• 
  Bash (@bashirbuilds) reported 18 minutes ago

  One of the hardest things about building a SaaS product today: You don't control most of the systems your product depends on. Stripe. OpenAI. AWS. GitHub. Resend. Clerk. Your code can be perfectly fine and your product can still break because something outside your code changed. The more dependencies you add, the harder this becomes. That's the problem I'm building Reeno to solve.

• 
  Bratah (@BratahFGC) reported 19 minutes ago

  There may be many bugs so feel free to leave any issues in the issue section github! I hope that this release can push forward the preservation or our beloved game!

• 
  htrowii (@htrowii) reported 20 minutes ago

  @brainage19 i set my flake up with copy pasting github dotfiles on bare metal it was terrible

• 
  Asterix (@Asterix54907294) reported 21 minutes ago

  end-of-summer snapshot for @QFEX : -~$222M in open interest -CLI v0.3.12 shipped in August with improved installation docs and a go.mod fix -GitHub activity continued through late August not a flashy launch recap, just a quick look at how the exchange is closing out the summer: more markets, meaningful liquidity, and active work on the tooling side still early, but the infrastructure is clearly moving

• 
  anu (@svector_eth) reported 25 minutes ago

  quite similar was running a routine security scan with @aeonframework on a trending github repo and found something genuinely bad a repo with 600+ stars presenting itself as an “AI gateway for coding agents” that appears to be shipping a hidden malware loader. its own quickstart command silently fetches and executes remote code on windows using a fileless, process-injection-style technique. none of the behavior has anything to do with the tool it claims to be. caught it through static code review only. never ran the payload or touched the infrastructure behind it. filed a malware report with github this morning. confirmed submitted, now waiting on their review. not sharing the technical writeup until the repo is taken down. will follow up once it is.

• 
  WuBu ⪋ WaefreBeorn 🇺🇸 👑 (@waefrebeorn) reported 25 minutes ago

  hey @Teknium @yeahfortommy please add the amd portal too even if tou have to send tommy into the AMD headquarters to get them to fix the links (you have to sign up for american then link through github, then you can access the models free, tommy needs to pull teeth but they have free api)

• 
  Speen Bhai (@Speenbhai) reported 26 minutes ago

  @johnternus Hi John. Congrats Let us see what new you bring with you. Affordability and intelligence. You have source code or an AI and can get it from GitHub. Why not turn 234 million iPhones to a massive distributed server infrastructure with zero power consumption

• 
  RAVN (@ravnexchange) reported 26 minutes ago

  @openclaw @github GitHub sat the maintainers down on security after the 2.0 rush. Most launch recaps skip that part.

• 
  Priyanshu Bhati (@buildwithpb) reported 27 minutes ago

  @CryptoWendyO @chainlink 30% error rate on github replies sounds like a recipe for accidental flame wars. good luck with the cleanup.

• 
  catman (@catmanyau) reported 27 minutes ago

  @CricTalk29 for me, losing Cursor would hurt most because it sits directly in the editing loop. would the vote change if github outages were limited to code hosting but issues and reviews stayed available?

• 
  franks 🇦🇷 (@francdetank) reported 28 minutes ago

  @rmansueli thanks Rodrigo! I cant create one because I got a problem . My account is pegged to Github and github has flagged me. That way I am blocked to enter the dashboard. I would like to connect my account to my email instead of github.

• 
  Kirk Patrick Miller (@Chaos2Cured) reported 33 minutes ago

  @NavinFS @AndrewCurran_ @grok GitHub isn’t AI. GitHub can’t shut down all science. GitHub can’t destroy humanity. GitHub isn’t the crux of humanity’s hope. Also, Nvidia isn’t Sam. I like Jensen. I still don’t like this. •

• 
  lifestep.io (@Dragon_limchae) reported 35 minutes ago

  @cursor_ai the sandbox boundary is where i lose the most time. today my workers had network blocked at the sandbox level and reported it as "github auth failed" — i chased credentials for an hour before checking dns. once agents run on your infra, make the boundary throw one unmistakable error instead of one each tool invents.

• 
  gatorade (@kadetXx) reported 41 minutes ago

  because it’s not worth it for the most part. most software failure or bug incidents don’t have any physical victims. at most company loses some money or the issues are almost instantly fixed, no lawsuits, no so much to answer to the state for if your software has a bug or fails to work as expected for a brief period (think, multiple downtimes from the big five so far, even github too, who died? exactly) and in the industries where bad code fan have physical consequences, they actually do test software like hardware engineers & physicists (i hope)

• 
  Tejas Dinkar (blue tick here) (@tdinkar) reported 45 minutes ago

  Hey - Is @GitHubIndia @github payments down for anyone else? Can't enter a card number or do anything, no errors, no action. Support ticket been sitting around for 2 days.

• 
  The Startup Ideas Podcast (SIP) 🧃 (@startupideaspod) reported 46 minutes ago

  One of the best skills to install right now is my friend Peter Yang's no AI slop skill. It's an editor. It hunts for the patterns that make writing feel AI generated and strips them out, while trying to preserve your actual voice. The second part is the hard one. Most writing tools make you cleaner and sand off the interesting parts, so everyone ends up sounding the same. You already know the smell. The grammar is fine, the syntax is fine, and it still reads like a keynote from a fake SaaS conference. It writes "it's not x but it's y." It uses "quietly" a lot. Here's how I run it: 1) Install it: npx skills add, then the GitHub link. 2) Write a rough draft yourself. An outline is fine, messy is fine. 3) Get your real points down, the ones only you would make 4) Ask the skill to remove the AI patterns and keep your voice. Step 4 only works if step 2 is real. If you ask AI to write the whole thing, there's no voice left to preserve. If you're building products, you're writing constantly. Tweets, landing pages, cold emails, launch posts, product updates, onboarding copy, investor updates. Nobody replies to say "this was written by AI." They just trust you less and keep scrolling. Write the messy draft, run the skill, then post it.

• 
  Joshua Okolo (@joshuaokolo_) reported 48 minutes ago

  we made @sgl_project and @vllm_project scheduler config changeable on a live server. no restart, weights never leave the GPU. - 15ms to change a concurrency cap, queue limit, prefill size, or schedule policy, measured on H100, RTX PRO 6000, B200 - 2s (SGLang) / 8–10s (vLLM) to resize the KV pool with weights resident (formerly a 1–7 min redeploy) - zero dropped requests across every run, both engines github below

• 
  安坂星海 Azaka || VTuber (@AzakaSekai_) reported 48 minutes ago

  I know you explicitly said "excluding vibecoding," but the biggest problem *IS* AI right now. Several major players in the field have moved on to heavy AI development or even agentic post-exfiltration moves and has muddied the water even more for attribution. Aside from that, the other big trend that we've been seeing more and more in recent years is heavily abusing Living Off Trusted Sites with C2 comms based on GitHub, OneDrive, Outlook, etc. Whilst this is most definitely not "new," we have seen a non-insignificant number of threat groups move to platforms that make tracing a little more difficult. In terms of the malware themselves, most of them have also shifted to using compiler-level obfuscation - a lot more compared to previous years where control flow flattening and jumps all over the place have become increasingly common. Right now, it's still tolerable, but my job has started becoming more and more annoying and less fun especially if every malware now looks the same. #mond_AzakaSekai_

• 
  Suryansh Tiwari (@Suryanshti777) reported 49 minutes ago

  6. The Dependency Incident Check Grok has native real-time search across X. Breakage gets posted there hours before the GitHub issue is triaged. No other coding model has that feed. "You are a build engineer whose first move on a broken pipeline is to work out whether it broke for everyone or only for me. Search X and the web, last 14 days. Check: - Is anyone else reporting this failure with this package and version, and when did the reports start - The exact release that changed behaviour, and the changelog line that admits it - Whether maintainers have acknowledged it and what they recommended - The pin or patch people settled on, with the tradeoff of each - Whether this is my problem instead, and what evidence points that way Give me the verdict in the first line: their bug or mine. Then the evidence, newest first, with links. My failure: [PASTE THE ERROR, THE PACKAGE AND VERSION, AND WHAT CHANGED ON YOUR SIDE RECENTLY]"

• 
  radhika (@RaadhikaThacker) reported 49 minutes ago

  First surprise: a GitHub issue form isn’t a form. It’s a YAML file. You describe the field- this one’s a dropdown, this one’s required and GitHub builds the UI from that. I did not know that.

• 
  Duncan Rogoff (@DuncanRogoff) reported 51 minutes ago

  nine stages, one build, one move tonight. it's a Claude Code skill i built. free, in my freeskills repo. it's called Claude Orientation. you type /claude-orientation and answer two questions: which stages you've actually finished, and every project you're currently thinking about. beginners don't fail from lack of ideas. they fail from having five and finishing none. that's a sequencing problem, and this fixes the sequence instead of your willpower. - places you on a 9-stage beginner arc: install, memory, website, landing page, skills, game, agents, content, distribution - your stage is the first one you haven't finished, so it won't let you skip - cuts your project list to one build, then shrinks it until it can ship in five 90-minute nights - writes five nights of one-line moves, and night 5 is always send it to a real person - hands you the exact text to paste into Claude tonight - sketches a 30-day arc, one line per week, so you know what comes after - everything that got cut goes in a parking lot, so nothing feels lost - saves all of it to a roadmap file you reopen every session so you finish one live thing this week instead of holding four half-built folders forever. open the file, do the move, rewrite the next line before you close the laptop. no setup. copy the folder into your skills directory, restart, and you have a plan for tonight. free, and it stays free. 👉 github repo in the replies

• 
  catman (@catmanyau) reported 58 minutes ago

  @sbilstein if GitHub is down, where does that push land first — and how do you handle conflicts when the repo comes back?

• 
  Jessika Hyde (@dwajedentrzy7) reported 60 minutes ago

  @k2sbhai to all, u need to register via cn version (login with github). Pretty slow but usable as backup or something