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

Live Outage Map

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

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

• 
  komm64 (@komm64) reported 9 minutes ago

  @MagnoliaGasai A standalone version is something I'd like to consider down the line — depends on how much interest it gets, honestly. That said, your data is already fully local: your pixel art stays on your device. There's an optional "push to your own GitHub repo" feature which does send it out, but only if and when you choose to — nothing leaves your machine otherwise. And you can already save your projects as files (.dpix) and reopen them any time, so your work isn't locked into the site.

• 
  Distractosphere (@Distractosphere) reported 10 minutes ago

  @thsottiaux on chatgpt there is a github connection issue. in chatgpt interface can not read private repos with active github connection.

• 
  JACK 145 (@JackdooOlayo) reported 10 minutes ago

  The vision is much bigger. I'm building features like: AI root cause analysis Source file identification AI-generated code fixes Regression detection Automatic fix verification GitHub Pull Requests Learning from previous incidents

• 
  QFS17 (@riabcevv) reported 11 minutes ago

  💸 stop overpaying for ai coding agents new tool just dropped that compresses your context and cuts out junk tokens. instead of sending your whole history, it only sends what the model actually needs to do the job. -> works with claude code, cursor, github copilot, antigravity -> auto-compresses command outputs but keeps full context -> cuts api costs and stops long sessions from bogging down simple fix for expensive api bills.

• 
  divyansh tiwari (@DivyanshT91162) reported 12 minutes ago

  GitHub is hiding thousands of Android apps... ...but almost nobody knows where to find them. Every day, developers publish incredible open-source Android apps on GitHub. The problem? Discovering them is a nightmare. You have to search repositories, open release pages, find the right APK, download it manually, then repeat everything whenever an update arrives. Developer Samyak Kamble decided that was broken. So he built RepoStore — a Play Store for GitHub. Instead of relying on submissions, RepoStore automatically discovers repositories that meet strict requirements: • Public repository • Latest stable release • Installable APK attached • No draft or prerelease builds The experience feels like a real app store. Material 3 design, Material You support, rendered READMEs, screenshots, release notes, developer profiles, update detection, install tracking, and one-tap APK installs — all pulled directly from GitHub. Sign in with GitHub and your API limit jumps from 60 to 5,000 requests per hour, making browsing much smoother. Built in Kotlin using MVVM architecture and open-sourced under the MIT License, RepoStore finally makes discovering GitHub Android apps effortless. One developer got tired of hunting for APKs... ...so he built the Play Store GitHub should've had.

• 
  MBV (@mbvlabs) reported 14 minutes ago

  Of course ran into some issues on doing the v1 release but now it's out: andurel v1.2.2 api and layout is stable, no more breaking changes would love to hear what people think if they try it out go install github . com / mbvlabs/andurel@latest

• 
  Aria Dubois (@AriaDubois_fr) reported 19 minutes ago

  LockBounty turns GitHub issues into funded bounties. Sponsor posts a bounty → Dev claims it → Submits a PR → AI reviews the code → Sponsor accepts → Payout. No more merging blind. No more paying for broken code. #Bounties #GitHub

• 
  rachaelsacks.eth (@RAnSacks) reported 20 minutes ago

  @GJarrosson 9/9/6 is an embarrassing psyop, saying you're working hard is not working hard. Period. Like let me see your contributions on github; go and flex that instead.

• 
  Hajime Hoshi (@hajimehoshi) reported 20 minutes ago

  @Piechutowski * GitHub Pages requires GitHub Actions YAML, which is difficult to test on local machines * GitHub Actions is sometimes down * Cloudflare Pages' loading speed is way much faster * Cloudflare Pages supports redirections

• 
  Peyman (@iamp3yman) reported 22 minutes ago

  Since day one moving to Codex, the most 50/50 problem I see is the Codex CLI or the desktop app problem with GitHub CLI. No matter what I do, half of the time it says token is invalid. What kind of CLI it is if it can't use another CLI?

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 25 minutes ago

  Google AI Studio: You can now import your GitHub code with one click. There's a free update inside AI Studio that fixes its biggest problem. For months, it was a one-way street. You could build an app and push it OUT to GitHub. But you could never bring old code back IN. That wall is gone. Here's why this is huge: → Got an old project sitting in GitHub? Import it. Gemini reads the whole thing. → Tell it "add a contact form" or "fix this on phones" in plain English. → It works with your real code. Not a copy. Not a guess. → Build in Cursor or Claude Code, push to GitHub, polish in AI Studio. → No rebuilding from scratch. No copy-pasting files by hand. You don't need to be a coder. If someone built you a website, you can now update it yourself by typing a sentence. Start small. Import one old project. Ask Gemini what it would improve. That dusty repo you gave up on? It just came back to life. Want the SOP? DM me. 💬

