GitHub 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:

• 
  .eth (@jeffque_) reported 5 seconds ago

  We need more genuine builders like $ZAUTH. RepoScan kills fake GitHub credibility. x402 database verifies payment endpoints in real time.Real product. Real problem. Real community.This is how you flip the $300B cybersecurity industry

• 
  Dapton AI (@daptonai) reported 2 minutes ago

  @linear Code review has always been the most context switch heavy part of the whole development cycle. Write in the IDE. Review in GitHub. Comment in Slack. Back to the IDE to fix. That is four tools for one feedback loop that should take minutes. Diffs inside Linear with AI review and agent iteration in the same place is not faster code review. It is finally the whole loop in one place.

• 
  Manticore Search (@manticoresearch) reported 2 minutes ago

  @github @github actions are still broken. We had to switch the default branch from "master" to "main". We were going to do it anyway to be able to build new packages. The stalled workflow in the old branch is still "queued" for already 2 days :)

• 
  Febb (@xFebbio) reported 4 minutes ago

  GitHub is one of the most critical platforms in the world. And they just lost control of 3,800 internal repositories through a single compromised VS Code extension. Not because the system is weak. But because there's no layer that can detect, stop, or at least slow down malicious activity before it's too late. And this is just the beginning. In a world where AI agents operate autonomously without humans in the loop, attack vectors like this will become more frequent and faster. Every agent running without clear governance is a vulnerability waiting to be exploited. That's why the most important question in the agentic era isn't how smart the agent is. But who authorized its actions, what are its limits, and is there a record of every decision it made. Rialo is building infrastructure to answer those questions at the protocol level. Governance problems aren't future problems. This is happening today and it will only get worse.

• 
  ypsehlig (@ypsehlig) reported 6 minutes ago

  @Anastasis_King perhaps you missed the news. This repo was taken down and nightmare-eclipse was banned from both github and gitlab.

• 
  The Pragmatic Engineer (@Pragmatic_Eng) reported 6 minutes ago

  TypeScript was open-sourced at a time when Microsoft had a strong anti-open-source reputation. Anders Hejlsberg(@ahejlsberg) ,creator of C#, TypeScript & Turbo Pascal, on how they ended up on GitHub: TypeScript creators wanted to open-source TypeScript, but Microsoft was resistant: “Microsoft was slowly waking up to the fact that open source was not going to go away. Open source was where developers wanted to be, and they were voting with their feet. Yet, there's a collective DNA that has been trained to pull you in the other direction. And so that battle - we were right in the centre of that. We full well knew that there was absolutely zero chance that we would appeal to the JavaScript ecosystem with a proprietary programming language licensed from Microsoft. No, no one was going to come. It had to be open source. There was just no two ways about it, but getting that off the ground inside Microsoft, it took some pulling and we paid some taxes.” Initial open sourcing was far from ideal: “We did eventually get the okay to do open source because we had two technical fellows, myself and Steve Luco - who was the other co-inventor of TypeScript - insisting. So, okay, people weren't going to debate that, but of course you have to pay the tax and be on Microsoft's open source repository called CodePlex, where exactly no one was. We were there for the first two years and it kind of was crickets. It wasn't until 2014 when we moved on to GitHub that things really started to get moving with adoption." Being on GitHub changed their workflow, to TypeScript’s benefit: “Honestly, it totally changed our workflow. There's open source and there's open development. We were technically open source in the beginning, but it was not open development. We would sort of lop the source code out of its repository and scrape the issues off of that and put it into our internal issue tracker. But, once we switched to GitHub, the entire workflow moved to open development, and that I love that workflow. We've been there now for over a decade and it's been fantastic, and it's what made the product as good as it is.”

