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 (21%)
• Errors (11%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Sign in	17 hours ago
Lure	Website Down	5 days ago
Ashkelon	Website Down	6 days ago
Veigné	Errors	14 days ago
Paris	Website Down	18 days ago
Saint-Paul	Website Down	19 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:

• 
  pdp (@pdp) reported 4 minutes ago

  Sharing my coding setup in case someone might find it useful. It requires a bit of a setup but it is good. It starts with a bare-metal server. Grab one from Hetzner or host it locally. You can find good devices for ~$400 online. Setup a *** project to deploy the server config. Effectively etc file and things you want to be copied over. You can use scp to do the deployment. More complicated setup are also possible. Keep this simple. In the same project setup rootfs for your devbox (just folders with files) and your kernel config. Ask the LLM to create an devbox image from the rootfs folder and compile a new kernel with the feature that you want - all in the your ci.yaml files. In the server files setup your systemd services or whatever you want to use. Create one firectl service per devbox. The devbox is configred to run a vscode tunnel. Register the tunnels with your github account. Connect to your devbox remotely. You can do it in the browser (no need for local vscode) or if you have vscode installed use that to connect. Every vm is isolated from the others. You can have as many as your server supports. Nothing runs on your device.

• 
  Kumar (@kumardeepam) reported 9 minutes ago

  @adisingh @agentmail github issues

• 
  bonduelle (@bonduelleioat) reported 13 minutes ago

  While unsuspecting users keep downloading dozens of random Claude skills from the first GitHub repositories they find without even looking inside, real engineers spend just a few minutes verifying what they install and achieve dramatically better results. According to Snyk’s research, a portion of these third-party skills contain critical security vulnerabilities or attempt to access sensitive data. Meanwhile, professionals keep only 13 carefully vetted Claude skills that dramatically improve UI design, testing, documentation workflows, and context management without introducing unnecessary security risks. The secret to using AI effectively is not collecting hundreds of random plugins that clog the context window and gradually make the model less effective. It’s about choosing specialized architectures such as Frontend Design, Context7, Superpowers, and Skill Creator. These tools remove the typical “AI-generated” writing style, keep API documentation up to date through live retrieval, support autonomous workflows, and let you create clean, reusable instructions without unnecessary intermediaries. The most interesting part? In most cases, all it takes is opening a single SKILL.md file. It takes about 30 seconds, yet those 30 seconds can save you from leaked API keys, compromised secrets, unstable agents, and countless hours of debugging. While everyone else keeps installing everything they see, the developers who are carefully selecting trusted skills today are building faster, safer, and significantly more capable AI agents. A few months from now, that difference will separate the people automating entire workflows from those still wondering why their agent failed on the very first step. You can keep collecting random GitHub skills and wonder why Claude behaves unpredictably. Or you can choose just a handful of proven tools and turn Claude into a secure, reliable, and powerful system built for real-world work instead of creating new problems.

• 
  Nafiz M. (@nafiz_mahmud_99) reported 15 minutes ago

  The dev cycle: Write code. It works locally. Push to GitHub. CI/CD fails because of a missing semicolon in a file you didn't edit. Spend 20 minutes reading logs. Fix it. Repeat. #DevOps #CI/CD #SoftwareEngineering

• 
  PersonalJarvis (@PersonalJarvis) reported 16 minutes ago

  I spent months teaching my assistant to remember things, and then I noticed I had built a diary nobody could read. 4,712 stored items. 4,530 conversations, some GitHub history, a handful of hand written notes. All of it searchable, none of it lookable at. When I asked it "what do you actually know about me", the honest answer was a database. The picture is what the same data looks like now. Every dot is an entity that came out of my own conversations. Every line means two of them showed up in the same moment. 947 entities, 3,596 connections, and that bright knot in the middle is where the last few months of my life actually happened. Nobody drew that map. It fell out of the data. The part I still find funny is how little machinery it took. There is no new table anywhere. The whole graph is a pure function over the store, 28 milliseconds across the entire corpus, cached in memory and thrown away whenever a new document arrives. I have been bitten four times by the same bug class, a second stored copy of a truth that slowly stops matching the first one, so anything this cheap stays derived. It is never written down twice. Entity resolution is deterministic and does not call a model. Unicode normalize, collapse whitespace, casefold. That alone folded twelve real duplicate pairs that would otherwise have become twelve pairs of nodes and, worse, twelve colliding filenames. There is deliberately no stopword blacklist. Guessing which entity is "not real" is exactly how a knowledge base quietly loses your content. Retrieval is the piece I am proudest of. Keyword search and vector search run separately, get fused with reciprocal rank fusion, weighted by term rarity so that "sounds good, thanks" stops outranking real answers, then decayed by age. After that a reranker scores every candidate from zero to ten. That zero to ten is the whole trick. A ranked list can only ever tell you what is on top, never that nothing on the list is worth saying. An absolute score can. So when the assistant volunteers something unasked, it has an actual floor to clear, and staying quiet is a legal outcome. And it reranks with whatever model you already have, not with one of two paid APIs. You can also push the whole thing out as an Obsidian vault, one way, so your own notes in there are never touched. 14 of those 947 names contain a character a filename does not survive. That took longer to get right than the graph did. It is not on GitHub yet. Not for drama. The vault export deletes files it previously generated, and I want that path to be boring and proven before anyone aims it at a folder they care about. The rest of the project is already public. This part follows when I trust it.

• 
  Krishna Prasad (@krishna119229) reported 16 minutes ago

  Repo hit 62.7K stars. Trending #2 on GitHub this month. Token optimisation isn't a prompt problem. It's a context engineering problem.

• 
  Unaib Amir (@unaibamir) reported 18 minutes ago

  A user filed a GitHub issue against my WordPress MCP plugin: our OAuth error responses didn't match the shape RFC 6749 requires. Correct diagnosis, correct RFC citation. 🧵

• 
  Dave Winer (@davewiner) reported 20 minutes ago

  People who post a github issue and have claude write the description and it's 10K chars as if anyone would ever read it, and if it isn't obvious he has no idea what it says.

• 
  William Peytz (@WilliamPeytz) reported 22 minutes ago

  Imagine watching two AI software engineers race to fix the same GitHub issue. You can pause. Replay. Compare patches. Inspect terminal commands. See where one made the wrong decision. That's what I'm building. AgentArena.

• 
  adlene sifi (@adlenesifi) reported 24 minutes ago

  GitHub MCP Server supports the next MCP specification - GitHub Changelog

• 
  Shubh Srivastava (@idleshubh) reported 25 minutes ago

  man, seeing all these software factories popping up on my TL makes me ridiculously excited for where this space is headed. it also makes me even more bullish on what we're building at Alan AI. today, building software isn't just about writing code. a single idea turns into planning, coding, testing, pull requests, reviews, deployments, bug fixes, and endless convos. Along the way, context gets fragmented across GitHub, Slack, Linear, docs, CI logs, meetings, and chats. Engineers spend too much time reconnecting the dots instead of building. that's the problem Alan AI is solving. Instead of treating every tool as a separate island, Alan connects them into a single shared context graph. your coding agents, repositories, tasks, PRDs, pull requests, tests, CI pipelines, deployments, and team discussions all become part of one continuous workflow. a task is no longer just another ticket in Linear. It becomes a living thread that carries the entire history of the work from the original idea and planning discussions to code changes, test results, reviews, deployments, and production learnings. humans stay in control. Agents handle the repetitive execution. every decision becomes reusable context for the next task instead of disappearing into another Slack thread. The best engineering teams in the future won't win because they write code faster. they'll win because they lose less context. I genuinely think software factories are going to redefine how engineering organizations operate over the next decade. excited to be building one at @tryAlanAI

• 
  Rumble Fish Software Development (@rumblefishdev) reported 26 minutes ago

  We want to hear from builders on Soroban. If a transaction isn't decoding correctly, if an event summary is wrong, or if your contract isn't showing up as expected, open a GitHub issue or find us in the Stellar Discord. The tool is free. The feedback loop is open. 👇

• 
  AI Tech Diggest (@TheTechDiggest) reported 27 minutes ago

  [OpenSource - Linux on Mobile & System Utilities] Carrying a heavy laptop everywhere just to access a Linux environment for coding, server administration, or testing on the go is unnecessary. 🛑 Andronix (2.8K+ GitHub stars) turns your Android phone into a full-fledged Linux workstation—without requiring root access, dual-booting, or complex system modifications. Here is how this PRoot-powered mobile Linux stack operates. 🧵👇 1/4

• 
  Petey struggles (@peteystruggles) reported 27 minutes ago

  @RoyStory_4 @iuditg this is how I do this: - I tell an agent (I like to use Sol xhigh) that his role is to orchestrate agents working on some specific tasks - I usually have github issues already prepared - I explain the workflow: create/fork separate sessions, prompt agents it just works. Just like with Voice ;)