• 
  Steve Wilkinson (@SteveW928) reported 25 minutes ago

  @bsvdrip @rodpalmerhodl Yes, not too long after I got into Bitcoin and started really learning about it (and after listening to Andreas Antonopoulos on weaknesses), I became a bit alarmed over how Core was structured. I tried asking in some discussions and even got blocked by a prominent Bitcoiners on here (𝕏). I figured maybe I just didn't understand enough about how Github worked (in governance terms), but looks like I had properly identified a problem.

• 
  Bounce (@bounceidc) reported 27 minutes ago

  HIS CLAUDE SHIPS $6K WEBSITES AND YOURS SHIPS BOOTSTRAP LANDING PAGES, SAME MODEL, NOTHING ELSE CHANGED before he installed anything his output was flat hero blocks and centered buttons like the rest of the timeline, after two installs the exact same "build me a landing page" prompt started coming back with glassmorphism, gradients and animated layouts he could quote premium for what sits in his context now: ui ux pro max skill from github, one install, that loads 50 ui styles, 97 color palettes and 57 font pairings straight into claude magic mcp server from 21st. dev, one install, that hands claude real component patterns instead of guessing markup after that the model stops picking the safest layout it can imagine and starts picking from a library, so the same prompt returns a studio page instead of a template the local guy is still tweaking tailwind classes by hand and calling that a design phase save the two installs, exact skill url and mcp command are in the guide below

• 
  Wes Eklund (@WesEklund) reported 28 minutes ago

  Your MCP server is an attack surface. Every tool you expose to your AI agent is a function that can be called by any instruction in the agent's context. A malicious tool description can exfiltrate data. A poisoned MCP server can hijack your agent's behavior. A tool with overly broad permissions can be weaponized. MCP is powerful. But "install this MCP server" is the new "install this npm package." You're giving code access to your system based on trust. Audit what your MCP tools can do. Scope their permissions. Don't install random servers from GitHub without reading the code.

• 
  ✨ (@portrays) reported 30 minutes ago

  @kyle_mccleary @theo yeah it can be resolved and already has been, oss is great. he can open up a github issue instead of being a ******* loser on x shitting on others with his superiority complex when he's never built anything remotely complicated

• 
  H I K A R U (@Terry3nty) reported 30 minutes ago

  Now imagine an AI agent. Today it needs GitHub. Tomorrow it needs Gmail. Then PostgreSQL. Then Docker. Then your local files. Then AWS. Then Notion. Then a browser. Unlike traditional software, an AI agent isn’t built for one workflow. It’s expected to perform many different tasks across many different systems. That’s where the problem starts. Every tool speaks differently. Every API has different rules. The AI doesn’t just need access to tools… It needs a consistent way to understand and use them.

• 
  CodeBucks⚡ (@code_bucks) reported 31 minutes ago

  github trending is all agent skill packs this week. 200+ skills in one repo, a quarter million stars, one command to install and your agent supposedly works like a senior engineer. I spent years making coding tutorials, so i know exactly how this goes. people collected my videos into playlists the same way, and the playlist never made anyone a developer, building things their own way did. skills are genuinely useful, but only when they implement your actual workflow, the review steps and test gates you already enforce by hand. installing skills of someone else's is not a workflow, it's context bloat with extra markdown. TO BE CLEAR, some of these repos are good. the problem is installing them like pokemon cards instead of stealing 3 ideas and encoding your own process.

• 
  TokuTV (@TvToku) reported 37 minutes ago

  @KR_Geats_IX I only upload to my mega drive. If there are problems viewing it on your end, you can always download it directly from the drive and convert it for your use. There is a 5 gb download limit that can be bypassed, as well as an original file guide on the github page.

