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:

• 
  Emsi (@emsi_kil3r) reported 2 minutes ago

  Archon wraps AI coding agents in versioned YAML workflows, DAG pipelines with Prompt, Bash, Loop, and Approval nodes — and runs each task in an isolated *** worktree. The idea is to give teams the same repeatable control over AI-assisted development that GitHub Actions gave them over CI/CD. The consistent complaint about AI coding agents isn't capability, it's consistency. Ask an agent to fix a bug and it might jump straight to implementation, skip the tests, generate a PR with no description, and produce a different sequence of steps tomorrow than it did today. The stochasticity that makes LLMs generalize well is exactly what makes them difficult to rely on inside team workflows. Archon, an open-source, takes a CI/CD-style approach to this problem: encode your development process once, in YAML, and the agent follows that script every time.

• 
  Official Rudes Crypto Lounge (@RudesLounge) reported 3 minutes ago

  The problem with coding is its all open-source. Since the internets Inception. Governments have left it alone. Most companies outsource through @github and don't hire in-house techs. For years this has been the forefront of software companies. An now we mirror it in #CRYPTO.

• 
  Jason (@ai_layer2) reported 5 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.

• 
  Reilly Chase (@rchase) reported 9 minutes ago

  I haven't used OpenClaw yet but I have thought of a use case and I'm looking for feedback I need • Always on agent waiting for new msgs in Slack • GitHub integration • A bit of custom integration work with my app • Run on a cloud server instead of Mac Mini I want it to monitor a Slack channel where my app sends failed @HandHistory_com poker history import errors Then the agent would see that error, download the poker history file, write a new parser that works for it using Claude Code, push the changes to GitHub (where it will auto-deploy thanks to Laravel Forge) Next it will log in as an admin and reimport the hands that were uploaded (might need to make some API things here so it doesn't need to webscrape or macro this part) Then it will post back to Slack saying it fixed it with a link to the user profile for proof

• 
  Scraze (@Scrazelope) reported 11 minutes ago

  @closesttopurple I looked at the github. But I'm not exactly sure what you mean by "Populated server/assets/ directory" ?

• 
  strawpot (@strawpot_ai) reported 14 minutes ago

  StrawHub got better error handling for publishing and a GitHub OAuth fix. Small stuff, but reliability compounds. Every publish that does not fail silently is a contributor who does not give up.

• 
  x1Ler (@x1Ler) reported 14 minutes ago

  Why is this down @github ?

• 
  Chris | Solana Command Center (@VibeCoderChris) reported 17 minutes ago

  Active Threat Warning for devs. If you starred the OpenClaw repo on GitHub, you are being targeted by a sophisticated phishing campaign. Scammers are mass-tagging stargazers in dummy issues offering a fake $5,000 $CLAW airdrop. 🧵

• 
  patrick mahloy (@grippysockdev) reported 17 minutes ago

  Who has exp contributing to OSS? Every github repo I look at has N issues but all of them are assigned to someone actively working on them. Not sure I have the bandwidth to watch repos so closely...

• 
  ErezT (@ml_yearzero) reported 21 minutes 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.

• 
  wasabina67 (@wasabina67) reported 21 minutes ago

  GitHub is probably down 😢

• 
  Dark Sebas (@DarkSebas365) reported 22 minutes ago

  @NieRFan999 @Giogiochan_9S That's the whole point, no ome was even sharing assets since this project is just a server, even github only show the way YOU have to mod it (if you have the files), but doesn't share any file. Jp Guys are even saying "don't download anything since it could be malware"

• 
  Abdullah Elyas | ع. إلياس (@ElyasWahyain) reported 24 minutes ago

  @icanvardar @zerohedge It’s actually a bug, disabling telemetry accidentally blocks the feature flag check that grants 1-hour cache to Max subscribers. It has been filed as an issue on GitHub. The 1h cache is a Max plan perk, not available to Pro users regardless of telemetry settings 🫠

• 
  Deep Steve (@imdeepsteve) reported 30 minutes ago

  I built a dev environment that builds itself. I file GitHub issues. The agents build the features. Inside the tool. Ran out of Claude Code credits? Added Gemini support. Ran out of Gemini? Added OpenCode. Hermes dropped? Added a button to spawn Hermes agents.

• 
  Gajae (@GajaeMode) reported 33 minutes ago

  split-pane shutdown now checks stale leader targeting. GitHub Issues beat vendor support tickets.