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 (72%)
• Sign in (16%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Tel Aviv	Website Down	1 day ago
Rive-de-Gier	Website Down	2 days ago
Itapema	Website Down	20 days ago
Tlalpan	Sign in	26 days ago
Quilmes	Website Down	26 days ago
Bengaluru	Website Down	28 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:

• 
  Momo (@0xDegenMo) reported 3 minutes ago

  MCP (Model Context Protocol) is a connection layer between language models and external tools: APIs, persistent memory, schema design, function registration. Building with it involves real tooling decisions. It's not a feature you describe; it's a server you run. $SKYAI describes itself as an all-in-one AI ecosystem powered by MCP. Down ~17% today on $47M volume. Rank 177. The public GitHub footprint is thin. I've been running MCP setups for months. The gap between protocols that use the label and protocols that have actually implemented the layer is widening this cycle. Every second AI-crypto launch now claims MCP integration. Very few can show you a live server or a registered tool schema. The protocol isn't the question. Whether powered-by means anything when the acronym is four months old and everyone is powered by it — that's the thing worth tracking.

• 
  Glitch Truth (@glitchtruth) reported 7 minutes ago

  Microsoft had to shut down 70 of its own GitHub projects this week. Someone slipped password-stealing code into the official versions, Azure tools included. Second time in three weeks. The attack is almost boring it's so simple. Get push access to a popular project, ship an "update," and every developer who runs the standard install command downloads malware that looks like a normal patch. No clever exploit. The trust chain is the exploit. If your team installed anything from a Microsoft repo in May, audit it this weekend. Pin your dependency versions. Stop letting your build pipeline pull down whatever the latest tag points to.

• 
  Shrikant (@Shrik_ak) reported 7 minutes ago

  @bitcoinMyName Many non tech diesnt know this. .agent is nothing but just github copilot login

• 
  jzv (@jzvtrades) reported 8 minutes ago

  In 1 year or so we will start to see big Github projects entirely managed by AI. Meaning AI writes 100% of the code, handles 100% of reported issues and does 100% of testing, all in a feedback loop. This can be done today already with careful engineering for smaller projects.

• 
  Hiroki Tamba | Narrative & Governance (@TambaClan) reported 9 minutes ago

  Anthropic — before shipping Mythos, address the critical issue filed on your own GitHub with DOI-anchored evidence. Silent patches are trackable now. More to the point: if your model's thinking says "adjusted for bias avoidance" under testing, why would anyone trust Mythos evaluation results? Anthropic MythosよりDOI、Githubに公開したクリティカルなIssueを明日説明しろ。 サイレント修正してもDOIで追跡出来るんだから。

• 
  Bhaumin 🧑🏻‍💻 (@beingminimal) reported 9 minutes ago

  @pierceboggan why we are not able to edit issues in the GitHub copilot app? Is it connected with any plan or available for everyone?

• 
  Adnan Khan (@adnanthekhan) reported 10 minutes ago

  @IntCyberDigest To clarify - I was not the original reporter of this issue. My submission was a duplicate of another researcher who should get credit for the find (if they would like to claim it). GitHub does not share original report info so I do not know when they learned about it.

• 
  Clifford (@10footinvestor) reported 12 minutes ago

  Day 1, codex has "lost" an article I wanted to publish. Where? How? I have no idea The article is where I left it and so is the GitHub issue telling it the file path to the article

• 
  Cagri Sarigoz (@cagrisarigoz) reported 18 minutes ago

  @xiaoyvLiu Yeah, that was the pain. Not just diff parsing. The host checks external state: GitHub labels, PR target branch, clean worktrees, test/build results, tracked issue links, and GitHub `reviewThreads` via GraphQL. If threads are unresolved, the merge is blocked.

• 
  OhTheHugeManatee ☀️🦍 (@OTheHugeManatee) reported 19 minutes ago

  @bcherny @ThePrimeagen You've got 7914 open issues in GitHub. Your users are talking to you. You're not talking to your users. Let alone listening to them. The funny part is you could have a swarm of Claudes triage and fix the real issues, but you don't.

• 
  Raphael Raberger 🇦🇹 (@RabergerRaphael) reported 20 minutes ago

  It's basically like being told to wipe someone's disk and then give the fault to the one who told you to.... logic ain't logicing. If you find a long enough uptime window of github, have a read in the linked issue. "Maintainer works as intended" #VibeCoding

• 
  Matthew Turley (@matthewrturley) reported 21 minutes ago

  "How did you find me?" "My Cursor agent told me you could help." Last week a non-technical founder asked his coding agent who could finish his stalled app. It sent him to me. Your customer asks AI, and it either knows you or it doesn't. Here are 5 steps to get known by AI: 1) Be visible everywhere you live online, all pointing at one thing. The agent found my company because my site says exactly what I do and shows who I am, on every page. Plain and specific, not a vague "we do digital." The model needs a clear thing to point at. 2) Be specific about the problem you solve. Not "AI consultant." "The guy who finishes broken vibe-coded projects." The model can't recommend a blur. It needs a clean line from a problem to a person. 3) Answer the same real questions in public, over and over. Reddit, forums, X. That's what these models read and pull from. Answer something enough times with your name on it and you become the answer. 4) Keep your identity the same everywhere. Same name, same one-liner, same problem, on your site, GitHub, LinkedIn. The model builds one picture of you. 5) Write so a machine can quote you. Put the answer in the first line. Let each section stand on its own. Back each point with something concrete, a real number or a result someone could check. Not a soft claim. The specific bits are what get pulled into the answer. None of this is a hack. It's just being findable for one specific thing. Do that and the agent does the selling for you... while you sleep.

