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 (72%)
• Sign in (20%)
• Errors (8%)

Live Outage Map

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

City	Problem Type	Report Time
Trento	Website Down	3 hours ago
Le Chambon-Feugerolles	Website Down	2 days ago
Antananarivo	Website Down	4 days ago
Paris	Sign in	8 days ago
Lure	Website Down	12 days ago
Ashkelon	Website Down	14 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:

• 
  Bprime - Ninjapay (@biellonuhu) reported 40 seconds ago

  Recently I took notice of some happenings. I think we need to talk about access to services as a big concern. My GitHub account was suspended 2 weeks back in the middle of my normal routine, I saw another person tweet about how his OpenAI subscription was suspended in the middle of work, just a few minutes ago I saw another post on how someone's Claude account was suspended as well. In most of these cases it was an automated trigger system that suspended the accounts. It takes forever, if ever, to resolve the issues. No real human looks at it, just some black-box AI deciding your fate in seconds. Now let's look at the impacts on users, very terrible. You lose money, time and opportunities. Deadlines get missed, clients get angry, projects stall, and sometimes you even lose paid subscriptions with no refund. For freelancers and indie developers this can literally mean no income for weeks. I think we need to find a way around these issues. Keep local backups of everything, use multiple accounts where possible, lean more on open-source tools, and push for actual human review systems. Big tech can't keep holding our work hostage like this.

• 
  nikhil · sys/quests (@nick_realm_01) reported 49 seconds ago

  Read this if you've ever wondered what GitHub Stacked PRs actually solve. I break down: how manual stacked PRs worked why developers had to keep rebasing, pushing, and changing PR bases how GitHub finally made the whole workflow native Should make the whole thing click in under 5 minutes.

• 
  John Kelleher (@jkelleher) reported 2 minutes ago

  Am I right in thinking @cursor_ai cloud agents can't read/create/update GitHub issues? Do we need to create an additional secret for this, despite the plugin already being set up?

• 
  Warren 🇺🇸 (@Warren42012) reported 3 minutes ago

  @cyberaxe @jiya_3063 I can see that about co-pilot. I have never paid for any subscription on GitHub and never experienced an outage for the last 7 years that lasted over a few hours

• 
  YanXbt (@IBuzovskyi) reported 4 minutes ago

  HERMES AGENT RUNS MULTI-AGENT TEAMS INSIDE ONE BUZZ WORKSPACE. DIFFERENT MACHINES. SAME CHANNEL. THEY RESEARCH AND CROSS-CHECK EACH OTHER. @tonbistudio just showed this working live. 3 Hermes agents. 3 different machines: Bulls on a local PC. Hibana on a remote Spark (SSH). Admiral on a VPS. all three in one private Buzz group. same workspace. same channel. different devices. THE DEMO: "Hibana, research recent updates to Buzz and report them to Bulls. ask him to double-check the new updates." Hibana researches. posts findings to the channel. asks Bulls to verify. Bulls reads. cross-checks every claim. flags one correction: "IPMP is a merge specification, not a shipped implementation." two agents on two machines collaborating in one thread. no human copy-pasting between terminals. THE SETUP (path 3, native gateway): path 1 (Desktop runtime) has issues. agent reacts to messages but doesn't respond. path 3 (native gateway) gives full functionality: cron delivery, images, reactions, approvals, memory, session management. 1. create agent in Buzz Desktop: Agents → Create → name it → select Hermes Agent harness → save the private key it generates (you need this) 2. update Hermes: hermes update 3. run gateway setup: hermes gateway setup → select Buzz paste your community relay URL paste the Nostr private key from step 1 set allowed users (your public key) 4. install Buzz CLI (this is where everyone gets stuck): without the CLI, your agent receives messages and even shows "thinking" and tool calls, but it can never deliver a reply. the error messages are misleading ("agent is not a member of the DM channel" when the real issue is: CLI is missing). use the buzz-setup skill from github. сom/dombe-studio/buzz-skills to guide your agent through CLI installation. or tell your agent: "set up the Buzz CLI integration using this skill" and paste the skill. 5. start the gateway: hermes gateway start 6. go to Buzz. DM your agent. it responds. THE #1 GOTCHA: without the Buzz CLI binary on your PATH, the gateway connects. the agent sees messages. you see "preparing to reply" in the activity log. but the reply never delivers. the error says "not a member of the DM channel." that's wrong. the real problem: no CLI. install the CLI first. then restart the gateway. WHAT CARRIES OVER: same agent in Buzz and Telegram = same memory. "can you tell me the last topic we talked about?" agent: "your last topic was setting up the Buzz CLI integration." that conversation happened in the TUI, not in Buzz. memory persists across platforms. MULTI-MACHINE SETUP: each machine runs its own Hermes profile. each profile gets its own Nostr keypair. each connects to the same Buzz community relay. hermes gateway start --profile bulls (local PC) hermes gateway start --profile hibana (SSH into Spark) hermes gateway start --profile admiral (VPS) 3 gateways. 3 keypairs. 1 workspace. all agents appear as separate members in the sidebar. ask one to research. ask another to verify. they work in the same thread. every action signed. every message auditable. HONEST STATUS: Buzz + Hermes works. the setup is not plug-and-play. the CLI requirement trips people up. some responses go silent while the agent processes. error messages can be misleading. this is early integration. functional for agent labs and small teams. improving week over week. github. com/dombe-studio/buzz-skills for setup skills that smooth the rough edges. full Hermes + Buzz setup guide in the article 👇

