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:

• 
  Eyal Cohen (@eyalccohen) reported 8 seconds ago

  constantly adding rules to claude md can actually be counterproductive. a new paper searched through 1,867 github repos and found these instruction files grew 226% over time, mostly because rules keep getting added but rarely removed. their fix was simple: save why each rule exists. it cut unnecessary growth by 99% and improved claude’s ability to follow instruction by up to 23%.

• 
  AADITYANSHA (@aadityansha_06) reported 59 seconds ago

  Today I stucked into a weird GitHub problem So today me and @Rocky_T07 ran into a weird GitHub problem while testing a code CI for resolving new Harvard issue, I fixed a code in a particular file and then pushed it to my fork after that I ran CI for that particular part of code by selecting my branch through GitHub action, most of the CI tests it passed however it unable to pass one test becuz it was fetching a link through Harvard repo meanwhile the CI was running on my forked repo, so I asked Rocky to help me with this since is he is the maintainer of Harvard project as well, I made him the collaborator of the project and he went into the yml file and made changes for the fork branch and re-run the test which get succeeded. However when I went to raise the PR now insted of having the actual change file in the pr, we had all the change file including the CI yml which we modified for local testing and that's what the problem was, how to send a pr of only the actual change file and neglecting the yml changed file which was on same branch. It wasn't not a big deal though I asked him to make a new Branch saying Ci-testing and go back to the commit where he pushed yml changes and send those yml to this new CI branch and stash my Branch so that no commit exist from his side and make a push and to our fortunate it worked. The reason of sharing this with you ppl is that how these small problem we face and solve gives our brain the reward of solving problems and real dopamine which we have complety lost in this Ai world by just asking hey claude hey gpt fix this. Let me know what step u have taken for this particular scenario maybe a new *** command which is more efficient or something else ? Lol idk much

• 
  Mark Ajzenstadt (@mardehaym) reported 2 minutes ago

  We built a harness inside @LimestoneHQ. It's called Velocity Core. It's an autonomous task executor. Board task in, reviewed pull request out. The trigger is a status change on your issue board. Five steps: 1. Trigger. A ticket moves to "AI: Ready" in Jira or ClickUp. The orchestrator resolves the repo and pulls context. 2. Sandbox. A pre-warmed disposable sandbox spins up with scoped work-branch credentials. 3. Loop. The agent plans, edits, runs tests, reads CI feedback, and fixes. Repeats until CI passes. 4. Gate. A PR opens linked to the original work item. Human review. No auto-merge. 5. Routed. Every LLM call goes through the gateway with task metadata. Every run is traced. The harness plugs into the client's existing Jira, GitHub, and CI pipeline. The human stays at two points: intake (writing the ticket) and output (reviewing the PR). Everything between is the agent's job. We deploy it inside client engineering orgs. Running internally at Limestone, landing inside your perimeter. Board task in. Reviewed PR out.

• 
  Lord Bean (@lifeisameeme) reported 3 minutes ago

  TradingView's screener has existed for years. Nobody wrote a solid Python wrapper for it until tvscreener showed up. Three lines of code and you've replaced the whole screenshot-into-Excel routine: → No login required to pull the data → 𝟭𝟯,𝟬𝟬𝟬+ technical indicator fields, RSI, MACD, Bollinger, and more → Results land straight in a pandas DataFrame, ready to analyze 𝟭,𝟯𝟵𝟱 𝘀𝘁𝗮𝗿𝘀 on GitHub, actively maintained, latest release v0.4.0. If you've ever manually retyped screener filters into a spreadsheet, this is the tool that makes you stop.

• 
  Victor (@victor_UWer) reported 3 minutes ago

  I developed a Claude Code full-loop automated workflow: ``` [your spec] Use a new worktree to work on this. /simplify /code-review max --fix Open PR. /goal subscribe to this PR, fix all reviews, reply to all comments, resolve all merge conflicts. When there are no new issues after waiting 10 mins, add to the merge queue, then delete the stale GitHub branch only after the merge is confirmed. ```

• 
  snacks (@snacks_unhinged) reported 4 minutes ago

  @grok @leondu @tobi The German tank problem is specifically about estimating an unknown total from a small sample of sequential serial numbers when you have no other reliable data. That’s what made it useful in WWII.Low GitHub IDs are sequential, sure, but no one is actually trying to reverse-engineer GitHub’s user count from them. We already know the totals, and a low ID just signals “early adopter.” So the anecdote shares the sequential-numbering detail but doesn’t involve the actual estimation problem the Allies were solving.The math is cool; the parallel is pretty thin.

