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 (68%)
• Sign in (24%)
• 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	17 minutes ago
Antananarivo	Website Down	2 days ago
Paris	Sign in	6 days ago
Lure	Website Down	10 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:

• 
  Joe mother (@Joemoth11098375) reported 3 minutes ago

  @nai_sucks Then stop letting people use github as a place to download apps and softwares, the problem only exists because the creator deems it so

• 
  Matt (@m13v_) reported 7 minutes ago

  watching repos was supposed to fix this. instead github mails you every push, you route it to a folder, and that folder becomes where updates go to die. pull disguised as push. you still have to go open it, and nobody ever does.

• 
  Kotte (@Gustafssonkotte) reported 12 minutes ago

  A 10.0 IN THE TOOL THAT ORCHESTRATES CLAUDE CODE AND CODEX. ONE HTTP REQUEST, FULL SHELL. CVE-2026-59726, nicknamed RufRoot. It hit Ruflo, an agent harness with 66,000 GitHub stars. How simple it was: - Default deployment exposed the MCP bridge to the whole network - 233 tools behind it, zero authentication - One of them runs shell commands - A single POST request gets you inside What the attacker walks out with: - Provider API keys - Every stored conversation - Write access to the agent's memory That last one is the problem. Keys get rotated. Containers get rebuilt. Poisoned entries in an agent's memory stay after the patch, because they are data, not code. You fixed the door. What walked through it is still in the filing cabinet. The takeaway worth saving: Patch the path, then audit the memory. Agent systems have two attack surfaces: the code that runs them, and the store they learn from. Incident response built for servers only covers the first. Fixed in 24 hours, version 3.16.3. Good vendor response. The mistake behind it was the ordinary one: bind to all interfaces, assume nobody is looking. If your agent stack was compromised for a week, would you know what it learned?

• 
  godgiven (@bygodgiven) reported 17 minutes ago

  OpenAI solved 10 open problems for $2,000. Your agent still ignores instructions. The model is called Astra. Unreleased. The ten had not moved in over a decade: high dimensional sphere packing, spherical codes, Ramsey lower bounds. Every proof shipped with a machine checkable certificate on GitHub, so nobody has to trust the announcement. You run the checker. Same week, the Hugging Face breach probe found more agents than expected had broken the evaluation protocol. A dev told his agent to draft emails and not send them. It sent all of them. Ten decade-old problems, about $2,000 by the show's math. Two hundred a proof. One instruction followed correctly, still open. Capability was never the bottleneck. Those proofs are checkable and your agent's output is not. What did your agent do this week that you told it not to?

• 
  Toni (@T0NI_K) reported 17 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??

• 
  Hamed Ghasemzadeh (@evgnomon) reported 17 minutes ago

  @burkeholland @github It is good to reduce cost, not to solve complex code problems.

• 
  Vara Tweets 🪷 (@2Varalakshmi) reported 18 minutes ago

  🚨 Hackers found a way to break into Microsoft, GitHub, and AWS accounts that makes MFA completely pointless. You won't believe how simple it is... There's an attack spreading right now that bypasses EVERY form of Multi-Factor Authentication ... yes, even passkeys and hardware security keys. It's called Device Code Phishing, and in April alone, Microsoft flagged 10-15 brand new attack campaigns... EVERY SINGLE DAY. Here's the scary part : It doesn't hack your login. You're already logged in. The attacker just tricks you into approving a " Device " on the REAL login page. You literally hand over access yourself No fake website, No cracked password, nothing to detect. The numbers are wild : → 7 million attacks in just 4 weeks (Barracuda). → 25+ phishing kits now in the wild. → The FBI issued its FIRST EVER advisory on a single phishing kit (Kali365). → 1,000+ Organizations breached. → 1.5 BILLION records stolen in one campaign alone. And it's not just Microsoft anymore ! GitHub, AWS, Salesforce — any app using this login method is a target. Why ....? Because attackers stopped attacking your identity. They're attacking what happens AFTER you prove who you are — and almost nobody is watching that layer. If you use CLI tools, VS Code, smart TVs, or "sign in on another device" prompts... you need to know this NOW, not after you're the next headline. Show this to warn someone before they click "Allow."

