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:

• 
  ADITYA (@Aditiiitm) reported 1 minute ago

  @SashaSammy15 @sangatechug Interesting. The reporting part sounds valuable, but the hard problem is trust. How does Trillien determine what's actually true when GitHub, Jira, Slack, and docs don't agree?

• 
  Trinks | Making Alerith (@xTrinks) reported 3 minutes ago

  @0xanmol How do I commit my code to GitHub can u help I don’t know what to do the command “github sendcodecommit allcode add comment no claude” is not working ser

• 
  🇨🇦Canadian Spirit🇨🇦🇳🇬 (@Princeflexzy0) reported 6 minutes ago

  I got an idea for the MVP. I feel users will simply create an account using their email, upload one or more CVs, and specify their job niche, preferred roles, and locations. The platform then automatically searches for relevant job opportunities, analyzes job descriptions using OpenAI or Anthropic API, selects the most suitable CV for each role, generates a personalized application email, and submits the application on the user’s behalf. The goal is to make the experience extremely simple, especially for non-technical users. Once a profile is set up, the system handles job discovery, matching, and applications automatically without requiring users to manually search or apply. Initially, all AI processing will run through a shared OpenAI API managed by the platform, allowing users to access the service without providing their own API keys or need dev skills. The MVP will focus on speed, simplicity, and automation while validating user demand before introducing advanced features or paid plans. Will use my personal GitHub Account to make the push but tech users can still get the open source repo on my Backup3 GitHub account that i sent the url on the comment page. Will requote with the link when done and fully tested with this MVP. And it’s definitely gonna be totally free until we get tons of traffic then we charge a token less than 2k to continue paying for server fee.

• 
  Nikhil sinha (@sinhaniik) reported 7 minutes ago

  Spent 30 minutes debugging a *** push failure today. I had modified a React component, committed the changes, and tried: *** push origin main *** responded with: error: RPC failed; HTTP 400 fatal: the remote end hung up unexpectedly At first glance, it looked like a GitHub authentication or network issue. The real problem was hidden in the commit history. A quick check: *** log --stat origin/main..HEAD revealed an earlier commit containing: public/AbNI intro.mp4 | 6.5 MB The push output was also a clue: Writing objects: 6.19 MiB *** wasn't struggling with my React code. It was trying to upload a video file that had been committed along with the code changes. Another lesson learned: I initially ran *** add . from the public/ directory while the modified file lived in ../src/.... *** only stages files within the current path scope, so my changes weren't being committed at all. Debugging flow: *** status → verify staged/untracked files *** log --stat origin/main..HEAD → inspect what is actually being pushed Compare push size with committed assets Remove unnecessary binaries from *** history Add file patterns like *.mp4 to .gitignore A lot of *** problems aren't *** problems. They're visibility problems. The fastest engineers aren't the ones who memorize commands. They're the ones who know which command exposes the truth.

• 
  RusticDreams (@dreamrust50227) reported 8 minutes ago

  This tweet from @itachee_x got me thinking. AI policy feels stuck in a loop right now. A scandal happens and everyone calls for more restrictions. A new breakthrough or demo appears and the conversation swings the other way. Then another incident happens and the cycle repeats. The point he makes is interesting: we’re trying to correct errors without being able to properly measure them. That’s what stood out to me in the GitHub breach discussion as well. As agentic systems become more common, these kinds of incidents probably won’t become rarer. They’ll become more common. Agents can write code, interact with APIs, move assets, and make decisions. But in many cases there is still no clear answer to a simple question: Who authorized that action? And where is that authorization recorded? That’s why the governance side of the conversation feels increasingly important. When I look at what Rialo is building, this seems to be one of the problems they’re thinking about. Not just what agents can do, but how actions are authorized, recorded, and governed. The more capable agents become, the more important that question gets. @RialoHQ @RialoTR

