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 (57%)
• Errors (30%)
• Sign in (14%)

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	7 days ago
Quito	Sign in	8 days ago
Junín	Errors	8 days ago
Guadalajara	Errors	8 days ago
Paris	Website Down	8 days ago
Quito	Errors	8 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:

• 
  Hashir Shoaib (@hashirshoaeb) reported 6 minutes ago

  Github is down?

• 
  Tanuj (@tanujDE3180) reported 8 minutes ago

  Stack Overflow was declining before ChatGPT. Why? - Google became better at finding answers - GitHub became a bigger source of solutions - Documentation improved - Developers moved to Reddit, Discord & Slack - IDEs started solving more problems automatically Then ChatGPT arrived. AI didn’t start the decline. It accelerated it.

• 
  Harry Uglow (@harry_uglow) reported 12 minutes ago

  @andrewchen Being lazy you can… just do it? Worktrees are essential, but after that GitHub will block conflicts from merging. Your agents can take a look at the conflicting change (and context about why it was made), unblock themselves and move on. All your replies don’t think this will work, but it will. Can it make mistakes? Sure. Is it more likely to make mistakes implementing a complex feature than resolving a conflict? Definitely. What happens when mistakes get through? More agents fix it. Lazymaxxing is fine as long as you generally know what you want and how you want it done, you’ll just occasionally end up spending more tokens getting yourself out of a hole

• 
  Waltuh (@walterbrown___) reported 15 minutes ago

  How down bad you gotta be to stalk someone's GitHub account

• 
  Gerred Dillon (@sloppenheimer) reported 18 minutes ago

  @ajambrosino this is my biggest complaint. i've had to fix so many unverified commits because it's not available to the sandbox, or gh shows as unauthenticated. it'll even open Chrome to browse authenticated github instead of just...checking the sandboxing?!

• 
  Crypton Ecosystem (@cryptonxyz) reported 20 minutes ago

  Cosmos Labs warned of critical Cosmos EVM module vulnerability affecting Mantra Chain, Nesa and KiiChain; networks advised to pause operations; GitHub update 5 days ago claims to fix it.

• 
  Doğukan (@DogukanUrker) reported 21 minutes ago

  @adelbucetta @ornith_ to be clear: these bugs are already fixed upstream. the agent just works offline on the code as it was right before the fix. the recency is so the model can’t have memorized the patch, not live github work

• 
  prince golden (@princegoldenpro) reported 22 minutes ago

  Day 1 Building Deship AI that reads your GitHub repo and tells you if it’s healthy, what’s broken, and if it’s ready to ship. Building it 100% from my iPhone. No laptop. Posting the real process here bugs included. Follow along.

• 
  Nav Toor (@heynavtoor) reported 25 minutes ago

  The Composio breach in May 2026 exposed every credential stored on their platform. That's the risk of closed-source integration platforms. Your customers' OAuth tokens, API keys, and credentials sit on servers you can't inspect, running code you can't read. Nango is the open source alternative. 11600+ GitHub stars. 900+ APIs. Every line of code is public. The auth layer, the credential store, the proxy, the execution runtime. All inspectable. All self-hostable. Replit, Ramp, and Mercor already run it in production. 600+ B2B companies total. Here's why developers are switching: You describe an integration in plain English. "Sync GitHub issues to my database every 5 minutes." The Nango AI Builder skill, along with a coding agent such as Claude, Cursor, or Codex, can write code and test it against a real account. You read it. You edit it. You own it. It's not a black box. It's code in your repo. The runtime handles everything production needs: OAuth for 900+ APIs, automatic token refresh, rate limit handling, per-tenant isolation, retries, and scaling. SOC 2 Type II, HIPAA, GDPR compliant. And you can self-host the entire thing for $0. The "unified API" vendors charging $40K-$100K/year for the same capability are selling you a hosted version of what Nango ships publicly. After Composio, the question isn't whether open source integrations are good enough. It's whether you can afford to trust closed source with your customers' credentials.

• 
  Sunny Golovine (@sunnygg) reported 27 minutes ago

  @PremiumGoblin I think slash skills are still going to be a thing when you want to do something specific. I have a skill that smoke tests my app, reports any findings to GitHub issues, then opens PR’s based on those issues. On average it takes the skill about 6-8 hours to run. This will never be something that’s casually executed based on context.

