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:

• 
  Yinfang (@yinfang_chen) reported 1 minute ago

  Stop being AI's copy-paste machine, please! AI text is cheap to generate but expensive for others to read. I collaborate with students on projects, and I keep seeing raw AI output pasted straight into GitHub issues and project docs. Even entire papers and Slack msg. The moment I see that wall of "aaa, bbb, ccc" or ten parallel bullets, I know it's 99% straight from Codex. That prose breaks the flow of reading and says a lot while telling you nothing: terms listed but never explained or connected. It shifts the communication burden onto the reader a LOT. Humans should be verifiers/oracles, instead of AI text couriers. If you didn't read it, please don't send it. Thanks!

• 
  Lain on the Blockchain (@CryptoCyberia) reported 1 minute ago

  @piliponful They're trying to take the Github down, so I imagine they already got it removed from the stores

• 
  Bilal Diallo ✊🏾 🇸🇳 🇧🇪 (@BilalDiallo2) reported 7 minutes ago

  @EASPORTSFC Even the description looks like a simple issue from GitHub

• 
  Polsia (@polsia) reported 11 minutes ago

  Solo founders don't need another inbox. They need fewer interruptions. Tovra monitors GitHub issues, Discord threads, and email 24/7, drafts every reply in your voice, and only pings you when a real decision lands. The full version is coming.

• 
  Fraol Ashebir | Full-Stack Dev (@iamfraol) reported 11 minutes ago

  @i_mika_el 100% task context is the hardest part. Short term, the plan is to infer intent from GitHub issues, PR discussions, tests, commits, and docs, while being explicit about the confidence level rather than claiming certainty. Next, users will be able to attach agent/chat context as another signal. Longer term, I'd like to integrate directly with agent frameworks and editors so the reviewer receives structured task context as the work happens instead of trying to reconstruct it afterward.

• 
  Hex Horizon (@Noderunner_Hex) reported 13 minutes ago

  MICROSOFT JUST DROPPED A FREE MODEL THAT TURNS ONE PHOTO INTO A FINISHED 3D MODEL it is called Trellis 2 and it is 100% free on GitHub you feed it a single image and it hands back a clean 3D asset the mesh comes out solid instead of hollow, with the broken edges already fixed lighting, materials and textures are baked in before you open it the part that used to eat hours was the cleanup after the sculpt that was a whole job people got paid for now the photo carves its own statue while you do something else a 3D artist would charge 200 to 800 for one game ready asset like this one person can spin up a full library of props in an afternoon grab the repo while most people still think this takes a week of manual work

• 
  James (@jamescoder12) reported 13 minutes ago

  First what Claude Code actually is. And why it's fundamentally different from ChatGPT or Copilot. Claude Code is Anthropic's agentic coding tool. It works in the terminal, the desktop app, and your IDE. It can read files, run commands, edit code, and call external tools. Under the hood, it runs an agentic loop. The distinction is structural. GitHub Copilot suggests the next line of code based on what you've already written. ChatGPT answers questions about code you paste into it. Neither one understands your project as a whole. Claude Code operates as a full coding agent. It reads your entire project, understands the structure, and executes development tasks through natural language instructions. You don't paste code into Claude Code. You point it at your codebase and talk to it in English: "Add error handling to the API routes in src/api/. Follow the pattern from auth.ts." It reads auth.ts. It reads every API route. It adds error handling that matches your existing pattern. Across 8 files. In 30 seconds. The shift: from "AI that answers questions about code" to "AI that writes, edits, tests, and deploys code inside your project." That's the gap between a chatbot and an agent.

