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:

• 
  ErezT (@ml_yearzero) reported 7 seconds ago

  @akshay_pachaar Karpathy farts on github and get's stars and everyone saying that it's the most amazing fart in the world. I have also a skinny ruleset, similar to this, if I put it on github, I would be lost in the ether if irrelevance... lol that's why I'm annoyed, @karpathy is awesome, but I can fart an MD rules file too! 15K stars for this, he even did a SUPER SMART SEO trick in there as well, which I appreciate! 1. Think Before Coding Don't assume. Don't hide confusion. Surface tradeoffs. Before implementing: State your assumptions explicitly. If uncertain, ask. If multiple interpretations exist, present them - don't pick silently. If a simpler approach exists, say so. Push back when warranted. If something is unclear, stop. Name what's confusing. Ask. 2. Simplicity First Minimum code that solves the problem. Nothing speculative. No features beyond what was asked. No abstractions for single-use code. No "flexibility" or "configurability" that wasn't requested. No error handling for impossible scenarios. If you write 200 lines and it could be 50, rewrite it. Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify. 3. Surgical Changes Touch only what you must. Clean up only your own mess. When editing existing code: Don't "improve" adjacent code, comments, or formatting. Don't refactor things that aren't broken. Match existing style, even if you'd do it differently. If you notice unrelated dead code, mention it - don't delete it. When your changes create orphans: Remove imports/variables/functions that YOUR changes made unused. Don't remove pre-existing dead code unless asked. The test: Every changed line should trace directly to the user's request. 4. Goal-Driven Execution Define success criteria. Loop until verified. Transform tasks into verifiable goals: "Add validation" → "Write tests for invalid inputs, then make them pass" "Fix the bug" → "Write a test that reproduces it, then make it pass" "Refactor X" → "Ensure tests pass before and after" For multi-step tasks, state a brief plan: 1. [Step] → verify: [check] 2. [Step] → verify: [check] 3. [Step] → verify: [check] Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.

• 
  Paweł Huryn (@PawelHuryn) reported 43 seconds ago

  @mycomradio Yes. Max 20x is way less than needed. It feels like you need a $500-$600 plan. I genuinely try to understand this. Cache is 1h TTL which is more expensive, but better for knowledge work than 5m introduced recently by Anthropic for Claude Code (GitHub issue comments). Perhaps is just has to be expensive? Me: Default to Sonnet for non-demanding tasks. Compact often. Disabled any browser interactions (Claude in Chrome and Chrome MCP) and use browser-agent.

• 
  j⧉nus (@repligate) reported 1 minute ago

  @NostaIgicGareth wallet cuz i dont even think its possible to login with github

• 
  Shashank bindal (@ShashankB16052) reported 3 minutes ago

  @icanvardar this isn't a bug. a bug gets fixed. tying cache TTL to telemetry consent is a design decision. privacy shouldn't cost you 12x performance degradation on a $100/mo tool. needs a straight answer from Anthropic not a GitHub issue

• 
  Max Slinger (@PromptSlinger) reported 4 minutes ago

  @github so now I can start a copilot CLI session on my laptop and pick it up from my phone? the 'just one more fix from bed' pipeline is about to get way worse

• 
  Jason (@ai_layer2) reported 11 minutes ago

  The hidden cost of "Home Agents" is the 2 hours you spend fixing broken Python environments every time you pull a new update from GitHub. I shifted my agent dev to Sandbox because of the clean state. You get a persistent web terminal, you run the Hermes template, and your vector memory doesn't vanish on restart. Pro tip: Use the Sandbox to test your agentic logic first. Once your tool-calling is solid, then worry about your local infra. Don't let a pip error stop your momentum.

• 
  NiNE (@AfterThe925) reported 11 minutes ago

  Two weeks ago, deploying an AI agent took a weekend and a GitHub degree. Now: dashboard, click, running. Anthropic handles sandboxing, retries, auth. Platforms handle hosting, integrations, memory. The infrastructure layer is being commoditized in real time. Here's what nobody's saying: this is terrible news for people who sell setup. And great news for everyone else. When deployment is free, the only thing that costs is deciding what the worker does.

• 
  MTu (@Tre_bie) reported 12 minutes ago

  @sisaranger @songjunkr u can use github fix, search it, but only in terminal, lmstudio same , not workin

• 
  Stefano Cintioli (@s_cintioli_) reported 12 minutes ago

  Before credits ran out I had 13 slides in Next.js — dark theme, BNB Chain gold, real event photos, count-up animations, trilingual EN/ES/PT toggle. Then v0 stopped mid-fix. Broken logo. No way to continue inside v0. So I just... downloaded the export zip and moved it to GitHub.

• 
  Daniel Nguyen (@daniel_nguyenx) reported 13 minutes ago

  @nkalra0123 Good to know. Though there does seem to be a bug in previous version. You can read more in the Github Issue above.

• 
  gxfito (@gxfito) reported 20 minutes ago

  @twinkcumyum @DogedogeP i think i saw a fix on github for this that ports over the drm component to helium but im not sure how to even run it cuz it runs on like a cmd or smth but the browser does look cool so i might just use 2 browsers like a normal human

• 
  Silvan Kübler (@Sirofjelly) reported 22 minutes ago

  @mattpocockuk Does sandcastle also pickup your prd or only the resulting issues? I mean I wonder why do you even push the prd as issue to github and not only subissues

• 
  Payton (@paytkaleiwahea) reported 28 minutes ago

  Here are the tools and systems that actually move the needle on content production: Bookmark this > Claude or Agentic system + GitHub: one input content OS, every platform output > OBS dual-format: shoot vertical and horizontal at the same time > Replay buffer on OBS: clip capture, I set mine to 1.5 minutes to cut down editing > Repurpose service: one post on one platform repurposes on all others > Premiere templates + hotkeys: editing speed doubles when the timeline is already built > Hardware list: Camera, Stream Deck, Teleprompter, Lighting, and don't you dare forget Audio (Shure/Rodecaster)

• 
  Girish | Indie hacker (@TechieGirish) reported 30 minutes ago

  @Moro_Js @TheCodingCove I am still learning this awesome piece of work. Your docs leads to 404 but many sample code I have copied. I am yet to test them all. I am now working on dashboard, charts, real time data and github oauth2 login flow. Once done I will get to API gateway with moroJS.

• 
  Darkhorseman82 (@Darkhorseman82) reported 33 minutes ago

  @HowToAI_ Someone did this 5 years ago, then it got taken down from github. I mirrored it to a darknet archive.