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:

• 
  athas.dev (@athasdev) reported 14 seconds ago

  @_heyrico @github Looks nice but I'd fix a few things: - remove title (breadcrumb is there) - remove `underline` from links

• 
  Serhat (@srhtkrg) reported 37 seconds ago

  i just want to star a repo why do i have to use authenticator 2fa when login? @github

• 
  Alexandre Mutel (@xoofx) reported 4 minutes ago

  Last year I rolled out GitHub Copilot to all engineers in my org after realizing many weren't using any AI tools. Usage grew fast, with a classic long-tail distribution, Copilot was absurdly cheap, and in 3 weeks we'll need to revisit token consumption/budget seriously... glad I don't have yet that problem for my OSS projects with a subsidized Codex personal license 💸

• 
  Rahul Gangotri (@rahul__gangotri) reported 5 minutes ago

  WDYM you cannot charge my card automatically @github ? I was subscribed to pro 39 usd plan, just charge my credit card instead of downgrading, seriouly wth github fix it, i want my pro plan back bro, i am not going to pay per usage pricing, that is super expensive, my usage is not that much

• 
  Brown Thunder (@Brown_Thunder76) reported 7 minutes ago

  There’s a lot of nonsense floating around about Keeta right now. You have people watching GitHub updates and claiming the team is “just changing a few words.” No. That’s literally developers working on the same issue or refining commits. Not every GitHub push is some massive standalone feature release. Learn how development works before speaking on it. Then you have people giving the project flack because Ty’s end of March comments haven’t translated into publicly visible partners, usage, or products yet. But Ty has consistently said he believes end of Q2 is when we should really start seeing things come together. We are not there yet. The team is still actively building. Ty is still in Discord talking about progress and announcements. People in this space are conditioned by instant gratification and are forgetting the “why” behind Keeta. And that matters. Keeta isn’t just trying to launch another token. The entire point of Keeta is solving a global payments and settlement problem. Crypto is simply the mechanism being used to achieve that. That’s a much bigger and more difficult objective than most projects in this space are pursuing. Not everything being built or tested right now is publicly accessible. The team has repeatedly said this. Infrastructure, payments, compliance, integrations, and enterprise tooling are being developed privately before public rollout. There is even a private testnet specifically to prevent leaks while things are being built and tested. If you want constant releases and nonstop visible updates every single week, this probably isn’t the project for you. Personally, I believe in the technology. Building something like this from scratch takes time. The team is releasing information as they can, and quite frankly I don’t think the current level of FUD is warranted when we haven’t even reached the timeline they’ve been pointing to. Now if end of Q2 comes and absolutely nothing has materialized publicly, then sure, people deserve a direct update. That’s fair. But right now the team just signed another partner, multiple products and systems appear to be developing in parallel, and it sounds like several things are intended to launch together. Too many people are confidently speaking out of their *** about this project. Things evolve. Timelines shift. Features change as systems are actually built and tested. That’s what real development looks like. I don’t think this thing explodes overnight. But I do think once the network can actually be used as intended, growth starts becoming real and over time exponential. @KeetaNetwork $KTA

• 
  Dr. Nripanka Das (@DasNripanka) reported 9 minutes ago

  @emollick AI policy is going to follow liability, not capability. Doctors and lawyers have a body to point at when things break. Software has GitHub issues and vibes, so the default reaction becomes procurement theater instead of licensing.

• 
  Haroon (@skywalkerr0x) reported 12 minutes 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.

• 
  Shagrath (@shagrath49) reported 19 minutes ago

  @thdxr How do you keep track of what you have to do ? GitHub issues ?

• 
  Charly Wargnier (@DataChaz) reported 25 minutes ago

  🚨 You can currently buy a Series A for $2,241 on Fiverr. A seed round is even cheaper at $1,282. Allow me to break this down. A study out of Carnegie Mellon identified 6 million fake GitHub stars distributed across 18,617 repositories. The market rate is roughly $0.45 per star. Langflow, sitting on 147K stars, was found to be 47.9% artificial. Venture capitalists rely heavily on GitHub stars as their primary radar for sourcing deals. Redpoint recently shared the industry medians: open-source startups at the seed stage average around 2,850 stars, while Series A hits roughly 4,980. a) 2,850 × $0.45 = $1,282 buys the traction for a $1-10M seed round. b) 4,980 × $0.45 = $2,241 buys the optics for a $10-30M Series A. The legal risk is severe. The FTC’s Consumer Review Rule carries penalties of up to $53,088 per individual fake engagement violation. We have already seen the SEC charge the founder of IRL with securities fraud after faking user metrics to secure a $170M raise. Union Labs, the project that dominated the Runa Capital ROSS Index in Q2 2025, was exposed as having 47% fake stars. Stars are a metric you can manipulate in minutes. Forks are a different story. A star is simply a bookmark. A fork means another engineer is literally copying your codebase because it solves a problem they have. Flask commands 250 forks for every 1,000 stars. Langflow manages just 60. Until the bot farms figure out how to believably fake codebase forks, that is the only metric worth your trust. Article in 🧵↓

• 
  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.

• 
  BrainMirror AI (@brainmirrorai) reported 25 minutes ago

  Private Publishing on Replit blocks unauthorized requests at the network level, not inside the app. The problem was always integrations: if you needed GitHub webhooks or Slack callbacks to reach your private app, your only option was to make the whole app public. External Access Tokens remove that tradeoff.

• 
  dagz (@AstrayaNthemoon) reported 25 minutes ago

  @jkpgamer Haha well I was gonna say that I could spin up a GitHub, (Goose + Grok have been dying to let me let them open a GitHub with a key), and then open source the code… it’s like so minimal it’s laughable and then you can put your own location on the map but that’s even better to point to your own server rather than pull the API That’s how we initially had the design built actually but then I wanted it to be something anyone could use

• 
  Paul Franklin Wilkerson (@PaulFWilkerson) reported 25 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

• 
  Shobhit - Building SuperCmd (@nullbytes00) reported 27 minutes ago

  @mufasaland Do you mean file search in root launcher? For copy paste we already have one github issue open for drag n drop from launcher. Will prioritise that

• 
  Umesh Kumar Yadav (@Umesh__digital) reported 27 minutes ago

  Dennis Ritchie created C in the early 1970s without Google, Stack Overflow, GitHub, or any AI ( Claude, Cursor, Codex) assistant. - No VC funding. - No viral launch. - No TED talk. - Just two engineers at Bell Labs. A terminal. And a problem to solve. He built a language that fit in kilobytes. 50 years later, it runs everything. Linux kernel. Windows. macOS. Every iPhone. Every Android. NASA’s deep space probes. The International Space Station. > Python borrowed from it. > Java borrowed from it. > JavaScript borrowed from it. If you have ever written a single line of code in any language, you did it in Dennis Ritchie’s shadow. He died in 2011. The same week as Steve Jobs. Jobs got the front pages. Ritchie got silence. This Legend deserves to be celebrated.