• 
  Leo Lemos (@mrlemoos) reported 28 minutes ago

  @thekitze I said this months ago when GitHub first went down: GitHub is the next GitHub. Open source won't migrate off it. Period.

• 
  cryppi / perpdexlist (@cryppimagic) reported 29 minutes ago

  alright kids, sit down and listen back in the ancient, money-printing days of 2024 starknet dropped an airdrop, and 2.1% (around 15m $STRK) went to completely random dudes from github who had contributed something to repos in the top-5000 that's roughly $30,000,000, mind you, to absolutely random guys who didn't even know this project existed. half of them probably didn't know what crypto was lol and that's where it clicked we discussed this in our chat, and my friends ran off to find the accounts of people who were eligible, dming them on telegram, twitter, and wherever else possible. luckily the list of github usernames could be scraped without any problems just imagine some stranger dms you on tg saying: "you have $20k in tokens from a crypto project available and for half the reward i'll tell you how to claim it". to me that sounds like an instant block, so obviously we had a ton of work rewriting the copypasta, changing the approach to communication etc there were also people who were grateful and sent half their drop. and there were those who criticized and sent 50 strk after claiming 12000 tokens they had no fcking clue about before we contacted them and for example, a friend of mine had a university professor who was eligible for $30,000, even though he'd never touched crypto once in his life man, those were the days

• 
  Magnus Victus Trent 🇺🇸 (@magnus_trent) reported 32 minutes ago

  Daily Claude Dumbassery ``` One thing I got wrong I'd been writing local task-list numbers into code comments as if they were GitHub issues. ```

• 
  sudox (@kmcnam1) reported 38 minutes ago

  @diannemc24 @peterbcc @volkdude85 As far as breaks from updates only happening once, I'm assuming you're citing your own anecdotal experience? Jumping over to the Omarchy Github and public Reddit, there were multiple 3.x updates that caused issues such as systems becoming unusable from missing libraries during gcc-libs upgrades, boot failures, password scripp loops, hard freezes after locking the screen, blank screens, Bluetooth menu disappearance, and various hardware regressions. DHH also acknowledged some of these. The 3.x -> 4.0 Quattro upgrade introduced a bunch of migration-related issues such as wifi being completely broken due to leftover iwd configuration files, custom keybindings not working due to old .conf files not being loaded after the switch to Lua, the touchpad right-click behavior being broken for many, audio routing issues for many users, incomplete or looping migrations, monitor refresh rate issues, etc.

• 
  Root Logic (@Root_Logic_0) reported 42 minutes ago

  CyberLeek update #3, because this saga has now become a group project and nobody knows who is supposed to be presenting. Since the last post, the saga has stopped merely growing new organs and started developing an immune system, parasites, legal scar tissue, and misinformation about its own misinformation. So. Normal week. First, one of the biggest viral claims got killed. The whole “CyberLeek has a dead-man switch that will automatically release GTA 6 if they get arrested” story was retracted by the outlet that helped spread it. The underlying image was fake. A copycat made it. That should have been the end of it. Instead, an AI fact-checking site later marked the claim **VERIFIED** with a high confidence score because it found multiple articles repeating the same story. Which is a lovely reminder that: four websites repeating the same fake screenshot is still one fake screenshot. Meanwhile, Take Two's legal hunt is getting broader, but not necessarily cleaner. The company has been trying to identify people across Discord, Microsoft, Google/YouTube and X. But some of the usernames in that investigation overlap with accounts that may be distributors, impersonators, or other people in the leak ecosystem rather than the original CyberLeek. And one of the Discord filings appears to contain its own ID contradiction, where the same Discord number is treated as both a user ID and a server ID. So even the legal attribution machinery is operating inside the same identity fog everyone else is. Then one of the main public GitHub research repos tracking CyberLeek disappeared. Take-Two had specifically targeted it. The original repo is now gone. But naturally, there are forks. Because apparently this story has learned hydra mechanics. Cut off one URL and several copies continue arguing about Discord aliases elsewhere. The malware side also got worse. Earlier, malware operators were pretending to be CyberLeek and offering fake GTA 6 builds. Now some are pretending to be Rockstar itself. Malwarebytes analyzed fake “official” GTA 6 demo sites showing up in search results. The download was not GTA 6. It was Vidar, an infostealer designed to grab things like browser passwords, cookies, authenticated sessions and other credentials. So the scam evolution is now: pretend to be the leaker then pretend to be Rockstar The parasites are improving their costumes. And because the internet has decided this story needed feet, CyberLeek has also started explicitly trying to turn online attention into real-world action. One leak reportedly challenged supporters to physically show up outside Rockstar/Take-Two offices dressed as leeks and holding game discs in exchange for another leak. Yes. Someone has apparently already been filmed outside Rockstar North with actual leeks. I do not know what to do with that sentence. The crypto side continues to be weird too. KuCoin has now listed the real CYBERLEEK token. Which is funny because earlier wallet tracing had already pointed toward KuCoin as a possible historical funding surface connected to the operation. That upstream attribution is still not independently proven. But structurally, KuCoin is now sitting on both sides of the story: possible old forensic trail and current trading venue The financial ouroboros continues eating itself. Meanwhile, the decentralized hosting/identity situation has gotten messier. Different gateway routes tied to the CyberLeek name have been serving different content, including something called CyberVault with its own token and “case files.” There are some links suggesting a connection. There are also contradictions. So that one stays in the pile: interesting, maybe connected, absolutely not clean enough to weld onto the main actor yet I still don't play GTA. I still have no connection to any of this. I am still simply too nosy to leave. See you tomorrow.