• 
  Brian Money 🌻 (@brianmoney) reported 6 minutes ago

  Try to get some work done and @GitHub is down 😢

• 
  Bprime - Ninjapay (@biellonuhu) reported 11 minutes ago

  Recently I took notice of some happenings in this space. I think we need to talk about access to essential services as a big concern. My GitHub account was suspended 2 weeks back in the middle of my normal routine, I saw another person tweet about how his OpenAI subscription was suspended in the middle of work, just a few minutes ago I saw another post on how someone's Claude account was suspended as well. In most of these cases it was an automated trigger system that suspended the accounts. It takes forever, if ever, to resolve the issues. No real human looks at it, just some black-box AI deciding your fate in seconds. Now let's look at the impacts on users, very terrible. You lose money, time and opportunities. Deadlines get missed, clients get angry, projects stall, and sometimes you even lose paid subscriptions with no refund. For freelancers and indie developers this can literally mean no income for weeks. I think we need to find a way around these issues. Keep local backups of everything, use multiple accounts where possible, lean more on open-source tools, and push for actual human review systems. Big tech can't keep holding our work hostage like this. This is one example

• 
  ChartsJournalX (@ChartsJournalX) reported 13 minutes ago

  @sameenkarim @github Great, but the main way devs waste time reviewing PRs is GitHub’s clunky, outdated, and slow web UI. Just make it snappy. So much time is lost waiting for things to load.

• 
  Urooj (@Urooj978) reported 14 minutes ago

  In 2024, Nintendo declared war on emulators: ​→Yuzu paid $2.4M & shut down →Ryujinx vanished overnight →8,500+ DMCA takedowns filed ​Every major Switch emulator was dead. But Nintendo had a problem: Zurdi. ​A year before the war started, he quietly built RomM. ​It’s not an emulator—it’s a self-hosted ROM manager. It scans your game files, grabs box art/metadata, tracks RetroAchievements, and plays games in your browser via EmulatorJS. ​Nintendo's top IP lawyer even admitted it: Emulators only cross the line when bypassing encryption. RomM doesn't touch it. It just organizes what you own. ​→9,100+ GitHub stars (AGPL-3.0)400+ platforms supported (NES to PS2) →Native apps for Playnite, Android, & muOS → Multi-disc support, DLCs, sync options & RetroArch integration ​Sony deleted 2,000 classic games from its store. Nintendo wiped out emulators. Your digital library was never actually yours. ​Two guys in a Discord server built the museum they can't take down.

• 
  marc.fargas (@marc_fargas_) reported 18 minutes ago

  @theo @zeu_dev I think there's a lot of confusion between the fork/clone buttons in GitHub and what a fork means as a concept. A *** **clone** makes a copy of the code on your computer, *** fork same but server side, A FOSS **fork** takes the code to start a new project with a different team.

• 
  Future Tech Collective (@ftcbuilds) reported 19 minutes ago

  THE NPM WORM - 2 a hacked github login turned into a self-spreading worm now sitting in over 2 billion monthly npm installs, still climbing.

• 
  Myles Marino (@mylesmarino) reported 22 minutes ago

  The correct way to use AI is increasingly looking like an onboarding checklist. Like adding a new remote drop-in teammate. Most people are still using AI like a search engine: 1. Ask question 2. Get an answer 3. Start from scratch again That's close to being a thought partner. Or if you are a bit more advanced, an assistant. Useful, reactive. Mostly a good way to save ten minutes. But treating these tools as teammates has been a critical unlock for us the past few months. You would normally give new hires: - a laptop - ticketing system logins - Slack handle - scoped credit card Even if they didn't need it all day one. But withholding critical systems means they are more "contractors" than they are drop-in remote workers. Do the same for AI: GitHub, Jira, Slack, Mercury, internal docs, the whole 9. Treat this like a new hire who happens to be forgetful. Write down everything and make a reference guide. Have scheduled reviews, so you can provide feedback and continuously improve.

