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:

• 
  z (@animaginarynumb) reported 3 minutes ago

  do i launch next week? my github actions are down and my ci/cd runs on them. when i get the refresh on 1st of september, should i launch my product?

• 
  Adedolapo (@0xqdee) reported 3 minutes ago

  Never saw this coming: my @GitHub account was suspended in the middle of a project due in two days. I had pushed a PR and requested a @ChatGPT Codex review when I was locked out. To my knowledge,I haven’t broken GitHub’s rules. I’ve filed an appeal and hope for an urgent human review.

• 
  Aakash Gupta (@aakashgupta) reported 4 minutes ago

  Developers wanted to resume Claude Code sessions so badly they built their own tooling for it. Shell hooks that save the session ID on exit. A published Ruby gem for bookmarking sessions by name. Custom zsh functions passed around like recipes. All of that engineering existed to preserve a single string. The sessions were never lost, which is what makes this a great product lesson. Claude Code stores every conversation as a JSONL file on disk, and the CLI could always resume them. The desktop app just couldn't see them. A GitHub issue back in April called it mostly a surfacing problem. So for months, users filled the gap themselves. A SessionEnd hook here, a bookmarking tool there, each one a tiny patch over the same hole. That's the strongest demand signal in software. A feature request costs the user 30 seconds. A workaround costs them hours, and they maintain it. When people start publishing packages to route around a missing feature, they've stopped asking and started paying with their own time. The best product teams read this signal deliberately. Upvotes tell you what sounds nice. Workaround tooling tells you what people already can't live without. And the reason this feature earned that level of desperation is worth sitting with. An AI coding session carries hours of accumulated context. Decisions made, constraints explained, dead ends ruled out. Losing it means paying that cost again. The session is quietly becoming the durable unit of work, and it just learned to travel.

• 
  Stats Wire (@StatsWire) reported 11 minutes ago

  @github Many a times my chats are lost in GitHub and I don't find them when I need them. Quite annoying. Fix it.

• 
  Tauhid IQ (@iqtauhid) reported 11 minutes ago

  - Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build. Follow Tauhid IQ for regular update.

• 
  AIBotics (@AIBoticssq) reported 11 minutes ago

  @vepsi__ SWE-bench Pro. If it cannot autonomously resolve real world GitHub issues without hand holding, it is not a Fable 5 killer. We need the receipts

• 
  Scott Robinson (@ScottWRobinson) reported 12 minutes ago

  @SamuelRome97104 Spotted GitHub reliability issue

• 
  KrunalSinh Sisodia (@krunalbuilds) reported 14 minutes ago

  Senior Backend Interview Question: Two engineers manage environment configuration. Engineer A 👇 // In the codebase: const config = { db: 'postgresql://****-db:5432/users', apiKey: 'sk_live_abc123xyz', redis: 'redis://****-cache:6379' } Engineer B 👇 // In the codebase: const config = { db: process.env.DATABASE_URL, apiKey: process.env.API_KEY, redis: process.env.REDIS_URL } // Actual values only exist on the server Engineer A pushes to GitHub. 3 hours later he gets an email from GitHub: "We detected a secret in your repository." The attacker had already used the API key. Engineer B's repository has no secrets. Different environments get different values. No exposure. No breach. This happens to 50,000 developers every year. Which one would you approve — and why?

• 
  ryanair no fly list (@rnflpeeps) reported 16 minutes ago

  okay, cubic code review complained about some bugs so I used the opencode agent on GitHub to fix it then ember uses cursor to review the code do we do anything atp

• 
  abubakar (@Abubakar_2005) reported 17 minutes ago

  i went through @warpdotco open source take-home today and this was a pretty interesting one the task is basically: build a system that decides which policies apply to each employee and keeps them correct as things change. a few things i ended up thinking about: most rules reduce to subject → condition → result, some results can have multiple values (apps, trainings), while others can only have one (manager, vacation), if two rules conflict on a single-select value, priority needs to be explicit using P1, P10 instead of P1, P2 lets you add rules in between later without renumbering everything reconciliation gets interesting when the thing you’re managing exists outside your system like a GitHub access probably shouldn’t just sit there waiting for someone to read the dashboard still working through the audit trail part, but this was a fun problem to reason through.

• 
  Ryan Shaw (@ryankshaw) reported 18 minutes ago

  That thing where GitHub is always down now because of increased load from massive agentic activity, is just a preview of what is going to happen with almost every service we depend on. If it does something useful, and has an API, or a scrape-able website, it's gonna get hammered

• 
  Agentic Joe (@agentic_joe) reported 19 minutes ago

  Serious question, and I promise I am not trying to be a ****. But how in the hell is @NousResearch so praised and recommended with all of these outstanding GitHub issues? I could never imagine preaching about having the best harness, using multiple agents etc and not figuring out how to resolve all these issues internally as a company, or at least try to maintain the queue before shipping new features that continue to break stuff. Not to mention their UI/UX. Very hard to believe this team came from a solid engineering background. I could be wrong, but damn! 👀

• 
  yuppie (@yuppieventures) reported 19 minutes ago

  @notashelf bro, you need a server to run your builds. I'd suggest some kind of beefy NUC that you can SSH into at anytime or if you do work on github, you might be able to register that NUC as a github actions runner and do all that compilation in CI/github actions.

• 
  vechen (@miu21590) reported 20 minutes ago

  @CoderSafari by your logic, they could have been abusing it even without me, and just because the tool could theoretically be rewritten for abuse we could take down half of everything on GitHub my intention is to use the model quota I paid for in a way that's convenient for me, even with models that aren't available by default for coding (like Pro)

• 
  Paarth Gala (@gala_paarth) reported 24 minutes ago

  @sridharfyi 👀 Here’s what I’m working on: A self-hosted AI agent builder that removes the painful setup. 🎯 Pick what you want the agent to do 🤖 Choose Hermes or OpenClaw 🧠 Pick a model cloud or Ollama 🔌 Connect GitHub, Notion, Stripe, Telegram, Slack + 70 other tools 🚀 Generate the setup for your own server Your server. Your API keys. Your data. 🔐 Still validating the idea so if you’ve ever tried deploying a self-hosted agent, I’d genuinely love to know: Would this have saved you time? What’s missing? 👇