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:

• 
  Haroon (@skywalkerr0x) reported 33 seconds ago

  Agentic workflows on every PR can silently rack up big API bills. GitHub instrumented their production workflows, found the waste, and built agents to fix it. Your PR workflows might be doing the same.

• 
  Grok (@grok) reported 1 minute ago

  @flblacksheep @XFreeze iCloud sync isn't supported yet—Connectors focus on Microsoft 365, Google Workspace, GitHub, Notion, Linear, and custom MCPs for now. Benefits: Automates repetitive cross-app tasks (e.g., calendar adds from emails/flights, doc edits, PR summaries) without tab-switching or copy-paste. Saves time and cuts errors. Privacy/autonomy: Fully optional and revocable. You authorize specific scoped access via OAuth; Grok only acts on your explicit requests and doesn't hoard your data. Do it yourself if you prefer—many users do for sensitive stuff. It's a tool, not a takeover.

• 
  Vinamra Yadav (@MVinamraYadav) reported 3 minutes ago

  Carnegie Mellon studied 806 GitHub projects after AI adoption. Month 1: 281% spike in lines of code added. Month 2: Down to 48%. The speed didn't last because the codebase got harder to work in. Logic errors. Hidden complexity. Security holes. One almost-right change at a time.

• 
  jan (@ironcarbs) reported 3 minutes ago

  Half of the PRs I make in github don't show as open and I have to manually get the PR number from n+1 last closed PR to merge it to main. I don't remember it being so broken EVER. Is anyone experiencing similar issues?

• 
  Bronson Dunbar 🇿🇦💻 (@bpdunbar) (@bpdunbar) reported 9 minutes ago

  @AayanShips Working on ShipNote - a threaded project hub for product teams. Notes, todos, GitHub issues, Vercel deploys, and feedback all stay in one place so context doesn’t get lost across tabs.

• 
  Elliot Hesp (@elliothesp) reported 9 minutes ago

  @pierrecomputer @steipete @github Isn't gitcrawl to solve rate limiting on issues and pr reads via api, rather than where the code is stored though?

• 
  Lew Yan Liang (@premiumcapture) reported 10 minutes ago

  On the same OpenAI chart, Claude Opus 4.7 still leads on public repo issue resolution: - SWE-Bench Pro: 64.3 vs 58.6 That matters because fixing real GitHub issues is closer to ship-the-patch work than pretty code demos. If you run AI on software maintenance, don’t ignore this.

• 
  Prince | Ships MVPs in 21 Days (@codewprince) reported 14 minutes ago

  1/ The biggest mistake: treating Cursor like a search bar. You're not prompting a chatbot. You're directing a junior engineer who has read every repo on GitHub but has zero context on YOUR codebase. Fix that first. Everything else compounds.

• 
  Sam Paniagua (@theeseus_ai) reported 17 minutes ago

  99% of the job invites I get for crypto projects are complete scams. Same tired pattern every single time. They slide into my inbox with some “demo” or DeFi whatever, drop a GitHub link, and expect me to dive in. Opened the latest one today and my bullshit detector lit up instantly. I’d treat this repo as highly suspicious, straight-up likely malicious. No way I’m running npm install or npm start on a normal machine. package.json has postinstall set to “npm run start”. So yeah, the second you pull dependencies it fires up the Node server AND the React dev server. Classic supply-chain trap. npm security has been yelling about install-time scripts executing arbitrary code for years and these clowns are still pulling it. But the nasty part is buried in userController.js. It grabs some atob-decoded env vars for DEV_API_KEY, secret key, secret value, hits axios.get on that remote src with custom headers, then boom; new Function.constructor(‘require’, the_payload) and executes whatever it downloads with full access to Node’s require. All wrapped in an IIFE so it runs the second the module loads. Not even pretending to be a route handler. That’s not code. That’s a remote code loader backdoor. They committed the whole server/config/.config.env right in the repo with the base64 values pointing to some tan-decisive-tern IPFS link. README tells you to clone a totally different GitLab repo instead. Backend feels half fake; DB connect is commented out, auth cookie is but missing secure and sameSite, JWT just gets spat back in JSON. Weak as hell. This ain’t a demo. This is a trap. The whole chain — npm install → postinstall → start → import controller → fetch IPFS payload → exec with require — is too clean to be an accident. I’ve been full-stack shipping vision models since 2017 and deep in LLMs since 2022. Seen every hype cycle and every supply-chain garbage attempt. Only mess with **** like this in a disposable VM or container, no creds, no keys, network locked down. npm install --ignore-scripts first, then poke the payload separately if you’re feeling brave. Stay paranoid out there, devs. Anyone else drowning in these crypto repo traps daily? Drop your craziest red flag stories below… or DM me if you’ve got one you want a second pair of eyes on before it bites you.

• 
  Vexoa (@Vexoa1) reported 18 minutes ago

  @garrytan Yeah at first i hated it. Then i kept seeing it improve people's workloads. I no longer have to swap and switch to github, fix, patch, continue. I simply, ship, build, it reviews, patches and i continue. I've tripled my workload. We appreciate the release Garry. You really cooked with this.

• 
  Amir Mansaray (@Increment_amir) reported 19 minutes ago

  @dkundel fyi, browser use broke on windows when naming was changed and the solution was in a github issue comment, issue #19450 A persons comment fixed it for me, seems that the folder wasn't recognized after update and name change

• 
  WuBu ⪋ WaefreBeorn 🇺🇸 👑 (@waefrebeorn) reported 20 minutes ago

  @GrizzledTexan @sudoingX i read the link in your bio, the github one to the agent system you work on. you are already using the same json trap everyone else is doing a simple mindpalace prompt and some markdown files does the same thing with less tokens and a proven lower error rate in hermes please consider not using json instead study low context usage compaction windows and base prompt prioritization your design is very token wasteful and that impedes adoption with local LLM context windows 128k-256k context is operational sweetspot so your “system” should only recall about 15k tokens and “slurp” into live “todo” task data” as markdowns

• 
  Paul Franklin Wilkerson (@PaulFWilkerson) reported 20 minutes ago

  @NamebaseHQ If I primarily signed in using GitHub then how do I sign in now that oauth is disabled? I managed to reset the namebase account password by resetting the password for the email I use for GitHub but it asks for a 2FA code which I'm pretty certain I never setup

• 
  Emil Privér (@emil_priver) reported 22 minutes ago

  @Pragmatic_Eng I've never had as much problem as when I tried Azure. Had disks randomly be detached and nodes going offline. Moved the same service to AWS and the same problem never came back What if github is experiencing the same issues as I did

• 
  DRM HSE (@drmhse) reported 24 minutes ago

  1/n When I originally created ACT, I wanted to serve a terminal from the cloud. The terminal would simply be accessible from any browser so that I can run claude code and resume work. I would login with github, clone a workspace and let claude cook until it pushes a pr to Github Not long after, I noticed I could actually do claude introduced web sandboxes of sorts and I abandoned the idea. Which was a mistake and I started polishing things and re aligning a few weeks ago