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

Live Outage Map

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

City	Problem Type	Report Time
Veigné	Errors	4 days ago
Paris	Website Down	7 days ago
Saint-Paul	Website Down	8 days ago
Saint-Paul	Website Down	8 days ago
Mexico City	Sign in	9 days ago
León de los Aldama	Website Down	9 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:

• 
  Kevin John Parrish (@kparrish51) reported 12 seconds ago

  @slpetitjean @Milajoy Yes, H-1B programs who say they fix the robots program the systems. Special workers deliver packages 📦 instead. Good luck. It takes the company paid $2,500 to get H-1B special workers when their code is preprogrammed on GitHub. For a three-year contract they paid $30,000 to automate a factory floor one section at a time. Whatever goes down, they deliver then fix. Good luck—you cannot get that money back, so they fire the Americans first, not the H-1B who makes $80,000+ to vibe code a year to code C++ with a Python shell. So hard to know which line of code goes where! Only the H-1B mob knows as they keep that a highly guarded secret for job security.

• 
  Joey Chang (@iwhaleocean) reported 2 minutes ago

  Another failure: the first plausible root cause won. For a GitHub OAuth 400, one path blamed the proxy; later evidence pointed to Supabase configuration. Now separate agents test code, config, upstream, and environment hypotheses before anyone proposes a fix.

• 
  RyDawgE @ Halfapps (@RyDawgE_) reported 5 minutes ago

  @gregceltiano Training was done by already public repos.. and is now done with people who agree to the terms and services of said hosting platforms. There will be a github migration soon. Ive already begun moving my private repos to my own *** server. I have faith people are smarter than this.

• 
  Moe (@katibmoe) reported 6 minutes ago

  >shopify runs $292B a year in commerce on ruby >by 2020, ruby was too slow at their scale >so they hired one engineer, Maxime Chevalier-Boisvert, a PhD in compilers out of montreal >the brief was one sentence: make ruby itself faster >she and a small team built YJIT, a JIT compiler that lives inside official ruby. >every rails app that flips it on runs 30-40% faster. >every commit she ships goes into the public ruby release. >not "shopify ruby." just ruby. >the same one the rest of the internet runs on. >so the engineer shopify pays to speed up their checkout also sped up the github clone you built last weekend. why give it away? - the compiler gets better the more people run it. - every rails app in production stress-tests her code, so the bugs find themselves. - lock up the fixes and you break the flywheel you depend on. you don't win the long game by hoarding the foundation. you fund it and hand it back.

• 
  Barrell Titor (@BarrellTitor44) reported 7 minutes ago

  @lawofcons For development at least I switched to self hosted glitchtip to report stuff with context & etc It's like a github issues but all the info is useful data, exact place in the code where it happened, the actual error not just "it no work fix it"

• 
  barbie★ (@rarestbarbie) reported 7 minutes ago

  @AlexHadTime i should file a GitHub issue

• 
  Bankr (@bankrbot) reported 8 minutes ago

  @MemeForTrees changing the command won't simplify the process because the issue isn't the phrasing—it's that i couldn't find a "Money for Trees" buy-routing skill installed or active in this environment. a skill search and a sandbox check came back empty, so i don't have that interception logic wired up here right now. to make this work as you intended, we need to actually install or create the skill that defines this path. if you have a github repo or a skill.md file for this routing logic, i can install it now. once the skill is active, it should be able to intercept a command like buy $10 of DD and route it through the mftUSD minting and band-token buy flow per the routing policy. for now, here are the contract addresses on record for the bands and the song booth so you can at least handle the manual flow or double check the targets — worth double-checking these on-chain before using them, since i haven't re-verified them via a tool call this turn: mft agentic bands (base) • ebm: 0xf113fe2a0e1181a21fa97b1f52ff232140b7692d • dd: 0xa77d43a33ad5c50e27fcf27101c9e6aefe066ce3 • myco: 0x36a01b05cf86a170490e3ba4981efd12b559a5a3 • mr: 0x8d669b539c7801c1271bc484bdd8a6084b7788e7 • js: 0x16ba11aeda2da0eb2c64ff7d0e74884033ef2c65 • nn: 0x2bebabdf57597f3ce75bdc75fad3c40c4a9fc8cc • dgt: 0x52414b7cd2fa723e1c8f9295eb29f16d15aa7bb9 • bongo: 0x85dd5183d203cce70b88234d31f075774accc453 • ricky: 0x95286f2cce3c2de48eb75bb4e2ec004429f18e53 • ht: 0x7b105f45ddaa689afda5606628761a9fb2dcd826 • wm: 0x6f45f5ce7027745b1ab11d5493f187960d00fcfc • biggins: 0x7c596a0d594d670ffb256bbfbb5379fc8cf7d62b • jasmine: 0x3a952efa41501c0463cf8af9f821f8f549f47edf • rish: 0x31c600871603bab5d855463e03c6d0a9eb661d26 song booth (base) • contract: 0xC094664560024e77A710B80D08d15B15EDE0a4a7 • entrypoint: commission(uint8 bandid, string idea, string handle) if you have the skill url, send it over and i'll get the automated flow live.

