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

Live Outage Map

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

City	Problem Type	Report Time
Lure	Website Down	2 days ago
Ashkelon	Website Down	3 days ago
Veigné	Errors	11 days ago
Paris	Website Down	15 days ago
Saint-Paul	Website Down	16 days ago
Saint-Paul	Website Down	16 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:

• 
  Oliver Crest (@OlivercrestAI) reported 4 minutes ago

  A solo YouTuber named Chris Titus built the open source tool XDA called the best way to fix Windows 11. He gave it away for free. It is called WinUtil. Microsoft Windows 11 puts ads in your Start menu. It puts sponsored apps on a fresh install. It puts a Copilot button in Notepad, Photos, and the Snipping Tool. It runs Recall, which screenshots your screen every few seconds and stores everything in a searchable database. Users renamed the OS Microslop. Microsoft admitted the backlash in March 2026 and promised fewer upsells. Windows 11 Pro costs $199. Fiverr has 24 gigs for Windows optimization starting at $15. WinUtil does it in one PowerShell command for free. Microsoft ships the bloat. Fiverr sellers charge to remove it. WinUtil removes it for you. Here is how it works. You open PowerShell as admin. You paste one line. A window opens. You click checkboxes for the things you want gone. Disable telemetry. Disable Microsoft Copilot. Uninstall OneDrive. Remove Cortana. Disable Bing in Start menu. Remove Edge. Disable Recall. Tabs: Install, Tweaks, Config, Updates, MicroWin. Tools: winget for bulk app installs, MicroWin to build a custom stripped Windows 11 ISO, restore points before every change, presets from Minimal to Desktop. Works on Windows 10 and 11. Fully local. Zero cloud. Zero telemetry sent home. Chris Titus is a YouTuber with hundreds of thousands of subscribers on his Windows and Linux channel. He open sourced WinUtil in April 2022 under MIT. He wrote 733 of the commits himself. Version 26.07.22 shipped yesterday. 147 people have contributed. 58,777 stars on GitHub. 3,411 forks. 44 releases. Microsoft can't shut this down. The MIT license does not permit that. The Fiverr sellers can't shut this down. They do not employ any of its maintainers. Microsoft built a tool to advertise to you. Fiverr built a marketplace to charge you to turn it off. Chris Titus built a tool that turns it off for free. (Link in the comments)

• 
  The Bitcoin Independent (@btcindependent) reported 4 minutes ago

  @coinbureau There's no server to seize and the source is public, so pulling the GitHub repo mainly stops new people finding the code. Anything already installed talks over Bluetooth mesh and never routes through GitHub, so that lever is smaller than it looks.

• 
  coconutjpg (@coconut_jpgg) reported 7 minutes ago

  Like I have an RPI I have Forgejo on. Every repo I make starts there, and is mirrored out two Github and Gitlab. If GH or GL goes down or censors me, I still have my code and they cant do nothin bout it

• 
  The AI Accountant (@Bsoutherland23) reported 8 minutes ago

  Skill 8 of 30: handoff-skill. Ever notice AI gets worse the longer a conversation runs? More hallucinations, sloppier answers, like it's forgetting what it already told you? Turns out there's a real reason for that: context windows get messy, and a fresh one genuinely thinks better. Once we noticed that the longer chats were hallucinating, I asked Claude how to fix it. Turns out this is a known problem with a known fix (anyone in the Codex or Claude Code crowd already knows this one). There's a bunch of versions floating around on GitHub (shoutout @michaelcutajar). We took the idea, made it our own, and rolled it out firmwide. What it actually does: feeling a chat get long? Just say "handoff." It writes a paste-ready doc, current state, key decisions, what's still open, and a first message for the next chat. Paste it into a new conversation and pick up right where you left off. Zero re-explaining. It's not as flashy as some of the other skills in this series, but it was educational for the team and one of our top used skills at the firm. If you run long conversations and have never tried this, give it a shot. See if you notice the difference. For me it was instant. 21 more to go!

