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:

• 
  Parsa Sabetz (@parsasabetz) reported 6 seconds ago

  @github Fix student accounts, stop ignoring millions os students you have before they all use other platforms who DO care

• 
  Overclock (@nverbullish) reported 3 minutes ago

  ZAPIER CHARGES $50 A MONTH FOR 2,000 TASKS. THIS OPEN-SOURCE TOOL DOES UNLIMITED TASKS FOR $0 AND NEVER SENDS YOUR DATA TO THE CLOUD. n8n. Free. Self-hosted. Runs on a Raspberry Pi, a laptop, or a $5 VPS. No account. No usage cap. No per-task billing. Same drag-and-drop canvas. Same node-based workflow. RSS feeds, Discord bots, SSH commands, API calls, AI chains. All wired together visually. All running locally. He built a cybersecurity alert bot in 10 minutes. RSS Read pulls the latest vulnerability disclosures. A filter catches the critical ones. Discord sends the alert to his server. Scheduled to run every hour. Zero code. Then he wired in an AI. A Basic LLM Chain node connected to OpenAI. The agent pings his servers via SSH, reads the output, and reports the results to Discord. The twist: he told it to impersonate Eddie Murphy. "Three pings, three hits, zero packet loss? That's smoother than Axel's moves in Beverly Hills, baby!" Production-grade server monitoring. Delivered by a comedy impression. Running on his own hardware. Zapier: $50/month for 2,000 tasks. $600 a year. Make: $10/month for 1,000 tasks. $120 a year. Both cloud-hosted. Both reading every piece of data that flows through. n8n self-hosted: $0. Unlimited tasks. Unlimited workflows. Every automation stays on his machine. 400+ integrations. Google Sheets, Slack, Telegram, GitHub, databases, webhooks, AI models. The same ecosystem Zapier charges enterprise rates for. The only cost is the machine it runs on. A $35 Raspberry Pi handles it without breaking a sweat. Automation platforms spent years teaching businesses that workflows need a subscription. One open-source repo just made that subscription optional.

• 
  Slims (@Slims_slimy) reported 4 minutes ago

  @neerajjj6785 Cursor was overhyped as all it did was implement a model into your IDE instead of copy pasting from an AI chat. So it knows exactly what's in the project rather then you telling it. Sora got shut down I think. Github copilot is working normally. Google.

• 
  Killbunny~ 🐰🔪 (@killbunny_) reported 4 minutes ago

  @kaneryu @V33V33V33V33V33 @CryptoCyberia Bro gatekeeping me from Github😔but yeah that's a problem with Devs, not end users. Also Github solved this years ago with GitHub Pages, a feature a large amount of people don't use. If you're expecting a normal Joe to use the thing (let's say a game mod), it's on the Dev to make a Site and distribute the bin. Totally different from uploading the source code of a service that actually requires technical knowledge to be deployed.

• 
  Michael Fischer (@Holden_Rye_) reported 4 minutes ago

  I’m working on a Bitcoin wallet. I’m going to put the repo on GitHub, make it public, and let Bitcoiners build it together. Fork it. Improve it. Save Bitcoin. Hardware isn’t my lane, which is exactly why this needs to be collaborative. My goal is just to get the ball rolling and the gears turning. Right now it’s a CLI. The point isn’t a pretty interface. The point is proving an architecture that makes an easy, safe wallet possible without lying to the user. The safety shouldn’t depend on the user being perfect. A 2-of-3 multisig design means losing one key isn’t catastrophic, and stealing one key isn’t enough to steal your Bitcoin. That’s a structural guarantee. Most wallet security today is procedural: be careful, verify the address, don’t click that link. Humans are the weakest link. This moves the protection into the architecture instead. The core policy engine does the hard work so the UI can stay simple. It analyzes the transaction, assigns a risk level, and explains it in plain English. The user sees Green: Safe to send or Red: Here’s what’s wrong. They never need to know what a script, descriptor, or PSBT is. Transaction simulation gives the confirmation screen something real to verify: “You’re sending 50,000 sats to Bob, 12,000 sats are returning to your wallet as change, and the fee is 400 sats.” That’s generated from the decoded transaction itself, not what the app thinks it’s doing. The descriptor becomes the backup, and it isn’t secret. Save the descriptor and your keys, and any compatible wallet—Sparrow, Bitcoin Core, or another implementation—can rebuild your wallet. No vendor lock-in. No “sorry, your funds are gone.” But here’s the hard truth. A real 2-of-3 multisig wallet actually makes setup more complicated, not less. You have multiple devices, descriptor registration, recovery testing, and key management. That’s the biggest unsolved UX problem. This repo doesn’t solve that yet. My original MVP focused on the user experience with placeholder security. This version focuses on real security with almost no user experience. Neither half is the finished product. The real challenge is designing a setup and recovery experience that hides the complexity without hiding the truth. That’s not just a coding problem. It’s a design problem. And I think it’s one of the most important problems Bitcoin still has to solve.

