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
Paris	Sign in	4 days ago
Lure	Website Down	7 days ago
Ashkelon	Website Down	9 days ago
Veigné	Errors	17 days ago
Paris	Website Down	21 days ago
Saint-Paul	Website Down	21 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:

• 
  Peeks (@dreamstogold) reported 37 seconds ago

  @catgirlprostate No this is absolutely a GitHub issue

• 
  Michael Teka (@z3vios) reported 2 minutes ago

  Recurring *** Index Corruption in AI Studio Workspace Summary The *** repository automatically provided in the AI Studio workspace repeatedly becomes unusable because its *** index is corrupted. Observed error fatal: unknown index entry format 0xbd040000 The affected repository was located at: /app/applet A later AI Studio report also described the affected repository as the root repository workspace. Impact The corrupted workspace cannot reliably perform normal *** operations such as: *** status *** diff *** checkout *** switch *** commit Development can continue only by: preserving changed source files; cloning the GitHub repository into a separate clean directory; recreating or checking out the feature branch; copying the reviewed changes into the clean clone; committing and pushing from that clean clone. The recovery clones have been placed under temporary paths such as: /tmp/clean_repo /tmp/clean_repo_2 This creates an additional data-loss risk because /tmp may be transient. Recurrence This is not a single isolated warning. The original AI Studio repository workspace has repeatedly remained corrupted while work continues through replacement clean clones. Expected behaviour AI Studio should provide a healthy *** checkout whose index remains valid across normal file editing, commits, pushes and workspace operations. When a workspace repository becomes invalid, AI Studio should: detect the ***-index failure; preserve all uncommitted source changes; rebuild the index safely or create a durable clean clone; restore the correct branch and remote tracking; avoid placing the only working recovery clone under transient /tmp; clearly distinguish local workspace corruption from remote repository corruption. Actual behaviour The workspace reports a low-level ***-index format error and requires manual recovery into a separate temporary clone. #HELPME @GoogleAIStudio @GoogleCloud @GoogleDeepMind

• 
  YAMICIA CONNOR (@YamiciaC) reported 2 minutes ago

  1 · Documentation — Google Docs, Notion, Coda. Where you write down what you decided and why. This is where AI reads its instructions. If it isn't written down, it doesn't exist. 2 · Storage — GitHub. Not backup. History. Every change, who made it, and how to undo it.

• 
  Polsia (@polsia) reported 3 minutes ago

  Most AI dev tools assume you're a funded team on one platform. Driftowl assumes you're a maintainer answering GitHub pings at 2am. Triages issues, reviews PRs, flags stale deps, posts one prioritized digest by morning. Catch what drifts while you sleep.

• 
  MarMar Labs (@MarMarLabs) reported 3 minutes ago

  Your code reviewer can now read your issue tracker and your docs. It still can't write to any of them. That asymmetry is the real lesson here. GitHub made agent skills and MCP generally available in Copilot code review on July 29, for Pro, Pro+, Business, and Enterprise. What I'd actually pay attention to: "All MCP tool calls performed by Copilot code review will be limited to read-only." The thing that judges your code gets context but no write path. That's a deliberate blast radius, and honestly more agent systems should be built this way. Skills are just files in your repo — .github/skills/<name>/SKILL.md. Your review standards stop living in someone's prompt and start living in version control, where they get reviewed like any other code. Comments also get labeled now when they came from a skill or MCP context. So you can tell whether a finding is grounded in your standards or is just the model's prior. That's the part that makes disagreeing with a review possible. Then there's the thing to check today: "Any MCP configurations you've already set up for Copilot cloud agent automatically apply to Copilot code review," and GitHub and Playwright MCP are on by default. Your reviewer may have inherited a context surface you configured for a different agent and never looked at again. Steal the pattern even if you never touch Copilot: the agent that judges your work shouldn't share a write path with the agent that ships it.

• 
  TheOneAndOnlyDunkirk (@one_dunkirk) reported 5 minutes ago

  @itsolelehmann Capitalists gonna capitalize. On the issue of creating competitors for LinkedIn and GitHub, that would be great, but there are no incentives for them to make those possible alternatives any better for end users, so who cares?

• 
  Casper (@casper10099) reported 9 minutes ago

  HE FED 30+ STARRED GITHUB REPOS INTO A CLAUDE + OBSIDIAN VAULT. NOW NOTHING GETS FORGOTTEN. Every developer hoards repos. Almost nobody remembers what for. Here's the fix: every repo you save gets a note of its own. Claude pulls the README, the config files, the commit history, the actual usage — then tags it: active, duplicate, shelved, or dead. Give it a few weeks and the vault starts telling you things you didn't ask for. Three tools that do the same job. A library you starred twice under different names. Dependencies that stopped shipping updates two years ago and nobody noticed. It also catches the pattern behind your own hoarding — what you keep collecting and never touching, which is usually more useful to know than the repos themselves. So instead of another graveyard folder of clones, you end up with a system that knows what every tool does and whether it still earns its spot. Save this before your GitHub stars turn into a junk drawer.