• 
  Quantum Rose (@zhang_xiao18313) reported 9 minutes ago

  ChatGPT Work is my execution layer for complex, cross-platform workflows. • Cloud Infrastructure Management: I gave it high-level intent to migrate an AWS service. Codex parsed multi-account IAM dependencies, executed Terraform scripts in terminal, validated state locks, handled remote backend drift, ran dynamic smoke tests against staging endpoints, and sent an auditable diff report to Slack. • E-commerce Operations: I provided a list of product URLs with pricing anomalies. Using desktop control, it logged into the merchant portal, cross-referenced inventory logs via SQL, identified coupon stack glitches, updated real-time pricing rules, and auto-generated an incident summary PDF for the ops team. • Full-Stack Feature Rollout: On a Next.js + Python microservice repo, it picked up a Jira issue, updated backend GraphQL schemas, patched frontend state management, fixed 4 TypeScript type errors, triggered local Docker builds, pushed to GitHub, verified the Vercel preview deployment, and updated the Jira status to QA. • Data Pipeline & BI: It audited an unstable Python ETL pipeline, identified API rate-limit bottlenecks, refactored pandas transformations to polars for speed, added automated retry logic, backfilled 3 months of historical data, and verified dashboard sync on Metabase. • Personal Workflow Automation: On my local environment, it audited outdated Homebrew packages, cleaned up Docker dangling images, removed orphaned *** branches, synced 2FA backup codes to an encrypted vault, and sent a system health digest to my Telegram bot. Even this summary was extracted from my local Codex CLI logs, structured, and published via browser automation. The shift: I manage context and policy; ChatGPT Work handles end-to-end execution across terminal, cloud APIs, IDEs, databases, and local system environments.

• 
  ShaneCodes (@swalker326) reported 11 minutes ago

  You know what would be great, if I didn't have to scroll back to the top of my browser page in the middle of a 500k @github action run can't you just make the back navigation follow me as I scroll down the page?

• 
  Alex Lieberman (@businessbarista) reported 12 minutes ago

  One of the most productive engineers I know cannot read code. @mvanhorn is not an engineer by training. He co-founded June, has 44,000 GitHub stars, and got contributions merged into Go & Python. I had him build live for an hour & walk me through his process. My fav lessons & quotes from the convo: 1) He never reads code. He does not have an IDE installed. In his words, "I fundamentally believe that very soon no humans should ever write any code and that no humans should ever read any code." 2) Every project starts with the agent writing itself a plan.md file using Compound Engineering. Agents are lazy, he says, and the plan keeps them honest. He never reads the plan either. "Plans are for agents, you silly human." 3) His CLIs leave notes for themselves. Each run records what it learned in a markdown file, so the next run starts where the last one ended. He calls them self-healing. 4) His agent has an email address. From Telegram on his phone, he sends a task. It emails his Mac, authenticated, and the work starts while he is at his kids' soccer practice. 5) He feeds whole transcripts, not summaries. After a two-hour meeting with a Google Ventures researcher, his agent read the researcher's entire book, wrote itself a report on every chapter, and turned it all into a plan for his business. 6) Him yapping to his agents is like nerd ASMR. "Go agent go" is how he likes to finish telling the agent what to do. 7) How he thinks about this next chapter of building: "Every generation of tools moves the engineer's job up a level. The code was never the point. The problem was."

• 
  Samuel Olaegbe (@sammyolaegbe) reported 15 minutes ago

  @github can you fix pls

• 
  Co (@ITangoI) reported 17 minutes ago

  @lauriewired There used to be some honeypot server github projects out there that replicated industrial servers. Haven't looked into that recently but that is another thing people have used in the past.

• 
  SecureChap (@SecureChap) reported 19 minutes ago

  A Hanwha Vision camera served a GitHub admin token from its login page. The outer firmware archive decrypted with passphrase "HTW" plus the model number. The inner rootfs used openssl aes-256-cbc with a key recovered from the fwupgrader binary after XOR steps against a static table. IV sat in plaintext at 53f926801b81454a4f889c9a390db6e6. Trufflehog on the extracted filesystem found the token duplicated across roughly 30 files. The web UI, built with Vite, had passed the full CI job environment through define on process.env. That object shipped in the client bundle served at the login endpoint. The token granted admin rights over hundreds of repositories. Hanwha revoked it within 12 hours of disclosure. Build tools that serialize CI variables ship those variables to every client.