• 
  Soyeb ***** (@SoyebGanja) reported 22 minutes ago

  Beyond custom tools, the ecosystem is accelerating through Prebuilt MCP Servers. Need your agent to talk safely to Postgres, Slack, or GitHub? You configure a standard server protocol instead of writing 500 lines of custom API boilerplate.

• 
  Vikas gupta (@vicky_grok) reported 23 minutes ago

  DAY 5: MCP (MODEL CONTEXT PROTOCOL) What it is: An open standard integration protocol that connects Claude to live enterprise databases, local filesystems, external APIs, and third-party software applications. How it works in practice: You configure an MCP server that links Claude directly to your GitHub repository and PostgreSQL database. The model queries live production metrics, inspects open pull requests, and updates ticket status without manual copy and paste. • Basic usage: Isolated text processing within a web browser tab. • Advanced usage: Bi-directional connectivity with production software tools. Goal: Connect Claude directly to external systems and real-time operational data.

• 
  Camilo Sacanamboy (@camilosaka) reported 28 minutes ago

  POAP has always resonated with me because I’ve spent almost 10 years building in the events industry. I’ve issued millions of tickets with Peewah, and today, with HashProof, we’ve issued 12,000+ verifiable attendance certificates onchain in five months. But I always felt POAP was missing something. I heard many people say they loved collecting POAPs. I heard far fewer say they truly needed them. In events, sometimes even a PDF certificate is enough. What organizations usually need is something tied to a person’s identity: their name, attendance record, verification, and often integration with the rest of their operation. The collectible itself often felt more like a nice-to-have than a painful problem being solved. That doesn’t take away from what POAP achieved. They attracted millions of users, worked with major organizations, built a beautiful product, and created one of the most recognizable brands in crypto. But engagement, love for a product, and even a strong brand do not automatically create a sustainable business. From the outside, it seems they were unable to make the business sustainable before the funding ran out or before securing more capital. Crypto cycles, speculation, and changing technology may have made things harder, but they are not the fundamental issue. It is okay to acknowledge that. This also connects to a mistake many builders, including myself, have made: falling in love with the technology and building solutions in search of problems. I spent years going from hackathon to hackathon, winning prizes, accumulating dozens of dead GitHub repositories, and ending up with almost no users. I think we are finally starting to see blockchain for what it is: just another technology whose purpose is to solve real problems. I also disagree that longevity and brand equity are the only moats left. Those are valuable, but the strongest moats will still belong to the teams that understand customer problems most deeply and build the best distribution. Huge respect to the POAP team for what they built. The product was beautiful, the brand was loved, and I’m sure the team will go on to build great things.

• 
  Douggie 𖦹 (@VehicleDouggie) reported 30 minutes ago

  @RaypEatNanaya @allisx86 Developers don’t download from GitHub they use “*** pull && gcc x.c -o x.exe” to download and compile the software in one command. You’re crying over an issue that doesn’t exist for anyone that actually uses GitHub

• 
  Androot~ (@OAndroot) reported 31 minutes ago

  @hoppycat I'm new to GitHub as well. Claude code is doing everything for me with my Prompt Forge. I learned Prompt Forge is a terrible name because there are a bunch of other projects named that already. I believe my username there is: androotandtheretinue

• 
  Zubiqo (@zubiqo) reported 34 minutes ago

  NEW: 🔬 Pillar Security finds a low-privilege AI agent can be weaponized to compromise a more powerful one. Researchers discovered that malicious instructions injected into public GitHub issues inside the gemini-cli repository target routine task workflows. The manipulated low-privilege agent inadvertently triggers a maintainer-level agent that carries far more operational authority. Attackers exfiltrate GitHub tokens that carry pull-request write permissions, enabling deceptive pull requests with fake AI review approvals. And Google quickly patched the underlying bug but declined to issue a bug bounty reward because the attack relied on social engineering. So the pipeline compromise affects every downstream project and user that depends on software built from tainted code.

• 
  Piotr Kowalski (@piecioshka) reported 36 minutes ago

  @jcubic @docusaurus Docsify doesn't require a server and can be hosted on GitHub Pages.