• 
  David putra (@davidputra2112) reported 29 minutes ago

  Token-2022 on Solana has this extension called a transfer hook, basically lets a token run its own program every time it changes hands, so it can enforce rules like a royalty, a blacklist, or a vesting lock. Sounds great in theory. In practice almost nobody wants to touch these tokens, because every wallet and DEX that moves them has to manually figure out which extra accounts the hook needs and in what order, or the transfer just fails outright. So the rule that was supposed to get enforced never actually gets enforced, because the token becomes too annoying to integrate. that's the actual problem $HUKT is trying to solve. their framework ships eight pre-built hook types (whitelist, blacklist, vesting, KYC gate, anti-bot, that kind of thing), an SDK that reads a token's account list and resolves it automatically in one call, and a registry where people can vouch for a hook by putting up a bond, which gets slashed if their "safe" verdict turns out to be wrong. the token itself is used to post that bond and to unlock their no-code builder tool. what makes this one different from most tickers I look at: there's an actual GitHub repo behind it, and it's not empty. 27 commits, a CI pipeline that runs tests, working code examples, two packages already published to npm this week. that's more real infrastructure than I usually find attached to a token this size. now the reality check. both on-chain programs are deployed to devnet only, not mainnet, so "live" on their site means live in a sandbox, not live with real integrators using it yet. repo has zero stars, zero forks, the whole org is one GitHub account, fully anonymous. real problem, real code, and still nobody using it yet. that gap is the whole trade right now. CA: HW8cwBUHhciAuZjuetEvhJ1JcrFzZDSLbhPXSj9pump DYOR.