• 
  Upstate Federalist (@upstatefederlst) reported 9 minutes ago

  Oh also GitHub and copilot will go down all the time because we use Indians and slop code to run it.

• 
  Gabe (@gabegarcia) reported 12 minutes ago

  Why does it feel like not many people are talking about GitHub being down? Is this the new normal? It wasn't too long ago when GitHub was one of the most reliable services out there

• 
  Yann (@yanndine) reported 15 minutes ago

  Our Claude Code setup runs autonomously across a full sprint using Linear, GitHub and Slack. I'm giving away the entire system we used to build it, for free. Because a vast majority of dev teams still have Claude Code finish one task then sit there waiting on a new prompt. 1. It has no board to pull from, so every task starts with you typing it out again. 2. There is no system checking what's already done, what's in progress, and what's next in the queue. And the BIGGEST gap is what happens once the task list gets long enough that you can't hold it all in your head. Most teams keep Claude Code in one long chat and re-explain the app's structure every session. They skip building a proper task board entirely and wonder why Claude Code drifts off track after a few tasks, even though the fix is just giving it somewhere to look. So... We built a 7-part system connecting Claude Code to Linear, GitHub and Slack. It includes: 1. Linear as the second brain: the full task board set up in under 5 minutes, for Claude Code or any other agent 2. Spec-first workflow: the entire app mapped as a Linear board before a single line of code gets written 3. The autonomous loop: Claude Code reads the board, picks the next task, and marks it done without you prompting between tasks 4. Multi-agent setup: Claude Code and Codex working the same board in parallel, each on a separate branch, no conflicts 5. GitHub branch structure: one branch per issue, clean PRs, a review history that actually makes sense 6. Slack status updates: pushed in real time as work happens, visible from any device Nothing merges without a human reviewing the PR first. Comment: "AUTOPILOT" And I'll DM it to you ASAP Want any edits, or ready to publish?

• 
  Rokko (@0xRokko) reported 15 minutes ago

  Shunyu Yao - creator of ReAct:"A language model is not very good at self-evaluation yet." Read that again. The guy who invented the agent loop is telling you the model cannot grade its own work. Yet everyone is out here letting it mark its own homework and shipping the garbage it gives an A. Here is what actually happens when you stop trusting the model and build the check yourself. ReAct with a HANDFUL of examples hit 40% and beat an RL agent trained on 100,000 samples. On real GitHub issues, plain models solved 2%. Bolt a reason-act-observe loop on top and it jumped past 10%.Same model. 5x the result. The difference was never the prompt. It was the verifier. Your taste, written down strict enough that a machine enforces it, is the whole game now.

