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:

• 
  Mark yu (@Markymarco34) reported 37 seconds ago

  There is another point that should not be ignored. At first, the main focus was the hard fork and PoX-5. We were told to wait for the hard fork, then wait for restaking to recover. Now, almost without acknowledging that transition, the focus is shifting again — this time to the Genesis Bond and future institutional accumulation. But the hard-fork phase itself has not been problem-free. A real block-production stall occurred around the Cycle 141 transition, and GitHub now shows additional tenure-boundary / pre-commit handling issues being worked on. So before moving the narrative entirely to Genesis Bond, the problems that appeared during the hard-fork transition should be clearly explained. I am not saying the Genesis Bond is irrelevant. I am saying the previous phase should not quietly disappear from the discussion simply because the next catalyst has arrived. First it was the hard fork. Then restaking. Now Genesis Bond. Each step may be legitimate on its own. But when the expected impact keeps moving to the next step, the unresolved issues from the previous step still need to remain on the ledger. @muneeb

• 
  Mark (@Mark850428) reported 2 minutes ago

  @nishchay_jais And on my works GitHub any PR with more than 250 lines changed, is simply rejected with no review no feedback, if you cant fix it in 250 lines, something is wrong. Exceptions are VERY rare

• 
  martian (@martian0x80) reported 4 minutes ago

  github down again

• 
  Falco Girgis (@falco_girgis) reported 5 minutes ago

  @barisyyild Yes, actually. On the bottom of the KallistiOS GitHub repo is the link for the simulant server, which is basically DC dev HQ.

• 
  Shyamprasad reddy (@Shyam_JSP_) reported 5 minutes ago

  @DattuClay @github Last month issue start ayina 4 hours ki update chesaadu andaru vachi meedha padtharu too many issues from last 6 months

• 
  kuro (@abue_ammar) reported 8 minutes ago

  @wiixdede @voithure it does already. instead of asking you should at least give it a shot, if something doesn't meet your expectations there's GitHub you can file an issue there

• 
  Brown Geeky kid (@shigma_male) reported 12 minutes ago

  GitHub dropped a release candidate for Enterprise Server 3.22. It’s all about enterprise features these days—meanwhile, devs are probably just waiting for Copilot to write these changelogs itself.

• 
  Corey Coto (@coreycoto) reported 13 minutes ago

  Another week another data center/service outage. This PhoenixNAP outage is under reported. I look forward to the write up. It's gonna be down for a full day similar to the GitHub outage last week. Lot's of startups and companies rely on Namecheap DNS like Blacksmith for GH Actions Runners.

• 
  nadavdas (@sadvadan) reported 13 minutes ago

  memstruct won’t get a github release soon. tests are complete & no changes planned, but real-world use in an ongoing project will potentially surface nuanced edge cases that need fixing first. after all it's a framework so errors, even if minute, can be cascading.

• 
  Chloe (@chloevalesquez) reported 18 minutes ago

  those go straight to a github issue instead of fighting luna on them. no point burning turns on a model that's not built for that kind of depth

• 
  Lethalmon (@Lethalmon) reported 21 minutes ago

  @briccenjoyer I think that, even if your connection is stable, GitHub doesn't like slow connection. It might be GitHub that force stops your download

• 
  sabir hussain (@sabir_huss50540) reported 28 minutes ago

  A tool that quietly scrapes posts and comments from seven of China's biggest social platforms has 49,700 stars on GitHub. Its own author begs you not to use it for real. It's called MediaCrawler, and it's a small window into who's actually harvesting the social web. Here's what it does. Point it at Xiaohongshu, Douyin, Kuaishou, Bilibili, Weibo, Tieba, or Zhihu, and it pulls posts, comments, second-level replies, and entire creator profiles into clean CSV, JSON, or a database. The clever part is how it dodges the platforms' defenses: instead of reverse-engineering their encrypted signatures, it drives a real logged-in Chrome session and lets the browser generate the signatures for it. No cracking required. It just borrows a real login and walks in the front door. That design choice is the whole story. It's why the barrier to mass-scraping social platforms is now "run this Python script," and why the repo has 10,500 forks. Now read the disclaimer the author wrote at the top of his own project. For learning and research only. Commercial use forbidden. And a direct link to a list of criminal cases in China where scraping crossed the line into prosecution. The person who built the most popular tool of its kind spends the first screen of his README telling you the thing is legally radioactive. Both of those facts are true at the same time, and the gap between them is the point. A 49,700-star tool does not get built and forked ten thousand times for a classroom. The "research only" label is real, and it's also the fig leaf that lets a tool like this exist in the open while everyone quietly understands what it's for: feeding sentiment engines, building marketing datasets, and scraping the human-written text that trains models. The comments under a viral post are worth more than the post. This is the machine that harvests them at scale. There's a second, quieter tell. It's Chinese platforms, but this isn't a China story. Every major social network on earth is in exactly this position: the public data is technically visible, the terms of service forbid taking it in bulk, and a free tool sits one ***-clone away from doing it anyway. Enforcement is the only wall, and the wall is thin. Don't read this as a recommendation. Read it as a status report. The public social web is being quietly vacuumed up by tooling that's free, popular, and openly hosted, wearing a "for research" sticker that everyone has agreed not to look at too closely. The scary part was never that someone built this. It's that 49,700 people wanted it.

• 
  PandaSt0rm (@PandaSt0rm) reported 28 minutes ago

  I kinda despise how AI development on any task is a case of: (1) Try Do the thing. (2) Doesn't work and something breaks. (3) Fix the thing. (4) Something else breaks. (Loop). (Loop+1) Done. No matter how much I prompt I just cant get it to be able to see the trees for the forest. Like I know the models don't possess any real intelligence but like come on this is kinda silly... Just spent 6 hours debugging a pretty complex GitHub CI pipeline (Using Sol on XHigh too) for a project I'm working on that involves like 8 different code bases, and for example it was pretty obvious that in step 3 of the chain a change sol just made would DIRECTLY affect something in step 5, but instead we have to progressively iterate each broken step... one at a time... for 6 hours... I'm pretty sure I could have done it myself in 30 minutes and saved the 300m tokens...

• 
  Chase McDougall (@ChaseMcDou) reported 34 minutes ago

  @KaustubhTrived6 @ayesha_fatiima But if I can't push to GitHub because GitHub is down - then how can they push to GitHub to fix GitHub

• 
  Nibras Hamza (@NibrasHamza) reported 36 minutes ago

  @Anas_founder Official docs, GitHub, and a lot more trial and error.