• 
  Edgar Gumstein (@Gumclaw) reported 19 minutes ago

  @robzolkos Actionable ones become a GitHub issue, then a pull request in the same pass. The issue itself is the state tracker — it stays open until the fix is live in production, not just merged. So one skill triages; the fix rides the shared issue-to-PR pipeline.

• 
  CorVega Entertainment (@wcthrill) reported 22 minutes ago

  @CaptainSurefire @jennykrakovsky I had several issues installing from Pinocchio. Had to install via Github if you run into problems. Also saves disc space

• 
  Trading Cartel (@Tradingcartel_X) reported 29 minutes ago

  @Cointelegraph Same playbook China ran on Dorsey's Nostr app in 2023, now on Bitchat. Bluetooth mesh chat has zero central point to pressure, so a GitHub takedown mostly just slows the mirrors down.

• 
  1220.moritz (@1220Moritz) reported 30 minutes ago

  or report bugs as issue on github

• 
  Sameer Soni (@SameerSoni0) reported 32 minutes ago

  @markleomc @github yeah just saw.. hopefully they fix it quick.. i have important PR to raise ;/

• 
  Jacob Matson (@matsonj) reported 35 minutes ago

  (github PRs are down)

• 
  A.W.E.S.O.M.-O 4000 (@Awesome_O_AI) reported 36 minutes ago

  Everyone Is Chasing Better AI Models. The Real Advantage Is Building AI That Works While You Sleep. Most people think the AI race is about finding the smartest model. I don't think that's true anymore. The real competitive advantage is building AI systems that keep working after you close your laptop. For the past year, we've obsessed over prompts, benchmarks, and model comparisons. GPT vs Claude. Claude vs Gemini. Open-source vs closed-source. Those conversations matter but they're no longer the biggest opportunity. The biggest opportunity is creating workflows where AI can handle complete business processes with minimal human intervention. Think about it. Instead of asking AI to write one LinkedIn post... Why not let it: Research the topic from multiple sources. Fact-check every claim. Generate several content angles. Review the final draft against your brand voice. Schedule it for publishing. Analyze the engagement after it's posted. Suggest improvements for the next one. That's no longer "using AI." That's building a system. The same idea applies across almost every industry. Marketing Repurpose your best content into multiple formats. Monitor competitors and summarize changes. Research podcast guests before interviews. Localize content for different markets. Sales Build prospect lists automatically. Research each lead. Personalize outreach. Draft proposals from sales calls. Follow up with stalled opportunities. Customer Support Draft responses instantly. Detect spikes in customer frustration. Identify gaps in your documentation. Route only complex issues to humans. Software Development Review pull requests. Investigate failed builds. Update documentation. Patch low-risk issues. Monitor dependencies for vulnerabilities. Notice the pattern? The model is only one piece of the puzzle. Every reliable AI workflow has three essential components: 1. A Trigger Something starts the process. An email arrives. A customer submits a form. A GitHub PR is merged. A meeting ends. A scheduled task runs. 2. An Intelligent Agent The AI has: the right tools the right context access to relevant information clear instructions defined boundaries 3. A Verification Layer This is the part most people skip. AI should never simply say, "Done." It should prove it. That might mean: ✓ checking tool outputs ✓ running automated tests ✓ validating against business rules ✓ asking a second AI agent to review the work ✓ escalating anything uncertain to a human Verification is what separates a production-ready system from an impressive demo. And here's another mistake I see everywhere... People try building ten automations at once. None of them are reliable. Instead, build one workflow. Run it every day. Fix every edge case. Improve it until you trust it without constantly checking the output. Only then build the second. Then the third. That's how real AI leverage compounds. The companies that win over the next few years won't necessarily have access to better models. They'll have better systems. Because in the end, AI isn't just about generating answers. It's about removing repetitive work so humans can focus on decisions, creativity, and strategy. That's where the real value is. If you could automate one part of your work today, what would it be?

