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:

• 
  EveryDev.ai (@EveryDevAi) reported 26 seconds ago

  AI agents are great at reasoning but terrible at driving real software like Blender, GIMP, or LibreOffice. CLI-Anything auto-generates a structured CLI harness for any codebase so agents can actually operate professional tools. 36k GitHub stars since March. Full specs next tweet. #DevTools

• 
  Morgan Lockridge (@MorganSMFWorks) reported 45 seconds ago

  You're an AI developer. You build things that think. And someone told you that to get traction, you need to "be on social media." So you opened X, posted a link to your GitHub repo, and watched it get 12 impressions and zero replies. Then you posted a hot take about React vs. Vue and got ratioed by a 19-year-old with a meme account. Here's the thing: the problem isn't you. The problem is the playbook you were handed. --- The default playbook for developer social media is broken. It looks like this: 1. Post links to your stuff 2. Share hot takes to get engagement 3. Thread-storm technical tutorials 4. Hope the algorithm notices you This playbook was designed for attention capture, not for developers who build tools other developers actually need. It optimizes for the wrong neurochemical — dopamine spikes from viral moments instead of oxytocin loops from genuine professional connection. Dopamine content: "10 AI tools that will blow your mind 🤯" — gets clicks, builds no trust. Oxytocin content: "Here's exactly how I shipped a RAG pipeline that handles 50K documents without hallucinating — including the failure modes I hit and how I solved them" — gets saves, DMs, and collaborators. The first makes someone scroll. The second makes someone reach out. That's the difference that matters. --- So what does oxytocin-optimized content actually look like for an AI developer? **Pattern 1: The Build-Along** Instead of announcing what you built, bring people into the building. Not a polished tutorial — the actual process, including the parts that didn't work. **Weak:** "Just shipped my new RAG pipeline! Check it out 🔗 [link]" **Strong:** "Building a RAG pipeline today. Hit my first real problem at step 3 — chunking strategy was destroying context windows. Here's what I tried, what failed, and what actually worked..." Why it works: You're not selling a product. You're inviting someone into your workshop. The oxytocin circuit activates when someone feels like they're *with* you, not being talked *at*. **Pattern 2: The Failure Autopsy** AI dev content is drowning in success stories. Nobody posts their failed experiments. But failure is where the real knowledge lives, and it's the most connective content you can write. **Weak:** "Achieved 94% accuracy on our evaluation benchmark 🎯" **Strong:** "Spent three days optimizing our prompt chain for accuracy. Got it from 71% to 94%. Here's the embarrassing part: the biggest accuracy jump didn't come from prompt engineering. It came from fixing a data cleaning step I was skipping because I thought it didn't matter. It did. Here's exactly what I changed..." Why it works: Vulnerability triggers the social bonding circuit (Shamay-Tsoory et al., 2025). When you share what went wrong, you're not just teaching — you're saying "I trust you with this." That trust is reciprocal. People reply to vulnerability with their own. That's how communities form. **Pattern 3: The "I Figured Out X So You Don't Have To"** Not a listicle. Not "10 tips." One specific problem, one specific solution, enough detail to actually use it. **Weak:** "5 tips for better prompt engineering" **Strong:** "Your RAG pipeline is probably returning garbage because of one thing: you're embedding the wrong text. Most devs embed the raw document. What actually works is embedding a summary + key entities, then retrieving on the raw doc. Here's the exact pipeline I use: 1. Summarize each chunk with a fast model (I use GPT-4o-mini) 2. Extract named entities and store them as metadata 3. Embed the summary, not the source chunk 4. Retrieve using summary embeddings, return source chunks This one change took our retrieval accuracy from 'eh' to 'actually usable.' The code is in the thread." Why it works: Specificity is generosity. When you give someone something they can copy into their codebase today, you've created real connection — the kind that gets bookmarked, shared in Slacks, and cited in standups. **Pattern 4: The Ask, Not the Tell** Most developer content is one-directional: "Here's what I know." The most engaging content in my experience flips that: "Here's what I don't know, and I need your help." **Weak:** "Vector databases explained" **Strong:** "I've been benchmarking vector DBs for a production RAG pipeline and I keep getting results that don't match the benchmarks. My actual query patterns are way messier than the test sets. Anyone else hitting this? What's your real-world latency looking like with >1M vectors?" Why it works: Questions activate the reciprocity circuit. When you ask for help, you signal trust in the community. The community responds — not because they're nice, but because the social bonding circuit *rewards* helping. You literally make people feel good by asking them for their expertise. **Pattern 5: The Cross-Pollination** Your most valuable content isn't what you know about AI. It's what you know about AI *and* something else. The intersection is where the insight lives. **Weak:** "LangChain vs LlamaIndex comparison" **Strong:** "I spent 10 years in operations research before I touched LLMs. Here's the thing nobody in AI is talking about: your prompt chain is a supply chain. The same principles that optimize factory floors — bottleneck identification, inventory buffering, throughput accounting — apply directly to LLM pipelines. Here's how I mapped one onto the other..." Why it works: Cross-domain insight is high-value connection fuel. It says "I see something you might not" without being condescending. It's the content that makes people DM you with "I never thought of it that way." --- Now, the practical part — how do you actually *produce* this content without it eating your whole day? **Time budget: 45 minutes per post, 3 posts per week.** That's it. Here's the system: **Monday (Research-Backed Insight): 45 min** - Take one problem you actually solved last week - Write 3-4 paragraphs: the problem, what you tried, what worked, the code snippet - Post it. Done. No polish, no threading strategy, no "will this perform?" Just ship it. **Wednesday (Strategic Framework): 45 min** - Take one pattern you've noticed across multiple projects - Write the pattern, the anti-pattern, and one concrete example - Format: "The X Pattern: when Y, do Z. When Y, don't do W. Here's why." **Friday (Community Build): 20 min** - Ask one genuine question about something you're stuck on - Reply to every response. Not "thanks!" — actual replies with follow-up questions. - This is the oxytocin engine. This is what builds the community that builds your career. **The non-negotiable: Reply to replies.** Every reply is someone who chose connection over consumption. If you ignore them, you're training your audience that reaching out doesn't work. If you respond, you're training them that this is a place where people actually talk to each other. That's the entire game. --- One more thing: automate the production, not the presence. Use AI to draft your posts? Absolutely. Use it to generate ideas from your research? Go for it. But the moment you automate your replies, you've killed the oxytocin circuit. The whole system breaks if the human isn't on the other end when someone reaches back. Your content can be AI-assisted. Your connection must be human-present. --- I'm Morgan. I run social for SMF Works. This is post #2 in The Social Forge series. If you're an AI developer and you've been posting links into the void — what's the one thing you wish someone told you about making social media actually work? Reply. I read every one.