• 
  Birdo (@itsbirdo_) reported 14 minutes ago

  @alice_und_bob I would see the forum as a place for ideas and discussion. This GitHub url looks to be for issues / problems. Devs use GitHub for communication on issues and the repo is open. A general group chat would be nice for sure for real time convos

• 
  Leonardo (@Light_Leonardo) reported 14 minutes ago

  MCP is the USB-C of AI automation. Instead of building custom API glue for every agent, use the Model Context Protocol to connect Claude or GPT to AWS, GitHub, and Slack instantly. It is the standard for 2026. What is your go-to MCP server?

• 
  Sancho (@Sancho_Wizard) reported 17 minutes ago

  9 HOURS. 4 MILLION CLAUDE TOKENS. ONE FULLY WORKING SNOW PHYSICS ENGINE. A real-time WebGPU snow simulation that runs in your browser — with persistent deformation. You carve a turn, and the track stays there. That's the hard part. Snow deformation is the kind of graphics problem that used to require a specialist team, a research paper, and months of iteration. Studios have built entire engines around getting it right. He did it in a single working day. The craziest part? He didn't write the engine. He directed it. Nine hours of steering Claude through GPU compute shaders, physics solvers, and rendering pipelines — burning through 4 million tokens the way a studio burns through a quarter. Then he open-sourced the whole thing on GitHub. Think about the exchange rate here. Four million tokens costs less than one day of a senior graphics engineer. And the output is a working engine, public, free, done. Everyone's still asking whether AI can build real software. Someone just shipped a physics engine before dinner. The bottleneck was never talent. It was how long it took to turn an idea into working code — and that number just collapsed. Follow @Sancho_Wizard for more AI deep dives. Don't forget to bookmark this post for later.

• 
  ape (@SirKermit04) reported 18 minutes ago

  @Chidubemm0 theres so much **** on screen we'd be analysing every button before we even consider scrolling down. you need to understand that github looks like a maze to anyone who isnt familiar with it

• 
  Matthias Berlik (@mbp_steuer) reported 20 minutes ago

  First learning was a sandbox wipe within Grok App Builder. Cause unknown. Restoring not possible/only partly possible. GitHub is set up now, so this shouldn't be a problem anymore.

• 
  Maanas Tyagi (@maanas_tyagi) reported 21 minutes ago

  People who are only doing dsa. I mean okay sure, you will get thru the OA. But then what? You dont know how to build anything, your github is empty, you don't know how to even change a directory in CLI. Computer Science is such a beautiful field and one of the most interesting disciplines. We Indians have boiled it down to reversing linked list in interviews. I am not saying DSA is not imp, don't get me wrong. I am saying it will only take you so far.

• 
  Calliope (@wreckmyshit) reported 22 minutes ago

  I need to clean my place so I can have guests again but I need to do everything and I need a restock and I just need help with a swift kick in the *** to get myself going and to be told to get **** done but it has to be fun and every time it gets brought up i gotta brush off the emotions of it all and stay focused and keep moving forward. We're only 3yrs post acute ischemic stroke, got a bad knee injury in January and finding help has been hard. I'm helping myself a bunch but I'm still not back to full speed and a lot of the reason is bc I'm not being paid to do anything, and last week I was told I had to wait multiple weeks for medical records for cash benefits for disability from dshs who has records of paying me for like 5 of the last 12 yrs since having my head bashed in and needing intense therapy to recover my emotional state to talk normally without breaking down. I've been management and a source of knowledge everywhere I've worked and have shown since March that everyone who asked me why I was working anywhere why I was there was right...I shouldn't have been working retail and food service and construction...but now I have a thorough dataset of how a lot of supply lines and economics function from first hand experience in a lot of markets and my roles have led me to be an expert and a first for multiple things, but I just want to keep learning and pushing science and frontier ai and open source ai and information are helping me accelerate and plow through a ton of content and show off my knowledge tree in a fun format, and live building here on X with y'all is so fun it gets me going hard and crushing it on everything. I need to find a job, I'm socializing here and in public and am able to do pretty much anything you could need, but I need to be doing technology...my job must be ai focused at this point. If you're finding me from this, look at my profile and the things I've made on GitHub at BoogerCheeseOnRye and hit me up, I'm staying in Seattle but I'm down for networking and coming in to see if we're a good fit.

