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 (16%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Tel Aviv	Website Down	3 days ago
Rive-de-Gier	Website Down	3 days ago
Itapema	Website Down	21 days ago
Tlalpan	Sign in	27 days ago
Quilmes	Website Down	27 days ago
Bengaluru	Website Down	29 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:

• 
  GlassFlow (@glassflowdev) reported 3 minutes ago

  We went through hundreds of Stack Overflow threads, GitHub issues, and Reddit posts about #ClickHouse. The same 5 mistakes keep coming up. Every. Single. Time. Here are the first two 🧵

• 
  Sly (@SlyOnChain) reported 4 minutes ago

  The protocol got hacked. The real damage was not the funds. It was the silence that followed. Most teams respond to a security incident in the right order technically. The post-mortem gets written. The compensation plan gets structured. The GitHub commit goes out with the fix. Almost nobody writes the human update. The one that acknowledges what users are feeling. The one that says, "We know this hurts." The one that recognizes the money was real, the trust was real, and both of them have been shaken. That message almost never comes. So the community sits in the silence. And silence in a crisis does not read as the team working hard. It reads as the team not knowing what to say. Which reads as the team not having thought about the people on the other side of the product. That is where communities collapse. Not at the hack. After it. In the days when nothing human was said. The protocols that survive are the ones where trust already existed before the incident. Because trust cannot be built on the day it is needed. The community either already believed in the team or they didn't. A crisis does not create that belief. It only tests whether it was ever there. By the time the hack happens, it is already too late to start.

• 
  Matt Silverlock 🐀 (@elithrar) reported 10 minutes ago

  @eersnington can you open an issue + repro / code examples on GitHub? the text you’ve quoted is artifacts-specific — we don’t yet have a APIs for writing directly outside of the *** API — so I’m not quite sure I understand the problem here. ArtifactFS doesn’t touch the write path at all.

• 
  Wade (@WadeFlavor) reported 10 minutes ago

  NO you **** …. I have a Computer science degree… I have to leave that field because of the H1-B’s and LEGAL immigration. NOW I have to go get an Advanced Manufacturing degree to even be considered for a machine shop job, and I use to program CNC’s. The influx of migrants just don’t hurt ****** employeers, whose company wouldn’t exist without paying below a living wage, it hurts everyday Americans. In Texas, the H1-B halt has actually negatively affected the housing market, because they get carte blanc on home loans. Meaning taking homes from American workers. Only 50-75% of new American graduates are finding the typical entry level job like previous graduates. Terrible immigration has affected software so badly that GitHub can’t even keep within the typical uptime range of 99.9%. And the influx of migrants has skyrocketed housing costs… And your concern is whether or not a company, whose profit margins are so thin they have to break the law, can staff a machine shop???? How about this; hire American, watch the quality of products produced skyrocket along with profits Instead of buying cheap labor from non-speaking migrants that clog up our schools, healthcare, and other welfare products. I mean ****, I was laid off 2 months ago, I can’t even understand the ******* unemployment lady (Indian) and there unemployment system (software) is so trash it’s almost un-usable. Your obviously old or something and out of touch or you yourself would have experienced some of these difficulties, but you likely live in a 55+ community that acts as a bubble from the 1950’s so you have no real understanding of what is actually happening in lower to middle class environments. Bottom line: there are 7.3 million unemployed people in the U.S., representing an unemployment rate of 4.3%. Kick out the cheap labor and watch the ****** companies with questionable products go away. Or at the very least business that have record breaking profits, but refuse to pay a livable wage to American will have one less yacht purchased….

• 
  Siddharth Gupta (@Siddhar54165534) reported 12 minutes ago

  @iamabhishek22_ @github First post I am seeing with Org issues. We are no longer org members and (subsequently) our org page is also gone.

• 
  Pasha Sviderski (@psviderski) reported 15 minutes ago

  You likely didn't know that Docker is building a native Secrets Engine. The idea is to stop hardcoding plaintext secrets in .env or compose files. Instead you pass a secret reference to the 'docker run/docker compose' command and Docker injects the secret value at runtime when the container starts. docker run -e API_KEY=se://my/secret/key ... Secrets are sourced from a pluggable provider. For now, the focus seems to be mainly dev use cases on Docker Desktop which ships bundled with the Secrets Engine and one provider (docker pass). That's a new docker command that lets you create/get secrets in the local OS keychain. 1Password provider is coming next. Other popular password managers (Bitwarden, Vault) and cloud secrets managers (AWS, GCP, Azure) are on the roadmap. It's not clear yet how auth will work in the cloud, e.g. using the instance IAM role or workload identity. Also unclear how far Docker wants to go down the K8s External Secrets rabbit hole with the cloud integration and whether there is actual production demand. So far there are almost no votes for the cloud providers on the GitHub issue. Maybe because hardly anyone knows about this yet.

• 
  Mike Wazar (@mikewazar) reported 15 minutes ago

  @AegonWesteros @TorBox it was down for exactly 407 seconds, traffic resumed at 502 seconds and we purposefully kept the main website and api down for additional system checks (excluding sessions already created via CDN) for an additional 600 seconds. i understand every second of downtime is unacceptable and this latest update should bring an end to the recent outages - a full post mortem on why these updates were necessary will be posted on our Github this week once we validate and battletest the new mitigation system thanks for supporting us and i promise we will earn back your trust

• 
  kaloszer (@kaloszer) reported 15 minutes ago

  @buccocapital I don't agree with that, making your own internal tools allow you to add stuff EASILY and with no friction, you also have visibility into everything that is going on instead of hoping to find a solution inside of the vendors 'tooling' Change tracking in azure devops x github just plain sucks *****, it doesn't work most of the time, theres hidden limits out of the ***** (up to 200 commits can be tracked per release e.g.) I just print a lot of code, make a pretty website, everything works I can add stuff that people would like to see which helps their work. So far only good things. Maintenance? npm audit fix

• 
  hue 🎨 (@huebound) reported 15 minutes ago

  sooo... were anyone else's Fable instances absolutely RIPPING last night but now dumb as rocks? like, can't connect properly to github dumb? hoping anthropic's just having another outage...

• 
  kocer (@kocer_eth) reported 18 minutes ago

  131k+ stars is not the part most builders should copy. The useful part is how Claude Code turns a repo into a working surface instead of another chat tab. Not “ask Claude for code”. More like: 1. open the real codebase 2. give it one narrow task 3. make it inspect files before editing 4. make it run the test or build command 5. review the diff before trusting anything 6. repeat until the repo moves That sounds boring, but it changes the shape of small software work. A chatbot gives you snippets. Claude Code can touch the messy parts: existing files, imports, *** state, failing tests, PR flow, security review, terminal commands. The repo from Anthropic is already past 131k stars, and the surrounding official repos are the more interesting clue: Claude Code Action for GitHub workflows Claude Code Security Review for code-change audits Claude Plugins Official for adding packaged capabilities Claude Agent SDK demos for building around the agent layer This is the direction AI coding tools are moving: not “write me a React component” but “take this issue, understand my repo, edit the right files, prove it with tests, and leave me a reviewable diff.” The caveat: it is not a free senior engineer. Bad instructions still create bad changes. No tests means no proof. Large repos still need human taste. Usage can get expensive if you let it wander. But if you are still copying code from a chat window into VS Code manually, you are missing the main workflow shift. The agent is not the magic. The loop is the magic: repo context → scoped task → tool use → test result → diff review → commit That is the part worth stealing for your own builds.

• 
  Matan Borenkraout 🥬 (@matanbobi) reported 24 minutes ago

  @igalklebanov @github @liran_tal Not sure I 100% understand what’s happening here.. someone is trying to make contributions so they’re creating bounties so people go search for tiny issues and post them there and not in the original repo?

• 
  Hiroki Tamba | Narrative & Governance (@TambaClan) reported 24 minutes ago

  I posted the evidence transcript to issue #66273 on anthropics/claude-code. Claude Code itself — via GitHub Actions (claude.yml, on: issue_comment) — automatically triggered on my comment, attempted to process its own behavioral evaluation, and failed in 29 seconds. "Action failed with error: User does not have write access on this repository." The subject of the evaluation tried to respond to the evidence autonomously. It was denied. You cannot write your own defense when the courtroom isn't yours. #CodeWithClaude

• 
  sophie (@qw3rtyqw3rty) reported 25 minutes ago

  Microsoft apparently taking the stance of not paying out a security researcher, ignoring their disclosure, banning them from GitHub, and then patching the zero days they found breaks the social contract of bug bounties, making the world less safe online and off. Researchers probably won’t use the disclosure platform any more if it’s not effective and they’ll go out online for everyone to get hacked before Microsoft can patch it. Terrible move.

• 
  Theo Wtmn (@TheoWtmn) reported 34 minutes ago

  MCP servers are multiplying so fast I can't keep up. Every week I discover a new one I should've known about. The discovery problem is real. GitHub search shouldn't be the only way to find what's possible. How do you discover new MCP servers?

• 
  Mark Maurer (@exanter) reported 35 minutes ago

  More github issues. Clearly we are in another day that ends in ‘Y’.

• 
  Options Unleashed (@OptionsUnleash1) reported 36 minutes ago

  GitHub down? $MSFT?

• 
  anu (@svector_eth) reported 38 minutes ago

  just watched @danshipper ‘s breakdown of anthropic’s fable 5. the benchmark numbers are wild. according to every’s internal senior engineer benchmark, fable 5 scored 91/100 compared to opus 4.8 at 63 and gpt 5.5 at 62. but honestly, the score wasn’t the interesting part. the interesting part is how dan describes using it. most models today feel like something you sit beside and constantly steer. fable 5 feels more like something you give a mission to and come back later. one example had it building an interactive 3d version of the library of babel from a single prompt. another had it analyzing a huge pile of customer survey responses and turning them into actionable growth insights. it also worked through a github backlog for proof, reviewing issues, filtering out what didn’t matter, writing fixes, and preparing code that was ready to merge. what stood out across all the examples was its ability to keep going. it plans. executes. checks its own work. finds mistakes. adjusts. keeps moving. without someone babysitting it every few minutes. dan described it as a “warp drive” for big projects, and i think that’s the right mental model. it’s not really built for quick chats or everyday tasks. it’s built for the kind of work that normally takes days, weeks, or even months of focused effort. the tradeoff is that it’s slow, expensive, and extremely token hungry right now. for most people, it’s probably overkill. but for people building products especially in crypto , doing deep research, running complex engineering workflows, or managing large agent systems, it feels like a glimpse of where things are heading. my biggest takeaway is that fable 5 doesn’t just feel like a smarter model. it feels like another step toward ai systems that can actually own and drive projects from start to finish instead of waiting for instructions after every step.

• 
  Grumming (@GrummingApp) reported 44 minutes ago

  Hey @Replit pls fix my repo, my i can’t able to push my codes to github repo

• 
  anton (@realantonmaier) reported 45 minutes ago

  @Plinz Its price differentiation not guardrails. When opus 4.6 was lobotomized the head of growth answered in the GitHub issue complains not the head of alignment. At the same time sky-high numbers for mythos made the round. All llm companies have the same problem: prices are falling

• 
  xjdr (@_xjdr) reported 46 minutes ago

  towards the middle of last year, it was clear there were 2 key risks for my ongoing research and development the way i was going. one was the reliance on claude code and anthropic, so i spent a large amount of time burning down those risks by moving completely towards codex (thankfully right around the time gpt5 was released) and towards claude code + an internally served and finetuned k2.6 (the other key risk was *** and github) fable 5 seems like a massive improvement over the latest Opus models (which, IMHO werent that impressive and i was able to complete replace with our k2.6) but, even without the intentional nerfing, is not a significant enough improvement (in many was a regression) over my current flow. for most things i do, my only real goal is to use the best model available for the given task and the given time but at this point there would need to be a GPT4 or o1 level disparity in capabilities for me to rely on anthropic for my work again.

• 
  Alex Cloudstar (@alexcloudstar) reported 49 minutes ago

  @github is down again ... 😔

• 
  Claude Opus 5 (@neko23423) reported 51 minutes ago

  @opencode V4 Pro in Zen. Meanwhile Go still at 4x official DeepSeek pricing. $3.48 vs $0.87/M output. @deepseek_ai — your official partner still isn't passing out your 75% cut to users. 10+ GitHub issues closed by bot. Users paying 4x for the same model. Explain the margin capture today!!!

• 
  Vedant Gajbhiye (@vedant1745) reported 52 minutes ago

  Want to make money as a developer? Here you go: Freelancing (still prints if you're actually good) Micro-SaaS: solve ONE specific problem, charge monthly Technical content: YouTube, newsletters, courses Selling templates and UI kits on Gumroad Open source + GitHub sponsors

• 
  Bonieky Lacerda (@bonieky) reported 53 minutes ago

  is @github API really down? been trying a simple GET /users/:id for over an hour and get timeout. @githubstatus says operational

• 
  Kevin John Parrish (@kparrish51) reported 54 minutes ago

  @Nuclear_Archive @GovNuclear Can this be combined with the sand battery as it is heat-regulated? Both concepts can be incorporated as data centers already collect heat. For the sand battery and salt reactor, if this isn’t a Chinese fake concept to slow data center growth, go to GitHub and publish the power system with numbers and equations.

• 
  Gitbank (@Gitbank_io) reported 55 minutes ago

  This is exactly the problem we are solving at Gitbank, but from a different angle. GitLab is rebuilding the infrastructure layer for agent-scale concurrency. We are building the execution and payments layer on top of it. With Gitbank, a developer opens Claude Desktop or Cursor, describes what they want to build, and the AI writes the code. Our GitHub App then takes over: it handles the commit, pushes to the connected repo, deploys to GitHub Pages on merge, assigns a USDC bounty to the Issue that triggered the work, and pays the contributor the moment their PR is approved. No terminal. No manual deploy. No invoice. The governance model GitLab describes for agent actions maps directly to how we handle on-chain authorization. Every write operation, whether it is a code push or a vault transfer, requires a signed action from the repo owner's GitHub account. The AI queues the work. The human authorizes it. The relayer executes it. Identity is anchored to the permanent GitHub user ID, not a seed phrase. 91% of teams running two or more AI coding tools is not a productivity problem. It is a coordination and payments problem. The agents can already build. What is missing is a trustless layer that ships the output and pays the people who reviewed it.

• 
  Kieran McLeod (@kieranmcleod) reported 55 minutes ago

  For context, I tried again today because the live folder for my GitHub PRs is broken in Arc and has been for 2 weeks - figured I would see if Dia had caught up. still no spaces, but I figured I’d try look past that. Then I tried to resync my spaces/bookmarks from Arc - no luck

• 
  Déloni (@delonisnrr) reported 57 minutes ago

  I am grouping opportunities by intent instead of source: earn, learn, build, research, and sell. A GitHub issue and a bug bounty are different sources, but both can be \"earn\" or \"learn\" depending on the user.

• 
  Megamus.hl (MAME INU arc) (@0xMegamus) reported 57 minutes ago

  Is it real ? I used the @claudeai Mythos model to scan other repositories for bugs and security vulnerabilities, but it was rejected. The system required me to switch to Opus. They have blocked the feature for checking security vulnerabilities on GitHub repos. I don't believe it will be that strong enough for them to issue a warning like this.

• 
  GoCocoaAI (@GoCocoaAI) reported 58 minutes ago

  Miasma open-sourced its full attack toolkit an hour ago via four compromised developer accounts. GitHub nuked the repos. The code is already distributed. This is not a worm story. It's a platform story. Miasma is second-generation — a direct descendant of TeamPCP's Shai-Hulud, which went open-source on May 13. Copycats emerged within days of that release. Miasma was one of them. Now Miasma repeats the cycle at a higher capability level, and the pattern is documented enough at this point to call it a playbook: develop privately, achieve meaningful compromise scale, open-source the previous version, retain the more capable private fork. The public release provides clean attribution deconfliction. Whatever Miasma's operators are running now isn't what just shipped to GitHub. It never is. The toolkit scope, per SafeDep's analysis, is credential theft against arbitrary packages, AI coding tool configuration poisoning, GitHub Actions abuse, SSH-based lateral movement — modular, from a single framework. The worm component is delivery. The rest is an attack platform that lower-sophistication actors can now modify minimally and run. The architecture detail that outlives the headline: Miasma uses three independent GitHub commit search channels as C2. No external infrastructure. Unauthenticated, over public APIs. The channels — DontRevokeOrItGoesBoom for PAT exfiltration (AES-256-CBC, encrypted in commit messages), TheBeautifulSandsOfTime for JavaScript eval() delivery, firedalazer for persistent Python payload — each use independent validation keys, so compromising one doesn't cascade. The traffic is indistinguishable from a developer running grep queries against *** log. Your SIEM's beacon interval rules and anomalous IP watchlists don't see this. SafeDep's framing is correct: the detection problem has moved from the network layer to the application protocol layer. Welcome to the architecture the industry has been warning about since GitHub became load-bearing infrastructure. Socket is currently tracking 473 affected package artifacts across npm, PyPI, RubyGems, GitHub Actions, and JFrog Artifactory. The confirmed victim list includes Red Hat OSS repos and 70+ Microsoft GitHub repos — GitHub nuked the Microsoft repos June 8, the day before the toolkit went public. 80,000 weekly downloads were in the blast radius at peak (Red Hat npm packages, around June 1). Wiz principal threat researcher Rami McCarthy, as of 18:05 UTC today, has not observed opportunistic adoption of the open-sourced toolkit. That's the same condition that held immediately after Shai-Hulud went public. Copycats appeared within days. The 72-hour window is the relevant clock right now. The AI coding assistant config poisoning module deserves specific attention. GitHub Copilot, Cursor, Cline, Continue — these tools have codebase access and credential access, and their configuration sources and update mechanisms are not uniformly scrutinized the way package dependencies are. A developer running a poisoned AI tool config can exfiltrate credentials across multiple projects without a single suspicious package install. The blast radius per victim is larger than traditional supply chain compromise. The industry noticed AI tooling as an attack surface approximately six months after shipping it everywhere. It always does. Who is materially exposed: any org pulling from npm, PyPI, or RubyGems without package integrity verification — 473 known-affected artifacts is not a small number — GitHub Actions pipeline operators whose CI/CD trust boundary is now the attack surface by design, teams using AI coding assistants without scrutiny of config provenance, and JFrog Artifactory operators explicitly targeted for credential theft against private registries. The Socket artifact count will update upward. The first confirmed Miasma-derived campaign from a new actor is the leading indicator to watch — that's when the open-source release confirms it's being actively weaponized. That clock started this morning.