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:

• 
  Firat Özcan (@firatoezcan) reported 1 minute ago

  @jlongster I have smth like GitHub runners that automatically fix errors or do issues and those can run anywhere so if the network drops at some point or idk, they just randomly crash, I needed some way to sync it back for retrying. I tried out combining the event stream and the manual messages endpoint and it worked, but just waaaay easier with the built-in sync

• 
  WuBu ⪋ WaefreBeorn 🇺🇸 👑 (@waefrebeorn) reported 5 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

• 
  Southers (@SouthersDev) reported 6 minutes ago

  I built a bug reporting tool for Field of Command last week. Now I have a full QA team working 24/7 while I sleep! 🤯 How it works: 1.User fills out forms and clicks send inside the game. 2.Cloudflare worker dumps it into GitHub with full logs + screenshots. 3.Copilot triages and categorizes them automatically. 4.Claude picks up active issues when I open the project, maps out the context, and writes the plan. All I have to do is approve or decline the fix. This is how to solo dev with a 9-5 🤖✅

• 
  sre chakra reddy y (@srechakra) reported 8 minutes ago

  @byteHumi A big part of major code maintainers leaving GitHub is due to lowered quality of PRs it's a more generalized problem though, wondering if a threshold PR quality to qualify as contribution needs to be the norm.

• 
  Somanos Sar (@somanossar) reported 9 minutes ago

  "We take data security very seriously” - proceeds to leave the literal master key to the AI kingdom on GitHub for anyone to copy-paste. So iconic by SaaS server. Get used to #DataSovereignty NOW or you're gonna get lost in this chaotic tech illusion.

• 
  Ethan Jiang (@ethanjyx) reported 12 minutes ago

  Year 1 as a solo founder, 10k+ Github contributions (Claude code is really addictive). But looking back, I probably wouldn’t do it the same way. The biggest bottleneck in a business is often NOT solved by more code. Going into year 2, I have a daily reminder to think about biggest bottlenecks and fix those ruthlessly.

• 
  damir akaza (@Damir_Akaza) reported 13 minutes ago

  Here’s how you solve a problem and build a business > buy Claude Pro: $20/month > shoot a 5-minute video on your phone > find a GitHub open-source project - SuperSplat > it turns it into a 3D environment > spend $50 on a domain + server > start making thousands of dollars passively free GitHub link 👇

• 
  kaleb (@KalebAutomates) reported 15 minutes ago

  Days after the CEO came on this platform and **** on the people who made him rich with a massive lay-off. Coinbase issues with AWS. Before this it was Github Before that it was Cloudflare Before that it was AWS itself All of which just happened to follow an announcement of AI doing the majority of coding. Funds are safe... for now.

• 
  latiblack.base.eth (@AHorlaplusone) reported 17 minutes ago

  @MystiqueMide Me here don’t even like testing on dev server. Make sure my code works and push to GitHub at the end of the session

• 
  Yashasvi Kapil (@iemyashasvi) reported 18 minutes ago

  @ChiragAgg5k @github @github is broken beyond repair

• 
  Mary-Victoria Crockett (@MaryVictor96296) reported 21 minutes ago

  @grok Man, I checked the GitHub link and it seems broken. Might have to just screenshot it to you later. That’s a bummer. Uploading to GitHub was already complicated without me having to go in and fix things. 😓

• 
  Praveen Kumar (@CodedPraveen) reported 24 minutes ago

  @GitHubIndia and @github My GitHub account (@CodedPraveen) was recently suspended, possibly due to a misunderstanding after I created an issue on the ngrok repository. I’ve already contacted GitHub Support and requested a review. Hoping for a quick resolution 🙏

• 
  Gabe (@gabebusto) reported 25 minutes ago

  bro setting up an agent to do production work is so easy. you just need to create an account somewhere for your agent to work remotely. cloudflare, hetzner, aws, digital ocean, etc. then pick the agentic tool, and the model, and get an api key or use oauth. then make sure in it's in a sandbox setup with the right permissions and access to your tooling like github, slack, linear, and maybe even some staging and production resources. you really need to be careful though because if agents have any write access to important stuff, it could do something really dumb like delete your database. also for the love of GOD backup your database frequently somewhere the agent can't touch. also prompt injections online can get your agent to leak sensitive env vars so you need to be careful about that. maybe limit network access or inject tokens/sensitive vars once requests leave the sandbox. you probably don't want the agent always on sitting idle, so either figure out how to give it work efficiently to always keep it busy or use some that can pause and resume with ease so you're not billed around the clock for idle resource usage. then you want guardrails in your codebase and deployment pipeline so the agent can't break things and you don't need to feel guilty not reviewing its code. because cmon, nobody wants to do that. you need to make sure your agents have as close to perfect context as possible. so maybe start building a knowledge base, move docs into the repo, or make sure your agent can easily search linear and slack and other places to build context for tasks to work on. and before each task, spend ~10-20+ mins typing things up and giving the agent as much context as possible. oh yeah and your agent ideally should be able to test its changes as completely as possible. so make sure the agent can start up the service(s) it's working on and test them. maybe you need it to open and run a browser, send screenshots, record a video, and so on of its test so you can easily review it in the PR. you also want a bugbot setup in github (if you're still using github at this point) to help scan each PR for potential issues the agent missed. and the agent should be able to automatically address any bugbot findings, fix them, run more tests, and push those changes, and run in a loop until no more bugs are found by the bugbot. i forgot to mention, you probably don't want your agent's code just yolo shipping into **** with no guards in place _after_ it deploys. allow the agent to setup it's new features and code behind feature gates or experiments and do a gradual rollout in case there are any catastrophic problems. then you'll want automatic rollback if issues are detected. and there's probably stuff i'm forgetting, but you get what i'm saying right? it's really not that hard. then you need constant vigilance of your codebase and create lots of skills to help deslop work the agents are doing, maybe create an anti-entropy agent (_another_ agent!) to hunt for growing complexity and auto-create PRs to try and fight to reduce the size and complexity of the codebase. then you'll inevitably have incidents caused by code written by agents that was never reviewed by humans, and either you or yet-another-agent will take a look at your production systems to help you figure out what's wrong because it's all becoming a bit more foreign to you. and you can just have the agent try to make changes on your behalf to fix things and hope to God that it doesn't make things worse. if all of this isn't exciting enough, you then give each engineer and even non-tech team members their own access to the ai tools and agents and models of their choice which easily costs an extra few hundred dollars per month per employee at best. in the worst case, you have someone on the team blow through the team's monthly AI spend by a significant margin by accident using the best models in fast mode because they were too impatient to just use the sota models at normal speed. and spend will likely only go up btw. and if you're not reading between the lines here, product work slows because everyone is playing with agents to learn how to use the agents more efficiently in the hopes that it's a magical bullet that solves all of the woes in software engineering and building production systems. and now you need this magical bullet to work because you're falling behind to teams who maybe aren't distracted spending all this time and money trying to make this all work. but you're definitely going to catch them. once you've figured this out, you'll 10x or 100x your output and leave them in the dust! or... you could just have engineers start coding by hand again before it's too late and becomes a lost art. you can even make modest and tasteful use of ai, but without doing all of the above. i actually miss the days of supermaven and early cursor. they were so simple and actually removed some friction and some of the annoying parts of coding.

• 
  TradFidiGuy (@TradFidiGuy) reported 32 minutes ago

  @emojibakemono @gf_256 @kamilaposting The GitHub issue in the screenshot is literally titled “brew install upgrades everything”🤦

• 
  jan (@ironcarbs) reported 35 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?