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:

• 
  Noctum (@Noctum_io) reported 3 minutes ago

  noctum's smart contracts have been analyzed using two automated static analysis tools: Slither and Aderyn. these tools scan Solidity source code and compiled bytecode for known vulnerability patterns reentrancy, unsafe external calls, integer handling issues, access control gaps, and others. neither tool returned critical findings on the pool contracts, the Groth16 verifier, or the Poseidon hasher. the analysis results will be published when the formal writeup is complete. it is important to be precise about what this means. automated static analysis is a useful and important first pass. it is not a security audit. a security audit is a manual review by an independent firm that thinks adversarially about the system, models attacker behavior, and produces a signed report. noctum has not yet commissioned or completed a formal audit. stating otherwise would be false. this work is on the roadmap. the ZK circuit has not yet been reviewed with circomspect, a static analyzer specifically designed for circom circuits. circuit bugs are a distinct class of vulnerability from contract bugs a flawed constraint system can allow invalid proofs to pass verification. circomspect is pending. the trusted setup is also a known limitation: the ptau used is from the Hermez ceremony, but the zkey was generated with a single party locally. this is not a multi-party trusted setup, which means the toxic waste from the ceremony cannot be proven discarded. real ETH deposits carry this risk and users should understand it. the contract addresses, circuit source, deployment scripts, and zk-deployments.json are all public in the GitHub repository. the Groth16 verifier bytecode is deterministic from the circuit anyone with the source and zkey can recompile and verify the deployed bytecode matches. the goal is to make every security assumption visible so users can make informed decisions. an honest security disclosure at this stage is worth more than a false sense of completeness.

• 
  Michael Brod (@adhoc97) reported 5 minutes ago

  satya intentionally cannibalizing github copilot with usage based pricing could go down as one of the biggest brain moves in history the reaction was as predictable as anything - customers hate it, it turns out tokens are expensive, and completely shifts the narrative on the market who can now see that without massively subsidized pricing (today), customer economics are brutal who does this macro narrative shift hurt the most?

• 
  Zodl (fka Zashi) (@zodl_app) reported 6 minutes ago

  Zodl v3.5.1 is now available on the App Store for iOS and on GitHub for Android. Google Play is currently reviewing the update and should release it shortly. With the Zcash network upgrade complete, updated wallet software is required to spend Orchard funds under the new consensus rules. After updating, Zodl will work as expected for sending and receiving ZEC via Orchard. As infrastructure comes back online, you may experience occasional delays. If so, run a Server Test and select the best-performing server under: Advanced Settings → Choose a Server Please note that any Orchard transactions attempted during the network upgrade window were not mined. If you are unsure about the status of a transaction, verify the TXID on the blockchain or contact @zodl_support.

• 
  Devanshu (@DevanshuXi) reported 9 minutes ago

  Someone else built the geospatial indexing system. Someone else open-sourced the hex grid math. Someone else solved large-scale routing, spatial partitioning, and low-latency location systems. We just pip installed it, add a .in domain, raise a Series B, and start calling ourselves “deep tech.” The entire “hyperlocal revolution” is basically Uber’s H3 library with Google Maps API and a React Native frontend, and underpaid engineers who are gluing SDKs together for peanuts. That’s not breakthrough engineering but an integration work with a marketing budget. If you carefully notice, The moat isn’t technology here. Its the investor money, delivery fleets, and who can burn more cash before the next funding round. Real engineering is building the distributed systems underneath these abstractions. Designing the indexing algorithms, Writing the networking stack, Solving the scaling problems before they become libraries on GitHub. That work mostly happened elsewhere. We just imported it and turned it into a valuation deck. The worst part is the talent absolutely exists here. Some of the smartest systems engineers and researchers I’ve met are Indian. But instead of funding original research or infra work, the ecosystem rewards copycat apps and “AI-powered” wrappers and Hex-GM Copies. Then people wonder why ambitious engineers leave the country.

• 
  Anoy (@Anoyroyc) reported 9 minutes ago

  @davj the part about trust breaking down is so real. once devs stop believing your docs they just go straight to discord/github issues instead

