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

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	14 days ago
Tlalpan	Sign in	19 days ago
Quilmes	Website Down	19 days ago
Bengaluru	Website Down	22 days ago
Yokohama	Sign in	22 days ago
Gustavo Adolfo Madero	Website Down	26 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:

• 
  TelepathicPug (@TelepathicPug) reported 26 seconds ago

  @50onice I can see some people leveraging it for routine ad copy and posting, but I can also see platforms banning people for this (normal folk aren't used to having their presence shut down). We're sort of seeing it already with the top 1%ers on social media and even places like github but when everyone is doing it... I don't know. Can YouTube swallow petabytes of AI slop? Can Facebook groups handle 20 socks posting about the same drop shipping service? Can local ISPs handle the loads? All super interesting questions. We're either speed running dead internet theory or making people more aware of the limitations and norms around usage. Also security but that that won't be a priority until the hype train settles. Definitely a fun time to be online.

• 
  Jeff Sosville (@JeffSosville) reported 2 minutes ago

  @mhp_guy @nathan_covey What about all the 2 factor Bs? Banking? GitHub? All the rest, how to get around that? My father in law was forced into a smartphone simply because of banking issues

• 
  Jongwon Park (@JongwonPar9958) reported 4 minutes ago

  2/ The full loop across those 1,874: 949 fixed (merged-PR), 149 fixing (open PR), 348 still open (open issue without PR), 425 closed with no merge. Most reported defects do get closed — but a real chunk is still open or in flight. "closed" on GitHub ≠ fixed. A health badge has to track merge evidence, not issue state.

• 
  Yusuf Nuh 🍉 (@SenseWave_) reported 5 minutes ago

  @ZackKorman @NinjaParanoid It's sick. Just days ago we see they're saving are passwords as plain text. And now threatening researchers for their research. They even took down one GitHub account, that published vuln

• 
  Davlatjon Sh (@dalisoft) reported 6 minutes ago

  @morganlinton @FactoryAI 2. GitHub issues are like stale and never gets enough attention. Need dedicated person to fix that (@FactoryAI i could be this person)

• 
  Mohit (@codewith55) reported 8 minutes ago

  Total monthly cost to run a startup: $20 - Claude = coding ($20/mo)💲 - Supabase = backend (Free)✅ - Vercel = deploying (Free)✅ - Namecheap = domain ($12/yr)💲 - Stripe = payments.(2.9%/transaction)💲 - GitHub = version control (Free)✅ - Resend = emails (Free)✅ - Clerk = auth (Free)✅ - Cloudflare = DNS (Free)✅ - PostHog = analytics (Free)✅ - Sentry = error tracking (Free)✅ - Upstash = Redis (Free)✅ - Pinecone = vector DB (Free)✅ There has never been a cheaper time to build

• 
  Wick filler (@ifillwicks) reported 8 minutes ago

  @Federico_Crypto If we can opt for a fees based system where every token that launches has to buy and burn some $STICK This structure could be changed down the line for sure % wise. Also might be worth looking at tokenising the GitHub or at least some functions and people will steal this data

• 
  kiki (@kxwxn13) reported 10 minutes ago

  I’m starting a small research project: Where do users actually get stuck in crypto wallet onboarding? I’ll be studying public complaints from Reddit, GitHub, X, and support forums. Early pattern: Mobile wallet failures are often not “user error.” Sometimes the wallet opens, but: - no approval prompt appears - no session is restored - the user is not returned to the dApp - the app cannot explain what failed That feels less like a connect button problem and more like a product observability problem.

• 
  Emile (@eledure) reported 10 minutes ago

  github down? @github

• 
  parag.dev (@ParagRangankar) reported 12 minutes ago

  Just wired up real-world OAuth in my app ✅ Frontend kicks off `/auth/google` or `/auth/github`, Passport handles the provider flow, backend issues JWT, then redirects to `/oauth-callback` to store token + fetch user. Feels clean and production‑ready. #webdev #oauth #nextjs

• 
  Zodl (fka Zashi) (@zodl_app) reported 16 minutes ago

  Attention users: Zodl v3.5.1 is now available on the App Store for iOS and on GitHub for Android. Google Play is currently reviewing the update and should release it shortly. With the Zcash network upgrade complete, updated wallet software is required to spend Orchard funds under the new consensus rules. After updating, Zodl will work as expected for sending and receiving ZEC via Orchard. As infrastructure comes back online, you may experience occasional delays. If so, run a Server Test and select the best-performing server under: Advanced Settings → Choose a Server Please note that any Orchard transactions attempted during the network upgrade window were not mined. If you are unsure about the status of a transaction, verify the TXID on the blockchain or contact @zodl_support.

• 
  Phil (@philaraujoPM) reported 23 minutes ago

  2/5 - Most of it was fine. My code is in GitHub. My vault came back. All my repos cloned down clean. And the CLAUDE.md files came with them, because those live inside each repo.

• 
  June Kim (@kimjune01) reported 26 minutes ago

  @bettercallsalva @theo you can most certainly rule out held-out set as soon as the problems become publicly available on github

• 
  Max 🌊📱 (@iamMXFSCHR) reported 30 minutes ago

  set up a raspberry pi 5 with batocera for retro gaming. cheap aliexpress N64 clone controller. A button triggers Back instead of Confirm. GUI re-mapping wouldn't take it. analog stick threw 'already mapped' because the D-Pad and the stick share the same physical axis on this clone. ended up reading the RetroArch source and an old github thread. fix was one line in batocera.conf: mupen64plus-alt-map=1 switches the keymap scheme for third-party controllers. exists specifically because cheap clones don't match the reference layout. an afternoon of source-reading for one config line. embedded linux is undefeated.

• 
  Emin (@eictn) reported 31 minutes ago

  @brunoborges What's really bad is that there is no more room for trial and error and experimentation anymore (7k tokens dry up in hours), unless we switch from github copilot to other providers, to those who don't switch to token-based billing, which makes the transition way more abrupt.

• 
  Jimmy Koppel (@jimmykoppel) reported 33 minutes ago

  @JongwonPar9958 I see. So your result basically counts Github issues over the lifespan of the project?

• 
  Tomasz Dłuski (@TomaszDluski) reported 36 minutes ago

  just spent a whole day trying to find an AI provider that would replace the broken GitHub Copilot subscription that would cost me a few thousand dollars a month from now on with the new pricing update

• 
  Jay-F. 😎 (@only1jayf) reported 41 minutes ago

  You have 6 agents. One for code review. One for deployments. One for writing docs. One for Jira. One for PR generation. One for standup summaries. You built a different agent for every domain. Wrong move. The teams still building a new agent for every problem are rebuilding the same scaffolding over and over while the winning teams write a skill once and every agent uses it. you don’t need a gazillion agents. You need one super agent with a library of skills and a shadow clone technique it loads on demand. A SKILL.md file. Name. Description. Instructions. Done. 57,000 repos on GitHub. 250,000 stars in 10 weeks. didn’t exist 6 months ago. That’s what you need. The agent loads only what it needs, when it needs it. Like a surgeon who doesn’t carry every instrument into every room. You’re not short on agents. You’re short on reusable process.

• 
  Raphael Mansuy 🍵 (@raphaelmansuy) reported 44 minutes ago

  @m_sturdevant @Copilot The root cause of the problem is structural: Anthropic does not belong to Microsoft, and routing Copilot through Claude models is simply too expensive to sustain at scale. This is what is forcing GitHub into the token-based billing model that is now driving users away — they are passing the cost of an external dependency directly onto their customers, and the math does not work for either side. The solution is clear, and the path has already been proven by a competitor. GitHub should adopt a high-performance Chinese open-weight model — such as Kimi 2.6, which is already on par with Anthropic's offerings — and fine-tune it specifically for coding tasks. This is exactly the strategy Cursor executed with Composer 2.5, and the results speak for themselves: Better than Claude Opus for coding tasks Significantly faster Reliable, with no perceptible quality difference compared to Claude Opus Drastically lower inference cost, which makes flat-rate unlimited pricing economically viable By owning the model layer — instead of renting it from Anthropic — GitHub would regain control of its margins, eliminate the need to meter users into paralysis, and restore the flat-rate, predictable licensing that made Copilot successful in the first place. This is not a theoretical solution. Cursor has already proven it works. The longer GitHub waits to follow the same path, the more market share Copilot will lose to competitors who have already solved the cost problem at the model layer.

• 
  Troyski (@MrTroy_) reported 46 minutes ago

  @kalidasrjv @GeoDanila It's designed to not work and get everyone to unsubscribe. It was a money loser for them. Fine. But don't shut it down this way and treat your customers like trash. Github is the enemy of the people.

• 
  wh (@nrehiew_) reported 47 minutes ago

  They next share some detail on their env creation pipeline. Total they have 94044 unique repositories 1) Start with github issues and PRs 2) An LLM agent creates the images from selected PRs 3) Validate by running the test suite and only keeping problems where the test suite fails initially and passes after the patch is applied 4) Filter non determinstic environments (random hardware limits or network timeouts etc) 5) Another agent rewrites the problem statement The filtered ones are used to create synthetic problems. To prevent reward hacking, they limit internet search, local *** history search and test changes

