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 (59%)
• Errors (32%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Colima	Website Down	1 day ago
Poblete	Website Down	2 days ago
Ronda	Website Down	2 days ago
Montataire	Errors	3 days ago
Montataire	Website Down	3 days ago
Tortosa	Website Down	6 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:

• 
  Alex 💪 (@awpthorp) reported 1 minute ago

  @webjuice_ie Yep been saying this for a while now. It’s an absolute dream to have the websites off Wordpress and some just plain html css js. GSC spotted an issue? Ask agent to check, push via GitHub. Audit trail. The same thing might have required a code injection via a plugin or an SEO app. No audit trail. Honestly I have no idea how Wordpress stayed so long it feels absolutely ancient to me now. Right now it has a benefit of “non tech” people wanting to upload content upload blogs etc. that’s it. Everything else is pointless.

• 
  Artur Schaback (@skyzer4ever) reported 2 minutes ago

  @TuahaJawaid @steipete @sama All their open GitHub issues and pull requests

• 
  👁‍🗨🔺Eyemaginative🔻👁‍🗨 (@eyemaginative) reported 3 minutes ago

  Swaps are now working. Just have to wire to fetch the swaps to the orders table and fetch tx data to db / update github to close this issue.

• 
  Manish Kukreja (@IamRealManish) reported 5 minutes ago

  @peer_rich Correct. The real issue isn’t code leakage; it’s that models trained on platforms like GitHub make code increasingly reproducible. Security and advantage both get weaker.

• 
  jan (@ironcarbs) reported 11 minutes ago

  @tonilopezmr you may have an app (Rize) that is using github regularly to store data. I recall this was an issue a few months ago. I’m unsure if it has been resolved.

• 
  Fahim (@echo247365) reported 12 minutes ago

  You can run Claude Code for free. No subscription. No API limits burning a hole in your wallet. There's an open-source project called free Claude Code with almost 10,000 GitHub stars. It acts as a local proxy on your machine. Claude Code thinks it's talking to Anthropic. The proxy quietly reroutes all traffic to a free provider instead. You run a lightweight server on port 8082. Set two environment variables. That's it. The most popular provider is NVIDIA NIM. Free tier gives you 40 requests per minute. No credit card required. No expiry date. You map Claude Code's three model tiers (Opus, Sonnet, Haiku) to open-source models like Kimiko 2 or GLM 4.7. Basic code generation and single-file edits work great. Complex multi-file refactors might struggle. But you get the full Claude Code interface. Terminal, VS Code, web, even Slack. All free. The setup takes under 20 minutes. What's the one AI tool you'd use more if the cost barrier disappeared?

• 
  beeman 🐝 (@beeman_nl) reported 16 minutes ago

  GitHub in 2005: "Let's use this rock-solid MySQL for metadata 🔥" 
GitHub in 2026: every other outage post -> "database cluster said no, moving data elsewhere ☠"

• 
  Skylar Bruton (@ConstitutionVio) reported 23 minutes ago

  @AP considering the serious of the nature Sylvia along with Microsoft and GitHub the ones responsible should be placed on a no bail status and you will see how thugs slow down tremendously or stop that they are doing far as the extortion and extra charges and money not refunded

• 
  gary IH fung (@garyfung) reported 30 minutes ago

  @Teknium That takes care of GitHub issues Replace GitHub next? 🙏🏼

• 
  CDCapital.hl (@CDCapitalHL) reported 34 minutes ago

  BREAKING NEWS 🚨🚨🚨 Hyperliquid GitHub docs are down , rug incoming !!!!

• 
  Aeyric (@amsryq) reported 35 minutes ago

  @Malay4Product @SantoshYadavDev that's not the whole github issue lmao

• 
  kron (@0xkron) reported 36 minutes ago

  Running everything as code on GitHub has always been better than anything else, even before LLMs. The problem was normal/non-programing people can never understand how to work with it. LLMs don't change this. So I'm really excited to see how this trend turns out.

• 
  Sam Huckaby (@samhuckaby) reported 37 minutes ago

  @elijahmcom You’ll always just have people ask “if this is just the same as GitHub, why would I not use GitHub?”. No matter how bad or unreliable GitHub becomes, it will always be “the GitHub” that people default to. I think in order to fix it, we need a complete shift of what people want in terms of functionality

• 
  Alpha Batcher (@alphabatcher) reported 39 minutes ago

  > opened GitHub > expected prompt slop > found product-marketing-context.md > realized every skill reads it first > CRO does not start with button color > copywriting does not start with clever headlines > pricing does not start with competitor averages > A/B testing does not start with vibes > AI SEO does not start with “rank higher” > programmatic SEO does not start with 10,000 thin pages it starts with context: > who buys > why they care > what they tried before > what made them look for alternatives > what scares them about switching > what exact words they use when frustrated then the agent can actually work CRO becomes: > is the page clear in 5 seconds > is there one CTA > is proof near the ask > are objections handled before they block conversion copy becomes: not “save time”, but “cut weekly reporting from 4 hours to 15 minutes” A/B testing becomes: > Because [data], > we believe [change] > will move [metric] > for [audience] > without breaking [guardrail] pSEO becomes: 100 useful pages beats 10,000 thin ones AI SEO becomes: make the page extractable enough for buying agents to cite it the cool part is the install is free npx skills add coreyhaines31/marketingskills the repo is free the cost is admitting your agent cannot fix marketing it does not understand build the product context first, then run the tactics

• 
  Doug Dimmadome (@tallhatdoug) reported 39 minutes ago

  @Una @github congratulations on fixing a non-existent problem instead of a real one

• 
  The_Daniel (@dan_mwita8) reported 39 minutes ago

  @fidexcode You still transfer properly , just don't hand them the keys and walk away. The move is to create the GitHub account for them, set it up, and transfer everything into it before the project closes. They don't need to understand *** to own a repo. They just need to own it so that when they hire the next developer, that developer has everything they need to pick up where you left off. Think of it like transferring a property deed. The homeowner doesn't need to understand construction to legally own the building. What you actually hand the non-technical client: 1. A simple document with all their login credentials 2. Clear labels for what each thing is ("this is where your website files live", "this is where your domain is registered") 3. A one-paragraph explanation of what to give the next developer 4. Your contact if something breaks in the first 30 days The goal isn't to make them technical. It's to make sure they're never held hostage by a developer who kept the repo.

• 
  eric (@ericlim) reported 40 minutes ago

  @domirosari0 @duolingo please fix github

• 
  planefag (@planefag) reported 42 minutes ago

  THIS. And, you know what? Valid. Same for people who google around for a solution to a niche problem and it leads them to a github page. Because, that's what niche solutions are for - people with niche problems! I'm just asking for a minor UX improvement, you psychopaths

• 
  Kevin Cho (@chokevinjs) reported 43 minutes ago

  I hammered github today with slop. Maybe it wasn't slop but either way it was a ton of code tossed into their servers. No wonder they are having scalability issues

• 
  Akshat Gupta (@Akshat_Gup) reported 49 minutes ago

  Github is fundamentally broken. It’s gotten harder than ever to review vibecoded PRs. Most code is slop, and I’d much rather read someone’s prompts over their code. So I built codebook, the *** for prompts. - Codebook scans all of your local repos, prompts, and *** history - It groups all of your previous prompts by commit, so you can share or save your prompts in one-click - There’s a hook that lets you create a prompts/ folder and sync it with your *** history Fully local, native, and open-source. (1/n)

• 
  Edison (@CodeEdison) reported 49 minutes ago

  GitHub — version control (free) Claude — coding ($20/mo) Namecheap — domain ($12/yr) Cloudflare — DNS (free) Vercel — deploy (free) Clerk — auth (free) Supabase — backend + database (free) Upstash — Redis (free) Pinecone — vector DB (free) Resend — emails (free) Stripe — payments (2.9% per transaction) PostHog — analytics (free) Sentry — error tracking (free) Total cost to run a startup: ~$20/month No servers. No DevOps team. No funding required. Just an idea and WiFi. There has never been a cheaper time to build. 🚀 Today is the best time to bet on yourself and build the things ⭐

• 
  yata (@whoyatagarasu) reported 50 minutes ago

  > i committed .env to a public repo in my second month of coding. > didn't notice for 6 weeks. > the key was rotated by the provider automatically. got lucky. >most people don't. > 29 million secrets leaked on GitHub last year. 64% of credentials from 2022 are still valid today. not because hackers are good. because developers never revoke what they leak. > your .gitignore is probably a template you copied on day one and forgot about. > it was written before .claude/ existed. before .cursor/ existed. before AI tools started storing your API tokens in config files you don't even think about. > one line in an ignore file. that's the difference between a normal tuesday and explaining to your team why production is down. full breakdown of what actually needs to be in it 👇

• 
  Manish Kumar (@Manixh02) reported 51 minutes ago

  @ahmad_dev49 Prompt: Create a GitHub design of "India taking down Pakistan" theme

• 
  Unfrosted Poptart (@unfrostedpoptrt) reported 51 minutes ago

  @kdaigle @sudobunni @github Thanks Kyle. With respect, the "we're scaling" excuse is falling a bit flat. At what point are we going to square with the real issue here, the fact that relying so heavily on AI for development just isn't working out?

• 
  Maor Ai (@Maor_Elkarat) reported 54 minutes ago

  In 2015, the Chinese police visited a programmer's home. They told him to stop working on his code. They told him to delete it from GitHub. He posted one final message before he obeyed: "Two days ago the police came to me and wanted me to stop working on this. Today they asked me to delete all the code from GitHub. I have no choice but to obey. I hope one day I'll live in a country where I have freedom to write any code I like without fearing." Then he deleted the repo. Then he deleted the message. Then something happened the Chinese government did not plan for. Within hours, the code was mirrored to thousands of other GitHub accounts. Within days, it became the #1 trending repository on GitHub globally. Within weeks, every Chinese developer who could compile code had a copy. The government tried to make it disappear. The act of trying made it permanent. The project is called Shadowsocks. The programmer's username was clowwindy. He built a tiny piece of software that let anyone in China bypass the Great Firewall and reach the open internet. No subscription. No company. No account. You set up a server somewhere outside China. You connect to it. Your traffic looks like normal encrypted web browsing, so the firewall cannot tell you are using it. Why this terrified the Chinese government in 2015: → It was open source. Anyone could compile it. → It was small. The whole protocol fit in a few hundred lines of code. → It looked like normal HTTPS traffic. The Great Firewall could not distinguish it. → It required no money. No accounts. No central server to seize. → It worked on every operating system. You cannot arrest a protocol. You can only arrest the person who wrote it. So they did. And the protocol kept spreading. shadowsocks-windows: 59,300+ stars. GPLv3. Still online 11 years later. The 2015 commits the Chinese government wanted deleted are still in the history. clowwindy was forced to walk away. The code never did. But DO NOT install it. The Great Firewall has feelings too. 100% Open Source. (Link in the comments) Must Follow For More updates.

• 
  George Saoulidis (@georgecursor) reported 55 minutes ago

  It's so annoying that devs think I'm one of them. No I'm not a nerd. Yes I have a GitHub. And a server. And local models running on my machine. And a bitcoin node. Why do you ask?

• 
  Scott Martinis (@scottmartinis) reported 56 minutes ago

  @morganlinton pretty much every gtm process can be reduced to code plans > github projects milestones issues software setup > yamls resembling terraform setup playbooks > skill files workflows > deployed skill orchestration regular reporting > trace logs how agent artifacts are prompted by humans, deployed, and produce pipeline outcomes verified by predefined operating model sql slices that point to a data lake

• 
  Binit Ranjan Das🇮🇳 (@imbinit17) reported 59 minutes ago

  Note : The above URL is where users access GitHub codespaces. VI 4G connection shows a download speed of barely 20 Mbps on the Ookla Speedtest site. Kindly fix this issue at earliest @reliancejio

• 
  Datastar Cult Leader (@DelaneyGillilan) reported 59 minutes ago

  @thomasglopes @code_department @github This isn't what the original ask was. Now you are showing your cards, you are complecting logic with display. If you don't see the difference then not much to talk about. Your components should be webcomponents, this has nothing to do with the root issue

• 
  Leo - mrlemoos.dev (@mrlemoos) reported 60 minutes ago

  @AnthonyPoschen @thdxr The central point of my argument is that moving away from GitHub is not enough to escalate the change for GitHub to become something more FOSS-focused/developer-first (unless Microsoft itself actively helps them do so). Atlassian never really changed their infra or UX, and people still use Jira and Confluence despite their archaic apps. In large companies, if the problem is performance (as the recent GitHub issues hinted at & seemed to be), they default to vertical scale.