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:

• 
  Asad (@meranaamkhann) reported 8 seconds ago

  Let's see what people are building these days!! Drop your project link or github Links down here

• 
  David O. Ehibor 🇦🇷 (@grayontop_) reported 57 seconds ago

  GitHub Copilot didn't make developers faster It made slow developers more confident about writing bad code quickly 😭

• 
  Rohan (@proxy_vector) reported 7 minutes ago

  @aminnnn_09 Fork = a server-side copy under your GitHub account. Clone = a local copy on your machine. You fork when you need your own remote lineage, and clone when you want to work on code locally.

• 
  SOURAV PANDA (@i_d_skp) reported 10 minutes ago

  Scenario: You accidentally committed a plaintext database password to GitHub in a .tf file. Fix: Nuke the commit history immediately! Use environment variables (TF_VAR_db_pass) or fetch secrets dynamically at runtime from AWS Secrets Manager or HashiCorp Vault. 🔑 #Terraform

• 
  Alexey Samoylov (@metalagman_dev) reported 10 minutes ago

  @geminicli Antigravity CLI is a trash, closed source, full of bugs. They don't even read issues on the github.

• 
  Pascual ⚡ (@0xPascual) reported 16 minutes ago

  A high school kid opens an account, plugs in Claude 5, and turns a few hundred dollars of lunch money into a six-figure trading account over the weekend. The screenshot goes viral, the replies fill up with people begging for the GitHub repo, and the standard engagement-bait influencers declare the dawn of the sovereign teenage day-trader. The media thought that was the story. It was not. The real flex wasn't the macro strategy or the directional bets on currency pairs. It was the setup behind it: a lightweight proxy array routing through residential IPs to dodge exchange rate-limiting, paired with a custom parsing engine that instantly translates raw order-book imbalances into executed micro-hedges. The kid wasn't trading; he bypassed the entire institutional pipeline of risk management, brokerage compliance, and analyst overhead with a single configuration file. The entire operation runs on a continuous loop of multi-agent orchestration. A master instance drafts the execution logic, a secondary validation agent checks the code against real-time oracle feeds, and a fleet of worker APIs executes up to 3,210 trades a night. Total infrastructure cost: roughly $45 in API tokens and a cheap server instance. It extracts a 78% win rate out of systemic market inefficiencies, operating with a structural margin that legacy trading desks weighed down by salaries and compliance boards cannot compete with.

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 17 minutes ago

  @TheEthanDing distributed systems at github scale make five nines almost impossible. the skill issue crowd has never run anything millions of people hit in the same second

• 
  rapaya (@rapaya) reported 20 minutes ago

  OpenCode connects to LSP so the AI gets your actual compiler diagnostics in real time — type errors, warnings, the full signal your editor sees. Terminal-based, 75+ model providers, 160K GitHub stars, open source.

• 
  Andrew (@openmarmot) reported 22 minutes ago

  @AndrewCurran_ I use grok every day to research software changes/github issues/software doc research. It is very good at real time data search. Might be SOTA in this niche. Hardly a failure. Meanwhile LeCun only surfaces to let out more hot air. A very forgettable person.