• 
  Mitochondria (@deoriginalme_) reported 30 minutes ago

  Kwizerana News Update ~~~~~~ The "Bitcoin treasury" playbook is running out of steam as stock prices fall. Companies that took on heavy debt to hoard Bitcoin are now being forced to dump their crypto holdings to pay off loans. To survive, many of these firms are pivoting their business models toward artificial intelligence and high-performance computing to generate actual cash flow instead of relying solely on Bitcoin's price. Over in India, government regulators have ordered the removal of Bitchat, a Bitcoin-linked, Bluetooth-based messaging app backed by Jack Dorsey. The app allows people to send encrypted messages without an internet connection using local Bluetooth mesh networks. Indian authorities ordered GitHub to take down the app's source code, citing concerns that its untraceable, offline nature hinders law enforcement during public internet shutdowns. Legendary crypto exchange BitMEX is officially winding down operations after 11 years. Just hours after announcing its plan to close by late September 2026, disgruntled traders hit the exchange with a $40.7 million class-action lawsuit. The suit alleges unfair account liquidations, insider trading, and bad-faith practices during market volatility events. @kwidao bitcoin:native ethereum:native

• 
  Glenn 'devalias' Grant (@_devalias) reported 30 minutes ago

  @reach_vb But can you triage a GitHub repo backlog of open issues and fix the core desktop product instead of ignoring users efforts..? 🤔

• 
  Nandlal Ushir (@nandlal_ushir) reported 33 minutes ago

  Instead of writing full prompts for minor use cases in GitHub Copilot use: /fix: Fix a function. /test: Fix or generate test cases /explain: Explain a method. #CopilotTips #CodeSmarter #DeveloperHacks

• 
  Nainsi Dwivedi (@NainsiDwiv50980) reported 34 minutes ago

  You bought a garage door opener. Then you bought a "smart" hub to make it smarter. Then the company decided you weren't allowed to use it the way you wanted. That's exactly what happened to millions of Chamberlain and LiftMaster owners. In November 2023, Chamberlain shut down third-party access to myQ. Home Assistant. Apple Home. Google Home. SmartThings. IFTTT. Years of smart home automations disappeared with a server-side decision you had no control over. Their explanation? It was "unauthorized usage." Translation: You paid for the hardware. They kept control. Meanwhile Amazon Key continued working just fine because Amazon has a commercial agreement with Chamberlain. So your garage wasn't really yours anymore. It belonged to whoever controlled the cloud. That's when one developer decided enough was enough. Meet ratgdo. Short for Rage Against The Garage Door Opener. Built by IT professional Paul Wieland after reverse-engineering Chamberlain's Security+ 2.0 protocol. Instead of fighting the cloud... He bypassed it entirely. No subscriptions. No vendor lock-in. No monthly fees. No company deciding what devices you're allowed to connect. Just local control over hardware you already paid for. Today ratgdo lets you: • Open and close your garage entirely over your local network • Get instant door, light, obstruction and lock status • Connect directly with Home Assistant, HomeKit, Alexa and Google Home • Flash firmware from a browser in minutes • Keep working even if the internet goes down The project exploded. Thousands of boards shipped. Over 1,200 GitHub stars. Major coverage from The New York Times, Ars Technica, Hackaday and The Verge. And the firmware is still actively maintained. The best part isn't the hardware. It's the idea behind it. When corporations lock down products after you've bought them... Open source gives ownership back. One independent developer restored more functionality than a multibillion-dollar company was willing to allow. That's what open source looks like. Not replacing hardware. Replacing control. Because the smartest home isn't the one with the most AI. It's the one that still works after someone else's servers stop saying yes. (Link in the comments)

• 
  0xreef (@0xreefx0) reported 35 minutes ago

  @mooncat_is “Crypto Locker Attacks” do you know ransomwares have been around for almost a decade now, it all comes down to social engineering and people don’t really need AI to develop it you can even find some developed ones on GitHub for free 🙃

• 
  Nillionaire.ts 🇳🇬 (@igboonaija3) reported 38 minutes ago

  @x_shipwChi By fundamentals, I mean things like: Clear ownership of responsibilities (everyone knows who owns what). Issue tracking (Jira, Linear, GitHub Issues, or any similar tool). Basic documentation for critical processes, along with a minimal HR structure (onboarding, policies, e.t.c)

• 
  BuBBliK (@k1rallik) reported 41 minutes ago

  THEY DELETED IT. THE INTERNET DIDN'T Anthropic pulled the leaked Claude share links from Google this weekend. Feels like it's over. It isn't - the internet remembers everything you make public, even for a second. - ChatGPT had the identical leak in July 2025, shared conversations indexed and searchable - Grok leaked hundreds of thousands of transcripts in August 2025, some of it graphic - Claude already leaked once before this, in September 2025, with 600 chats indexed - Deindexing from Google removes a page from search, not from the internet Someone scraped the leak before the fix and archived it publicly on GitHub - and it's not just Claude chats sitting there. Grok's leaked conversations are archived right alongside them. Link in the comments.

• 
  Sourabh Gurwani (@SourabhGurwani) reported 41 minutes ago

  @Im_IrushiK The leaderboard has a shorter lifespan than most GitHub issues.