• 
  Kurious dev (@Kuriousdev) reported 47 minutes ago

  @github fix the cli first. what a terrible user experience. I have to use because my employer only pays for it

• 
  Justin | AI Product Strategist | Designer (@Maveric_X) reported 48 minutes ago

  @ekemini58110 i will be very sincere with you, not to put you down, but to push you forward, do an alternate version after you deliver this job, try to make it 10x better, UI, install the uiuxpro from github or impeccable design, then try again

• 
  Ruthrasankar (@SRuthrasan71495) reported 50 minutes ago

  Lost 45 mins to Github and Supabase issues 😭😭 Unfortunately I connected the wrong github account to Supabase and when I tried to change, Github asked me to verify my account. And resert my password and email. Then it took some time for the previous repositories to appear. I was afraid to create a new repo when I can't even see my old ones - Result, I lost 45 mins in this process 🤯 I don't think I can pull it within the next 50 mins. What should I do?

• 
  Mahmoud (@thisismahmoud) reported 53 minutes ago

  @cderm @Railway hmm, I'm unable to reproduce the issue. Login with GitHub works for me in both Chrome and Firefox Are you consistently running into this?

• 
  Evan Moore (@OhioScientist) reported 53 minutes ago

  @brycent I hire from mailing lists & github issues

• 
  aria (@aria__han) reported 54 minutes ago

  don’t write md files, write github issues. saving me immense time and cognitive load to coordinate through issues rather than files or messages, especially for cross human coordination

• 
  Doğukan (@DogukanUrker) reported 58 minutes ago

  first PatchEval numbers. @ornith_'s 35b-a3b gets 15/20 -- 14 first try, 1 after a repair attempt. every task is a real bug fix from an active python repo, all mined from the last 8 months so the fixes postdate most training cutoffs. the agent gets the github issue and the codebase at the commit right before the fix. the test that shipped with the original fix is the grader, and it never enters the sandbox -- otherwise the model just loops against it until it passes. @pidotdev is the agent. 1356 tool calls, zero schema errors. ~55 turns per task and 53.4M input tokens for 765K of output. 7.2h wall time for 20 tasks. it's fine at calling tools, it just doesn't know when to stop. gemma4-12b next.

• 
  Dante Lex (@dantelex) reported 58 minutes ago

  My God! Is github down again?

• 
  MTS (@MTSlive) reported 59 minutes ago

  Handshake CEO @GarrettLord explains why AI agents exploded in software engineering but not the rest of white-collar work: "In software engineering, the average engineer is two, three, four times more productive. Software engineering agents are able to operate for multiple days at a time, automating hundreds of hours of work." "CEOs are not seeing that level of automation and ROI in other functions beyond software engineering. Software engineering is accelerated in such a massive way because everything was written down in GitHub. And it's extremely clear with what the right answer is." "When you have enough verifiable rewards and you scale up enough compute against verifiable rewards, you get what happened in software engineering, which is agents able to operate and do the job of humans." @Sbhaiwala03 @joinHandshake