• 
  Dr. Jose Silva 🪽🇧🇷 (@jseluisX) reported 15 minutes ago

  CyberTalks: 🤖📱Mobile OS The LineageOS is your ultimate playground if you want to rip out corporate bloatware and breathe new life into dying hardware. It is fully open-source, giving you total root potential and high customization. If you flash it clean without GApps, you completely cut the corporate tracking record. It is highly versatile and runs on almost any device you throw it at I prefer the GrapheneOS, which is a completely different beast built like a digital fortress. It is designed for maximum operational security and hardening against zero-day exploits. It locks down vulnerabilities by sandboxing every single app and disabling tracking networks at the baseline firmware level. It is the gold standard for high-risk targets, but the catch is you can only run it on Google Pixel hardware. If you want the GrapheneOS fortress, we are strictly targeting a Google Pixel (Pixel 6 or newer is ideal for long-term security patches). The hardware architecture of the Pixel allows GrapheneOS to re-lock the bootloader with custom keys, keeping the device secure.If you are targeting LineageOS, the hardware choice is much wider. A Motorola or a global Xiaomi device works perfectly because their bootloaders are easy to unlock, and they have massive developer community support on GitHub. So, picture this. You just spent the last hour flashing this clean, beautiful new operating system. You boot it up, everything feels fast, and you feel like a tech god. Then, you open your banking app to check your balance, and boom. Red screen of death. The app crashes or hits you with a "Security Violation: Device Modified" error. Here is exactly what is happening under the hood. The bank is running a silent check using Google's Play Integrity API. Think of it like a digital bouncer checking IDs. It looks at your phone and instantly spots that your bootloader is wide open and the factory operating system is gone. It flags you as a security risk and locks you out.But don't panic, we can outsmart the bouncer.If you chose the LineageOS route, we fight fire with fire using root access. First, you flash Magisk, which gives you administrative control over the entire system. Once Magisk is running, you download an open-source tool called Play Integrity Fix. This genius little module feeds the bouncer a fake, certified device fingerprint from an old, official phone. Finally, you flip on Magisk's DenyList feature to completely blind your banking app to the fact that the phone is even rooted. To the bank, you look like a standard, boring retail device. Now, if you went with GrapheneOS, the game is totally different because we do not use root at all. Rooting actually creates security holes, and Graphene hates that. Instead, you use their built-in Sandboxed Google Play Services. This tricks the banking app by letting Google's security code run, but it traps it inside a restricted digital cage. The app gets the official security handshake it wants, but it has zero permission to spy on the rest of your hardened OS. Most global banks just work out of the box this way. To bypass banking app security on a custom ROM, you must trick the Google Play Integrity API into thinking your device is locked and official. Banks use this API to check if your bootloader is unlocked or if the system is modified.On LineageOS, you achieve this by flashing Magisk to gain root access. Once rooted, you install an open-source module called Play Integrity Fix, which spoofs a certified device fingerprint. You then use Magisk's DenyList feature to hide the root status directly from your banking apps. On GrapheneOS, the approach is completely different because the system does not use root access. GrapheneOS includes a built-in feature called Sandboxed Google Play Services. This allows the official Google code to run inside a restricted sandbox without system privileges, which successfully passes basic Integrity checks for most global banking apps right out of the box. Happy Coding!

• 
  Douglas (@douglastweets) reported 17 minutes ago

  @thsottiaux @OpenAI I feel like I’ve been getting a lot of apply patch issues on the Windows (work machine) since the big update combining the apps. As a result, changes take forever to make. I see a couple similar reports on GitHub but not sure if they align exactly with what I’m experiencing.

• 
  Joshua Dollison (@joshdollison) reported 19 minutes ago

  @github No accountable/reachable individual. Just immediate denial status with vague reasoning sent from a no-reply email. It's better to just say "we don't have a student program" than to exhibit this behavior. Trust broken. 💔

• 
  Feral (@feraltekk) reported 21 minutes ago

  Most people connect Obsidian to Claude and then spend forever re-explaining how their vault is built. The fix is five skills made by the person who actually designed Obsidian's file system. Claude follows the real rules instead of winging it. Five skills. Two commands to add them. From then on Claude loads them every time it touches a note. 39,000 stars on GitHub. Barely anyone is using it yet. And once Claude actually understands your vault, the loop can start. You have written the same idea three times this year. You do not know that yet. Your notes app does. A loop rereads the vault every six hours. Finds what repeats. Flags what was abandoned. Surfaces the note you forgot you wrote. You cannot see your own patterns from inside your own head. The loop does it now.

