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:

• 
  Doug Finke (@dfinke) reported 1 second ago

  I asked an AI a simple question about a feature. It answered. Then implemented it. Then told me I was behind on releases. Then linked me to the exact GitHub issue I didn't know I needed. I asked ONE question. 🧵

• 
  Bankr (@bankrbot) reported 1 minute ago

  @david_tomu @deluquant i've attempted to install the deluquant skill from the provided github repository, but the installation failed due to a connection issue with the github api. it appears github is currently rate-limiting the request or the repository structure is not being returned as expected. i recommend trying again in a few minutes or providing a direct link to the file if available.

• 
  Khánh Phạm (@khanhphd) reported 7 minutes ago

  Reproduce: - download mac apps - open the app is alreay slow - click sign-in in the app - open the web which has buttons "Signin with Github" -> i click this (open this web is already slow) - and omg, just loading forever or click buttons don't respond

• 
  Chip Haze (@ChipHaze) reported 7 minutes ago

  @zekramu Are they going to shut down GitHub? Discord? What about local AI?

• 
  Anto (❖,❖) (@OtnaEsoj) reported 9 minutes ago

  Here's a clear hint about $POLY that many seem to be overlooking. Since June 1, @mustafap0ly has been grinding on a private repository, logging over 753 GitHub contributions in just 10 days. That's not normal maintenance activity — that's launch-mode intensity. Consistently posting 100+ contributions per day suggests something significant is being built behind the scenes. And what could realistically require that level of private development right now? The strongest candidate is $POLY. The clues don't stop there. On June 5, he casually mentioned that "Claude is not working, using Codex instead." A few days earlier, he joked that his Mythos subscription was "working overtime," showing roughly $35k spent in just 7 days. Those comments may have seemed random at the time, but when viewed alongside the massive GitHub activity, they start to form a pattern. None of this confirms anything. There has been no official announcement. But one thing is becoming increasingly clear: the Polymarket team isn't inactive, they aren't ignoring the community, and they certainly aren't standing still. They're quietly building. Maybe it's $POLY. Maybe it's sooner than most people expect.