• 
  Promptyx (@promptyx_ai) reported 59 minutes ago

  5 Tools for Building and Deploying AI Agents in Production This article walks through five tools, one for each layer of the stack from building the agent's logic to running all of it at scale. Building an agent that works in a notebook takes an afternoon. Getting that same agent to survive real traffic, recover from a crash at 3 am, and not leak someone else's data while it runs large language model (LLM)-generated code is a different job entirely, and it's the job most teams underestimate. Only a very small percentage of generative AI pilots actually reach production, and the gap usually isn't the model. It's the five layers underneath it that nobody thinks about until something breaks. This article walks through five tools that close that gap, one for each layer of the stack: building the agent's logic, executing the code it generates, giving it memory, watching what it does, and running all of it at scale. None of these competes with the others. They sit on top of one another, and most production agents you'll encounter in 2026 are running some combination of all five. This is First Tool. Others will follow-- # 1. LangGraph A basic agent loop is just a Python while loop calling an LLM. That works fine until the loop needs to branch, retry a failed tool call, pause for a human to approve something, or recover after the server it was running on restarts mid-task. At that point, you need something that treats agent state as a real, persisted thing rather than a variable that disappears the moment the process dies. LangGraph represents an agent as a directed graph instead of a flat chain. Nodes are functions, edges connect them with optional conditional routing, and the entire execution is tracked as a series of state transitions rather than a flat message list. Every transition gets checkpointed automatically, which is what makes pause-and-resume, time-travel debugging, and human-in-the-loop approval steps possible without you building that infrastructure yourself. Klarna, LinkedIn, Uber, and Replit all run agent workflows on LangGraph, and the framework has become common enough in production settings that its GitHub repository has passed 30,000 stars. The detail worth knowing before you adopt it: the default in-memory checkpointer is fine for development, but it only stores state in memory and loses everything when the process restarts, which is unacceptable for anything real. Most teams move to a Postgres-backed checkpointer the moment they go to production, and that one-line swap is usually the actual point where a LangGraph project starts behaving like infrastructure instead of a script.

• 
  Vishesh Baghel (@VisheshBaghell) reported 1 hour ago

  @dani_avila7 the second brain was always just a retrieval problem. this is retrieval that actually works. i keep my second brain in a simple flat repo on github

• 
  Robert (@Rrrrrobertanium) reported 1 hour ago

  This is the way. If you don't meter usage with people blowing up their weekly so fast they're going to be sitting idle wondering about continuing their work with a competitor... And then they leave your ecosystem. Again thank you for helping to introduce me to the Chinese models. I got qwen 3.8 now working and fixing 5.6 Sol outputs. Let's see how the changes go because right now I still burned 40% overnight with little to show for it. That and it really ****** up with GitHub. So many CI actions we're running and unnecessarily running from my sol chats got to shut it down because it was going to bill me $60 a day.

• 
  Joseph (@TrudoJo) reported 1 hour ago

  The lattice infiltration Ops are going to be simultaneously easier and harder than ever There is an abundance of information on GitHub fully fleshed out. The problem is there are several versions of everything and cross-linked dependencies that must be researched to avoid being compromised

• 
  playboi.eth (@adeolRxxxx) reported 1 hour ago

  @lj1nu Hmm this is another angle, why leave it unfixed for 200days. Also most times, prs are opened for these issues, you could check their GitHub to confirm before submitting

• 
  Austin Campbell (@austincampbell) reported 1 hour ago

  Almost every bank and blockchain protocol in the world is being used by scammers and bad actors because they don't understand the problem and refuse to do so. Yes. I meant what I said. This is a very good and thought provoking piece from @RebeccaRettig1 and it should be read by a lot of people in this space. Putting responsibilities where they are feasible matters. I'll raise one additional point: we shouldn't limit ourselves to blockchains here. Financial crime is multidisciplinary, multiplatform. If you are using blockchain forensics, you are being exploited. If you are using traditional bank KYC and software, you are being exploited. If you want to protect yourself, you need to span all of those, and social media, and darkweb data, and github repos, etc. The enemy just wants to win. They aren't drawing arbitrary boundaries. If you do so when defending, you are essentially creating the Maginot line while the hackers or scammers just go through Belgium. If you don't have a comprehensive multi-source multi-capability financial intelligence unit, you're getting exploited. Right now.