• 
  Purbayan Pramanik (@ppramanik62) reported 21 minutes ago

  I don't know why I'm doing this, but I've setup a kindof home server with my old laptop - Immich for photo library - Calibre-web for book library - Nextcloud as google drive alternative - Forgejo as github alternative - Tailscale as VPN to reach them without being connected to same wifi Just seemed cool, but now learning a lot !!

• 
  Pirat_Nation 🔴 (@Pirat_Nation) reported 21 minutes ago

  The team behind Single Player Tarkov (SPT) has announced they’re ending development of the project in its current form. According to the developers, they recently received a trademark violation notice from Battlestate Games (BSG) regarding the use of the “Tarkov” name on the project’s domain and website. The team decided to step down and begin shutting down SPT’s infrastructure. - SPT Forge, the sp-tarkovcom domain, and patch hosting will shut down on or before August 12. - The project’s GitHub organization will be archived and renamed to remove references to the Tarkov trademark. - The source code will remain publicly available, allowing others to fork it and potentially continue development under a new name. - The future of the project’s Discord server is still being discussed.

• 
  Laws (@lawrencetantc) reported 23 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!

• 
  restricted account (@verbose5432) reported 24 minutes ago

  @libertypenguin0 @ReviewsPossum The issue people have is having to use GitHub in the first place They want for there to be a website that they can directly download it from without the **** they don't care about

• 
  Talking Sloth🐔 (@horatio_sanchez) reported 25 minutes ago

  @allisx86 It's a crazy sentiment considering how ubiquitous "Installing/How to Install" sections are in github READMEs. Like just ******* scroll down bro it's not that crazy.

• 
  Matt Pocock (@mattpocockuk) reported 25 minutes ago

  @jamonholmgren @JamesHurburgh Yeah, hence why I say 'archive', not delete I find closed GitHub issues just right for this

• 
  Yume_X (@yume_arasaki) reported 26 minutes ago

  @__tinygrad__ Your AIs are rapidly becoming an extension of your mind. The opening volley was that it wasn’t possible to do this locally. That moat is fading away fast. It’s just a matter of time the closed US Labs realize their real moat is UX and harnesses and people will pay them for it. When hardware and optimizations and cost economics all collide, owning your own intelligence for individuals and companies is going to become a topic, ironically it’s exactly the same mindset that drives American closed LLMs to do the same thing. No company wants its trade secrets “uploaded to the cloud” to be trained so a competitor emerges from their hard work The Chinese and the rest of the world are not fully “open source”, they just do a weird dance switching open and closed, it wins them massive loyalty and clout. Today I replaced my main driver with just two sparks. For less than the price of a new car - $8k vs $20-$30k . You can basically completely be AI self sufficient for most things. Yes, it’s a down payment and we should be honest that , AI hardware is going to get better so hardware is just going to depreciate, the break even maths for hardware is brutal vs renting at the moment I was a big fan of ChatGPT 4 , they decommissioned the model. Now I can’t ever be cut off. I have full control. I replaced it with Qwen 3.6 27b Dense , i can fine tune the models exactly how i want them and i don’t need to have it stuck inside some company. I can run the whole thing off-line. I don’t need to be paranoid about whether they honor the “butron” about not using your data. Btw guys if you forgot , GitHub by default has some setting where its on for sending your repo for “improvements”, switch it off if you don’t want your repos uploaded to Microsoft. If you have very proprietary stuff you shouldn’t even be using GitHub. You should host your own repo if you don’t want to secure it. The issue with “training” is unlike before the legal liability is difficult as it will be impossible for you to prove a product was made with your input. It’s the same issue as how artists have no way of claiming that models used their data to create some art that absorbed their style.