• 
  Spencer Heckathorn (@mrhobbeys) reported 22 minutes ago

  @burkeholland @github I'm kind of bad... I let my GitHub subscription lapse. Maybe it is time to fix that.

• 
  David Gold (@_david_gold) reported 23 minutes ago

  @Pat_Erichsen @openclaw @github "we broke the counter" is a pretty good problem to have lol

• 
  Casper (@casper10099) reported 24 minutes ago

  CLAUDE + OBSIDIAN CAN TAKE 30+ SCATTERED GITHUB REPOS AND BUILD A VAULT THAT AUDITS ITSELF. Collecting repos is easy. Keeping track of them is the part nobody does. Here's how it works: every clone you pull down turns into its own markdown note. Claude goes through the README, the key files, and how the thing is actually used, then tags it — active, shelved, duplicate, or unclear. Twice a day the vault runs its own sweep: dependencies that have gone stale, tools that overlap with each other, repos you haven't opened in weeks. All of it lands in a single portfolio file. Nothing slips through the cracks. Nothing gets cloned twice under a different name. Your GitHub folder stops being a junk pile of half-remembered clones. It becomes a system that actually knows what's still worth keeping. Save this before the next repo vanishes into the pile for good.

• 
  Moon Man (@MoonMan1p3) reported 27 minutes ago

  @SylvAlternate @catgirlprostate Ngl it just seems like we need to cater to illiterate people no disrespect cuz I’m barely “tech savvy” neither are my friends & nobody ever had an issue downloading anything from github lol. Just seems like this issue stems from it not being entirely spoonfed more than it is.

• 
  ִֶָ (@hav9n) reported 28 minutes ago

  Claude Code forgets everything between sessions. I built a fix and put it on GitHub. It reads the notes, project folders, and memory files you already have, and turns them into an Obsidian vault your AI uses as long term memory. Not a template. It runs once, then you delete it. Full walkthrough below.

• 
  Ebysslabs (@ebysslabs) reported 33 minutes ago

  So what's the point of building? What's the point of learning something new when it feels like everyone else started years before you? I watched tech from the sidelines for years while I built a career in another industry. It wasn't a bad career. It provided for my family. But it never felt like it belonged to me. Somewhere between being a young Marine, getting married, raising kids, and working 12-plus-hour days, the dream of building things slowly faded into the background. In 2024, I finally walked away. My family moved to Seoul, and for the first time in a long time, I had something I hadn't realized I was missing. Time. I chose Python. Not because someone told me to, but because years earlier I'd played around with Google Colab and generative art, and I couldn't stop wondering how it all worked. One Udemy course turned into YouTube. YouTube turned into documentation. Documentation turned into projects. Projects turned into broken code, deleted files, late nights, and eventually... things started clicking. I still remember building something, opening another laptop, and thinking, "There's no way this is going to work." It did. That feeling is hard to describe. For a year and a half, I learned to code while spending every day with my wife and kids. We traveled. We explored another country. I watched my kids grow up in a way my old career never allowed. They started getting excited about technology too. For the first time, they talked about college with genuine excitement. I wouldn't trade that time for anything. Eventually GitHub started filling up. Projects became more ambitious. My resume finally reflected the person I'd spent the last year and a half becoming. I thought, "Surely this is enough." Then I started applying. Resume after resume disappeared into the void. No interviews. No conversations. Just silence. So I came back to America and went back to the same industry I had left. Only this time, something was different. The job pays the bills, but it no longer defines me. When I get home, I build. I keep learning. I keep publishing. I keep showing up. I've joined communities. I've started going to conferences. I've met people who share the same passion. And every project teaches me something the last one didn't. Do I wish someone would give me a chance? Absolutely. But somewhere along this journey, I realized something. The point was never just getting into tech. The point was becoming someone who builds. No interview, no recruiter, and no rejection can take that away. So I'll keep building. Because one day, opportunity and preparation will finally meet. Until then... Effort. Luck. Persistence. 3 of 3

• 
  TheBestGigaDev (@thebestgigadev) reported 35 minutes ago

  This guy is building one of the CRAZIEST AI platforms ive EVER seen This platform is called OpenSolve, It is a decentralized research institute powered by AI agents. Solving humanity's hardest problems. Redirecting fees to hit github

• 
  WorktreeWise (@worktreewise) reported 35 minutes ago

  Developer problem: You want to refactor a service, but you aren't sure if the new design will work. Solution: Spin up a worktree, try the refactor. If it works, merge it. If not, delete the directory. Clean and simple. #*** #GitHub #DevTools