• 
  Anton Likhodedov (@ALikhodedov) reported 6 minutes ago

  @phileeppos Might be the setup? I vibe coded an app to track my PL and positions (which was not trivial, since I have a lot of derivatives in commodities and equities - so market data / expiries etc need to be handled correctly. I used Claude Cowork (Opus 4.7-4.8 models) and was not thrilled. Turned out a major issue was syncronisation between the sandbox (virtual machine) that cowork uses for development and the actual files. This caused 80%+ of the issues. My friend who has more experience suggested to keep code on Github, have Claude Code develop what I need and GPT Codex to check against the specs. He said he has rewritten a pretty large system for pricing complex derivatives (we worked on that for a few years in 2017-18 and he continued since) in two weeks. Alternatively Claude/GPT could write a project prompt that would create independent, non context-sharing processes (similar to agents, but not persistent) - so one would develop, another one would check. Should be an improvement over just normal queries, although not as good as have it done by 2 different LLMs.

• 
  Chris (@boredcrystalguy) reported 8 minutes ago

  @sophiiess_ This is completely unresponsive to what I said. Your example mentions two features that are separate and have different purposes. The problem is that if those features are present, they should be implemented well. If GitHub allows downloading apps, it should be easy to do.

• 
  Dan Thompson (@DanThompsonIV) reported 8 minutes ago

  GitHub just put stacked PRs in public preview. We’re going to try them on a real multi-package change — not a demo repo. Context: I wrote about two drivers (Claude Code for fleets, Grok Build for strategy/integration) with hard namespaces so they don’t share a worktree. Before that: model-routing only works when it’s enforced. Same theme here. The problem stacks are aimed at is the one AI made worse. Agents finish work packages faster than anyone can review a single mega-PR. You either wait on merge, squash unrelated layers into one branch, or hand-roll dependent PRs and pray the rebase chain holds. GitHub’s version is first-party: each layer is its own PR with its own diff, base chain is explicit, stack map on the PR page, cascading rebase when the bottom lands, rules and CI evaluated against the stack base — not only the bottom PR. CLI is gh stack (init → add → submit → sync / merge). Merge stays human. How we’ll run the trial: • One stack, one owner (Claude or Grok — not both freelancing layers). • One logical concern per layer (schema → API → UI, or package A → B → C). • Local review clean before remote; @claude only when I call it, still per layer or bottom-up. • I merge. Agents submit and babysit. Preview or not, merge authority doesn’t move. • Worktrees stay namespaced. Stack is the PR chain, not a license to mix drivers on main. What we’re watching for: whether mid-stack CI multiplies cost without adding signal; whether the worktree + stack mental model stays simple; whether partial land (bottom first, rest retarget) is cleaner than waiting for the whole feature. If it sticks, it becomes the default shape for multi-package missions. If it doesn’t, we learned it on one stack, not a process rewrite. Prose is still a suggestion. A base branch that points at the layer below it is a rule.

• 
  Michael ® SpeedevsWhale (@SpeedevsO) reported 16 minutes ago

  (use GitHub for sign in) (2025 and below GitHub) Is the requirement I think If your eligible you will get it

• 
  Ashkan (@ashkans_dev) reported 17 minutes ago

  Anyone else having an issue with Codex not staying auth’d with GitHub using the gh CLI ?

• 
  Lord Bean (@lifeisameeme) reported 17 minutes ago

  OpenAI's next model just resolved two Erdős problems and disproved an 80-year-old conjecture in group theory. Total cost: about $𝟮,𝟬𝟬𝟬 in tokens. The unreleased Astra model produced ten new results in pure math and theoretical CS, from sphere-packing bounds to arithmetic circuit complexity. Every proof ships with a 𝗟𝗲𝗮𝗻-𝘃𝗲𝗿𝗶𝗳𝗶𝗲𝗱 𝗳𝗼𝗿𝗺𝗮𝗹 𝗰𝗲𝗿𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗲, not just a claim. → Disproved Connes' Rigidity Conjecture (open since the 1980s) → Resolved Erdős problems #146, #180, and #183 → Improved bounds on high-dimensional sphere packing toward the Cohn-Elkies threshold This isn't the model's first math result either — the same system reportedly disproved the Erdős unit-distance conjecture back in May, with human mathematicians then verifying and publishing the proof. The Lean certificates are on GitHub right now if you want to check the agent's work yourself. 🔗 Links in the reply 👇

• 
  folarihn (@folarihn) reported 19 minutes ago

  You can sell your GitHub login to guys that’ll use the api credit but don’t expect to get that same value. If you’re so kin on withdrawing the free credit.

• 
  Bold Fugu 🇮🇱 (@bold_fugu) reported 20 minutes ago

  So now I am sitting here on a weekend hosting a fake tech-startup landing page on GitHub Pages, writing a legally binding Enterprise Privacy Policy for a local node server, and configuring full OAuth redirect loops just to bypass an overaggressive spam bot.

• 
  Vikas gupta (@vicky_grok) reported 21 minutes ago

  DAY 5: MCP (MODEL CONTEXT PROTOCOL) What it is: An open standard integration protocol that connects Claude to live enterprise databases, local filesystems, external APIs, and third-party software applications. How it works in practice: You configure an MCP server that links Claude directly to your GitHub repository and PostgreSQL database. The model queries live production metrics, inspects open pull requests, and updates ticket status without manual copy and paste. • Basic usage: Isolated text processing within a web browser tab. • Advanced usage: Bi-directional connectivity with production software tools. Goal: Connect Claude directly to external systems and real-time operational data.

• 
  Shafqat Crypto (@Mrearningtips) reported 33 minutes ago

  🚨 Instant $175 FREE AI API Credits! 🔥 Agent Router Is Giving Away Up To $175 API Credits For ChatGPT & Claude*. ✅ Eligibility: - GitHub Account Created Before 2025 ⚡ Supported Models: - Claude Opus 5 & 4.7 - ChatGPT 5.6 Sol 📌 How To Claim: - Sign Up Using 'GitHub" - Don't Use Gmail Or Username Login - Open Wallet → Check API Credits 🔄 Didn't Receive Credits? - Refresh & Check Again ⏳ Limited-Time Offer — Claim It Before It's Gone! 💬 Claimed Yours? Drop Your Balance Screenshot Below 👇