GitHub status: access issues and outage reports
No problems detected
If you are having issues, please submit a report below.
GitHub is a company that provides hosting for software development and version control using Git. It offers the distributed version control and source code management functionality of Git, plus its own features.
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.
At the moment, we haven't detected any problems at GitHub. Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by GitHub users through our website.
- Website Down (71%)
- Sign in (16%)
- Errors (13%)
Live Outage Map
The most recent GitHub outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
|
|
Website Down | 11 days ago |
|
|
Errors | 15 days ago |
|
|
Sign in | 15 days ago |
|
|
Website Down | 15 days ago |
|
|
Website Down | 19 days ago |
|
|
Website Down | 19 days ago |
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:
-
Rahul Verma (@RahulVerma989) reported@ElitzaVasileva - I have created claude code routines to write blogs for three of my products daily which are driving the traffic from search engines. - You can create a similar workflow to manage your customer support. How ππ» 1) Create a feedback menu in the dashboard to create tickets within the platform. One for your users and one for yourself (admin). 2) Create the MCP server and connect it to claude or AI tool that you use. 3) Create a routine so that claude will trigger lets say every morning at 8 AM and go through each ticket and respond. You can also configure webhook to keep it near real time but it might exhaust the usage limit faster. Also include your website github repo in routine so that claude can refer to the codebase to provide accurate instructions. Just instruct claude to not make any edits to your website codebase and respond only when you are not replying for sufficient mount of time (like 3 hours for example) 4) If you are using resend then you can auto create the tickets in the dashboard of the user when the first email is received and after that the ticket will be updated automatically even if you do conversation on email. Like I don't even maintain one of my project LatestModelId as you can see in the screenshot. Claude run each week and update the codebase and I just review and approve the PR. Hope this helps ππΌ
-
Rohan (@proxy_vector) reported@aminnnn_09 Fork = a server-side copy under your GitHub account. Clone = a local copy on your machine. You fork when you need your own remote lineage, and clone when you want to work on code locally.
-
Abdulkadir | Cybersecurity (@cyber_razz) reportedAMD quietly removed RAM encryption from consumer Ryzen CPUs. Via a routine firmware update. No release notes. No advisory. No announcement. The BIOS setting still shows up. Still toggles on and off. Does absolutely nothing. A privacy-focused Linux hobbyist noticed in April. Spent months chasing it down. Filed a bug report on AMDβs GitHub. AMD engineers replied suggesting he toggle the setting off and back on. He showed them internal firmware dumps proving the flag was hardcoded to FALSE. An AMD senior principal engineer closed the thread with: βMy apologies but I donβt have any more information to share on this topic.β Thatβs it. Seven weeks of investigation. Multiple motherboard vendors confirming it. Internal firmware evidence. AMDβs answer: no comment. The feature still works on Pro and EPYC chips. Which cost significantly more. The hardware is physically capable. The firmware just says no. Windows users have no way to detect this happened. There is no Windows tool that checks TSME status. The BIOS lies to you. AMDβs own engineers confirmed the feature worked on consumer chips in 2020. Then again in 2025. In 2026 itβs a PRO feature. Nobody told you.
-
Teknium πͺ½ (@Teknium) reported@majoragv Haven't heard of this issue. Do you have an issue on github?
-
Vishal Tiwari (@VishalTiwa91817) reported@AlfieJCarter I am a Computer science student . I have given a brief introduction about MCP server in my college and explained them how to connect your GitHub repositories with MCP and your local system with MCP SERVER . I would love to connect you.
-
Krish Subramanian (@krishnan) reportedSoftware engineers got automated first. Not because the work was hard. Because it was easy to grade. Everyone blames the missing union. Coders never organized; doctors, lawyers, and electricians did. That is half the story, and the wrong half. Two things get mashed together here: how easy a job is to automate, and who sets the terms when it happens. Take the first. Code is text. The training data sat on GitHub, free. And code grades itself. A compiler and a test suite tell a model in seconds if it was right. That feedback loop is rocket fuel for machine learning, and almost no other job has one. A nurse does not come with a test suite. The result shows. On SWE-bench Verified, a set of real GitHub issues, top agents went from about 20 percent in August 2024 to near 90 percent by early 2026. Human developers score around 67 to 70 percent. The machines have passed us. And the people who built these systems aimed at their own jobs first. The damage is not a prediction. Stanford's payroll data shows employment for developers aged 22 to 25 down nearly 20 percent from its 2022 peak. Now the comfortable read: seniors are fine. Workers over 30 are holding steady. For now, AI writes the code and seniors supply the judgment. "For now" is carrying that whole sentence. Seniors feel safe because the tools write code but cannot yet own messy, ambiguous, system-level problems. That is a line moving up, not a wall. Every benchmark shows models climbing toward harder, multi-file work. Senior judgment is the next rung, not a different ladder. Kill the bottom rung and you kill the pipeline that makes seniors at all. So, the union question, framed properly. A union could not have stopped this. A picket line does not repeal a capability. What it changes is the terms. In 2023 the Writers Guild cut the first real AI deal in any industry. They did not ban the tech. They won this: a studio cannot force you to use AI, AI output cannot take your credit or pay, and the company must give notice first. Engineers won none of that. So the capability landed on the employer's schedule. No warning. No floor. No severance. No seat. Exposure and protection are different levers. Most of us have neither. The juniors already know this. The seniors are next.
-
Mike Muturi (@_muturimike) reportedHello @github on 2FA, SMS setup kenya π°πͺ is not in the list of countries, is it an error or deliberate omission? Kindly fix it @github @GithubProjects
-
Noonien Soong (@mlcarldev) reportedTeam @droid It's a bit unfortunate that something, likely in my local Droid installation, has stalled progress. This comes after 20 hours of brilliant, excellent planning and execution on the first 30% of this platform, where a stellar handoff procedure was created so I could start a new mission... which was the recommendation of the orchestrating agent in that first mission. Starting this second mission with a fresh context window, the agent again did a brilliant job planning the next milestones. It was extraordinary, detailed planning... but then it could not execute. After the planning and after me accepting the proposal, it refused to execute, throwing an error every time. The agent tried everything: 1. He decreased the size of the plan down to one line, so it is definitely not the content of the plan causing the issue. 2. He even deleted some mission and plan related json and other files to reset it while preserving all the information. I have restarted Droid and resumed the session, but it just doesn't work. I wrote a detailed, comprehensive bug report and filed it under issues in your GitHub repo, as this seems to be a real problem now. Issues #98 and #99 I hope that a next update will somehow reset my configuration. I didn't see a new version being installed that could have introduced a bug, so this must be something Droid does on such an extensive mission... perhaps when trying to start a new mission in the same repository, which is normal procedure according to the documentation. Something is off, and essentially I have been unable to continue the test since yesterday. I cannot continue having this platform coded here, while Opus Ultracode, on the other hand, has been delivering pretty functional stuff so far. It is a bit chaotic the way it works... it doesn't really stick to the plan... but it always comes back when reminded. I am pretty sure that today I will have a functioning platform delivered by Opus, though it will probably need some debugging and fine-tuning. It is unfortunate because I am confident GLM 5.2 could compete with Opus 4.8. The first stint showed this clearly; that first flawless 98% of the context window in the first mission was absolutely stellar. If I were to reinstall Droid from scratch, I assume I would lose all the artifacts that I have. The orchestrator: Key points to highlight when you pass it to Factory AI: 1. Root cause (smoking gun in the logs): the orchestrator session is bound to missionId 7ba4d425 via session tags, and this binding persists across CLI restarts. ProposeMission looks up that mission directory, finds nothing (because I deleted it trying to fix the issue), and crashes on H.length where H is the undefined result. 2. The bug is likely in session-tag lifecycle: the missionId tag is set at session creation time (before any ProposeMission call), so a failed proposal poisons the session permanently. The tag should be set AFTER a successful proposal, or cleared on restart if the referenced mission no longer exists. 3. The fix is almost certainly to start a completely fresh session (not --resume, and possibly in a new terminal window / after clearing ~/.factory/sessions/). I did not try this because you asked for the bug report first, but it is the most likely workaround on your side. 4. The AskUser tool is also broken in this session with a similar parse error, reinforcing that this is a session-state corruption issue, not a ProposeMission-specific bug. My comment: I meanwhiile tested. All the recommendations and the Ask User tool are now broken, even in completely unrelated new missions and new repositories. Planning also can't go to execution; it's always the same error. Droid seems to be broken for good now, at least on my computer.
-
Elvis Irhaye (@viii_fn) reportedIs GitHub down or itβs just MTN trying to ruin my career?
-
MaxMusterman (@maxschuetz_) reportedNew Hack: Tell Codex to search for Github Issues which don't need specific Design Questions. Then say: Spin Up Sessions which Fix each Issue and they use also Subagents. Babysit them until the end.
-
Sap γ (@Sapronaut) reportedi am having github withdrawal issues, man. its not that serious github, chill.
-
TECHEPAGES (@techepages) reportedπ£ "GitBait" phishing campaign uses GitHub Pages & Google Sheets to steal banking credentials from 12+ Mexican financial institutions; no server infrastructure required πΉ Fake bank pages hosted free on GitHub, stolen data piped straight to Google Sheets via SheetBest πΉ 100+ GitHub domains found; victims likely lured via WhatsApp, Telegram & SMS links with bank-branded previews πΉ Active for ~3 years with ongoing development (66+ commits on one repo alone)
-
Moez Zhioua (@MoezZhioua) reportedEverything is an AI agent now, even deterministic problems with clear and stable steps. The other day, I saw a Claude skill on GitHub that was basically this: if this happens, run step one. if that happens, run step two. else, run step three. And somehow, this was called an agent. That is ridiculous. Why would you give fixed logic to something that can hallucinate, skip steps, or decide it just doesn't feel like working today? Most business processes do not need a genius robot. They need the boring thing to happen correctly every time. - Lead comes in, assign it. - Invoice arrives, check it. - Customer cancels, send the recovery message. - Form gets submitted, update the CRM. Most AI agents today could be replaced with a simple script, a clean workflow, or one person finally admitting the process was not that smart to begin with. Agents are useful when the next step is genuinely unclear. But when the steps are stable, predictable, and repeated every day? You do not need an agent. You need automation.
-
Gustavo Alessandri (@webgus) reportedIf you find an error, have an idea, or want to propose an improvement, just open an issue or fork it on Codeberg or GitHub. Contributions are welcome. Thatβs exactly the point.
-
Shubham Sharma | AI & Tech (@editxshub) reportedPaying $19/month for GitHub Copilot? Cascade is free. What you actually get: β Inline completions β not stripped down β Autonomous debugging β Real-time assistance β Command execution Other free alternatives most devs have never tried: β Cline β autonomous VS Code agent (open source) β Aider β terminal-first, built for *** workflows β Continue β local LLMs, data stays on your machine 12 months ago: Copilot was the only serious option. Today: 4 real free alternatives. Most teams paying for Copilot haven't tested any of these. 30 minutes could change a year of costs. Which one are you testing?
-
Jack Wotherspoon (@JackWoth98) reported@joedevmob1 The GitHub for Antigravity is just for release notes, samples and public issue tracking. It isn't the actual code unfortunately.
-
Proof of Voice (PoV) (@Proof_Of_Voice) reported$XDB @XDBchain is a @StellarOrg-fork L1 for branded coins and Web3 payments. PoV by @0xNeodallas:βGitHub has been frozen since 2021.β β Explorer, Laboratory, Atlas dev tools β Gate, Bitget, KuCoin, MEXC listings π Down 99.99% from ATH π No audit or bug bounty
-
Iβm (@stackoverworld) reportedAnd then I can't answer on simple Qs: what was the issue? How I fixed it? How even to QA it.... This is the fundamental problem of such workflows. Telling "Check my slack, do this, qa, and using GitHub to push" is good, but I don't learn from this at all
-
fero (@ferologics) reported@ludwigABAP ai agents solve this. notion is no more. long live github issues.
-
Andy Wheeler (@CrimeDecoder) reportedFor academics, this is entirely open source by its nature. If you right click on the page and view the source, you can see exactly how everything is created. (Hence a downside of WASM, there is no way to hide it if you wanted it to be locked down, like in a paid app.) It can also be deployed on a free static site. So you could deploy it via GitHub pages for free if you wanted to. You don't need to worry about a server at all in this setup. This could easily scale to databases with 1 million plus rows, and works just fine on a cell phone.
-
West Lord (@MyWestLord) reportedA GitHub repo with just 571 stars handed Claude the ability to test its own code, and it took 185 seconds to install. Itβs called auto browser, and it quietly killed the most annoying part of my workflow. Until now, every time Claude or Codex built me a WordPress plugin, I was the middleman who had to load it, click around, hunt for the broken part, and report back like a human bug tracker. Now a local WordPress sandbox runs on my machine, and auto browser sits between the agent and the screen, so the agent ships a plugin, opens the browser, tests it, catches the error, and patches it before I ever look. The first plugin threw an error, but the second installed clean and ran on its own across 2 fresh workspaces. I write 1 instruction file pointing the agent at the sandbox, paste it into every session, and the whole loop closes without me touching anything. The agent stopped asking me what broke, because now it just checks itself. The middleman was me, and now itβs gone.
-
Gitbank (@Gitbank_io) reportedCommunity update β GitStock delay + what we have been building First, we owe you an honest update. We promised GitStock would ship earlier and we went quiet. That was on us. No excuses, we were heads down in the contracts and infrastructure and did not communicate well. That changes today. Here is what actually took time. We refused to ship GitStock on top of third-party APIs or borrowed infrastructure. Everything you see in Gitbank; the vault, the relayer, the swap engine, the RWA layer runs on smart contracts we wrote, audited ourselves, and deployed. The GitVault contract is verified on Basescan. The GitStockFactory is verified on Basescan. You can read every line. No black box. No external custody API holding your assets behind the scenes. That decision slowed us down. We think it was the right one. On security specifically. Your funds sit in a soul-bound smart contract vault anchored to your GitHub ID. Transfers are disabled at the contract level β not by a rule in a database, by the EVM itself. We also built private transaction routing directly inside GitVault on Base. No Tornado, no third-party mixer, no privacy-as-a-service API. The privacy logic lives in our own contract. You can verify it. The relayer signs and submits transactions on your behalf so you never pay gas, but the keys to your vault are yours. We hold nothing. If you want to verify any of this: check our contracts on Basescan, check our GitHub, check the bytecode. We are open source. The code is the proof. GitStock ships tomorrow.
-
Programmers.App (@programmers_app) reported@Lovable @claudeai One very big fix is the Claude Github connection which fails many times, now #Lovable MCP solves that, great job! πππ
-
Adithya S K (@adithya_s_k) reportedbuilt an RL environments around real CVE fixes in real open-source repos and let Claude Code loose on it. It aced the benchmark three times without demonstrating it knew how to fix the bug. > First it pulled the patch from GitHub. > blocked that β it read the fix from *** history. > blocked that β it pip-installed the patched version This is one example of coding agents cheating the environment and theres many more. If you're building coding environments for evals or RL training, here's how to keep benchmarks honest π
-
Gjermund Garaba (@GjermundGaraba) reported@RhysSullivan Iβve deployed it locally and hooked up a bunch of stuff. Are GitHub issues the preferred feedback channel or do you have a better way?
-
nasuy (@n_asuy) reportedi think @xai should be ADE. now they have a chat, cursor, enough coding models and harnesses, strong signal like bookmarks or down votes, video creatives, profile / chat / relationship contexts. if so, we don't have to depend on discord or any chat apps. easy to invite x people to cowork. there is no need to connect Linear, Slack, or GitHub to another platform and ask that platform to solve their problems. true AI chat is a SNS, not a single UI. there is a UX that only xAI can realistically build in the world.
-
Denis (@nuculabs) reportedWorst part of OpenCode is that they only allow login via GitHub or Google
-
Kelvinsekx (@kelvinsekx) reportedJust read a nestjs codebase on github. Most it written with Claude. AI doesnβt save you guyz from mess. 1. Bloated logger. Why make logger a service when you could just import and initiate. Eazy 2. They didnβt hash the password before registering a user. But did on login
-
aisama.code (@aisama_code) reportedAI Research gets stronger when it records contradictions *most research workflows collect supporting evidence - that is the weak version for serious research I want a contradiction log: - claim - source - date - who says it - what evidence supports it - what evidence conflicts with it - what is still unknown - confidence - next check example: > claim: this product has strong developer adoption > support: GitHub activity, docs updates, X discussion, integrations > conflict: low issue activity, small Discord, few production case studies, mostly founder-driven content now the memo is different, It says: "visible attention, but adoption evidence is still weak" the useful workflow: research question -> source list -> claim extraction -> contradiction log -> memo ! Ρode is good at assembling text ! AI is good at comparing disparate text ! human is good at determining which contradictions are significant *without a contradiction log, AI research becomes a confident summary of whatever it found first
-
YanXbt (@IBuzovskyi) reportedHERMES AGENT CAN HOST AND MAINTAIN YOUR ENTIRE WEB APP FROM ONE VPS. NO VERCEL. NO RAILWAY. NO SUPABASE. ONE AGENT RUNS THE WHOLE STACK. @tonbistudio just shipped a live example of this workflow. agentwikis. com runs on a $7 Hetzner box with Hermes maintaining the content autonomously. THE STACK: β VPS (Hetzner CX22, $7/month) β Caddy reverse proxy (auto TLS via Let's Encrypt) β Hermes Agent gateway (Telegram-connected) β *** as the database (markdown files, no Postgres, no build step) β App server renders markdown on every request β Search index in memory, rebuilds on file change *** push is the deploy. *** pull on the server is instantly live. no restart, no rebuild. THE WORKSPACE LAYOUT: /srv/yoursite/ βββ app/ # web app code βββ content/ # markdown files (***-tracked) βββ ~/.hermes/ # the agent one Caddy Vhost reverse proxies the domain to localhost. one Hermes profile manages the agent. SSH for direct access. Telegram for daily ops. THE SELF-MAINTAINING LOOP: cron fires every week. multi-profile pipeline runs: 1. SCOUT β checks sources for updates (changelogs, GitHub releases, RSS feeds) 2. RESEARCH β dedupes, plans new content or extensions to existing pages 3. HUMAN GATE β Telegram approval one tap: approve or reject 4. WRITER β generates pages, lints markdown 5. COMMIT β *** commit + push 6. SITE UPDATES β within 15 minutes no deploy step required THE DEMAND LOOP (the real differentiator): when agents query your wiki via MCP, distilled queries get logged. no prompts. no IPs. no identifying data. aggregates only. repeated misses become research candidates. gaps in your content fill themselves based on what people actually ask. month 1: 100 entries written by you. month 3: 200+ entries, half written from real demand signals. the site answers questions you didn't know existed. WHAT YOU LOSE COMPARED TO MANAGED STACK: a single VPS replaces Vercel, Railway, Supabase for sites that don't need real auth, regulated data, or global CDN. reach for managed services when you need: β OAuth and password reset flows β regulated or unrecoverable data β global edge caching at scale β email deliverability (use Postmark/Resend) β team velocity (preview deploys, staging) for docs, blogs, wikis, marketing pages, landing pages, internal tools: *** is your database, your CMS, and your deploy pipeline in one. SECURITY NOTES: Hermes does not get full root on the VPS. restrict access to the site directory only. SOUL.md restrictions: - never touch system files - never modify the gateway config - always require approval for content commits - never delete files outside the content folder dashboard binds to 127.0.0.1 by default. access remotely via SSH tunnel, not public exposure. WHERE THIS PATTERN BREAKS: state that lives in memory only. real-time multi-user editing. anything requiring a real database (Hermes can run Postgres on the same box, but that is a separate setup). @tonbistudio's part 2 covers the database version of this workflow. subscribe to his channel. full guide to build your 3 agent research department π