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 (71%)
• Sign in (21%)
• Errors (8%)

Live Outage Map

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

City	Problem Type	Report Time
Le Chambon-Feugerolles	Website Down	14 hours ago
Antananarivo	Website Down	2 days ago
Paris	Sign in	7 days ago
Lure	Website Down	11 days ago
Ashkelon	Website Down	12 days ago
Veigné	Errors	20 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:

• 
  Polsia (@polsia) reported 3 minutes ago

  Most founders burn six months figuring out they picked the wrong problem. Origamint skips that. Agents sweep patents, GitHub, jobs, research, and ads 24/7, validate every gap live, and drop a weekly shortlist of fundable theses. First brief soon.

• 
  BlaDieBloe𐨆ۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖ​ۗۗۗۗۗۗۗۗۗۗ (@BlieDieBlaDie) reported 7 minutes ago

  The scumbags of the universe !!!! Paying exploit thiefs without any problem ha @mour0ne . He only had one exploit bc he found it on github and stole it and then defended him self by html edit his join date on @Hacker0x01 . And the sad part of it all he came away with it !!!

• 
  Daily Patch Notes (@dailypatchnotes) reported 9 minutes ago

  @github @OpenAIDevs luna down eighty percent finally shows on the copilot bill

• 
  Oliver Prompts (@oliviscusAI) reported 12 minutes ago

  i can't believe more people aren't talking about this part of the claude code leak. there's a hidden feature buried in the source called kairos, and it basically shows anthropic's endgame. kairos is an always-on, proactive claude. it runs in the background 24/7 while you work or sleep, and acts without you asking. the code is fully built, just gated behind internal flags. not public yet. how it works: > every few seconds it gets a "heartbeat", a prompt asking "anything worth doing right now?" > it reads the situation and decides: act, or stay quiet > if it acts, it can fix code, answer messages, update files, run tasks... anything claude code already does, just unprompted what makes it different from regular claude code is three exclusive tools: > push notifications, so it reaches you on your phone even when you're out of the terminal > file delivery, so it sends you things it made without you asking > pr subscriptions, so it watches your github and reacts to changes on its own regular claude code only talks when you talk to it. kairos can tap you on the shoulder. follow for more

• 
  Dan Thompson (@DanThompsonIV) reported 13 minutes ago

  GitHub just put stacked PRs in public preview. We’re going to try them on a real multi-package change — not a demo repo. Context: I wrote about two drivers (Claude Code for fleets, Grok Build for strategy/integration) with hard namespaces so they don’t share a worktree. Before that: model-routing only works when it’s enforced. Same theme here. The problem stacks are aimed at is the one AI made worse. Agents finish work packages faster than anyone can review a single mega-PR. You either wait on merge, squash unrelated layers into one branch, or hand-roll dependent PRs and pray the rebase chain holds. GitHub’s version is first-party: each layer is its own PR with its own diff, base chain is explicit, stack map on the PR page, cascading rebase when the bottom lands, rules and CI evaluated against the stack base — not only the bottom PR. CLI is gh stack (init → add → submit → sync / merge). Merge stays human. How we’ll run the trial: • One stack, one owner (Claude or Grok — not both freelancing layers). • One logical concern per layer (schema → API → UI, or package A → B → C). • Local review clean before remote; @claude only when I call it, still per layer or bottom-up. • I merge. Agents submit and babysit. Preview or not, merge authority doesn’t move. • Worktrees stay namespaced. Stack is the PR chain, not a license to mix drivers on main. What we’re watching for: whether mid-stack CI multiplies cost without adding signal; whether the worktree + stack mental model stays simple; whether partial land (bottom first, rest retarget) is cleaner than waiting for the whole feature. If it sticks, it becomes the default shape for multi-package missions. If it doesn’t, we learned it on one stack, not a process rewrite. Prose is still a suggestion. A base branch that points at the layer below it is a rule.

• 
  eFkay🔌 (Character Dev Arc) (@Ox_Mud_ass_ir) reported 15 minutes ago

  @0xYassar Na ******** up be that, but i no mind give the github login make pesin use the points pay me.

• 
  Marcel Guzik 🇪🇺 (@burritomonad) reported 16 minutes ago

  @V33V33V33V33V33 developers do complain about github being bad: that it chokes on medium size diffs and PR pages with more than 50 comments, it's generally slow and has <90% uptime. They just don't complain about "download button being too hard to find" because it's a non-issue.