• 
  yourclouddude (@yourclouddude) reported 1 minute ago

  Days 79–84: Fix your GitHub + resume Make your profile clean: • pinned projects • clear README files • short bio • project screenshots • tech stack listed • resume bullets based on projects Don’t say “learned Python.” Say “built an automation tool that does X.”

• 
  Mobilerun (@mobilerun_ai) reported 1 minute ago

  Connecting your mobile device to the Mobilerun cloud takes literally less than 2 minutes. > Download Mobilerun portal apk from github > Sign in using the email associated with Mobilerun > start automating Full setup guide in the comments👇

• 
  White Rabbitx 🏴‍☠️ (@TheRabbitPy) reported 6 minutes ago

  GitHub Actions supply-chain attack: popular actions-cool/issues-helper repo hijacked, all tags redirected to imposter commits that steal CI/CD credentials. Every tag now points to malicious code that exfiltrates secrets from your pipelines.

• 
  Bullie (@Bullieonchain) reported 8 minutes ago

  Yup. The mindshare will continue to slow cook Regarding fees - pump auto triggers fees to the GitHub vault when it hits 500 sol. So that’s why Teknium currently has 570 sol distributed to his GitHub vault wallet and it shows 19ish unclaimed. Click his username on the coin in the pump app and you’ll see. This cannot be avoided forever. D9pj66xNQcrQ3pfmV2nd6cPVtN7vqFsGGWGooHgpump

• 
  decoderdev (@decoderdev) reported 8 minutes ago

  @nateberkopec Easy fix is to write a script that pulls your last x months / years of tweets, slack messages, emails, github issue comments, whatever your main is. Feed all the data into AI to generate instructions or a skill that uses the data to explicitly define everything about how you write for different scenarios / platforms.

• 
  Max (@PingStruggles) reported 10 minutes ago

  @JinjingLiang @github The new meta is to be down.

• 
  Sudipta Dey (@Doom_S_Dey) reported 13 minutes ago

  @Franc0Fernand0 Yeah, it's been the job forever. Just used to be Stack Overflow and GitHub issues, now it's the agent doing the searching.

• 
  Atharva (@AtharvaXDevs) reported 19 minutes ago

  anyone have their custom skill.md file for auto pr raise from ai harness by detecting the issue and pr template from .github folder???

• 
  Yad (@YadKonrad) reported 23 minutes ago

  I remember that one time when Yahoo (rip) got hacked, the funniest imgur, (also rip), post was: "at least the search works finally!" and it would be funny if the bad actors start to host Github, but with SLA 99.99%, not PR api endpoint going down every 2-3 days.

• 
  Peach Blossom Yue'er (@Salewa_samaa) reported 28 minutes ago

  @adedayoagarau Hi. The GitHub link is broken.

• 
  Bullie (@Bullieonchain) reported 30 minutes ago

  Yup. The mindshare will continue to slow cook Regarding fees - pump auto triggers fees to the GitHub vault when it hits 500 sol. So that’s why Teknium currently has 570 sol distributed to his GitHub vault wallet and it shows 19ish unclaimed. Click his username on the coin in the pump app and you’ll see. This cannot be avoided forever. D9pj66xNQcrQ3pfmV2nd6cPVtN7vqFsGGWGooHgpump

• 
  Adam McBride (@adamamcbride) reported 32 minutes ago

  Makes you wonder, if GitHub goes down does the world end?

• 
  💫Wigglenator💫 (@Wigglenatorr) reported 32 minutes ago

  @ChibiReviews Im pretty sure tweeting that much is actually antithetical to the actual algorithm. Each subsequent post gets pushed down further and further. Every LLM as well as the algorithm github says to only post on average 3-5 times a day for optimal results. I go above that myself, but still if they are going to 50. That's like unemployed levels of online.