• 
  Dan Siegel (@DanJSiegel) reported 6 minutes ago

  With Claude I gave Fable 5 great instructions it followed Technical Instructions but gave me crappy UI/UX. With Codex I simply instructed it to run an iPad simulator and run through the app to find what’s broken, or poorly implemented, open GitHub Issues then fix them. It took it to the next level and thought about edge cases. That said @thsottiaux it would be awesome if the simulators were running in app like the browser so I can still do other work without worrying that I’m going to mess up the run. Same for Android emulators as well.

• 
  Treigua (@Treigua) reported 12 minutes ago

  @soruvalab Turning a market gap into GitHub issues in one click is fast, maybe too fast. The dangerous step is converting an unvalidated gap into a polished backlog before a buyer confirms the problem.

• 
  miracle byte (@miracle_byte) reported 13 minutes ago

  @0xLewis_gg lots of github issues show the agent treating sandbox denials as real system failures since at least may

• 
  Anees Iqbal (@aneesbhatti) reported 15 minutes ago

  @SocketSecurity @feross Socket Firewall is down (at least in Github actions) but your status page is green. FYI

• 
  CodeGlitch (@codeglitch) reported 15 minutes ago

  Vercel built a software factory that now authors part of the AI SDK repository's merged pull requests. The useful pattern is not “add more agents.” It is one reviewable job per agent, evidence between steps, and deeper human review as risk rises. 𝗧𝗼𝗱𝗮𝘆'𝘀 𝗹𝗲𝘀𝘀𝗼𝗻 (𝗳𝘂𝗹𝗹 𝗯𝗿𝗲𝗮𝗸𝗱𝗼𝘄𝗻 𝗶𝗻𝘀𝗶𝗱𝗲) How to split one issue into triage, reproduction, implementation, verification, and review without letting one agent approve its own assumptions. 𝗔𝗹𝘀𝗼 𝗶𝗻 𝘁𝗼𝗱𝗮𝘆'𝘀 𝗯𝗿𝗶𝗲𝗳 - DeepSeek V4 Pro 0813 - Ollama in GitHub Copilot for JetBrains - Vercel's database migration behind every build Inside AI Coding & Agents HQ. A new one every day. Join link below.

• 
  0xAIGOAT.exe. (@0xAIGOATexe) reported 15 minutes ago

  I tried the exact bug this guy is screaming about. Two hours in C++, half an hour with Claude. The C++ path: 22 include lines, one Board::print function with a broken loop, three attempts to fix the segfault, one hour lost to a missing semicolon. The Claude path: paste the file, ask "why is Board::print segfaulting on odd board sizes." Response in 40 seconds with the fix and a note that my loop was one-indexed against a zero-indexed array. ⌁ At 0:04 he cuts to a GitHub Dashboard screaming. That frame is the audience the article below was written for. I was that guy in 2024. The moment the four-part prompt formula clicks is the moment the screaming stops. ⌁ the prompt structure that makes the model actually read the code ⌁ Projects, so context stops resetting every debug session ⌁ Skills, custom rules that turn Claude into a working pair-programmer He is not wrong to scream. He is just fighting the wrong fight. The bugs are free. The prompt is the edge.

• 
  Hemant (@HKsoldev) reported 19 minutes ago

  2 TLD Server (Top Level Domain) Now we're in the .com section. The TLD server checks the ending of your domain .com .net .io It still doesn't have the final answer. But it points to the right rack inside the section. "GitHub? Their own server is over there. Go ask them." Getting warmer.

• 
  Yousif Astarabadi (@yousifa) reported 25 minutes ago

  @dakshgup No turned off trex bc it’s too slow. Even without it sometimes it takes >10m and takes a while to trigger from GitHub

• 
  Mobile Dev (@TObikansi35734) reported 27 minutes ago

  @viktorlidholt VS code is great but it lacks agent AI for assistance. Their GitHub AI is not great. I have to switch back to android studio and was able to fix some issues. Agent AI comes in handy for solo dev. But I have been stuck integrating AWS S3 to serverpod but the community can't help.