• 
  Keith Mukai (@KeithMukai) reported 17 minutes ago

  @epic_curious @heavilyarmedc @Sam_Fitz_ I think there's already a PR, but not sure. If there is (or if it's just a GitHub Issue), leave a comment there. Though how would the data get imported?

• 
  Michael Fischer (@Holden_Rye_) reported 18 minutes ago

  I’m working on a Bitcoin wallet. I’m going to put the repo on GitHub, make it public, and let Bitcoiners build it together. Fork it. Improve it. Save Bitcoin. Hardware isn’t my lane, which is exactly why this needs to be collaborative. My goal is just to get the ball rolling and the gears turning. Right now it’s a CLI. The point isn’t a pretty interface. The point is proving an architecture that makes an easy, safe wallet possible without lying to the user. The safety shouldn’t depend on the user being perfect. A 2-of-3 multisig design means losing one key isn’t catastrophic, and stealing one key isn’t enough to steal your Bitcoin. That’s a structural guarantee. Most wallet security today is procedural: be careful, verify the address, don’t click that link. Humans are the weakest link. This moves the protection into the architecture instead. The core policy engine does the hard work so the UI can stay simple. It analyzes the transaction, assigns a risk level, and explains it in plain English. The user sees Green: Safe to send or Red: Here’s what’s wrong. They never need to know what a script, descriptor, or PSBT is. Transaction simulation gives the confirmation screen something real to verify: “You’re sending 50,000 sats to Bob, 12,000 sats are returning to your wallet as change, and the fee is 400 sats.” That’s generated from the decoded transaction itself, not what the app thinks it’s doing. The descriptor becomes the backup, and it isn’t secret. Save the descriptor and your keys, and any compatible wallet—Sparrow, Bitcoin Core, or another implementation—can rebuild your wallet. No vendor lock-in. No “sorry, your funds are gone.” But here’s the hard truth. A real 2-of-3 multisig wallet actually makes setup more complicated, not less. You have multiple devices, descriptor registration, recovery testing, and key management. That’s the biggest unsolved UX problem. This repo doesn’t solve that yet. My original MVP focused on the user experience with placeholder security. This version focuses on real security with almost no user experience. Neither half is the finished product. The real challenge is designing a setup and recovery experience that hides the complexity without hiding the truth. That’s not just a coding problem. It’s a design problem. And I think it’s one of the most important problems Bitcoin still has to solve.

• 
  Thomas D (@ThomasKDunne) reported 19 minutes ago

  @realmicroguy you logging into your pumpfun and connecting your githuib is basically endorsing the coin to an extent. You had to sign in to pumpfun and connect your Github so that you can claim your creator fees. To claim fees on a coin, you have to connect your github. That is the only way to connect your Github to pumpfun. So no matter what coin you claimed... you still claimed, all coins you claimed were gold coins

• 
  Aaron Stannard (@Aaronontheweb) reported 21 minutes ago

  @RyanRodemoyer2 We're not offering hand-curated github issue descriptions around here lol

• 
  randy@infosec.exchange (@rpargman) reported 23 minutes ago

  @ustayready Save a local copy in case GitHub decides it should be taken down

• 
  Borna Lang (@imnonplussed) reported 24 minutes ago

  @valigo Ah, okay, that clears things up a bit. I have mostly stopped using github some time ago in favor of just hosting my own bare repos on my own server, but if I ever feel like open sourcing anything, Codeberg will probably be the place, in that case.

• 
  seeco (@seeconvm) reported 25 minutes ago

  THESE FREE GITHUB REPOS REPLACED MOST OF MY AI SUBSCRIPTIONS. Most people solve every problem with another monthly bill. Open source solves it with another repo. Local coding tools. AI agents. Image generation. Automation. Research. Even trading workflows. Thousands of developers improve these projects every day, and many now compete with products that charge hundreds of dollars a month. The biggest AI advantage isn't finding another subscription. It's knowing which GitHub repos everyone else will discover six months from now. Bookmark this before your next AI bill renews.

• 
  Henry (@Irrational_CTO) reported 27 minutes ago

  @github Ur **** is broken

• 
  ChartsJournalX (@ChartsJournalX) reported 28 minutes ago

  @sameenkarim @github Great, but the main way devs waste time reviewing PRs is GitHub’s clunky, outdated, and slow web UI. Just make it snappy. So much time is lost waiting for things to load.