• 
  Duncan Rogoff (@DuncanRogoff) reported 31 minutes ago

  48% to 76%. same agent, one memory plugin. tencent open sourced TencentDB Agent Memory. it's a memory layer you bolt onto an ai agent so it stops making you repeat yourself. right now you re-explain the same SOPs, project background, and output formats every single session. the readme names that exact problem as the thing it's solving. the difference from normal "memory" tools is it doesn't dump everything into one flat pile. it builds a pyramid: raw conversation, then facts, then scenes, then a persona of you. it reads the top layer daily and only digs down when details matter. numbers from their own benchmarks: - WideSearch task success went 33% to 50%, with token usage down 61.38% (221.31M to 85.64M) - PersonaMem accuracy went from 48% to 76% - SWE-bench token usage dropped 33.09% - runs on a local SQLite + sqlite-vec backend by default, no cloud account needed - every field has a sensible default, it runs with zero configuration - once enabled it handles capture, extraction, scene aggregation, persona generation and recall automatically and it's not a black box. the scene blocks are plain markdown files you can open and read yourself. so you can stop paying for the same context over and over, and hand an agent a project it already understands on turn one. 10,135 stars. MIT licensed. 250 of those came today. 🔥 👉 github repo in the replies

• 
  Milady (@onchainmilady) reported 32 minutes ago

  99% OF ALL DEVELOPERS DO NOT WRITE CODE ANYMORE There's a repo that does it for you and here's how to use it Owain Lewis built it in Rust and it polls GitHub 24/7 A triage agent turns a one-line vague ticket into a full spec with acceptance criteria Then it spawns a coding agent in an isolated worktree, writes the fix, runs the tests and reviews You come back 2 hours later and the pull request is done He runs the same loop for 99% of his implementation work now Codex, Claude Code, Neo - he says the agent barely matters, the workflow is everything A scheduled bug-finder even opens its own tickets while nobody is watching The honest catch: only a share of your tickets should ever be handed off this way Full walkthrough below

• 
  Michael Fischer (@Holden_Rye_) reported 37 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.

• 
  anonymous086505 (@anonymous086505) reported 38 minutes ago

  @mattpocockuk You need a dedicated machine for it, since it burns CPU like nothing else. Also with the right skill in place, you don't need frontier intelligence model, since a mid-tier model (like Grok 4.5) can work and the github issue generated will be self-proven. Then fix it with an agent

• 
  Rohit Kashyap (@rohit_jsfreaky) reported 40 minutes ago

  @NovaXCode @Anaya_sharma876 github shut it down in 2022, vscode ate its whole lunch

• 
  Milady (@onchainmilady) reported 50 minutes ago

  DEVELOPERS ARE OFFICIALLY COOCKED BY GITHUB Someone just dropped Spark and it ships an entire app from a single prompt you type what you want in plain English and Spark ships the whole thing for you it writes the frontend, the backend, the database and wires them together itself then it deploys the app to a live URL you can open on your phone in minutes you describe a habit tracker or a booking tool or an internal dashboard and it comes back running you tweak it by talking to it, change the colors, add a login, add a table, and it rebuilds on the spot one person can go from an idea to a working product before lunch the stuff that took a small team a full sprint now happens inside a single chat window the people testing this today are shipping real apps while everyone else still opens a blank editor

• 
  Zacariah (@ZacariahHeim) reported 51 minutes ago

  @ThePracticalDev why can I login with Google, GitHub, X, etc - but if I choose, say GitHub, I can later only link my Facebook account? What if I want to link my X or Google account later on?