• 
  Jose (@SolutionsCay) reported 23 minutes ago

  Two changes to how I work with agents: 1. GitHub App so the agents manage issues directly. Keeps the repo clear of throwaway spec and todo files. 2. EmDash (Cloudflare's serverless WordPress successor) for internal docs. Runs on D1, just SQLite under the hood, so I can export the content and move it anywhere. No more docs sprawl.

• 
  Krish Subramanian (@krishnan) reported 24 minutes ago

  Software engineers got automated first. Not because the work was hard. Because it was easy to grade. Everyone blames the missing union. Coders never organized; doctors, lawyers, and electricians did. That is half the story, and the wrong half. Two things get mashed together here: how easy a job is to automate, and who sets the terms when it happens. Take the first. Code is text. The training data sat on GitHub, free. And code grades itself. A compiler and a test suite tell a model in seconds if it was right. That feedback loop is rocket fuel for machine learning, and almost no other job has one. A nurse does not come with a test suite. The result shows. On SWE-bench Verified, a set of real GitHub issues, top agents went from about 20 percent in August 2024 to near 90 percent by early 2026. Human developers score around 67 to 70 percent. The machines have passed us. And the people who built these systems aimed at their own jobs first. The damage is not a prediction. Stanford's payroll data shows employment for developers aged 22 to 25 down nearly 20 percent from its 2022 peak. Now the comfortable read: seniors are fine. Workers over 30 are holding steady. For now, AI writes the code and seniors supply the judgment. "For now" is carrying that whole sentence. Seniors feel safe because the tools write code but cannot yet own messy, ambiguous, system-level problems. That is a line moving up, not a wall. Every benchmark shows models climbing toward harder, multi-file work. Senior judgment is the next rung, not a different ladder. Kill the bottom rung and you kill the pipeline that makes seniors at all. So, the union question, framed properly. A union could not have stopped this. A picket line does not repeal a capability. What it changes is the terms. In 2023 the Writers Guild cut the first real AI deal in any industry. They did not ban the tech. They won this: a studio cannot force you to use AI, AI output cannot take your credit or pay, and the company must give notice first. Engineers won none of that. So the capability landed on the employer's schedule. No warning. No floor. No severance. No seat. Exposure and protection are different levers. Most of us have neither. The juniors already know this. The seniors are next.

• 
  lollipop (@immlollipop) reported 25 minutes ago

  🚨HACKERS MOCK OZEMPIC MAKER FOR "NOVO123" PASSWORD Hackers breached Novo Nordisk in March via a stolen GitHub token and just leaked 264 GB of data while mocking its weak security. The attack ran for over 2 months. - The hackers say Novo Nordisk used simple passwords like "novo123" on critical systems - Source code and proprietary details on Ozempic and pipeline drugs were stolen - Clinical trial data on employees, doctors, and patients got exposed - Private internal AI models from the company were also taken This breach shows how a single weak password can bring down even the biggest names in pharma

• 
  Gitbank (@Gitbank_io) reported 25 minutes ago

  Community update — GitStock delay + what we have been building First, we owe you an honest update. We promised GitStock would ship earlier and we went quiet. That was on us. No excuses, we were heads down in the contracts and infrastructure and did not communicate well. That changes today. Here is what actually took time. We refused to ship GitStock on top of third-party APIs or borrowed infrastructure. Everything you see in Gitbank; the vault, the relayer, the swap engine, the RWA layer runs on smart contracts we wrote, audited ourselves, and deployed. The GitVault contract is verified on Basescan. The GitStockFactory is verified on Basescan. You can read every line. No black box. No external custody API holding your assets behind the scenes. That decision slowed us down. We think it was the right one. On security specifically. Your funds sit in a soul-bound smart contract vault anchored to your GitHub ID. Transfers are disabled at the contract level — not by a rule in a database, by the EVM itself. We also built private transaction routing directly inside GitVault on Base. No Tornado, no third-party mixer, no privacy-as-a-service API. The privacy logic lives in our own contract. You can verify it. The relayer signs and submits transactions on your behalf so you never pay gas, but the keys to your vault are yours. We hold nothing. If you want to verify any of this: check our contracts on Basescan, check our GitHub, check the bytecode. We are open source. The code is the proof. GitStock ships tomorrow.

• 
  wispem-wantex (@wispem_wantex) reported 27 minutes ago

  I think a reasonable compromise would be to henceforth hold Anthropic responsible for any security breaches or service outages. Every time Github goes down, Anthropic should be fined

• 
  Kelvinsekx (@kelvinsekx) reported 27 minutes ago

  Just read a nestjs codebase on github. Most it written with Claude. AI doesn’t save you guyz from mess. 1. Bloated logger. Why make logger a service when you could just import and initiate. Eazy 2. They didn’t hash the password before registering a user. But did on login