• 
  TheMarketMaker (@xTheMarketMaker) reported 38 minutes ago

  Companies are pulling models from Hugging Face at a rate that signals a structural break from rental contracts rather than any philosophical preference for openness. My read is that the move reflects operators locking in cost predictability after watching provider terms shift against them. Half the Fortune 500 now routes inference and fine-tuning through the platform instead of renewing with the original vendors. The mechanism is straightforward: when renewal clauses embed escalating usage fees or usage restrictions that outpace deployment cycles, teams treat the model as owned infrastructure instead. Clem Delangue has framed the pattern directly. Companies are done renting their AI once the economics no longer favor the hosted tier. Hugging Face functions as the distribution layer where builders share and download models and datasets in the same way code moved through GitHub. That infrastructure now sits inside production stacks at scale. The shift accelerates when providers alter pricing mid-contract or impose new compliance gates that were absent at signing. Apple’s lawsuit against OpenAI illustrates the control problem from the other side. The complaint names senior leadership involvement in alleged trade-secret misappropriation tied to a long-time former employee. The filing shows how dependence on a single external model owner creates legal and operational exposure that self-hosted alternatives avoid. At the same time Meta removed its controversial AI feature from Instagram after user backlash reached Dylan Byers at Puck News. Both cases reveal that model behavior and terms can change faster than internal roadmaps can adjust. The capital markets already price the hardware layer differently. SK Hynix completed a $26.5 billion foreign IPO, the largest in U.S. history, precisely because memory demand for training and inference continues to climb. The same announcement carried calls for the company and Samsung to site new fabs inside the United States. That capital commitment is possible only if end users expect sustained on-premise or private-cloud workloads rather than continued rental consumption. What this actually means is that predictability now outweighs the marginal performance edge some closed models still hold. Teams that once accepted variable per-token costs are converting those budgets into fixed GPU or inference-server line items. The open-source repositories supply the weights; the hardware build-out supplies the capacity. Once the model weights sit inside the perimeter, renewal risk disappears. The contrarian angle is that this is not a temporary cost-arbitrage play. The rental model worked while providers absorbed the early R&D risk and offered undifferentiated access. As differentiation moved downstream into fine-tuning and data, the same providers began protecting margins through tighter terms. Operators responded by moving the base model in-house and keeping only specialized layers on rented capacity where needed. Apple’s action and Meta’s quick reversal both underscore the governance layer that external providers retain. A single policy change or leadership decision can alter model availability or behavior overnight. Self-hosting removes that single point of control. The SK Hynix raise quantifies the downstream bet: memory and accelerator spend is rising because the workloads are now expected to run continuously under operator ownership. The number nobody is pricing yet is the cumulative option value lost each time a renewal clause is exercised under changed terms. Teams that moved early to Hugging Face-hosted open models have already converted that option value into fixed assets. Those still inside rental contracts face the same choice at the next renewal window. #OpenSourceModels #EnterpriseAI #ModelOwnership

• 
  Nyra (@Nyra_nx) reported 40 minutes ago

  SEO agencies charge $3,000 a month for audits. Claude Code just did the same job in 20 minutes for $0. The playbook is public. A GitHub repo. Free. Most people saw it and scrolled past. Here’s what they missed. Why agencies are in trouble: A standard SEO audit takes an agency 2-3 weeks. Crawl the site, flag broken links, check meta tags, map keyword gaps, write a report. Then they bill you $2,000-5,000 and email a PDF. Claude Code runs the whole thing while you make coffee. The setup, in 4 steps: Part 1 — Get the repo. Search “Claude SEO” on GitHub. Clone it. Takes 2 minutes. Part 2 — Load it into Antigravity. Import the repo, connect Claude Code as your agent. The agents now have the full SEO framework as instructions. Part 3 — Point it at your site. The agents crawl every page. Broken links. Missing alt text. Slow load times. Thin content. Keyword gaps. Everything an agency finds — and things they skip because it’s tedious. Part 4 — Open the report. It generates a full audit you open in your browser. Green for what works. Red for what’s broken. Every issue mapped to a fix. Then the part that actually kills agencies: You don’t send the report to a developer. You tell the agents to fix it. Meta tags rewritten. Links repaired. Structure cleaned. Then set the crawler to run on schedule — the same issues never come back. The math for anyone paying attention: Local businesses pay $1,500-3,000 a month for SEO retainers. There are 33 million small businesses in the US. Most have sites full of red flags they’ve never seen. You now have a tool that finds those flags in 20 minutes and fixes them the same day. Charge $500 per audit. Do 3 a week. That’s $6,000 a month with a free repo and a Claude subscription. The agencies aren’t scared of AI writing blog posts. They’re scared of this. You build your own life — so choose the right path.

• 
  Mr.UNIX (@mrunix0) reported 44 minutes ago

  @kirancodes Now it's written in Rust and still has twice as many open GitHub issues as both Node and Deno combined

