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:

• 
  Kuldeep Kumawat (@kuldeep_kumawat) reported 40 seconds ago

  In 2022, a developer named @jarredsumner started building a JavaScript runtime from scratch in Zig - trying to fix how slow and fragmented the JS toolchain had become. Bun combined a runtime, bundler, test runner, and package manager into one binary - no more juggling Node + webpack + Jest + npm separately. It's now crossed 95,000+ GitHub stars (3,00,000+ weekly downloads) and is used as a drop-in Node replacement by teams chasing faster installs and cold starts. In December 2025, @AnthropicAI acquired Bun - betting on it as the infrastructure powering Claude Code and the Claude Agent SDK. Still fully open-source, still MIT-licensed, same team building it. One tool replaces four. And now it's powering the AI coding stack too.

• 
  U N C L E BIGBAY ✨ (@unclebigbay143) reported 2 minutes ago

  Why Was *** Created? 🌱 Before ***, large software projects struggled with slow and unreliable version control systems. In 2005, Linus Torvalds (@Linus__Torvalds) needed a better way to manage the Linux kernel after the project lost access to its previous tool. So he built ***. It was designed to be fast, distributed, and able to handle thousands of developers working on the same codebase. Takeaway: *** wasn't created for GitHub. It was created to help developers collaborate on one of the world's largest open-source projects.

• 
  John (@hello_code_) reported 3 minutes ago

  @DanielSmidstrup Langchain. Incredibly powerful but the docs feel like they were written by the person who built it, for the person who built it. Half the answers live in random GitHub issues from 2023.

• 
  Nathan Skene (@n_skene) reported 4 minutes ago

  UK is going to have to up it’s game in response to this: - Peer review is broken. Why are we not actively seeking replacements? - Grant applications are not as useful way of determining what big projects need to be done - Conferences / power point festivals should to be banned - Papers should be GitHub repos - Our institutions lack any systems for encouraging coordination / field building All the institutions of science need reform. America seems to have grasped this, what are we going to do?

• 
  Ishan (@ishanxtwt) reported 6 minutes ago

  It's not really related to *** at all. *** (the tool) just talks to whatever URL you point it at, if you rename the repo on GitHub, your local *** remote still points to the old URL until you manually update it with *** remote set-url. The old links keep working purely because GitHub (the website) adds server-side redirects.

• 
  Nyx (@nyxiereal) reported 7 minutes ago

  @akku1139 weird, can you please report this issue on our github if you havent already?

• 
  Mehmet Mars Seven 🐴 (@MehmetMars7) reported 7 minutes ago

  1/3 A case from my own experience: as some may know, I prompted GPT on Erdos problems and posted them on github, and one proposed solution was eventually accepted as correct. Never claimed, "I solved it," because I didn’t. GPT produced the solution.

• 
  Martin.... (@MartinJames0905) reported 11 minutes ago

  oh would you look at that @github is having issues again completely unable to merge...

• 
  Pranay Suyash (@pranaysuyash) reported 12 minutes ago

  A GitHub repository is not automatically proof of work. It proves that code exists. It does not immediately show: What problem was solved What actually works Which decisions were difficult What evidence supports the result Where the system still fails Why the project matters For someone to evaluate a project quickly, I now think it needs a proof package: A one-line problem statement. A working demo or short walkthrough. The architecture and key decisions. Evidence from real inputs. Known limitations. A clear next step. The code is the asset. The proof package is the interface to that asset. If another person needs a 30-minute call before they understand what I built, the work is still under-packaged.

• 
  Dinudsi (@dinudsi) reported 14 minutes ago

  @merishabh_singh What could be the problem, resume based sorting? For engineering roles I think GitHub should be consider at highest.

• 
  Harukoxd (@surveys347) reported 15 minutes ago

  @psomkarbuilds In the server it should never read it, as it should be placed by you. In local for things like github tokens I use a vault that never print or logs, its a skill that use that vault to decrypt the github token and pass it through another script, so its never in the console neither

• 
  Bramble King (@Tudmotu) reported 15 minutes ago

  @NathanFlurry It's not Github that's the problem, it's ***.

• 
  Harshit singh (@HarshitXXME) reported 20 minutes ago

  @Anshmishra1414 @github Hey @github please help him with this problem......

• 
  Andrew Barba (@andrew_barba) reported 24 minutes ago

  @joesaunderson @clerk Looking into this asap. Can you send actual error or better yet open GitHub issue

• 
  Austin S. Lin (@siraustin) reported 30 minutes ago

  @prd_008 dear lord no… Sites is a fine name for what it is (it’s cloudflare pages and workers abstracted). one big issue is that you get different levels of github access from within chatgpt app depending on whether you have chat (no access to private repos), work (access to existing repos), or remote selected (full github access to create and manipulate repos).