• 
  Amit Kulkarni (@amitkulkarni863) reported 48 minutes ago

  shadcn just got a very interesting update, and I don't think most developers understand the size of it yet. With GitHub registries, any public GitHub repository can now work like a shadcn registry. You do not need to publish a package. You do not need to run a registry server. You do not need to generate and host separate JSON files. You add a valid registry.json file to a public repo, define your registry items, and someone can install them directly with: npx shadcn@latest add username/repo/item-name A GitHub repo can now distribute files directly into another project through the shadcn CLI. And the files do not have to be UI files. You can share: TS files TSX files CSS files utility functions project conventions config files design system pieces starter feature kits agent workflows Claude skills rules files internal project templates This changes shadcn from "a component installer" into something much broader. It becomes a clean way to share reusable project patterns. Imagine keeping your own public toolkit repo with: your preferred eslint rules your agent workflow files your project conventions your auth helper your dashboard layout your AI coding rules your reusable utilities Then every new project can pull the exact files you want with one command. No copy-pasting from old repos. No hunting through folders. No "where did I put that file again?" And for open source creators, this is even more interesting. You can now publish small, focused registries for real developer workflows: a Next.js SaaS starter registry a design system registry an AI agents workflow registry a Tailwind pattern registry a project conventions registry a backend utilities registry a team onboarding registry The best part is that it still feels very simple. For developers who already reuse the same patterns across projects, this is going to save a lot of boring setup time. For creators, it opens a new way to distribute useful code without turning everything into an npm package.