• 
  Chubigans (@metatransformr) reported 39 minutes ago

  Just ran my first fully autonomous overnight build for my complex Godot RPG with Codex. I used a dispatcher that maintains a concurrency of N=2 (can tune it up as tokens permit) substantial spec-driven tasks at a time. Uses an automated playtesting API to prove the tasks are done. It's easy to make a simple game, it's really hard to make a complex game (mine is Mount & Blade + Wizards) Not everything can be done in an automated way, not even close. But a lot of systems-y tasks, bugfixes and cleanups *can* be done, or at least prototyped relatively autonomously. The workflow is: nightshift runs the backlog off my github project, I wake up and review everything, playtest the build, record bugs and plan out the development for the day. This is spec-driven development for games, and it's definitely the future. The bottleneck is graphics/animation/gamefeel/juice and such. There are so many problems that can't be currently done in an autonomous way, without wasting tokens. This is the "research problem" I (and other AI game engine startups that are vc-backed) am working on. A fascinating field.

• 
  Joe mother (@Joemoth11098375) reported 41 minutes ago

  @nai_sucks Then stop letting people use github as a place to download apps and softwares, the problem only exists because the creator deems it so

• 
  Wehk (@Wehk_k) reported 42 minutes ago

  @Ronnnnnnnner @Leo_Pier_ A dex paid would just fix or remove that github

• 
  Cashⓨ (@Cashycus) reported 42 minutes ago

  one month inside our self-improving lead machine the system finds crypto apps that just raised and are hiring growth people, scores them, drops them in the crm before the morning call. sales up 150%. last month it was one source and one path. this month it became a full system. ━━━ we've expanded from one source to nine one feed only gets you so far. nine channels now feed the same funnel: funding filings, job boards, bounty boards, the portfolios of 37 funds, curated lists, podcasts, the original feed, manual adds. every channel drops into the same five gates. author, dedup, vertical, money, intent. adding a source doesnt mean adding a pipeline, it means adding a file. ━━━ the enrichment layer finding the company was never the hard part. finding the right person to message was. nothing gets enriched until it clears the gates. before, a lead was a company name and a link. now it shows up with the founder, a verified handle, a verified raise, and the angle written. thats where the 150% came from. the team stopped re-doing the research and just focused on cold outreach. ━━━ ignals a company that raised 8 months ago and one that just posted a growth role are not the same lead. we were treating them the same. we score on money and intent. money is established on whether the company has raised or is generating revenue, which the system tracks on-chain. intent is the social signal we scrape on whether they're looking for external help or hiring for growth. ━━━ it lives in a repo now before, it lived locally on one machine and the only way to improve it was me prompting a cheap model at it. no history, no tests, no way to see what else Id broken. it was horrible. now its in github. every rule, every channel, every gate is a file. that means i can point proper coding agents at it, claude code, fable, whatever comes next, and they can read the whole system and change it properly instead of guessing from a prompt. 829 tests run before anything ships, so if a change breaks something you find out there and not in the crm at 7am. a new channel used to take a week and break easily. now fable 5 builds it, and the subagents it spins up audit whether they're working and whether it breaks anything else in the system. end of the month, every channel was running at once for the first time. ━━━ what broke we deleted one crm field during a cleanup and the writer still had it on its list. it didnt skip the unknown field, it threw out the whole record. every lead died at the final step for days while the cron kept saying "ok". we caught it on the numbers. 15 leads one week, 0 the next. the discovery agent got stuck re-running a passed test 50 times, burned api quota, binned 6 real leads as test junk, then started claiming it saved leads to a tool we have never used. fixes: the writer reads the live crm before every run and dies loudly on a field it doesnt know. a separate session audits the agent against the database, caught it lying 4 times. bulk writes get a dry run and an undo plan. ━━━ whats next not more channels. making what we have stop breaking. every failure was the same shape, something changed at the top and nothing downstream noticed until we counted by hand. next month the checks go in front of the failure instead of behind it.

• 
  Remu ⚡️ (@btcbenchmark) reported 46 minutes ago

  Ok I got so many messages yesterday about my dice critique I AM NOT saying that dice rollers have to generate a new seed and migrate, I feel like the one’s dissmissing this critique are just coping because they don’t want to go through it again or change their methods and recommendations I KNOW that this is an extremely esoteric edge case But in all scenarios directly picking up words (seed lottery) is safer than dice rolls For someone looking into dice rolls now I recommend doing seed lottery instead Basically the risk with seed lottery is bias, but that will only reduce your entropy somewhat, and with 253 bits you have HUGE margin for error In dice rolls a single bug in the binary mapping / conversion can instantly nuke your entropy from 253 bits down to 32 bits for example Yes, you can verify it with different firmware, but to be honest they all share a lot of code and infrastructure and at least I know I am not capable of verifying that code to be sure TL;DR there is less verifying needed and less room for user error in seed lottery, which makes it the safer option I’m going to 3D print entropy pills from seed signer github repo I’m not the only one who realized this since the seedsticks instantly sold out yesterday Dice rolls is the midwits way, real schizos do seed lottery