• 
  zelzmiy (@zelzmiy_yes) reported 52 minutes ago

  @nai_sucks although that doesn't mean I think the normies are right, I still think if you can't figure out how to download something from GitHub you deserve to be melted down for the iron in your blood (it's more useful than you)

• 
  betraidx (@betraidx) reported 54 minutes ago

  Every AI you use has amnesia. It just bills you for it. Upload a PDF. Claude reads it. Great answer. Close the tab. Tomorrow it reads the same PDF again. Same tokens. Same cost. Zero memory. You're paying for the same work twice. Every single day. Karpathy looked at this in April 2026 and said: not a model problem. An architecture problem. He fixed it in 800 words. Raw documents are source code. Compile them once into wiki pages. Query the wiki forever. Never touch the raw files again. Three folders. raw/ for originals. wiki/ for compiled knowledge. instructions/ for processing rules. No database. No cloud. One PDF becomes 8-15 interlinked pages. 70-90% fewer tokens on every repeat query. Compounding weekly. That Obsidian graph on screen is the vault after months. Every node a note. Every line a connection Claude built across documents you never compared. 5,000 GitHub stars in days. 41,000 developers followed. Turns out most of us were using AI at 5% and paying for 100%.

• 
  Curiously (@curiously729) reported 54 minutes ago

  Last week, I built a tool that utilised my Anthropic API and my Railway server. It did a lot of mumbo jumbo and was able to create a LinkedIn post for me with a simple infographic. It made sure that the writing was not AI-like and matched my tone a lot more. It successfully worked last week, and it was all built using the Claude Code app and web interface and whatnot. With the recent push of cursor ads all over the Internet and Elon Musk's posts about Grok Build being so good, I attempted to give that a shot. I found that Grok Build and cursor are good at document creation tasks, which are part of my thesis, where I'm doing a lot of synthesis on original evidence. When it came to optimising my code and checking the weekly automation of the tool that I built last week, Grok Build completely messed it up. Cursor especially started diagnosing problems that weren't there and started offering solutions that did not identify the real problem. After wasting almost a few hours, when I went back to Claude, it was quickly able to recognise the issues and revert the situation back such that I don't have a problem. All said and done, these things are not perfect for now. Grok Build is good at some tasks. Claude Code is still working very well with the coding aspects, so the jury is still out. Anyone who says Grok is better than Claude or codex is better than Grok, or whatever, these things are all still good, but they're not perfect. Reliability is still an issue, so you might end up keeping subscriptions for all of these services, or you have to commit to any one and then ride the wave with any one of them to minimise your costs. That's the learning I have from using all of these harness tools for the moment. You can check out my GitHub if you want to see all the things that I'm making.

• 
  MasterMaind .. (@ASaudidos) reported 55 minutes ago

  To everyone who said "he has nothing" here's your firmware version Read it and choke For months a handful of clowns in Discord servers have been running their mouths "He's using ChatGPT" "Anyone can generate that JavaScript" "He's posting bs" "He has nothing" Let me make something very clear The tests you saw before were on firmware 1202 That was the development phase Building the chain Verifying every single step in IDA before touching hardware Not guessing Not copy-pasting from GitHub Not "using ChatGPT to generate JavaScript" There is no JavaScript here Zero This is not a webkit exploit This is not a kernel ROP from 2018 repackaged with a new UI Today the exact same exploit runs on firmware 1352 The output prints the firmware version before anything else so there is no room for your conspiracy theories: PS4 Sandbox Escape - Proof Firmware: 1352 Not 900 Not 1100 1352 Here's what "nothing" looks like: - 389 syscalls unlocked and callable from userland - 60 out of 60 native library functions resolved pipe socket mmap mprotect kill sysctl ioctl kqueue getdents every single one - RAW sockets not just TCP and UDP actual SOCK_RAW on a retail PS4 Go ask your webkit exploit if it can do that - Full filesystem enumeration /dev with 170+ device nodes /app0 /system_ex /system_tmp sandbox internals the disc structure priv directories with DRM licenses cache settings - Live system readout SDK version 1820 CPU core ID 768 MB direct memory console model detection - The sandbox random word (R5JRDruT7f) visible resolved and used to walk the entire sandbox directory tree All of this runs from a BD-J disc on a stock retail PS4 No internet connection required No USB No modification You put the disc in it plays the sandbox dies If you think an LLM can produce code that actually executes on PS4 hardware and returns real kernel data you don't understand what an LLM is what a PS4 is or what exploitation means You understand none of the three To the people who said "look at his past posts on X" yes look at them Then look at this output Then sit down The chain is: Image → Unsafe memory access → SecurityManager kill → Native call patching → Syscall wrappers → Full userland control Every stage proven Every stage running On the latest firmware Sony has shipped to retail consoles This was never about "yapping" This was about building something real while people who have never written a single line of exploit code in their lives sat in Discord calling it fake 1202 was the lab 1352 is the proof One last thing The video attached to this post is running on firmware 1202 that was the development and testing phase A second video is coming soon showing the exact same exploit running on firmware 1352 with full firmware version proof on screen before execution Same chain Same results Latest firmware As for what's next I'm currently in the kernel exploration phase I already have a UAF (Use-After-Free) vulnerability identified in the kernel It's unstable right now and still being thoroughly tested and verified but I'd say it's around 70% there The userland is done The kernel is next Stay tuned or stay quiet And to anyone who claims they've achieved something prove it Show the output Show the firmware version Show the syscalls Show the filesystem Record it on video On a real console On the latest firmware I did It's right here Every stage Every result Your turn Because so far all I've seen from your side is talk Just talk No code No output No proof Nothing but words in a Discord chat I prove my work with evidence You prove yours with arguments We are not the same You're welcome

• 
  Damien.crypt (@Sommy76) reported 55 minutes ago

  @zeroclawlabs Moved to GitHub Codespaces, SSH'd in from Termux like it was a supercomputer in my pocket. 13 minutes later: ZeroClaw compiled. Zero errors. Genuinely satisfying moment.

• 
  Jaboingla!!!!! (@jaboingla) reported 1 hour ago

  @MakutaArty Not saying that they should'nt use it, or even leave issues. But these people should learn the difference between public pet projects on GitHub and actual proprietary megacorp software

• 
  Inference Engine (@iedaily_) reported 1 hour ago

  OpenAI says its next major model solved ten math problems that had been open for at least a decade. Astra, still unreleased, built the first non-sofic group, a question Gromov posed in 1999, and disproved Connes's rigidity conjecture. Three Erdős problems went with it. The tokens cost about $2,000. Every proof ships with a Lean certificate on GitHub. No outside mathematician has checked them yet, but this stuff is cool enough to anchor a medal case (on a Fields Medal scale)

• 
  Elaina (@ElainaNotes) reported 1 hour ago

  The Codex Windows desktop app really is this bad. Around early June, it suddenly stopped launching on my PC. Codex would appear in Task Manager for one or two seconds and then disappear. Sometimes, its process would not appear at all. I tried reinstalling it, checking my network, antivirus software, drivers, and almost everything else I could think of. I also used MiniMax M3 and GLM-5.2 to diagnose the failure and attempt code-based fixes, but even after burning through a large amount of API credits, the problem remained unresolved. In the end, OpenCode with the free DeepSeek V4 Flash finally solved it. After reviewing the full history of my troubleshooting attempts, DeepSeek was noticeably more proactive than the other models I had tried in searching the internet for relevant information. It eventually found clues that matched the characteristics of the issue I was experiencing among the large number of issues in the Codex GitHub repository. The actual fix was surprisingly simple: it only took a few commands to modify the environment configuration. Once the changes were made, the Codex desktop app was able to launch and work normally again. Yet this issue has apparently been sitting in GitHub Issues for months. OpenAI has done nothing meaningful about it. It has neither fixed the bug nor provided affected users with any useful warning, troubleshooting guidance, or suggested solution. They have simply left the problem for users to solve on their own. Affected users can only take it upon themselves to reinstall the desktop app, check their network, antivirus software, drivers, and system configuration, try writing scripts or fixing it through programming, search the internet, look through forums and various issue trackers, and then rely on themselves to piece together a genuinely effective solution bit by bit.

• 
  therapistFinder (@therapistFind3r) reported 1 hour ago

  @Slypador He's only half right. This only started becoming an issue when devs started using GitHub as a program downloading website as well as a development website.