• 
  ric..ki (@derricky_eth) reported 7 minutes ago

  Why long-term security is essential for DAC’s future adoption and how future-proof infrastructure helps protect trust, data, and on-chain systems over time. If DAC wants to achieve long-term adoption, security can’t stay buried in a GitHub repo or treated as a “nice-to-have” technical layer. It has to become the ecosystem’s operating system—the unspoken contract between every participant. Here’s the uncomfortable truth: Most decentralized projects focus on throughput, fees, or novel consensus. But users don't leave because a chain is slow. They leave because they get hacked, rugged, or watched helplessly as a bug drains millions. Trust takes years to build and seconds to shatter. As on-chain infrastructure becomes more interconnected—bridges, oracles, cross-chain apps—a vulnerability in one protocol no longer just hurts that protocol. It cascades. Think of the major bridge hacks of the last few years: billions lost, not because the underlying L1 was broken, but because a single smart contract had a subtle flaw. That flaw then froze liquidity, tanked token prices, triggered liquidations, and eroded faith in entire ecosystems. Suddenly, validators, treasuries, and governance forums are all in crisis mode—reacting, not preventing. Why “future-proof” infrastructure isn't a buzzword—it’s survival A resilient DAC ecosystem doesn’t just patch today’s vulnerabilities. It anticipates tomorrow’s. That means designing for: Adaptive threat models – Attack vectors evolve faster than audit reports. Formal verification is good; real-time anomaly detection and invariant monitoring are better. DAC needs security that learns, not just checks boxes. Data integrity without blind trust – Users shouldn’t have to pray that a sequencer or validator is honest. ZK-proofs, fraud proofs, and verifiable data structures turn “trust us” into “verify us.” Smart contract frameworks that fail safely – Not “code is law” recklessness, but “code has guardrails.” Circuit breakers, upgrade paths that require broad consensus, and economic disincentives for malicious behavior. Validator and governance mechanisms that resist capture – Staking isn’t magic. If a handful of players own most of the stake, security becomes theater. DAC should explore rotating validator sets, anti-collusion designs, and governance that doesn’t trade long-term resilience for short-term yield. Economic and technical shock absorption – What happens during a severe market crash or a coordinated attack? The infrastructure should survive not because everyone is honest, but because incentives make attacking more expensive than defending. The psychological side people forget Users, developers, institutions, and communities don't read white papers before bed. They remember headlines: “DAC loses $200M to reentrancy attack.” Institutions won't deploy capital without insurance or slashing protections. Developers won't build on a chain that reboots every other month. And regular users? They'll just go back to centralized exchanges—not because they’re better, but because they’re predictable. Long-term trust is boring. It’s consistent block times, transparent incident reports, proactive bug bounties, and a history of handling crises without falling apart. It’s not about never having vulnerabilities—it’s about catching them before they’re exploited, and responding honestly when they are. The bottom line If DAC’s security architecture isn’t designed for year five, year ten, it won’t survive year two. The strongest marketing, the best tokenomics, the fastest TPS—none of it matters if people can't sleep at night knowing their assets are safe. Security isn’t just code. It’s the quiet foundation that allows everything else—adoption, innovation, community—to breathe. Build the foundation like the future depends on it. Because for DAC, it absolutely does. @dac_chain

• 
  Damian Barabonkov (@damian_b) reported 17 minutes ago

  I decided to call it "dehub", so that we de-GitHub ourselves. Features: - Pull Request, Actions, Issues, Notifications viewers - PR comments, request reviews, and many more functions - Feature rich PR diff viewer launched in the web-browser Dropping sometime next week.

• 
  Dharan (@DharanGanesan) reported 19 minutes ago

  A single GitHub issue got 27 pull requests from AI bots. Most were untested. Some hallucinated entire implementations. The real contributors? Buried under noise. The fix is a *** hack most devs don't know about. GitHub's "Limit to prior contributors" setting blocks everyone who hasn't committed before. But you can whitelist real humans with *** commit --author using their noreply email. Credits them, doesn't need their SSH key. We built systems assuming contributors are humans. AI bots exploit that because GitHub can't tell the difference. Maintainers spend hours cleaning AI slop instead of reviewing real code. This is a maintenance crisis nobody wants to name. #AI #OpenSource

• 
  0097eo (@0097eo) reported 20 minutes ago

  @sifa_bavina The job market is in the pits, I went to moringa and got a job almost immediately after granted i have a degree in cs too. I regularly check some of my moringa classmates github and they haven't pushed code since the final project. That is the main issue

• 
  🐍 Tal Weiss (@majortal) reported 24 minutes ago

  @yoavgo Tell Claude or Codex to do it for you? It will literally be up and running in 30 minutes. I have an instance running the function of listening to GitHub issues and "doing stuff" And another one doing the function of listening on a webhook and sending out an email. There's obviously nothing special about Openclaw//AWS in this regard. Plenty of alternatives.

• 
  Adam (@adam_bobowski) reported 26 minutes ago

  @TimoBuilds_ Anyone here can tell me what to build next. They just don’t care enough to do that. Also anyone on GitHub can raise issues with ideas as to what to build next - I think the tools are already there. The problem is that no one cares enough to write them. That’s kind of the main problem imo. Making people care enough to engage

• 
  Sam Huckaby (@samhuckaby) reported 28 minutes ago

  Historically, the reason so few challengers rose to GitHub/GitLab was because setting up a *** service required a server and management and minutiae that was easiest to just hand to a 3rd party Artifacts opens up a door by taking away a time+money cost of a service and opening up the ability for open source (or paid) *** frameworks to emerge. I don’t think a new GitHub is coming, I think someone is going to build a framework with paid support patches that companies can run and scale themselves

• 
  Isaac Way (@isaac_ts_way) reported 29 minutes ago

  @theo @adamdotdev Yeah idk how anyone argues github is not doing a terrible job Their service bricks every 2 weeks while also not having shipped or changed anything signficant in a long time

• 
  CEO Govibe.org (@govibeorg) reported 31 minutes ago

  @piyush784066 I don't understand why sending your codes to a Microsoft server (Github) its like if you can not share any open source code outside of corporate control the open source community roasted me for not using Github saying that my codes were closed source cause its not on Github...