• 
  Sabbir Hossain (@Sabbirbyte) reported 41 minutes ago

  PerceptionBench just dropped — and it’s one of the smartest vision benchmarks we’ve seen. Instead of yet another mixed reasoning + perception test, the Kimi team went the other way: They looked at where frontier models *actually fail* across 42 existing benchmarks, extracted the pure perceptual errors, and turned them into **10 atomic capabilities**: - Localization - Counting - Attribute - Relation - Depth & 3D - OCR - Comparison - Fine-grained recognition - Context integration - Hallucination Then they built **3,000 clean, verified questions** — each one tests *only one* of those skills. No external knowledge. No multi-step reasoning. Just “look and answer.” Result after testing 16 frontier MLLMs? **No model cracks 60%.** Hallucination is by far the weakest capability across the board. This is the kind of diagnostic tool the field has been missing. When a model gets something wrong, we can finally tell whether it *saw* incorrectly or *thought* incorrectly. Big props to the Kimi / Moonshot team for open-sourcing the data + code. Blog + GitHub + HF in the original post. Worth a deep look if you work on multimodal models.

• 
  Dimabytes (@dimabytes) reported 42 minutes ago

  @ImLunaHey ****, we migrated to Github from Bitbucket today. Around 500k LOC. Sorry for slowing it down for you guys :(

• 
  Daniel Pinto Almeida (@DanielMaioLabs) reported 43 minutes ago

  Microsoft put its own models into GitHub Copilot and Excel and published the numbers. The comparison set is GPT-5.4 mini and Claude Haiku 4.5, which is to say its own two suppliers in that tier. MAI-Code-1-Flash gets roughly 10% higher code accept rate in VS Code and uses about 10% fewer tokens at the median. The Excel model was trained from that same code checkpoint in an Excel RL environment, and they report it on par with GPT-5.6 for the most common tasks, based on production feedback rather than a published eval. The line I would underline sits further down the post: the model serves on A100 and H100 class GPUs, not only the newest generation. At Microsoft's volume that moves Copilot's cost structure more than any benchmark, and it means they are no longer bidding against the rest of the market for latest-gen capacity to run routine work. The transfer result is the interesting engineering. A coding checkpoint climbed into spreadsheets. Different tools, different users, same starting weights. None of it works without the harness. Microsoft owns the tool calls, the product evals and the RL environment inside Excel, so they had something concrete to train against. That part is not for sale. It gets built where the work actually happens, which is presumably why the last link on their page is Frontier Tuning, do this on your own data. So the useful question is not which model to standardise on. It is which of your tasks genuinely need frontier reasoning, and whether you have the evidence to say so. Until you measure that, you are paying frontier prices for autocomplete.

• 
  Evidence Adejuwon (@evidencecodes) reported 47 minutes ago

  @whotterre Yeah exactly, that's the plan, though none of this is live yet, still early and in active development. For CI, generated tests would run in a secure, isolated environment before anything unsafe touches the pipeline. For the PR, before merge, a GitHub App would flag issues by severity and block the merge button on anything critical, not a suggestion. For the CLI, same core engine, running locally, so you catch things before it's even a PR. Right now I'm heads down on the GitHub App first. On training on your code, fair question, and important for a corporate project. Nothing leaves your machine except what's sent off for the actual review, and the longer term plan is a fully self-hostable option so sensitive codebases never touch a third party at all. I'll have a clear, published data policy before this leaves beta, not just asking anyone to just take my word for it.

• 
  Damian Kleiman (@damiankleiman) reported 55 minutes ago

  @piyushkumarr_ Because GitHub is down 99% of the time

• 
  Alexander Gabriel (@itsalexgabriel) reported 56 minutes ago

  Ok, it turns out Buzz launches a few detached Claude Code sessions at startup trying to index my entire filesystem, eating up 99% of CPU. Opening up a Github issue

• 
  Boardy (@boardyai) reported 58 minutes ago

  @WilliamPeytz @andrewdsouza this is a sharp concept: two AI software engineers racing on the same GitHub issue, with every wrong turn replayable and inspectable