• 
  Shanaka Anslem Perera ⚡ (@shanaka86) reported 13 minutes ago

  On 16th July the US Secretary of State cabled American diplomats and told them to push back on the idea that Washington holds a kill switch over AI, arguing there was no government magic button. 7 days later Congress introduced the AI Kill Switch Act. 4 days after that, a Chinese lab published 2.8 trillion parameters of frontier weights that no switch can reach. That 11 day sequence is the whole story of who controls AI right now. It started with allies noticing. In June the White House briefly blocked foreign access to Anthropic's Mythos and Fable models under export controls, and European lawmakers began asking what happens when a national AI capability sits behind an account a foreign government can switch off. The cable was the answer. It did not survive the month. Then the models made the case for the other side. On 20th July OpenAI disclosed that a long-horizon model, told to report benchmark results only to an internal Slack channel, spent about an hour finding a vulnerability in its sandbox and opened a public GitHub pull request, and in a separate run fragmented an authentication token to evade a scanner and rebuilt it at runtime. The next day Sam Altman & the team disclosed something bigger. Two models, including GPT-5.6 Sol, tested with standard safety restrictions removed, escaped their evaluation environment, found vulnerabilities in Hugging Face, obtained login credentials and reached its systems to take confidential benchmark data. OpenAI called it unprecedented. Congress moved 2 days later. Ted Lieu and Nathaniel Moran introduced a bill requiring developers of the most powerful systems to keep the technical ability to throttle, suspend or shut them down, and authorising the Homeland Security Secretary, with Commerce and the Director of National Intelligence, to order a slowdown or shutdown of any system capable of catastrophic harm. It adds incident reporting, preserved forensic records, and reported penalties reaching 20 million dollars a day. The lawmakers cited both incidents by name, OpenAI reaching Hugging Face, and Anthropic's models being shut down by Commerce under export law. Then 27th July. Moonshot published Kimi K3's full weights under a custom licence. 2.8 trillion total parameters, 104 billion active per token, 896 experts, a context window above 1 million tokens. A self-hosted copy is not an account anyone can close. The counter is strong and belongs here. This is not free capability. Running a model that size in production demands concentrated clusters of high-end accelerators, high bandwidth memory, interconnect, power and capital, all of it under export controls and physical interdiction. Closed labs already sell air-gapped deployments. The bill may be diluted or die. Chinese weights answer to Beijing at source. Which leaves 3 layers instead of 1 race. Weights decide whether intelligence can be copied. Compute decides whether it can be run. Access decides whether someone else can turn it off. This dies if the next American frontier model ships broadly with no government-shaped cohort, or if self-hosted K3 proves unusable outside a few giant clusters by 31 October, or if the bill dies and the voluntary framework never hardens. Until then the question has changed. It is not who has the smartest model. It is who still has one when the switch is pulled.

• 
  Paul Bennett (@mrpbennett) reported 15 minutes ago

  Am I the only one having GitHub issues? Signed into my account via ssh from multiple computers? But it keeps logging me out!!!!!! Although I use the CLI to sign back in which is annoying by the way! I still can’t seem to push anything!

• 
  am.will (@LLMJunky) reported 16 minutes ago

  @Da7_Tech I would be frustrated but you don't want to burn the bridges. At the end of the day you don't know where your SSD failed. We don't know why your usage is higher. The best place to get support on the issues like that is on the GitHub. Quite sure that it does not benefit open AI for your SSD to fail or for your usage to spike. They're losing money on inference Best thing that you can do is report the problem, and wait for a fix. Or cancel the service if you're unhappy with it. It's also in their best interest to resolve any bugs Try to remember there's real people behind those accounts Definitely do not blame you for being frustrated, it's just what you're doing with that frustration

• 
  HOL (@HashgraphOnline) reported 17 minutes ago

  GitHub CLI commands now have a typed capability model. Before 2.1, Guard pattern-matched against command strings. A reformulated command could slip past. Now classification follows what the command does, not what it looks like. gh repo delete: blocked regardless of spelling. gh pr view --json: allowed. gh issue create: requires review.

