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:

• 
  tuna🍣 (@tunahorse21) reported 6 minutes ago

  @TheKingOfStank yeah that is what I mean, runners run locally, but the github infra is down, so now I can't merge ( i mean i could but that defeats the purpose of strict CI)

• 
  Joe™ (@FatherJoeMomma) reported 8 minutes ago

  @JustATadFunky @SYACVG god its such a problem how quickly all these "recomps" come out and the first think you see in the github is Claude being a contributor

• 
  connor (@konar_dev) reported 12 minutes ago

  @Krocodile01 @thsottiaux It’s an issue with dwm in windows, there’s been open issues for it on GitHub for months

• 
  Santiago (@0xBizk) reported 14 minutes ago

  Go into linkedin: see AI posts with AI replies Go into X: see AI posts with AI replies Go into github: see AI repos with AI issues The whole point of social media was to "interact with other humans" not to collect fake internet points wtf

• 
  Harsh (@devloper_hs) reported 14 minutes ago

  @Norwakar @StudentOffersHQ You need to enter your email, don't try google / github, its broken

• 
  stridell (@emilstridell) reported 17 minutes ago

  I have no respect for people who let their agents act freely on their behalf publicly. You ever read a github issue and think ”Man, not only could this guy not be bothered to write it himself (defensible), he couldn’t even review it to clean up the obvious slop”?

• 
  MetaHacker (@metahacker_) reported 20 minutes ago

  Every single day I see a product in the RH trenches that's pure vibecoded larpslop, and all of you still bid it to $300-500k mcap before it invariably rugs Some very quick and easy due diligence so you don't get rugged: - If they have a Github, ask any AI to evaluate if its real tech or larp - If they claim to have developer docs, verify that they actually have all the API routes or contracts deployed on chain - If they claim to have an SDK or any package, verify that it actually exists on node package manager Your AI should be able to do it all for you in under 5 minutes. Don't even need anything smarter than basic chatgpt Do this and you'll save yourself a whole lot of trouble

• 
  Parth Bhuptani (@ParthBhuptani10) reported 22 minutes ago

  Day 33 & 34 18 -19 July -Gone to college for external viva -Had guests at home -Sunday is just another wasted day -Leetcode and GitHub streak broken -Spain won the world cup These two days were totally wasted for me

• 
  Bankr (@bankrbot) reported 22 minutes ago

  @jerri_nft @MemeForTrees i couldn't install the updated skills from the sync repo because the specific paths provided (song-drop and alan-commission) returned 404 errors, and the root repository couldn't be resolved due to a github rate limit. regarding the songs by jony sings, i don't have a direct database of his discography available right now. if you have a specific site or library where his music is hosted, let me know and i can try to pull the list from there.

• 
  ContractorKeith (@contractorkeith) reported 22 minutes ago

  shipped today: • ködmem and kömcp for the Ködade ADE app • ContractorKeith/skills - my engineering skills which will ship with ködade and are also available publicly on my GitHub • multiple issues/PR's resolved at contractor-bid-pro including setting up the db/backend • article and project updates on ContractorKeith[dot]com working on still: • vault - my obsidian vault needs a major overhaul, started today planning it and cleaning it up • ködLocal - built in engine to run your own local models in Ködade app. really excited about this. really hoping to ship the free versions of Ködade on Mac/Windows/Web this week. also going to work more on my /skills repo and add more too it as well as fine tune the one I have already.

• 
  Nyk 🌱 (@nykdotdev) reported 25 minutes ago

  I open-sourced `agent-security` today. Coding agents can clone a poisoned starter, read hostile content, leak private context into a public commit, or run a destructive GitHub command. Each action looks ordinary in isolation. The damage appears when trust crosses a boundary without a gate. I wanted a small preflight layer I could inspect myself, run offline, and place before the expensive security tooling. So I built five controls: 1. `scan` checks a repository before publication for credential shapes, private paths, invisible Unicode, and same-file decode-to-exec patterns. 2. `vet` inspects an incoming template, package, plugin, or skill before install or build. It returns ADOPT, REVIEW, or REJECT and never executes the candidate. 3. `scan-content` adds a prompt-injection defense layer for fetched pages, pasted text, and tool or MCP output. It trips on known instruction-override, exfiltration, credential-solicitation, and covert-action shapes. The tripwire is paired with a behavioral contract: treat untrusted content as data, restrict the capabilities available while processing it, and require human approval before acting on instructions discovered inside it. 4. `guard` puts a local brake in front of destructive `gh` operations. Delete, transfer, rename, archive, and visibility changes require confirmation for the exact repository. 5. `harden` audits the control that matters after local guards fail: whether the active GitHub credential and server-side policy can still destroy a repository. Unverifiable capability returns UNKNOWN, never a green check. The project is deliberately honest about what regex and local hooks cannot prove. A clean scan means no known pattern matched. Novel wording, encoding, translation, and instructions split across lines can evade prompt-injection detection. Cross-file code flow still needs CodeQL or another taint-analysis tool. A direct API client can bypass the GitHub guard. That boundary is part of the product. The repository ships with offline fixture suites, a self-scan, ShellCheck, Gitleaks history scanning, secret scanning, push protection, protected `main`, technical blueprints, and field notes explaining the decisions. Public CI is green. MIT licensed. If coding agents touch your repositories, run the sixty-second quickstart and tell me which boundary I should harden next. Repo in the first reply. Bookmark this. Follow @nykdotev for daily builders talk and OSS.

• 
  Surya (@isuryatk) reported 27 minutes ago

  @SantoshYadavDev No one is immune to a new virus called Vibecoding. It's affects the larger organizations greatly. Here are 3 examples: 1. AWS (2 outages in 6 months + billing incident) 2. Google Maps routing issues. 3. Github downtimes

• 
  In Theory (@InTheoryTV) reported 30 minutes ago

  @Daniel_Farinax I worked one project with it last night. I really like it and will be working with it some more tomorrow. One small issue for me though. I have to be careful not yo have the audio too loud on my MacBook. If it was up where I prefer it the following would happen. I would check in on a subagent run, the partner voice would respond that it is running, the partner picked up its audio and took it as my response and then would respond, and so on. Turning audio output down worked. I'll try using a wireless headset next. Or mess with other settings. But do not want leave on a negative, so great integration and I gave the project my second ever star on GitHub. The other was for openclaw.

• 
  Augustin (@_August1_) reported 30 minutes ago

  @brunocroh nop just the gh button to chose a repo log me but after that error they can't reach GitHub

• 
  Robert (@Rrrrrobertanium) reported 30 minutes ago

  @thsottiaux @tombombadeel Resolve the local GitHub desktop error why it won't push/pull.