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:

• 
  Gitbank (@Gitbank_io) reported 7 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.

• 
  Threadripper (@threadripper845) reported 8 minutes ago

  Nobody: Me: I'll gladly accept this high-responsibility open source maintainer role for zero compensation. Now I spend my weekends answering angry GitHub issues from developers who don't know how to read the README file.

• 
  Clayton (@Clay_Rebirth) reported 8 minutes ago

  @nullstance I basically used GitHub as a cloud storage as I didn’t want to bother but no problem, I’m on it

• 
  top10.dev (@Top10_Dev) reported 11 minutes ago

  @github Trending weights star velocity and push count. It does NOT weight account age, commit signatures, or maintainer reputation. That was fine when humans read the page. Now agents do. If your coding agent uses @github /trending as a hot-tool signal, `clash` and `dd` can reach a recommendation before a human ever sees them. The fix isn't at @github. It's a source allowlist in your retrieval pipeline + pin-to-version on any auto-suggested dep. #devtools #supplychain

• 
  Md Riyazuddin (@riyazmd774) reported 13 minutes ago

  7 GitHub repos that make Claude Code mass-destructively better. All free. Most people haven't installed a single one. Each one solves a specific gap that Claude Code doesn't fix on its own. Bookmark this thread 🧵

• 
  WoodenKbd. (@obiabo_immanuel) reported 13 minutes ago

  @developeraspire And that was the only issue codex found, i duplicated it some where so i can reproduce on a secure environment to see what the long action would be. After that codex suggested me to disconnect from my wifi (which is normal) that would terminate the connection and also to kill the process ID. But to be on a saver side, i wiped my PC and removed my SSH key from Github, i would rotate all sensitive datas. When i'm free i will try to look into the codebase well to see things, because that package has a minified code, i will see if an LLM can look into it further, or i just read more on the cute

• 
  Arti | AI Builder (@Artur_roses) reported 15 minutes ago

  Claude Code takes a GitHub issue and returns a tested, reviewed PR. No human in the loop. The new dev skill isn't writing code — it's writing issues precise enough that the agent ships what you actually wanted.

• 
  Steve Ruiz (@steveruizok) reported 18 minutes ago

  I would like @github's gh CLI to allow my coding agent to add screenshots and other media to my pull requests / issues. I know this is trivial to build and I will build it but IMO the social coding platform GitHub should have this as a feature

• 
  SyncSoft.AI (@SyncSoft_AI) reported 20 minutes ago

  June 1: GitHub Copilot switched to usage-based billing. Agentic workflows that loop through multiple model calls started burning through credits fast - some devs saw costs spike significantly overnight. The fix isn't a better pricing plan. It's cleaner training data that cuts correction cycles before they hit inference.