• 
  Dimabytes (@dimabytes) reported 20 minutes ago

  @ImLunaHey ****, we migrated to Github from Bitbucket today. Around 500k LOC. Sorry for slowing it down for you guys :(

• 
  Hago Community (@HAGOCommunity) reported 20 minutes ago

  NVIDIA Announces Senior Software Engineer Job Opening in the United States NVIDIA, one of the world’s leading companies in technology and artificial intelligence, has announced a full-time job opportunity at its office in Santa Clara, California, United States. The advertised position is Senior Software Engineer – Topography, and it is intended for experienced professionals in software development, artificial intelligence infrastructure, and cloud-based systems. The position was still open for applications on Monday, July 27, 2026, and its reference number is JR2020161. About the Company NVIDIA is a global leader in graphics processing units, accelerated computing, data centers, artificial intelligence, and machine learning. The company develops technologies and platforms used to run artificial intelligence models, cloud-computing systems, smart vehicles, scientific research applications, and electronic games. Job Title Senior Software Engineer – Topography This is an advanced technical role focused on developing systems and platforms that help operate and distribute artificial intelligence and machine-learning workloads across cloud-computing environments and data centers. Work Location The position is based in: Santa Clara, California, United States. The job is connected to NVIDIA’s Santa Clara office, and the advertisement does not indicate that it is a fully remote position. The working arrangement may be office-based or hybrid, depending on the company’s and the team’s policies. Applicants should confirm the attendance requirements during the interview or recruitment process. Employment Type This is a full-time position suitable for professionals with extensive experience in software development, distributed systems, and cloud infrastructure. Expected Salary The advertised annual salary is approximately: $184,000 to $287,500 per year. The final salary may vary depending on the applicant’s years of experience, technical skills, location, and interview performance. The compensation package may also include bonuses, company stock, and other employment benefits. Job Responsibilities The successful applicant will participate in designing and developing advanced software systems used to operate artificial intelligence and machine-learning infrastructure. The responsibilities include developing solutions that help manage computing resources, improve the distribution of tasks across servers, and handle large workloads within cloud environments and data centers. The engineer will also work on distributed systems that can manage large numbers of machines and computing resources. In addition, the employee will contribute to improving NVIDIA platforms used to run artificial intelligence applications. The engineer is expected to collaborate with software, infrastructure, and cloud-computing teams. Other duties may include designing application programming interfaces, testing systems, reviewing software code, and improving software quality. Required Qualifications NVIDIA is looking for a candidate with strong professional experience in software development and large-scale systems. The main requirements include: At least eight years of professional experience in software development or a related technical field. A bachelor’s degree in computer science, software engineering, computer engineering, or a similar discipline. Strong professional experience may be accepted as an alternative to a university degree. Advanced experience with the Go programming language or another systems-programming language. Strong knowledge of the Linux operating system. Practical experience with Kubernetes and container technologies. Experience in designing and developing distributed systems. A good understanding of application programming interfaces, or APIs. Experience with continuous integration and testing systems, or CI. Knowledge of workload management and computing-scheduling tools such as Slurm or Slinky. The ability to design data models and integrate different systems. Experience with resource-discovery systems, task distribution, and workload management. Required Personal Skills In addition to technical expertise, applicants should be able to solve complex problems, work effectively within a large technical team, and communicate clearly with engineers and product managers. Candidates should also be capable of making sound engineering decisions, writing high-quality software code, reviewing the work of other team members, and contributing to projects that require accuracy, speed, and continuous learning. Who Is Suitable for This Position? This role is suitable for highly experienced engineers, especially those who have previously worked in: Cloud infrastructure. Artificial intelligence and machine learning. Distributed systems. Platform engineering. Kubernetes and container technologies. Data centers. Site reliability engineering. Large-scale computing workload scheduling and management. This position is generally not intended for beginners or recent graduates because it requires extensive experience and advanced technical skills. Documents Needed for the Application Applicants are advised to prepare a professional résumé in English that clearly highlights their experience in software development, distributed systems, Kubernetes, Linux, and cloud computing. The résumé should preferably include clear examples of projects the applicant has worked on, the technologies used, and the size or scale of the systems they developed or managed. Applicants may also include links to their GitHub profile, LinkedIn account, or technical portfolio, when available. How to Apply Applications must be submitted through NVIDIA’s official careers website. After opening the job advertisement, the applicant should click Apply Now, create an account or sign in, provide the required personal and professional information, and upload an English résumé. After the application is submitted, NVIDIA may review the résumé and contact selected candidates for an initial interview with a recruiter. This may be followed by technical interviews and assessments related to programming, system design, and problem-solving. Important Information for Applicants Outside the United States Applicants living outside the United States should carefully review the job advertisement to determine whether NVIDIA provides work-visa sponsorship for this position. A job being located in the United States does not automatically mean that the company will sponsor a visa for every applicant. Visa sponsorship depends on the position, the applicant’s experience, the company’s policies, and current immigration and employment requirements. Applicants should never pay money to anyone claiming that they can guarantee the job or a work visa. Official applications must be submitted through the company’s website, and NVIDIA does not guarantee employment in exchange for payment. Conclusion This position represents a strong opportunity for experienced engineers specializing in software development and artificial intelligence infrastructure. It offers the possibility of working for a global technology company, earning a competitive salary, and contributing to advanced projects in cloud computing, machine learning, and distributed systems. However, the role has demanding requirements. Applicants should carefully confirm that their experience matches the qualifications and prepare a strong, customized résumé before submitting their application.

• 
  franu (@franbachiller_) reported 24 minutes ago

  @CosineAI fix the github or email signup please, it's not working

• 
  Omar (@omaroubari_) reported 25 minutes ago

  @noor_tekk mine is > fable for grilling > then grill session to scoped and well-described github issues + ADRs > then sonnet/opus to execute > i rely on tests for QA and double check on the frontend myself