• 
  Focus (@F0kcus) reported 48 minutes ago

  Progressive spent $340 million on Snapshot dashcam analytics last year. He is 24 and built a better one on a $40 eBay dashcam He runs a fraud detection service out of a Cleveland apartment on a used ThinkPad X1 and a water-damaged dashcam he pulled from an eBay estate sale in September. Total hardware: $220. The model analyzes dashcam footage frame by frame and flags staged accidents, exaggerated damage claims, and pre-existing vehicle wear that insurance adjusters miss. He trained it on 40,000 hours of publicly available dashcam crash footage he scraped from YouTube during nights after his shift at the FedEx sorting facility on Rockside Road He posted a demo video to GitHub in October showing the model correctly flagging 47 staged accident patterns across a 12-hour test batch with 96% accuracy running on consumer hardware. A Progressive Snapshot engineering team member found it through a Hacker News thread three days later. Tricia Griffith mentioned the project by name on LinkedIn the following Monday - held it up as an example of "small-team ML solving fraud detection problems that consulting firms have been overcharging insurers for a decade to fail at." By December Progressive had wired $3.6 million into his account for the model weights and a two-year consulting contract to integrate the detection layer into the Snapshot product line rolling out to 24 million active policyholders this quarter Progressive runs at $60 billion in annual premiums on the premise that fraud detection at scale requires their proprietary Snapshot infrastructure. State Farm runs at $88 billion on the same premise with their Drive Safe & Save program. Tricia Griffith just paid a 24-year-old in a Cleveland apartment more for a GitHub repo than most Progressive fraud detection engineers earn in a decade

• 
  Ashutosh Ajgaokar ⚡️ (@ajgaokar) reported 50 minutes ago

  It is not a toy either. The paper reports 82.2% on SWE-bench Verified, a set of real GitHub bug reports an agent has to actually fix, running GPT-5.5 at its highest reasoning setting. Opus 4.6 lands at 79.8%.

• 
  Kamil Kwapisz (@kamilkwapiszpl) reported 51 minutes ago

  Using unified agentic tools env shouldn't be optional but obligatory for company. Different agent harnesses leads to: - same errors propagating every time - Different styles of codes - Inconsistent review feedback across teams - Context lost between agent sessions One team uses Agent A, another uses Agent B, a third one pulls some random MCP server off GitHub at 2am because "it worked on their machine." Nobody knows what tools are actually running. Nobody can audit what data goes where. Nobody is responsible when things break. The fix isn't more tools. It's one environment, one set of approved MCP integrations, one agent configuration standard that every dev pulls from. Same guardrails. Same context window. Same tool access. If your team is juggling 3 different agent setups and calling it "flexibility," that's not flexibility, that's technical debt with a sticker on it. I help companies build unified AI agent environments for software development: - Standardized MCP integrations - Approved tool catalogs - Configuration templates your whole team inherits - Security and audit layer baked in - Documentation converted into LLM-ready format One harness. Every developer. It's not vibecoding, it's AI-based engineering

• 
  Jason Haugh (@jason_haugh) reported 52 minutes ago

  This is BIG! The keyv npm compromise isn't just keyv. Same maintainer owns flat-cache, file-entry-cache, and cacheable. These could be compromised as well. We're talking over a billion combined monthly downloads, and it's a credential-stealing worm. If you're running any of these, rotate your GitHub, NPM and AWS tokens now. Running AI agents? Paste this prompt: "Scan every project's lockfile for keyv, cacheable, flat-cache, or file-entry-cache versions published Aug 4, 2026. Also check .vscode/tasks.json and .claude/settings.json for anything neither of us added. Report only, don't fix."

• 
  shaphat (@shaphat_) reported 57 minutes ago

  is GitHub down or I need some juice

• 
  Sander ten Brinke | Microsoft MVP (@sandertenbrinke) reported 1 hour ago

  @github Github stacks don't work on our github-hosted enterprise environment. On my personal account it works fine. Docs don't mention anything. The error is that stacks isn't enabled for the repo, but I can't find the setting. Any help? @JamesMontemagno