• 
  Collegen Bob (@collegenbob) reported 48 minutes ago

  @giteaio @Malix_Labs @codeberg_org I'm building my own *** hosting because GitHub is a broken piece of ****. I can't imagine having your own and choosing to continue with MS for anything critical

• 
  Sam Thapa (@SThapa123456) reported 48 minutes ago

  i told claude to fix a github issue without reading the issue myself. it opened a pr. looked clean. now i'm sitting here trying to do three things at once. understand what the issue actually is. understand what the pr actually does. steer the architecture if it went the wrong way. all in the same head. in the same moment. with a slack notification from my ceo pending. something i'm realizing as i do more agentic engineering: skipping the plan doesn't save effort. it just defers all of it to the worst possible moment. @theo and @steipete aren't big fans of the talk-talk-plan-execute flow. the argument is roughly that modern agents are capable enough that the ceremony slows you down more than it helps. just let it cook. i get it. but what i'm finding for myself is that plan-first isn't ceremony, it's a cost-spreading strategy. you pay the "understand the issue" cost when it's cheap, before anything is built. you pay the "shape the solution" cost at the plan stage, when changes are one sentence instead of a re-implementation. by the time the pr exists, the model is already in your head and reviewing it is just verification. skip those stages and the cost doesn't disappear. it stacks up and lands on you all at once, after the code exists, when every decision is now expensive to change. the polished pr is the trap. it looks like progress. it's actually a bill coming due. want it shorter, or is this length working for the thread you have in mind? (credits to claude for articulating this for me)

• 
  Lummox (@Lummox_eth) reported 49 minutes ago

  PEOPLE INSTALL 30 PLUGINS, BUILD 15 FOLDERS, AND NEVER OPEN OBSIDIAN AGAIN AFTER DAY 1. They build a system for an imaginary version of themselves. If capturing a thought takes more than 10 seconds, it does not happen. The fix is 4 folders only. Inbox for everything unprocessed. 5 plugins worth installing : > Templater for consistent formatting > Dataview to query notes like a database > Calendar for daily note navigation > QuickAdd to capture from anywhere > Obsidian *** for automatic backups to GitHub. The weekly review is where the system compounds. 20 minutes every Sunday. Process inbox, open 3 random notes and ask what they connect to, plan next week. That single habit turns a vault from an archive into a thinking partner.

• 
  George Danila (@GeoDanila) reported 51 minutes ago

  Just cancelled my GitHub Copilot subscription. They clearly wanted to shut it down with the new pricing model.

• 
  Piselli Moves (@piselliii) reported 54 minutes ago

  the hardest thing for any project isn't surviving a crisis. it's letting go of the story you used to tell about yourself and accepting reality as it is. most projects take the survival route after a major hit: another announcement. another partnership. another GitHub commit. Movement and its team could have done the same. instead, they seem to be making a very different bet — on payments, distribution, and emerging markets. will it work? I hope so. but adaptation has always been more interesting than a slow decline.

• 
  tc (@tekyesilolsun) reported 54 minutes ago

  @argofowl My Link to my GitHub repos disappeared in the cloud so now I don’t know how to transfer my files … seems they really have some issues

• 
  🇱🇧 pickwick 🇱🇧 (@pickwickpick) reported 58 minutes ago

  @TermsAccepted @edzitron AI coding is only useful while it's being subsidised, if you were having to pay the genuine cost of its use it wouldn't be quite so useful. Just look at how the GitHub copilot pricing changes are going down

• 
  Marc Pacheco García (@marcpachecog) reported 60 minutes ago

  @github @Microsoft "Go from issue to broke" may be a more accurate description