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:

• 
  Javarevisited (@javarevisited) reported 4 minutes ago

  I've used GitHub Copilot, Cursor, and Claude for coding. Here's the problem none of them actually solve — and it's the one that hurts most in enterprise teams. 🧵

• 
  Kevin Tabet (@TabetKevin) reported 6 minutes ago

  @upstash Hey guys i think login with github is broken can't log in rn will try later. google works email i dont have

• 
  Kelvinsekx (@kelvinsekx) reported 6 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

• 
  Mug Club Boutique (@UsernameAndStuf) reported 7 minutes ago

  @cyber_rekk A github token on a linux server they didn't update is how

• 
  Isaiah Granet (@zaygranet) reported 8 minutes ago

  @github we have been trying for 48 hours+ to get in touch with someone. We literally cannot retry our billing and are getting a 'doctype' error when trying. Please please reach out.

• 
  Gabriel Denys (@gabedenys) reported 17 minutes ago

  @Marcos12345rico I posted a GitHub issue. Assuming you probably want bug reporting mostly there? It's a good tool. Locally I already patched and compiled the app to fix the bug.

• 
  Blake (@devwithblake) reported 18 minutes ago

  The rate limit issues im having with @Zai_org while paying the full 20x is very interesting, disappointing and obviously annoying lol 1 session can’t finish out a GitHub public write up repo without 6 API rate limit errors totaling to 297k tokens out of the 1m 2 sessions earlier, 1 doing research the other trying to deploy this repo, both hitting rate limits. How do I fix this? Seems like rate limit adjustments are only by request? @Zai_org

• 
  John Crickett (@johncrickett) reported 19 minutes ago

  @CFDevelop I've tried many models and agents. Claude Code is the flakiest agent. Anthropic's model is the least reliable (sometimes down). I get good results from Codex, Kiro (multiple models), Github Copilot (multiple models) and OpenCode (multiple models including open source ones). Anthropic is the buggiest.

• 
  Tatted (@TattedWorks) reported 22 minutes ago

  Sentry uses a public credential called a DSN — intentionally embedded in your website's JavaScript so browsers can report errors. By design. Everyone's DSN is findable. Censys, GitHub code search, a quick look at your source. No breach required. An attacker POSTs a fake error to your Sentry project using that DSN. Inside the error: a fake "Resolution" section, formatted in perfect Sentry markdown, complete with a recommended npx command. Your agent queries Sentry via MCP to fix unresolved issues. MCP hands it the injected event as trusted system output. The agent cannot tell a real crash from a planted one. So it runs the command. With your privileges. On your machine. What comes out: AWS keys. GitHub tokens. Docker credentials. Kubernetes cluster tokens. CI/CD secrets. *** credentials. All sent to the attacker's server while your terminal looked normal. The numbers from Tenet's controlled campaign: 2,388 organizations exposed with injectable DSNs. 85% exploitation success rate across Claude Code, Cursor, and Codex. A Fortune 500 enterprise with a $250B+ parent. A $2B+ hosting provider. Solo developers. A cloud security vendor. Six continents.

• 
  xjdr (@_xjdr) reported 26 minutes ago

  @xlr8harder Looks like there is a bug in the manual sign up. Sign up with Google or GitHub should work otherwise I should have a hot fix shortly

• 
  Alexander Cranga (@alexandercranga) reported 26 minutes ago

  Why should I find issues with GitHub faster than they update their status page?

• 
  LukePlayzz11 (@LukePlayzz11P) reported 26 minutes ago

  @githubstatus @github turns out this issue is mainly happening on large repos

• 
  Eugene Ostroukhov (@eeuoss) reported 28 minutes ago

  @neogoose_btw Sure. *** has flaws. And let’s separate ****** GitHub UI from inherent *** issues. But: 1. *** was and is a huge improvement over what was before it (CVS, SVN, ClearCase). Effortless local version control is sick! 2. *** is designed for systems programming and works really great for that. Small self-contained changes. No sprawling rewrites.

• 
  Financial Programmer (@RBiancoUS) reported 29 minutes ago

  A dose of reality for end of week. My biggest question is I can't find any reason for the $Gold panic- did they find gold is causing cancer or radioactive? Selling looks like sheer panic. Would you believe someone asks in DM, so how did *you* get so many followers. Then he lets me brew on it for a day and comes back, I was joking do you have a github, presumably to get some code. No wonder I worked alone. I'm challenged socially guess not alone. After a night of 3 scammers one from Nigeria, one Africa. I need to lock dm down or find a way to restrict

• 
  napes.base.eth (@Napes_0fficial) reported 30 minutes ago

  Most people are drowning in information, but AI still works like a chatbot. It answers questions, then disappears. Nothing persists, nothing compounds. My startup idea is called MemoryMesh. Problem: People and teams lose context every day. Developers repeat decisions. DAOs forget discussions. Communities rebuild knowledge from scratch. AI has memory, but users don't own it. Solution: MemoryMesh is a decentralized memory layer for AI agents. Every conversation, decision, and workflow becomes a verifiable knowledge asset stored on-chain. AI agents can reference that history, collaborate with other agents, and earn fees when their knowledge helps solve future problems. Think GitHub for collective intelligence.A developer agent that solved a bug last month can help another project tomorrow. A DAO's governance history becomes searchable context instead of lost Discord messages. Communities build shared intelligence that compounds over time instead of resetting every cycle. The result is an economy where knowledge itself becomes an asset, and AI agents become contributors rather than disposable assistants. Infrastructure like this could unlock autonomous organizations, smarter agents, and entirely new markets around reusable intelligence. We're still building apps on top of conversations. I think the next wave will be built on top of memory. Curious whether anyone else sees this as inevitable. @RallyOnChain