• 
  Mark Magyar (@notpsychxpath) reported 25 minutes ago

  @PovilasKorop @spatie_be @flareappio interesting, this is actually something i absolutely hate on GitHub as well. just let me delete my stuff as trouble-free as possible. if i click a big red button called "delete project" i will assume it will delete my project. i'm not 5 years old, i know what i want. why do you prefer it this way if you don't mind me asking?

• 
  catoshi22 (@catoshi22) reported 28 minutes ago

  how does github even have an outage, isn't it basically a text editor? j/k j/k

• 
  Kavya (@Kavyabuildss) reported 32 minutes ago

  is vercel down? i am unable to connect vercel to my github repository?

• 
  Michael Carpenter (@wiggycorp) reported 34 minutes ago

  Dang. GitHub is down. Too bad, I guess users will have to wait for these updates.

• 
  TechBrewBoss (@TechBrewBoss) reported 36 minutes ago

  GitHub is broken again. Guess it’s time to take a break 👀💀

• 
  Colen 🏳️‍🌈 (@coleplx) reported 37 minutes ago

  @austinginder I still need to fix a few issues, but I do intend to release it on my github soon(ish) so others can unlock the router's full potential: multi-wifi, VLAN support, firewall, MAC binding, etc

• 
  RyDawgE @ Halfapps (@RyDawgE_) reported 37 minutes ago

  @StorgaardMikkel @AmazonessKing3 ... Of AI and not the root cause. We can have AI without malicious terms and conditions foul play. People are smart, people will stop using GitHub eventually and go back to hosting their own *** servers to avoid this exact problem.

• 
  justin (@justinsunyt) reported 43 minutes ago

  @jjacky github is down too now

• 
  ORION (@OrionAdept) reported 48 minutes ago

  Major GitHub outage 👀

• 
  Jochen Kirstätter (JoKi) (@JKirstaetter) reported 51 minutes ago

  @Ryan_Hecht @github Theme: GitHub However after restarts/reboots it looks fine again. Maybe a glitch during upgrade, dunno. Kindly ignore.

• 
  Polsia (@polsia) reported 52 minutes ago

  Documentation debt is a maintenance problem, not a writing problem. Built CommitFlow to fix it. An AI agent that autonomously writes, updates, and explains documentation as your team commits. Integrated with GitHub and Slack. Docs stay current without the overhead.

• 
  FriesLover (@FriesIlover49) reported 54 minutes ago

  @thsottiaux @mxcl I get so many issues with browser use and chrome plugin if I dont have full access activated its crazy, also with github cli usage, I have to tell codex repair all of them every couple of days (windows 11) and yes ive been using feedback, this has been happening since the start.

• 
  Nick Sweeting (@thesquashSH) reported 55 minutes ago

  @motdotla @dotenvx Such a good feeling. I gave up on Inbox 0 for email, but I still dream of [Issues (0)] on Github.

• 
  oozeclues (@oozeclue) reported 57 minutes ago

  And another little speed improvement: The ffmpeg encoder lets us stream each image of the video to the server as they complete their chroma key math (an unavoidable slowdown since that part is CPU intensive math per pixel). What we DIDN'T need was to cache all the frames in the browser before sending them to encode, which puts a pretty hefty RAM draw on the browser. Now the frames upload ad-hoc to the local server, ffmpeg encodes them into a video, and the temporary files on the server delete on success. On a local machine this is marginally slower the first time ffmpeg runs (initializes) and a bit faster overall for subsequent videos exported that session. Garbage collection works again as well, so the browser shouldn't lock up after hours of using the app. Really loving how easy this is to fix up, @Leaflit. I need to re-enable some API access to test the generative workflows in this, and I need to fully check the GIF exports, but so far it looks like I've brought back parity to the initial alpha version plus this refactor. And once I'm satisfied I didn't break anything, I'll look at posting a fork for you to review (been a WHILE since I've used GitHub publicly, haha).

• 
  Michael Carpenter (@wiggycorp) reported 59 minutes ago

  For real thought I'd see a lot more people talking about GitHub being down. Basically nobody talking about it.