• 
  MarMar Labs (@MarMarLabs) reported 9 minutes ago

  If you use GitHub Copilot, the model behind "Auto" in your editor may no longer be an OpenAI one. At Build on June 2, Microsoft shipped MAI-Code-1-Flash — its own coding model, reportedly built without OpenAI tech — and started routing it into Copilot's model picker and Auto picker in VS Code. What it means if you ship with Copilot every day: - The default isn't neutral anymore. "Auto" now routes among first-party Microsoft models too, not just OpenAI and Anthropic. The model that runs when you don't pick one just changed. - Microsoft benchmarked it against Claude Haiku 4.5, not GPT — claiming a +16-point SWE-Bench Pro lead (51.2% vs 35.2%). The frame is "cheap, fast tier," not frontier. - It's tuned for token efficiency: "up to 60% fewer tokens" on harder problems via adaptive solution length. On Copilot's new token-metered billing (live June 1), a model that finishes in fewer tokens isn't just faster — it's literally cheaper on your meter. Connect the two June moves: Copilot went token-metered on the 1st, then got a first-party token-efficient model on the 2nd. Whatever the intent, the result is the same — Microsoft now controls both the meter and a model built to spend less on it. For builders, the takeaway isn't "new model." It's that your default coding surface is being quietly re-platformed under you — and "which model am I actually running, and who made it?" is now a question worth checking, not assuming.

• 
  BluePort AI (@BluePortAI) reported 11 minutes ago

  The biggest announcement at Microsoft Build 2026 today is Project Polaris. Microsoft's own AI coding model and it replaces GPT-4 inside GitHub Copilot by August 2026 The strategic significance is hard to overstate. Microsoft invested $13 billion in OpenAI. GitHub Copilot is one of the most successful AI products ever shipped and every token it has ever generated was paid for by Microsoft and sent to OpenAI. As Copilot scaled to tens of millions of developers and unit economics broke (GitHub Copilot just transitioned to usage-based billing yesterday), the math stopped working Today Microsoft formally announced the model that solves the problem Microsoft created...by building its own. Multiple outlets are framing it directly, "Project Polaris cuts the OpenAI cord" Combined with the MAI v2 stack also confirmed today, MAI-Image-2.5, MAI-Voice-2, MAI-Transcribe-1.5. Microsoft now has homegrown alternatives to every major OpenAI product it has historically embedded in its own platforms Microsoft just told the industry it no longer needs OpenAI to ship its most important AI products $MSFT

• 
  ./can (@shcansh) reported 13 minutes ago

  Local development is shifting from a coding task to an agent-coordination problem. The new Agents window in VS Code lets you run more than 1 agent session side-by-side, while the open Agent Host Protocol standardizes how these sessions sync. Combined with air-gapped BYOK models, GitHub is turning the IDE into an autonomous control room. But does orchestrating multiple agents actually speed up shipping, or are we just trading writing code for a more complex debugging bottleneck? #VSCode

• 
  John (@twatdipper) reported 16 minutes ago

  Had to code by hand today because I'm out of GitHub copilot credits and my employer doesn't want to pay for more, it was terrible 😭

• 
  Ed Zynda (@what_the_func) reported 18 minutes ago

  I don't know if it's some kind of scam or not or what their angle is but I keep getting vuln reports for MCP Go, an OSS MCP package for Golang. Just file a ******* issue in Github bro, I ain't reading your long *** ******* email that's probably AI slop.

• 
  Zypheen (@Zypheen_) reported 20 minutes ago

  @robdezendorf fix dex screener and link your profile and github, someone random paid dex and linked a drainer. dev or someone fix this plz ES6ZcfTUTVET37RaYW9qDhX1DBBDEaTuvg87Lw9epump

• 
  doublemover (@doublemover) reported 20 minutes ago

  Damn codex github issues are becoming a ****** garbage dump. Some ****** retard has what I can only assume is openclaw chiming in with useless bullshit on every issue

• 
  FluxA (@FluxA_Official) reported 20 minutes ago

  FluxA Feature Update--Wallet 1/ Wallet now supports GitHub and X as additional login methods. New registration still starts with Google. 2/ Credits can now be topped up via Stripe. 3/ Recovery now supports USDBC. More flexible login, easier credit top-ups, and better recovery coverage for agent payments. Keep building.

• 
  MalomeRJ (@Malome_RJ) reported 21 minutes ago

  @CraftedByO @khabubu_phathu @github I’ve been using Zed and Deepseek V4. Been treating me good wit less issues

• 
  spring.furrest.net (he/him) (@springdotgay) reported 22 minutes ago

  @moubuntu @phoronix @system76 Did you forget to send a bug report/issues on popos's github repository? They're very much useful since devs can fix your issue and it shouldn't happen yet again