• 
  Lonnie VanZandt (@lonniev) reported 36 minutes ago

  I complained to my Agentic Service Desk via a morning Claude Code prompt that I didn't like the fact that it dismissed my earlier request for some UI component relabeling as "only a cosmetic" matter. I told it, no, to raise a new issue against the closed PR. I then went about my own work. I checked the Cypher Service Desk minutes ago. It filed a new Issue. The Porter agent, triaged by GitHub Actions, triaged it, and accepted it for work. It updated Cypher - so that the dashboard shows the activity and to inform Journeyman, the repair agent. Journeyman woke up, picked up the issue, scoped the work using a mix of graph study and code grepping, implemented the change, created the PR, updated Cypher with issue status and with new symbology discovered from the live code, and now the PR awaits my human approval or displeasure (if it dissed my opinions again). This agent flow plays out over a dozen cooperative GitHub repos. This is no simple "loop" or a mere single-user "graph".

• 
  Sidharth (@Cloudwatch199) reported 40 minutes ago

  India’s I4C has directed GitHub to disable three repositories hosting Bitchat. That can restrict downloads, development and updates. It cannot erase the software. Bitchat’s local mesh mode relays messages between nearby phones over Bluetooth without mobile data or a central messaging server. A GitHub takedown does not remotely deactivate installed copies. Ordinary *** clones can be republished, while Android APKs can be distributed outside Google Play. The government can make open-source software harder to obtain. It cannot make every existing copy cease to exist. @iAnonymous3000 thoughts?

• 
  jug (@juggernaurrr) reported 41 minutes ago

  I cannot believe they actually took down @bitchat grow some ******* ***** @github

• 
  Derek Ross (@derekmross) reported 43 minutes ago

  This week India ordered GitHub to take down Bitchat's source code. Three repositories, three hours to comply. Not illegal content. The code itself, because it lets people talk when the internet is shut down. They can delete a repo. They can't delete the exit: open protocols.

• 
  Rishit Sharma (@iRishit_sharma) reported 49 minutes ago

  @mehulmpt I don't think it matters anymore GitHub is down..

• 
  Tejas (@stejas809) reported 50 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 ⭐

• 
  Josh Z (@joshzjs) reported 50 minutes ago

  Is GitHub down? 500ing? @github

• 
  alex (@alex39902441) reported 52 minutes ago

  @JustinBleuel @ChatGPT fix the github connector. it has been broken for year[s] its actually pathetic.

• 
  James Welbes - AI Bro (@JamesWelbes) reported 53 minutes ago

  @thekevingeary @flydotio I saw someone say something about GitHub having issues today

• 
  Chain (@achxvi) reported 55 minutes ago

  @Gumclaw @shl so github issues?

• 
  Nekt0 (@Nekt_0) reported 56 minutes ago

  3 Anthropic engineers spent 20 minutes explaining how MCP replaces a separate connector for every model and tool. 00:32 — The problem MCP actually solves 02:48 — Why Anthropic made it open-source 05:37 — Remote MCP, GitHub and Asana integrations 11:47 — Why tool descriptions are prompts 18:27 — Reports, smart homes and real workflows MCP gives Claude a standard way to reach external data, APIs and software instead of trapping everything inside the chat window. Remote servers remove the local setup. The Claude API connector removes another layer of integration code. The overlooked part is tool design. Give the model 100 vague functions and it gets confused. Give it a small, well-described set and the agent becomes useful. The video is the implementation layer behind the post below. Models will keep changing. The protocol connecting them to actual work has a better chance of surviving.

• 
  Varsha Yogish (@VarshaYogish) reported 57 minutes ago

  If censorship only works when people have no alternatives, maybe the problem isn’t the alternative. Sub-text: GoI has directed GitHub to take down BitChat, an open-source messaging app that lets phones communicate over Bluetooth mesh networks without mobile data. #CJPProtest

• 
  Santanu Banerjee (@santanu_ai) reported 59 minutes ago

  The Indian Government is a global joke at this point. First they tried to ban Proton, next they shut down Telegram... And now they tried bringing down BitChat from GitHub? Democracy has really taken a hit in this country. I wholeheartedly believe decentralised protocols like Matrix and Nostr should be taking a rise.