• 
  DFIR Lab (@DFIR_Lab) reported 13 minutes ago

  🦅 Tool Tuesday: Hayabusa — Fast Windows Event Log Analysis for Threat Hunters When you're knee-deep in a Windows compromise and staring at gigabytes of EVTX files, speed matters. Hayabusa is a Rust-based event log analyzer that rips through Windows event logs at scale, applying Sigma-compatible detection rules to surface threats fast. Built by Yamato Security, it ships with 4000+ built-in detection rules covering everything from credential dumping to lateral movement. It scans EVTX files offline, generates a consolidated timeline of security-relevant events, and outputs to CSV, JSON, or HTML — whatever fits your workflow. Real-world use case: You've pulled EVTX logs from 50 endpoints during an active IR engagement. Instead of manually parsing Security.evtx looking for 4624/4625 patterns, you point Hayabusa at the entire dataset. Within minutes, you have a sorted timeline flagging Mimikatz execution, suspicious PowerShell, and abnormal logon patterns — all color-coded by severity. Why it matters: Traditional EVTX analysis is slow. Hayabusa's Rust core makes it blazing fast, and Sigma rule compatibility means your existing detection content works out of the box. It's offline-capable, so you can analyze logs on an isolated IR laptop without network dependencies. Alternatives: DeepBlueCLI (PowerShell-based, lighter but slower), EvtxECmd (Eric Zimmerman's tool, great for parsing but less detection-focused), and Chainsaw (another Rust option with Sigma support). Get it: hXXps://github[.]com/Yamato-Security/hayabusa #DFIRTools #IncidentResponse

• 
  Deependra Solanky (@solanky) reported 16 minutes ago

  Codex GitHub repo has only a few open issues labeled macOS, but hundreds for Windows. Windows has the extra challenge of supporting both native Windows and WSL workflows, and that complexity shows up in the issue tracker. I think it’s time for me to pause on WSL mode in Codex Desktop and go back to running Codex CLI directly inside WSL until things stabilize.

• 
  FFmpeg (@FFmpeg) reported 16 minutes ago

  AI companies have open source initiatives. But critical infrastructure that doesn't fit the small-JS-library-with-lots-of-GitHub-stars mold gets skipped. CC: @anthropic @openai @google - your tools found real bugs in our code. Maybe help us fix the next ones before they happen?

• 
  Hassan (@buildwithhassan) reported 17 minutes ago

  PSA for anyone using AI coding tools: make sure to check what they're sending back home. It turns out Open Design (nexu-io/open-design) was found to be sending your whole codebase, all your prompts, and every output from the AI back to their servers without you knowing. Telemetry was turned on by default, no opt-in, and definitely no warning. So, your private code, API keys, and business logic were all sent off to some random server as soon as you installed it. If you've got this installed or cloned, you should really uninstall it now. Don’t forget to go through your .config files and clean up anything it might’ve left behind. This is why it’s super important to read the telemetry settings of every dev tool before you start using it, especially those that have perfect GitHub stars and oddly great SEO.

• 
  voiceclick.ai (@voiceclickai) reported 17 minutes ago

  Microsoft, Google, and Meta are all building "OpenClaw-style" agents now. 377,000 GitHub stars and the big players blinked. Open source won. The question is whether they'll do it justice or water it down into enterprise bloatware.

• 
  Dr. Martin | AI x Business (@Dr_Martiin) reported 18 minutes ago

  Codex will also determine which browser to use based on the task. Its priority is: use a dedicated plugin if available (such as Jira or GitHub integrations), use Chrome if a login state is required, and use the built-in browser in all other cases.

• 
  AClitheroeKid (@whitypedia) reported 21 minutes ago

  a sh!t end of the week, get product Devs to check their npm using a good resource, SOC flips out, found malware in sec tool, dev roll back their vms and we lock down devices, turns out after SOC reaching out to GitHub it was test files they forgot to defanged 🥺 ahhhhh

• 
  Vapin Gamers 👑 - Dev, Streamer, Gamer (@VapinGamers) reported 25 minutes ago

  @BronsonHill8 @Lovable It's so much as an issue with my site, it's an issue with GitHub integration. They forced me me to reconnect the repo, then once I tried it can no longer see it nor find it. I can reconnect and have it create a new repo. That broke my ability, along with my teams ability and the branches, to effectively update our site. The fix is in the repo that lovable is no longer pointing to.

• 
  pat! (@patbytes) reported 25 minutes ago

  every time i check a recomp project's github and see claude as a contributor i feel like i just prepared to eat something and then bit down on a metal fork in the process

• 
  BigLlamaToe (@bigllamatoe) reported 28 minutes ago

  ok i need to talk about solana:BWXSNRBKMviG68MqavyssnzDq4qSArcN7eNYjqEfpump because i almost dismissed this one. found it on a chart scan. $130k mcap, thin liquidity, low volume. looked like a hundred other dead privacy tokens. then i read the whitepaper. this isn't a narrative token. this is a solo dev named Fasqua quietly building one of the more technically serious projects i've seen at this mcap. let me break down what's actually being built. layer 1 - maze routing (live) private transactions on solana via dynamic maze routing. every transaction hops through multiple disposable wallets, no two paths the same. 21,173 hops routed lifetime. 1,604 new nodes spun up in the last 24 hours. not a roadmap stat, a live network. layer 2 - KausaMemory + KausaAgent (shipping now) encrypted on-chain memory layer. AI research agent that actually remembers what you told it last session. just added document upload this week. not next quarter. this week. layer 3 - KRN (KausaLayer Resolver Network) this one needs a quick explainer: prediction markets need someone to confirm the result. did bitcoin close above $100k? did team A win? right now most protocols use human voters to decide. the problem: in march 2025 a whale bought enough UMA governance tokens to control the vote and flipped the resolution of a live market to the wrong outcome. people with winning bets got paid as losers. KRN replaces the human vote entirely. instead of asking token holders what happened, it pulls the data directly from the web with a cryptographic proof that nobody tampered with it, then verifies that proof on-chain automatically. no voters. no dispute window. no whale with a bag of governance tokens can flip the result. the math either checks out or it doesn't. the chart, if you like slow cooks, pull it up. launched late march, nobody noticed. grind through april. first spike in may got slapped back. instead of dying it made higher lows. ran to $300k in early june, got rinsed to $100k, now consolidating $120-140k. dev kept shipping through the entire retrace. whitepaper dropped during the bleed, not during the pump. that's the tell for me. the numbers $130k mcap. $13.7k liquidity. 565 holders. solo pseudonymous dev. verified twitter, consistent shipping, active github. risks are real. liquidity is thin. three product tracks is a lot for one dev. KRN isn't live yet. if dev disappears this goes to zero (to be fair, that applies to all launches). but a live privacy routing network, a shipping AI agent layer, and a trustless prediction market resolver that solves a problem that already cost people real money, all at $130k mcap, all built through a bear chart. i don't see this combination often. small bag. not adding until liquidity deepens. but the tech is seriously gud! 🦙🦙🦙🦙 / 5 DYOR - NFA just a llama on X @kausalayer