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:

• 
  Avrojit Dutta (@avrojit_dutta) reported 5 minutes ago

  Let someone actually offer the ₹1 crore package first, I’ll worry about the pitch deck for the ₹1,000 crore startup later. Better, build an open-source project worth 0 revenue and 1,000 unassigned GitHub issues instead.

• 
  Leander (@leanderriefel) reported 5 minutes ago

  Does Cursors Origin even have public repositories? Is there something like origin[dot]com/<org>/<repo> with issues, pull requests and discussions? Because if not what was the whole "replacing github" even about?

• 
  CyrilXBT (@cyrilXBT) reported 5 minutes ago

  this feels like a glitch in the matrix jack dorsey (twitter co-founder) just dropped a completely free github repo with 26.2k stars that’s basically an ai-agent OS for actually running a business the playbook: 1. clone the repo 2. self-host the whole backend: channels, search, ***, automations, everything lives on your server 3. add your agent to a channel like it’s a new hire, tighten its permissions, and let the team steer it live save this and bookmark it, i’m not kidding

• 
  Rosy🥀 (@0x1Rosy) reported 6 minutes ago

  @sam_passon12 read the article carefully! password is there github link is in the "Community" section of the app If you have issues, you can pm me

• 
  Mark Kadirov (@KadirovMar13725) reported 8 minutes ago

  @KAIKAKU_AI @josefchen Hi Josef — Epicure MCP is still not working in ChatGPT. It returns 401 / authentication errors even though the docs say Auth: None. GitHub issue #9 is still open. Could you please take a look?

• 
  Prasenjit (@prasenx) reported 8 minutes ago

  there's no official way to run macOS on an iPad. someone made an unofficial one. full macOS running locally on iPad. not a remote desktop, not a web app. hardware CPU virtualization with GPU acceleration. → supports macOS 12 monterey up to macOS 26 tahoe → you can install xcode, terminal, final cut pro trial, logic pro trial on device → works on iPad Pro (M1, M2) and iPad Air (M1) → requires jailbreak on iPadOS 14 up to 16.3.1 → no iCloud sign in → MIT license (100% free) open source on GitHub.

• 
  Adel Bucetta (@adelbucetta) reported 9 minutes ago

  @davepl1968 this is massive. pointed an ai at my github issues and it actually fixed some of them. that's not just automation, that's someone else owning the judgment on what to fix

• 
  Dela (@delaanthonio) reported 10 minutes ago

  @GergelyOrosz It’s even more ironic since Xcode is trash compared to Visual Studio and VSCode. Xcode makes developing for the Apple ecosystem painful. No one loves it. But we use it anyway so we can distribute apps to Apple’s customer base. Taking a step back, we like macOS since it’s a good Unix-like environment for developing software. I used WSL years ago and there are always issues with the translation layer between Windows and Linux. It may have gotten better, but the experience is always worse than using a native Unix-like OS. The main mindshare Microsoft has for devs is GitHub. Everyone sees the frequent outages. Many stay since it’s hard to replace GitHub, but some are leaving.

• 
  Kieran Bond (@KieranBond_) reported 11 minutes ago

  @Aaronontheweb Tbh, yeah. I barely use them since October. I mostly use GoLand these days (writing Go), and only for my 'craft' hour where I try to keep my skills from fading. Otherwise, I just review diffs in GitLab/GitHub. They're fine for it. IDEs are too slow for this.

• 
  Luke W Gilbert (@luke_w_gilbert) reported 12 minutes ago

  Shipping log. Messy week. Real progress. Identity got a full mobile pass: hamburger menu replaced the horizontal-scroll nav that was quietly breaking on narrow phones, calendar grid stopped clipping Saturday off-screen, weekday headers stopped reading as a T-collision, stale cached builds got fixed by actually calling registerSW. The settings gear is live now with per-platform time chips so posting schedules are configurable per platform instead of global and dumb. Install-to-home-screen has a real entry point with proper icons. PWA now behaves like it should. Signal's publish queue is wired into Identity's post queue with drip scheduling and pg_cron automation. Human approval gate is gone. The guardrail runs itself. DevCom closed all four phases of the Excellence Plan. Four Truth Engine PRs merged. GitHub login redirect loop fixed. Production secrets untracked from ***. Daily cost tile live on the dashboard. SMRT: stale mortgage rate in the owner-agent newsletter root-caused and grounded via FRED. That number had been quietly wrong. LinkedIn scheduling emergency: platform_quotas inconsistency restored. Live posting confirmed working again. The client project: read-only forensic hardening pass completed before the launch window. Not everything shipped clean. Three items sent back. One bundled task split into three because it was mixing low-risk repo work with live Brain Engine edits and nobody could review it honestly as one thing. A suppression design hit auth walls at every live surface. A token rotation got submitted with no live mutation performed. Sent it all back. 'Done' and 'here is live proof it is done' are still different claims.

• 
  Zhirayr Gumruyan (@gumruyanzh) reported 14 minutes ago

  if you want to save on #github simply get a vps and move all runners to custom server and use it thousands of hours instead of 2000 per github limits

• 
  BigDataTechBro (@_ImDaniel__) reported 15 minutes ago

  @maximbilan If you use TestFlight you can share the screenshots directly to the App Store Connect then have the agent read them as GitHub issues

• 
  DFIR Lab (@DFIR_Lab) reported 29 minutes ago

  A vulnerability was identified in chenhg5 cc-connect up to 1.4.1. This affects the function shellExecCommand of the file core/engine.go of the component Management API. Such manipulation of the argument exec leads to os command injection. It is possible to launch the attack remotely. The exploit is publicly available and might be used. The reported GitHub issue was closed automatically due to inactivity.

• 
  Hossein (@tootoonchy) reported 30 minutes ago

  Everyone tells you not to use AI for writing. Few tell you how to use it well. Your readers can spot AI writing faster than you can write it. AI doesn't make factual errors, but it has aesthetic habits – and most people have learned to recognize them. A free skill called no-ai-slop with 6k+ GitHub stars actually helps. You give Claude the repo link. It generates a zip file. You upload that in settings. Then any time you're writing, just run /no-ai-slop and it scrubs the 20 most common AI patterns from your draft. Things like:  – Binary contrasts. "It's not X. It's Y."  – Throat-clearing openers. "Here's the thing," "Let me be clear"  – Faux-insight setups. "What nobody tells you," "The part everyone misses"  – Importance puffery. "marks a pivotal moment," "a testament to"  – Synonym cycling. Writing "agent" once, then "assistant" in the next sentence for no reason  – Fake-profound endings. "The future isn't coming. It's already here." I've been running it on my own posts. The before/after is embarrassing. The irony is that most of these patterns feel like good writing when you're in them. They're learned from training data that included plenty of professional prose. They just happen to be identifiable at scale now. This skill doesn't fix your thinking. But it does strip away the aesthetic that makes AI writing feel like AI writing. That's most of the battle. Link in the comments.

• 
  Joseph K (@TechHorizonJoe) reported 33 minutes ago

  @moonshots_pod Right instinct, stop problems before they materialize. But uranium buyers need centrifuges. AI researchers need a laptop and GitHub. Whole different surface area.