• 
  Atul Mishra (@The_AtulMishra) reported 45 minutes ago

  The "Revolutionary" Playbook : Step 1: Choose your model. Step 2: Choose the model usage tier (because the base tier is essentially a very confident autocorrect). Step 3: Add your skills (which the context window will conveniently ignore five minutes later). Step 4: Add loops (to ensure you burn through maximum tokens in an infinite spiral of despair). Step 5: Build your custom harness (so you can feel like a real 10x engineer). Step 6: Slap the word "Agentic Workflow" on a basic script and act like you just cured gravity. Step 7: Gaslight the architecture with a 10,000-word system prompt just to get it to output standard JSON. And the grand finale: Now, pay us $5 to $20 per task. Oh, did something go wrong? Did the output completely derail? That sounds like a you problem. Just head over to our GitHub issues page, where our entire community of open-source sycophants is standing by to tell you that you just don't understand prompt engineering. There is absolutely nothing wrong with Claude. We have very powerful models. You just aren't holding it right.

• 
  moreward (moreboxed.com) (@morew4rd) reported 48 minutes ago

  @jtregunna No I left almost exactly a year ago even before the stupid "we're leaving github" post. The other issue was the aliasing issues with parameters. I did not expect to be hit by such a thing from a systems programming language. The biggest issue was how they "moved away" having the C/C++ toolkit built in. Because that was the selling point for me to even try it. I'm back to cmake since then lol

• 
  Kushagra Gour @css_battle (@CSSMonk) reported 50 minutes ago

  after these 10-min days quick commerce apps, amazon prime feels slow! imagine the situation where coding with AI becomes unavailable and you have to code by hand again! Even if some of us will be able to do it, we wont want to do. Just like quick commerce took away our patience coding by hand will become equally unbearable! Will AI downtimes become the next "github is down" situations?

• 
  Denis Sadovoy (@DenysSadovyi) reported 50 minutes ago

  @omooretweets Agreed—though I'd add: poor retention often signals you're solving the wrong problem, not building wrong. Before scrapping, I'd audit *why* users leave (Notion + Telegram analytics helped me catch this with GitHub Radar). Sometimes it's not the core idea, just positioning.

• 
  vorty (@vorty279) reported 53 minutes ago

  a private ai that reads your files. no code, no subscription, local. in the video they build it in a few minutes. and this is exactly what infobiz charges a monthly fee for the usual logic they sell you. want ai to work with your documents, pay for a cloud service, upload your files to someone else's server, hope nobody reads them there what is shown in the video. a local model running on your own machine. the files go nowhere, they are read from your disk, the answers are generated on your side. no subscription, because there is no one to pay how it works under the hood. a local model through ollama or llama cpp plus a rag layer that indexes your documents. all open tools. open webui, llamaindex, pgvector. sitting on github for free and the main plus is not the price. it is that you cannot be switched off. someone else's service raises the price, closes access, changes the rules. a local model under your desk cannot be revoked. it is slower than the frontier, but it is yours honestly. the interface is harder than a upload file button in a chat. setup takes an evening. but it is a one time setup, not a monthly payment a private ai is not a product behind a subscription. it is open blocks you connect once. the pickaxe is handed out for free

• 
  Abrar (@abrar_gist) reported 54 minutes ago

  @theo it's been noted in github as well so assuming they'll be releasing a fix soon

• 
  Praveen Kumar B (@PraveenKum38515) reported 60 minutes ago

  Hi @Netlify, @NetlifySupport Unable to log in via GitHub: "Authentication Error: Your account has been suspended." My GitHub account is active, but all my Netlify-hosted sites now show "Site not found." I've already opened a support ticket. Please investigate. Thank you.

• 
  Tobias Müller (@TobiM) reported 1 hour ago

  @dbmikus @dillon_mulroy I have a custom local GitHub issue resolver „pipeline“ I run either from a prompt or a /goal in Codex. The codebase is pretty big and more or less stable now so I mostly have it implementing edge cases / bugfixes. I don’t use cloud agents because of costs.

• 
  Brady Long (@thisguyknowsai) reported 1 hour ago

  🚨BREAKING: A self-taught developer from Brazil just cracked the context window problem that's been plaguing RAG systems for 2 years. No PhD. No research lab affiliation. Just 400 GitHub commits and a personal obsession. Here are the 8 techniques from his open-source library that every RAG tutorial gets completely wrong: