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:

• 
  Plebian (@Plebian_2) reported 1 minute ago

  @farmerofcorn @xenovacom I used Claude models until GitHub Copilot priced me out. Now I'm using DeepSeek v4. Just as good. More bang for your buck. Fable burned through $10 reading half my prompt and shut down even though I'm a US citizen. $11K benchmark vs. $500? Can't even do identity services?

• 
  X (@TheMsterDoctor1) reported 2 minutes ago

  Burp Suite Professional costs $475/year per seat. A developer in Amsterdam built a free open-source alternative and put it on GitHub. His name is David Stotijn. The tool is Hetty. ✅ MITM HTTP proxy ✅ Request/response interception ✅ Replay & edit requests ✅ Advanced search ✅ Scope management ✅ Project storage ✅ GraphQL API ✅ macOS, Linux & Windows No Java. No license server. No telemetry. No subscriptions. Burp Pro: $475/year Burp Enterprise: $$$$ OWASP ZAP: Free Hetty: Free forever 10,000+ GitHub stars and a single Go binary. Find bugs. Earn bounties. Keep the $475. Your proxy. Your binary. Your bounties. (Link in comments)

• 
  Kodark🃏 (@kodarkweb3) reported 3 minutes ago

  Lesson 2: The projects that survive aren't the ones with the best marketing. They're the ones that kept building when nobody was watching. Github commits during bear markets tell you more than whitepapers during bull markets. Check what teams do when the price is down.

• 
  jayesh (@0xjayeshyadav) reported 7 minutes ago

  Onchain indexes hold about $100 million combined today, while the TradFi index industry holds tens of trillions of dollars. That gap is the entire opportunity, which most people read backwards. They see $100M and conclude nobody wants an onchain index. But after spending the last year building index products, I see it differently: nobody has built one correctly yet, and the underlying assets were never ready. The first problem is that every onchain index today sets weights manually, through token-holder votes or governance plus an offchain supply feed. Inserting a committee or token vote between methodology and basket simply rebuilds a discretionary fund wearing an index label. Its performance decays with governance attention. The two multi-year category leaders are both down 80 to 98% from peak TVL, showing this was a design problem, not a demand problem. The second reason is subtler: the only assets available to index onchain were crypto. A market-cap basket of volatile tokens is a leveraged bet on two or three names unless real methodology is applied, which almost nobody did, leaving the product fragile and narrow. What I am building is the opposite of discretionary. Weights are computed entirely onchain from float-adjusted market cap, capped and redistributed using the same iterative rules S&P and Nasdaq have run for decades. They are fed by a supply oracle that treats circulating supply as a bounded, explicitly named trust assumption rather than an unguarded feed. There is no committee and no vote; the methodology itself is the protocol. I am betting on much more than crypto. The index is the most successful product structure in finance history and already holds tens of trillions offchain. It has been stuck onchain not because the structure fails, but because the only assets available were volatile tokens. That changes as tokenized treasuries, credit, and equities arrive onchain at scale, which is already underway. The wrapper that manages trillions in TradFi finally gets a native onchain home. An onchain index of tokenized RWAs can then do what its offchain cousin cannot: settle continuously, show every holding in real time, rebalance programmatically, and remain in self-custody. Broad index ETFs are already cheap, so the honest comparison is not against a Vanguard fund but against the stack of intermediaries wrapping every index product, and against crypto index funds that still charge 1.5 to 2.5% a year. A fully autonomous onchain index removes that entire layer, replacing the administrator, custodian, and licensing fee with code while swapping the market-maker spread for open solver competition. Because the methodology runs itself, the fee can be a fraction of what crypto index products charge today. I'm building the reference implementation, and the code is on GitHub 👇

• 
  reza ramadhan (@rejaramadhan98) reported 8 minutes ago

  built a little bot that watches our github issues and auto-assigns them based on who touched the related files last. took maybe 30 minutes to write. our sprint planning meetings went from 45 minutes to 15. turns out most of the time was just arguing about who should own what

• 
  Ayush (@electr1fy0) reported 9 minutes ago

  i think github is down again, at least partially

• 
  Nav Toor (@heynavtoor) reported 14 minutes ago

  Burp Suite Professional costs 475 dollars a year per seat. A senior software engineer in Amsterdam built the open source replacement as a side project. He put it on GitHub for free. It has 10,569 stars. His name is David Stotijn. The software is Hetty. Here is what Hetty is. An HTTP toolkit for security research. A machine-in-the-middle proxy that sits between your browser and the target. Every request and every response flows through Hetty. You can read them, search them, intercept them, edit them, replay them, and send them again. This is the core loop of every web application security test ever performed. Burp Suite charges 475 dollars a year for it. Hetty does the same job for zero. Here is the feature set. A machine-in-the-middle HTTP proxy with full logs and advanced search. An HTTP client for manually creating and editing requests, and replaying any request you already proxied. Request and response interception for manual review, with full edit, send, receive, and cancel control. Scope support to keep your work organized to a single target. A web-based admin interface that runs in your browser. Project-based database storage so multiple engagements stay separate. A GraphQL service for programmatic access. The installer is a single Go binary. Works on macOS, Linux, and Windows. No Java runtime, no enterprise license server, no machine fingerprinting, no telemetry. Here is the price ladder. Burp Suite Professional: 475 dollars a year per seat. Burp Suite Enterprise: thousands per year, contact sales for a quote. Burp Suite Community Edition: free, but throttled, no scanner, no project save, no intruder rate. OWASP ZAP: free and open source, now owned by Checkmarx after a 2024 acquisition. Hetty: zero. Forever. One binary. No account. A pentester working full time pays Burp 475 dollars a year. A team of 10 pentesters pays 4,750 dollars a year. A bug bounty hunter who finds one vulnerability has already paid for Burp twice over. Or they download a 30 MB Go binary written by a freelancer in Amsterdam and keep every dollar they earn. David has not pushed a new commit in 16 months. The last commit was January 13, 2025. That is normal for a tool that is feature-complete. HTTP has not changed. The proxy still proxies. The intercept still intercepts. MIT licensed code does not expire when the maintainer takes a break. Buy a domain. Find a bug. Cash a bounty. PortSwigger took a free industry tool and put it behind a 475 dollar paywall. A freelancer in Amsterdam gave it back. On every platform. For zero dollars. Your proxy. Your binary. Your bounties. (Link in the comments)

• 
  루이 (@_chiiazu66) reported 16 minutes ago

  @Fluffyquack If anyone is stuck on finding the update like I was, just go through the RE Framework github, the latest update is on there and it works perfect once you replace it with that one. Some mods may still be broken (the fov one I used needs an update for example)

• 
  Sybre Waaijer (@SybreWaaijer) reported 16 minutes ago

  @dannyvankooten Hi Danny! Yes, it's a known issue with WP 7.0. It's a "floating" title that dynamically calculates its offsets. It appears only when you input text, and it should take the appearance of the text input. In WP 7.0, they messed with the height and line height of the input fields, and the calculator doesn't account for these yet. The colored checkboxes on the SEO Settings page are also broken (but the next update makes them much better). And the new odd 3-color "modern" admin scheme lets the dynamic color scheme fall back to the old "fresh" one (because 3 isn't 4 -- this will also be much better in the next update). Some backstory: WordPress still doesn't provide a proper styling API. Many devs complained about these changes in various tickets, so I held off to see if they would be addressed (obviously, they haven't). Then WP 7.0's release was delayed, so I just kept developing new features, and my release schedule got messed up. Then GitHub Copilot announced major changes to its service, so I had to reorganize everything because I kept getting rate-limited (on their biggest subscription). To still make the most of it, I sprinted to launch another project (which turned into a marathon that consumed 1.216 billion tokens in 3 weeks—oops). All in all, this is why there's no update yet. TSF officially states that it's compatible with WP up to 6.9.4. The only thing that really changed with WP 7.0 is the jarring interface with the ever-so-more-jarring view transitions. I was secretly hoping they would revert all that, so I didn't feel the pressure to address it quickly. If anything, I'm eagerly awaiting a proper admin API, as any modern CMS should have. I just picked up development for TSF again. I still need to triage what's important and decide whether to release an update sooner rather than later.

• 
  subwxxf 🏴‍☠️ (@subwxxf) reported 17 minutes ago

  @ItakGol a bunch of nerds doing **** for free on GitHub because they're not working

• 
  Techjunkie Aman (@Techjunkie_Aman) reported 18 minutes ago

  Over 400 Arch Linux AUR packages were just compromised. And this is a reminder that open source doesn't automatically mean secure. Attackers reportedly hijacked package maintenance and injected malware capable of: • Stealing GitHub credentials • Extracting SSH keys • Harvesting browser cookies • Accessing Slack, Discord & Teams data • Collecting VPN credentials • Deploying an eBPF rootkit The scary part? Many developers install AUR packages without reviewing every PKGBUILD. Affected systems may have exposed: • GitHub tokens • npm credentials • Docker & Podman secrets • HashiCorp Vault tokens • SSH artifacts • Browser session data If you're running Arch or an Arch-based distro and recently installed AUR packages: • Audit installed packages • Check for indicators of compromise • Rotate credentials immediately • Consider a clean reinstall if rootkit activity is suspected This isn't an Arch Linux problem. It's a software supply chain problem. One compromised package can put thousands of developer machines at risk. Do you review PKGBUILDs before installing AUR packages, or do you trust the community by default?

• 
  bluehatone (@bluehatone) reported 18 minutes ago

  Stop one giant bot. Hire small AI employees with one job in Hermes. Route tasks in Slack, Telegram, WhatsApp. Run on local, Docker, SSH, Singularity, Modal, or Daytona. Security AI runs pip audit and npm audit, files GitHub issues. Not magic. Measure results.

• 
  Danzel (@CryptoDanzel) reported 19 minutes ago

  @MageArez @veryvanya @github i don't understand how this is at 12k i might be slow in the head or something

• 
  Nikiton (@Nikitont) reported 24 minutes ago

  I PARSED EVERY SKILL ON GITHUB, CLUSTERED THEM AND RAN EVALS. THE RESULTS ARE NOT WHAT YOU EXPECT. • 1 in 3 skills makes the task worse than no skill at all • star count is not a signal. not even close. • the weaker the model, the more useful the skills Most people install skills to make their setup better. A third of them are actively making it worse. The skill marketplace has a quality problem nobody is talking about.

• 
  Sir Yusuf (@yusufxdev) reported 25 minutes ago

  digitalocean support told me they’re winding down their participation in the github pack and credits will expire on july 31 2026 check your billing credits page so you don’t leave paid resources running after that