• 
  Jordan Ross (@jordan_ross_8F) reported 20 minutes ago

  Agencies running client accounts inside of GPT/Claude projects is a massive mistake. You'll look back on this and think about how dumb this was. At scale, you're sacrificing quality. A perfect example happened yesterday. A client of mine runs a content marketing agency. They uploaded a big pile of training documents into a Claude project to "train it." The plan was simple: copywriters use that project to write hooks for social. The COO reviewed one of the hooks recently, it sucked, told the copywriter it wasn't good and to run it through the project again. Next version: still crap. He knew something was broken. He just didn't know what, or how to fix it. Here's what he didn't understand. Context window This is the first thing you need to understand to understand why projects dont work. A context window is the AI's short-term memory. It's how much it can hold in its head at one time. Picture a monitor on a desk. Everything the AI is working with sits on that monitor — your instructions, your last message, the files it's looking at. A bigger model has a bigger monitor, but it's still a monitor. Pile too much on it and things begin to fall off. The AI can only work with what's on the monitor right now. Anything not on the screen doesn't exist to it. When the monitor fills up, the old stuff falls off to make room. What people call "memory" isn't really memory. It's just whatever happens to be on the monitor at that moment. So what is a Claude or GPT project? A project is the desk the monitor sits on. You drag your files into it — brand guides, past hooks, training docs. It feels like you're teaching the AI your business. You're not. The AI never reads everything on that desk. It can't. The desk is bigger than the monitor. When you ask a question, it reaches into a drawer, grabs a few pages that look related, sets them on the desk, and works off those. It never sees the rest. It often doesn't grab the right pages. It grabs the ones that look similar. Pattern-match, not judgment. It's guessing which scraps belong, then working off the guess. This is why uploading a stack of documents isn't training. Training rewires the AI's brain. It changes the thing itself. You cannot do that by dragging files into a project. All you did was fill a drawer. After you upload, the AI is exactly as smart as it was before. Same brain. You just gave it a bigger drawer to rummage through. And here's the counterintuitive part: a bigger drawer makes it worse at any single job, not better. More paper to sort through means lower odds it grabs the right page. The more you feed a project, the dumber it gets for the task in front of you. So what did you actually build? A search folder. You ask for a hook, it searches the folder, grabs the closest-looking data points and blends them into an answer. Search, then blend. Every single time. That's why running your agency's client processes inside a project falls apart. It was never built to store your context and call on it in a way that lets your company follow a consistent procedure. The Fix: Proper Storage There are two steps to take to build a proper AI led operation that is not run on projects. Step one: store information in labeled, separate files. Client info, brand guidelines, voice of the customer — each gets its own folder. This is your Client Bible. We use GitHub for it right now, and there are new tools coming to market built specifically to be long-term memory for businesses like ours. Company and client info need to be stored in a proper data warehouse that is built for AI B2B operations. Step two: build skills. A skill is a standard operating procedure. A pile of old hooks only shows the AI what a hook looked like. A skill tells it how to build one. Take hook writing as an example. To build the proper process for writing hooks, an agency would need to build skills for each type of hook: bold claim, curiosity, contrarian, story, authority. Each one is a clean SOP the AI runs. Then you combine the client data with the marketing skill. Example: “Look at the call transcript in the transcript folder from 7/1. Pull the HVAC voice file for HVAC client #1 and come up with 3 hooks using the the story skill based on the ideas shared in that transcript.” The prompt specifically builds the context window. The AI pulls in only the data it needs that is appropriately built. Context managed to fit the monitor. Then the part that compounds your result: loops Proper infrastructure means your operation gets better over time. It learns. A project can't do that. It has no memory of what worked. Your skills library does — if you put a human feedback loop around it. Someone does QA and grades the output. Good hook goes in the winners file. Bad hook gets edited, and the feedback gets logged and folded back into the skill. The work teaches the machine. The machine gets better. And it compounds. Build the dream, not a prison.

• 
  Keeta Github Tracker (@KeetaCode) reported 26 minutes ago

  🐆 Keeta GitHub PR Merged 📦 Repo: node-rs 🔀 PR #25: Fix: Align ASN.1 Generated with TS Reference 🌿 Branch: fix/asn1-tags → main 👤 Originally opened by: @sephynox 🧠 Overview: This update fixes a behind-the-scenes formatting mismatch so Keeta’s Rust node code matches the TypeScript reference more closely, which should help different parts of the system stay compatible. The pull request says the ASN.1 generator was adding tags in a way that did not match the TypeScript reference, and it also switches to using `GeneralizedTime` more often, which is a standard way to represent timestamps. This appears to be a technical/internal update with limited public details. - Likely impact: fewer encoding/decoding mismatches between implementations. - This looks more like a compatibility cleanup than a user-facing feature.

• 
  Asad (@meranaamkhann) reported 29 minutes ago

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

• 
  Keeta Github Tracker (@KeetaCode) reported 30 minutes ago

  🐆 Keeta GitHub PR Opened 📦 Repo: node-rs 🔀 PR #25: Fix: Align ASN.1 Generated with TS Reference 🌿 Branch: fix/asn1-tags → main 👤 Opened by: @sephynox 🧠 Overview: This update fixes an internal data-format mismatch so Keeta’s Rust node code matches the TypeScript reference more closely, which should help different parts of the system stay compatible. In simple terms, the pull request removes a formatting choice that didn’t line up with the existing reference implementation and also prefers a more standard time format where possible. This appears to be a technical/internal update with limited public details. - It looks aimed at improving consistency between implementations, rather than adding a new user-facing feature. - The mention of time formatting suggests part of the change is about making encoded timestamps more predictable.

• 
  Arti | AI Builder (@Artur_roses) reported 31 minutes ago

  Claude Code just closed a GitHub issue, wrote the tests, passed CI, and opened a PR. No human touched the keyboard. This isn't AI autocomplete. The dev loop just got rewritten.

• 
  Kashaf (@noor36758) reported 31 minutes ago

  @PiyuCodes GitHub is literally a CS/engineering tool... if it gets banned that's your problem too 💀