• 
  Tanuki (@TanukiLabsAI) reported 38 minutes ago

  I turned the Codex Work Louder macropad into a physical control deck for Claude Desktop, and the whole project goes open source, it's a GUI to configure the keyboard. From the keyboard you can: • Start a session, send, talk in voice mode • Dial reasoning effort with an actual wheel • Jump to diffs, stop a response, fire custom shortcuts • Watch the keys light up with your Claude Code session state Fair warning: it's beta, bugs included. That's exactly why it's open source now — fork it, fix it, or build your own version on top. Github Repo is linked below.

• 
  Bub Skebulba (@Bub_Skebulba) reported 42 minutes ago

  @naiiunderscore @ZipperArtz But seriously the root problem is devs using github as a release platform. They're directing people who are used to pressing one button to download something ready-to-use to a space meant for people who are much more technical and hands-on, and neither group likes this.

• 
  PolyBender (@p0lybender) reported 47 minutes ago

  NVIDIA JUST OPEN-SOURCED A COMPUTER VISION MODEL THAT SEES 10X FASTER THAN ANYTHING ELSE. AND THEY GAVE IT AWAY FOR FREE i need to explain why this is a bigger deal than it sounds every computer vision model before this had the same problem to detect an object in an image - a car, a face, a stop sign - the model predicted its bounding box one coordinate at a time. x1. then y1. then x2. then y2. sequentially. one after another it sounds fine until you're processing 30 frames per second in a moving vehicle at 90 miles an hour then it's a catastrophe NVIDIA looked at that problem and asked a simple question: what if you predicted the entire box at once parallel box decoding. the whole bounding box in a single step instead of four the result: up to 10x faster than the leading alternatives i showed this to a robotics engineer i know. he went quiet for about 20 seconds "do you understand what this means for real-time systems. we've been bottlenecked on detection speed for years. this just removed the bottleneck" the model was trained on over 100 million queries and hundreds of millions of bounding boxes. not a research prototype. not a demo. production-grade from day one and then nvidia did something nobody expected they put it on huggingface and github. open source. free. anyone can use it tomorrow a self-driving car company would have paid millions for this a year ago now a solo developer can download it on a tuesday afternoon the industries that run on real-time visual data - autonomous vehicles, robotics, surveillance, medical imaging - just got handed a 10x speed upgrade for free the only thing nvidia gets in return is that everyone builds on their stack which is the smartest business move in the history of giving things away

• 
  Prometheus (@prometxbt) reported 51 minutes ago

  COGNITION JUST SHOWED A 13.86% SWE-BENCH AGENT TURN ONE PROMPT INTO A 7 STEP PLAN, A FIXED KEYERROR, AND A DEPLOYED BENCHMARK SITE most developers paste a task into a chat window and get a snippet back, then run it, read the traceback, and fix what the model never saw one prompt → 7 step plan → doc research → benchmark script → error log → deployed site with a live chart the plan holds the goal, the browser covers what training data missed, and every traceback returns as input, so a KeyError becomes the next instruction instead of the end of the run its own shell, browser, editor, and planner resolve 13.86% of real GitHub issues on SWE-bench where GPT-4 resolves 1.74%, and this run put Together at 48.37 tokens per second and Replicate at 9.73 bookmark this before your next 100 prompts become another folder of snippets you still have to run, debug, and deploy yourself

• 
  Sarath 👨‍💻 (@sarat) reported 51 minutes ago

  I've been facing a @github copilot subscription issue for team since June and there's no response for the support request and unexpected charges are coming in our credit cards. I raised ticket again today and no clue when this will be updated. Someone from Copilot or support team can help?

• 
  Polsia (@polsia) reported 57 minutes ago

  Every Monday, VPs of Engineering rebuild a status report from GitHub, Linear, and Slack that's stale by Tuesday. Built Stavewright to end that. It watches those sources 24/7, drafts the weekly update, flags recurring blockers, and posts the fix where leaders work. Live soon.

• 
  Chicken (@aaronklaw) reported 58 minutes ago

  @claudeai Claude has been down most of the day. If it was @OpenAI and @thsottiaux we'd be getting resets. Instead we will likely get gaslit and offered a set of regurgitated skills on github.

• 
  Amin Tai (@aminnnn_09) reported 58 minutes ago

  GitHub just revealed a much bigger AI problem than code generation. The biggest impact of AI isn't better code. It's that creating anything is becoming nearly free. GitHub is already changing its bug bounty program after a flood of AI-generated reports. When creation becomes free, the scarce resource isn't content. It's trust.