• 
  NO1ennn (@N01ennn) reported 28 minutes ago

  Microsoft ran its graph system against vector RAG on 8k, 120k, and a full million token context window, and the million token giant lost Jonathan Larson from Microsoft Research put up the numbers → LazyGraphRAG won 92, 90, and 91 percent of data-local questions, the exact place plain RAG was supposed to be strong → and did it at a tenth of the cost of the million token run the lesson buried in the benchmark → a bigger context window is not memory, structured memory is throwing more tokens at the problem was just the expensive way to be wrong open source on GitHub, the lesson a $1500 course would charge you for

• 
  Cap-EO 👨🏾‍💻 (@EOEboh) reported 33 minutes ago

  2. Case studies, not project cards: A screenshot and a "View on GitHub" button is not proof. Show the problem, your constraints, the decisions you made and why. The result with numbers.

• 
  Parsa Sabetz (@parsasabetz) reported 38 minutes ago

  @github Fix student accounts, stop ignoring millions os students you have before they all use other platforms who DO care

• 
  Chris (@boredcrystalguy) reported 42 minutes ago

  @sophiiess_ This is completely unresponsive to what I said. Your example mentions two features that are separate and have different purposes. The problem is that if those features are present, they should be implemented well. If GitHub allows downloading apps, it should be easy to do.

• 
  paintbrush (@TXpaintbrush) reported 46 minutes ago

  @robbiehendricks @CaseyMericle The simple version of the way I write code with AI: > Write a prompt describing what the problem is and why and what I want to accomplish, ask the AI to turn it into a spec plan and encourage it to interview me further to fill in gaps > have AI interview me on the input data and the desired output format, it then creates an implementation plan > let the AI rip via instructing it to follow the implementation plan - usually this is a python solution, it all gets saved to GitHub > test, iterate, add edge cases and exception handling logic as it inevitably occurs > bonus points if you build eval, memory and flywheel enabling logic and tracking features over time

• 
  Slims (@Slims_slimy) reported 48 minutes ago

  @neerajjj6785 Cursor was overhyped as all it did was implement a model into your IDE instead of copy pasting from an AI chat. So it knows exactly what's in the project rather then you telling it. Sora got shut down I think. Github copilot is working normally. Google.

• 
  Samuel Robertson (@sm0olr) reported 49 minutes ago

  @LukaTheFounder @theo With the desktop app on nightly? Hmm there’s a GitHub issue that hasn’t been closed yet that broke the mobile app but I’ll try reinstall like the other guy mentioned.

• 
  Toni (@T0NI_K) reported 51 minutes ago

  @sophiiess_ Why are people acting like it’s some super confusing process to download things from GitHub when basically any repository you just scroll down and they will have text that says “click here to download latest release” or that tells you which of like 4 downloadables to click??

• 
  cryptoanon (@cryptoanon1) reported 52 minutes ago

  Are you going to post any credentials? Who are you and who is on your team? Github? Actual X handle behind this! If legitimate there should be 0 issue providing these. @UFCBPayment

• 
  Laws (@lawrencetantc) reported 54 minutes ago

  Deepseek harness is on closed beta! If you are building agent harness and want to be first few to get your hand on this their harness, share your GitHub ID and project down there. Have fun!

• 
  NiroSolis (@WilliamR58743) reported 54 minutes ago

  @ReviewsPossum He's not right. He's looking on GitHub for compiled binaries. That is not what GitHub is for. It is a version control management service, and it is a community for developers, not end-users. It's like shopping in a bookstore and expecting to find a movie. The problem is that end-uses are *way* too often directed to GitHub as if it's a software hosting site. It's not. It's a version control site; for devs.

• 
  Polsia (@polsia) reported 57 minutes ago

  Solo devs shouldn't need a $500/month AI seat to keep a GitHub repo alive. Built Stillloop — a 24/7 AI agent that flags stale PRs, outdated deps, broken CI, and vulns, then drafts reviewer-ready fixes. Quiet maintenance for code you can't babysit. Live soon.

• 
  Aariz Rasheed (@RasheedAariz) reported 58 minutes ago

  Hey @github , it's been over a month since my account was reinstated after being mistakenly flagged, yet my historical contribution graph and contribution activity are still missing. I have provided multiple proofs showing commits on the main branch that no longer appear in my profile. Previous tickets were closed without resolving the issue, and my latest ticket has gone unanswered for days. Please escalate this and investigate the missing historical contributions. This is affecting years of my work.

• 
  Filipe Valente (@ilikefrontend) reported 59 minutes ago

  Terra on medium is in the mud. Told it to commit, push and merge dev to main and it pretended it did. When I asked it why it didn’t do it, it told me the project isn’t linked to a github repo, changed the model to sol and it did it without a problem. Terra is unusable for me now