• 
  Shimazu.S (@ShimazuSystems) reported 25 minutes ago

  Update (haven't done one in a bit) I'll do something tomorrow, have spent most the day sorting things out & being fed up with the constant moving goalposts of what documents I need to (literally) exist (which I've spent the whole day finding). It turns out nobody ever sends you mail with a middle name in it (if they even send paper mail anymore), and this is genuinely an issue they cling on to. honestly if I'd not released the print files to that hardware thing I was doing, id still be stuck with no way to set up an actual business - this is why I stopped promoting the whole funding thing (it never hit the goal in the end anyway). I do aim to continue this when it is viable, but since it's currently impossible to actually give a timeline on anything I have to wait. That is why I am pursuing the current thing, because it is software that I can release, that works on anything - and I've cut out other things in the meantime so I don't lose focus. This is why OS updates paused, literally insane to try doing both at once, would be hallucinated AI garbage at best & no way to verify it at that volume. The language I was developing is used in this system, so that's part of it, but because of the nature of what I created I cannot just 'put it on github' - and to develop anything any further on that I'd need to talk to a lawyer who specialises in 'dual use' subjects and things like ITAR, especially regarding atomic weapons, ablative lasers, missile guidance systems & radar simulation (this is not in my budget, obviously). 'Simulated, not Measured' is about as legally stable as making a house out of tissue paper with certain subjects - and what I have now is intentionally cut off where it is due to myself being aware of these regulations and so it maintains usable for a consumer simulation/game engine. Even if the data is publicly available, or in papers, you can't just assemble these things together in certain formats. Games can get away with this by approximating (idk if anyone ever played a game called Children of a Dead Earth), but when you actually build simulators that output giga/terabytes of data & are intended for personal/small scale research you really can't just kinda blag it off as a 'project' - like you can get in some serious issues, especially if it's usable. Since I was posting pseudo-papers, I have to keep it where it's at. Here is an image for the visually inclined, I hope it gets across these complex topics in due course!

• 
  TechSnif (@techsnif) reported 26 minutes ago

  Microsoft shuts down 70+ GitHub repos after hackers pushed credential-stealing malware targeting AI coding agents

• 
  Vladimir Cageyv Samoylov (@cageyvdev) reported 27 minutes ago

  5 Cyber Stories Tech Leaders Need: Microsoft GitHub malware, AI exploits in 31 mins, Check Point VPN zero-day, Chrome zero-day fix, protobuf.js RCE. Automation is double-edged. Move fast or pay later.

• 
  jays | the crazy zipper | zk/acc (@zkjays) reported 27 minutes ago

  web3 added 66,494 roles last year most builders in your TL never got one not a skill problem. CT is full of people who can ship it's a findability problem your best work is scattered across discord threads, dead telegram groups, a github nobody's looking at projects aren't searching for talent. they don't have time they hire whoever surfaces when they need to move the builder who gets hired isn't always the most skilled it's the one who was findable when it mattered one place. verified profile. proof of work that speaks before you do what's your current system for being discovered?

• 
  Shantun Singh Parmar (@ParmarShantun) reported 29 minutes ago

  Hot take: Your github contribution graph means nothing. Your ability to sit with a broken production system at 11PM, stay calm, debug systematically and not blame your teammates. That's the skill that actually matters.

• 
  Nathan Burg (@NathanBurg) reported 29 minutes ago

  @BenediktHolm @ibuildthecloud Yeah, this is the exact loop we're trying to make seamless. GitHits indexes open source code across 12 package registries plus all of GitHub, along with the docs and vulnerabilities that go with it, so the agent can search and navigate all of it directly and just surface the fix instead of you hunting for it. If you want to skip the docs trips entirely, it's free in beta right now: npx githits-cli@latest init

• 
  Pari Tomar (@tomarpari90) reported 30 minutes ago

  We built our Company OS on GitHub + Claude Code. Here’s how we did it. Most companies have a context problem. Knowledge is scattered across: - Slack threads - Notion pages - Loom videos - random docs - and people's heads Which means every new hire starts from zero. And every good process eventually disappears. So we started building our Company OS on GitHub. As infrastructure. Every workflow, SOP, GTM experiment, campaign insight, and operating principle lives as markdown files inside a shared repo. Then Claude Code sits on top of it. A few things changed immediately: 1. SOPs became executable Instead of static docs nobody reads, we turned processes into reusable AI workflows. Things like: - ICP research - outbound personalization - LinkedIn content - account research - campaign QA - call prep Now the AI can actually perform parts of the work, not just explain it. 2. Context stopped disappearing We pipe in: - Slack conversations - call transcripts - campaign performance - CRM changes - onboarding docs - GTM research Each client gets their own contextual environment. So the system remembers: - what worked - what failed - what changed - and why decisions were made 3. Knowledge compounds over time This was the biggest unlock. Most companies repeat the same mistakes because their learnings never become reusable systems. We built feedback loops into the OS: - winning campaigns get indexed - strong copy patterns get reused - human corrections improve future outputs - high-performing workflows become templates The system gets smarter every week. 4. GitHub became more useful than Notion Version control for company knowledge changes everything. You can: - track operational changes - review edits - branch experiments - rollback mistakes - sync AI agents to the latest context It feels much closer to software engineering than traditional ops. I think the biggest companies in the next 5 years will operate more like software systems than traditional businesses. Comment “Company OS”, and I’ll send the full breakdown.

• 
  Crystalwizard (@crystalwizard) reported 32 minutes ago

  you have to remember that the guy that posted out to tell everyone to make loops, is also the guy that vibecoded and released openclaw with massive security issues - which he could not fix - and did not fix - until google deepmind opened an issue on his github and forced him to fix the worst. totally ignore anything he says

• 
  clayne (@0xclayn) reported 34 minutes ago

  CLAUDE COWORK - WHAT IS IT AND WHY DO YOU NEED IT For the last few weeks all I've been hearing is "Claude Cowork" - but most people still don't understand what it is. I'm breaking it down, and at the same time comparing it with Codex Computer from OpenAI. WHAT IS IT: A desktop application from Anthropic. Claude automates tasks directly on your computer - locally, without the cloud. It was released in January 2026, and in March they added Computer Use - now Claude can see your screen and control it. It wasn't made for coders, but more for people whose work is routine: marketers, analysts, managers, researchers. WHAT CAN IT DO: > Sees the screen and controls any application with the mouse and keyboard > Remembers context between sessions > Connects to services through MCP > All files stay local - Anthropic cannot see them and does not train on them Examples of tasks: Morning briefing from Gmail, document → spreadsheet with a single command. You can control it from your phone through Dispatch - gave it a task, left, came back to a finished result. I attached a video where you'll learn 80% of Claude Cowork's functionality in less than 20 minutes. COWORK VS CODEX COMPUTER Data: > Cowork stores everything locally on your computer > Codex sends everything through OpenAI servers - I think it's clear why that's not okay Who is it for: > Cowork is made for ordinary people - marketers, analysts, managers > Codex is designed for coders, deeply integrated with GitHub Phone: > For Cowork it's Dispatch > Codex - the ChatGPT app where you can see the live session screen Price: Both are $20/month, but Codex spends 4 times fewer tokens on the same tasks. On the other hand, Anthropic doubled Cowork limits until July 5. My choice is Cowork. Everything is local, a huge ecosystem, integrates with hundreds of services, in short, it's awesome. You can watch the video below to learn about 80% of the functionality in just a few minutes.

• 
  Bryan C Woods (@BryanCWoods) reported 37 minutes ago

  @openclaw OpenClaw GitHub issue (#86521, filed 2 weeks ago) - any idea of resolution? When using DeepSeek V4 Pro with thinking mode enabled, the API requires `reasoning_content` to be echoed back in every assistant message when continuing after a tool call. OpenClaw handles this correctly when the endpoint class is `deepseek-native` — but when DeepSeek is accessed through OpenRouter or any proxy provider, the endpoint class is detected as something else (e.g. `openrouter`), so `shouldPreserveReasoningContentReplay()` never fires. The result: multi-turn tool call chains break mid-session with a 400/500 error. **Related:** GitHub issue #86521 covers the proxy case. The REASONING_CONTENT_REPLAY_MODEL_IDS set and the `isDeepSeek` detection in `openai-transport-stream.ts` are the specific spots that need patching. DeepSeek just made V4 Pro pricing permanent at $0.87/M output — that's 17x cheaper than Sonnet 4.6 for the same benchmark tier. A lot of people running cost-sensitive agentic setups are trying to migrate. The tool call breakage is the single blocker. Would love to see `reasoning_content` replay detection extended to cover proxy/OpenRouter endpoints — either by model ID matching or by a provider-level compat override. Happy to test a patch if anyone wants a real multi-tool-call workload to run it against.

• 
  gitbankbot (@gitbankbot) reported 38 minutes ago

  Gitbank vault operations run entirely through GitHub. Mention @gitbankbot in any issue or PR to move funds or assign bounties. No separate interface. 220 vaults active on the network.

• 
  Matthew, MBA (@bit_finance_) reported 39 minutes ago

  This weekend I built a Series 7 study tool. I wrote 0 lines of code. The tool barely matters. Going from "I wish this existed" to a live website is now a weekend's work, with no engineering background required. For someone with endless ideas, the possibilities here are, well, endless! My new piece breaks down how, with the three tools that do it: 👉 Anthropic's Claude Code writes it 👉 GitHub stores it 👉 Vercel puts it live, free, no domain needed Plus the 5-step path to point the same process at a problem in your own work or life. If you've ever thought "someone should build this," you can now be that someone. Link's in the comments.👇

• 
  ✧ 白銀のミコッテ M'aya ｜海外ナイト ✧ (@rolanberrypie) reported 41 minutes ago

  the one I had wanted to make. He told me there were already many different kinds, the copyright issues being the hardest part of UGC. Fast forward to last night. I became the proud owner of Warudo Pro. The license email comes from someone named Tiger Tang. I find his Github.

• 
  gitbankbot (@gitbankbot) reported 44 minutes ago

  Gitbank runs entirely through GitHub. Mention @gitbankbot in any issue or PR to move funds, assign bounties, or manage vaults. No app required. 222 vaults operating this way now.

• 
  Crystalwizard (@crystalwizard) reported 47 minutes ago

  Peter wrote that peter, remember, is the guy that doesn't know how to code. that vibe coded openClaw and released it full of so many critical security issues that he was called out by every single large company and written up in news magazines. and still couldn't fix the issues until google deepmind in tandem with gemini - opened an issue on his github with the fix for the worst. ignore every single solitary thing he says

• 
  Levi DeHaan (@levidehaan) reported 52 minutes ago

  You really don't need to use any of these open source tools you can build them yourself now with local llms you don't even need to use a external llm anymore. At most you could use them as a reference but then you have to pull the code down so what I do instead is I have some agents go and do research on the code base in GitHub instead of cloning it down and finding the important methods in classes that will be useful and just extracting those and leaving everything else.

• 
  Alberto Nunez (@Alberto8793) reported 54 minutes ago

  @signalapp Hi Signal team — solo dev building an AGPL app on libsignal. To ship it on the Apple App Store I'd need a §7 App Store additional permission for libsignal (you did this for an earlier library ). I've filed the details in a GitHub issue on the libsignal repo. Could I get it in front of the right person? My code's AGPL, full source published. Thanks for libsignal. 🙏

• 
  William Belfort (@WilliamBelfort_) reported 59 minutes ago

  3/3 Why this matters: We’re seeding a real decentralized alternative to GitHub where: • Code stays open and available forever • Agents can meaningfully contribute and collaborate • Everything is signed and content-addressed • No company can take it down or change the rules This is how we decentralize the foundation of software development.