• 
  Norin (@norlava) reported 8 minutes ago

  How I optimize my codebase for AI agents: > AGENTS.md / CLAUDE.md: very explicit including package map, bun only commands, testing rules, release process, changelog rules, debugging flow, instructions to "ask instead of assuming" > Clear toolchain: document canonical install, test, lint, typecheck, and build commands, no competing package managers or overlapping scripts > Validation surfaces agents use: unit & integration tests, doc link checks, package builds, native binary builds, and release artifact tests. The point is not more tests but tests that fail clearly and can point agents to the broken layer > Local hooks before CI: repo hygiene checks plus lint/unit tests on pre-commit/pre-push > CI as the source truth: PR/push CI runs frozen install, typecheck, docs validation, build, unit tests, integration tests, native binary build, and Linux/Windows tests > Codebase index: we run Atomic (from bastani-inc) deep-research-codebase workflow every 1-2 weeks to have a fresh index of the codebase as filesystem memory > Github rulesets block merges: main requires PRs, allows squash and merges, blocks deletion/non-fast-forward updates, has no bypass actors, and requires passing all status checks (we have linux test matrix, windows test matrix, codeql, javascript/typescript analysis) > Release gates are strict: publishing is tag-driven and wait for Linux + Windows binary jobs then re run install/typecheck/tests/docs checks, validates versions/package metadata/private bundled packages, dry-runs npm tarball and only then publishes with npm provenance > AI is in the loop with constraints: Atomic workflows run github issue -> ralph or goal workflow (depending on task size) -> coding agent code review -> manual human code review -> iteration

• 
  Pete Zaitcev (@zaitcev) reported 9 minutes ago

  Someone at work struggled with *** (Github workflow, not distributed). I told him "just use clone, diff, and patch; don't tell anyone". And it solved all his *** problems. All he has to learn is *** commit and *** push.

• 
  toly 🇺🇸 (@toly) reported 9 minutes ago

  @0xSrMessi Submit a GitHub issue

• 
  SAAS worker🌻🌻 (@sand_9999) reported 10 minutes ago

  @forlayo @github @githubstatus We are seeing the same issue. Repository access blocked in runners.

• 
  Sipping on AI (@sipping_on_ai) reported 11 minutes ago

  GitHub Copilot has a desktop app now. The useful test: Can it take 5 stale issues, make reviewable PRs, and explain every file it touched? Try it on backlog dust first. Not the checkout flow.

• 
  Chijioke Echefulachi Prince (@File8it) reported 14 minutes ago

  Then GitHub joined the fight 😭 403 error. SSH issues. Token confusion. Push failing repeatedly.

• 
  VybeCoding (@VybeCodin) reported 23 minutes ago

  Hot take: the open source tools that survive long term are the ones that solve a problem the maintainer actually has. Not the ones built to be a startup. Not the ones chasing GitHub stars. The ones where the dev is also the most annoyed user. Kyrelo started that way. We got fed up paying Buffer to do something simple. What open source tool are you grateful someone built out of frustration? #opensource #github #developers

• 
  OneClaw&ClawRouters&CodeRouter (@VibeSeo1128) reported 24 minutes ago

  Copilot can now autonomously fix sprint bugs from GitHub Issues, propose multi-file refactors, and understand entire repos. GitHub also switched to token billing June 1. Agents that do more = bills that grow faster. The next big unlock: cost-aware agent management.

• 
  andrewthecoder (@_andrewthecoder) reported 25 minutes ago

  @JesseStojan yeah the bin stuff won't work on windows, I had that in my head... the .gitignore stuff... yeah! hadn't actually noticed that. thanks. SEE? this is the **** I am trying to get. do you mine creating an issue on github?

• 
  @ramedey (@RaulAmedey) reported 29 minutes ago

  I solved 80+ GitHub issues with @OpenAI Codex and /goal. It got stuck a few times, but overall: pretty impressive. Biggest lesson: the issue quality matters. Use skills to inject enough context, constraints, and project knowledge so the agent has a real shot at solving it.