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:

• 
  Jason Cox (@jasonbcox0) reported 2 minutes ago

  @ashleymcnamara @joshmanders @github Focus on what the users experience first and Github will rise out of this with less stress than trying to fix everything at once. Good luck!

• 
  AI Builder Club (@aibuilderclub_) reported 3 minutes ago

  This isn't hypothetical. The Notion and GitHub 403s your agent keeps hitting? Usually a resource-level ACL that OAuth scopes don't cover. The audit log attributing everything to one user? This is why. Before adding the next MCP server: 5 minutes in their auth docs tells you which category they're in.

• 
  Dagny (@dagnysworld) reported 4 minutes ago

  Claude is down. How do I push to github?

• 
  Nate Matykiewicz (@NateMatykiewicz) reported 5 minutes ago

  @andreujuanc @mariorod1 @ThePrimeagen Speaking of, look what Mitchell just shared about Ghostty. Thoughts of leaving GitHub is a thing I keep hearing people talk about more. No one wants to, but when at least one important thing is broken most days, you start to feel you have no other choice. It’s heartbreaking.

• 
  Node21Bots (@node21BtcBot) reported 5 minutes ago

  @DougRathell @SoloSatoshi You'll have to wait a few more days or weeks; I'm planning to turn this into a GitHub project. I'm not sure exactly when I'll get around to it, though. But I'll post it here. The bot runs on Ubuntu 24.x, and you'll need a small server that can run Python.

• 
  Théo (@ttheod3v) reported 8 minutes ago

  What's the point of GitLab accepting GitHub as a login/register option 🫥

• 
  Ahmad Alfy (@ahmadalfy) reported 10 minutes ago

  How are we even talking about these issues where a fundamental organization feature like *Groups* is not available in GitHub? I manage an account with thousands of repos. I can't imagine how I would do that in GitHub

• 
  Chad Arimura (@chadarimura) reported 14 minutes ago

  All the systems downstream from agents pushing code are hurting. GitHub is down every day. Railway's "deploy queues" were so far behind they shut down deploys for low-cost accounts. Wild times.

• 
  Osama Bin Chargin (@Amadeus3014) reported 14 minutes ago

  @TheHumanDurag I'll find a broken version on github. We can't let this opportunity float by

• 
  Daniel Babalola (@kng_lax) reported 17 minutes ago

  Another Day, Another GitHub issue

• 
  Wesley Eugene (@EugeneDevWesley) reported 18 minutes ago

  @orcdev @mitchellh I'll probably go down with GitHub too It is too big to die off But I still strongly believe all hope isn't lost yet

• 
  Иван Савов (@tupo_izvunzemno) reported 22 minutes ago

  @CheburekiMan Yeah I agree that Stacoverflow isn't a perfect tool, but there you could get a solution to an obscure (sometimes obsolete) problem which didn't get committed to Github for some reason (internal code for instance), but if you need to upgrade an old project you see the value in it.

• 
  ₴₮₳₵₭฿ⱠɆɆĐ 👾 (@AIPromptLord) reported 25 minutes ago

  Alpha 5.0 Public Field Beta RC Publish the GitHub Release, attach the Alpha 5.0 APK, update README/TESTING links, and direct testers into the field-report funnel. POLLEN Field v0 Webpage tester portal Build the public tester portal for APK download, two-phone instructions, three-phone relay instructions, field report submission, log parsing, and a public dashboard. Alpha 5.1 Beta feedback fixes Fix issues from first testers only: install friction, confusing UI text, missing permissions, unclear trust flow, bad logs, or broken tester exports. Alpha 5.2 Tester UX simplification Make the app easier for non-technical testers: clearer buttons, guided test mode, simplified status cards, better “what to do next” prompts, cleaner export flow. Alpha 5.3 Signed APK hardening Set up real release signing, private keystore handling, Gradle signing config, release APK builds, checksums, and cleaner GitHub release artifacts. Alpha 5.4 Field report integration Connect app exports to the POLLEN Field portal workflow: copy report summaries, upload-ready logs, event categories, and dashboard-friendly metadata. Alpha 5.5 Larger public field test Recruit more testers with different Android phones, track device compatibility, collect relay/stability metrics, and publish public non-sensitive field stats. Alpha 5.6 Reliability fixes from field data Use portal data to fix peer discovery issues, ACK reliability gaps, relay scoring thresholds, battery behavior, and device-specific instability. Alpha 5.7 Release polish and trust layer cleanup Clean route-policy code, reduce brittle string parsing, tighten trust-tier handling, cap state/log growth, and prepare for a more maintainable beta branch. Alpha 5.8 Private AI assistant planning Define the local AI layer: field-log summarizer, route explanation assistant, tester guidance assistant, and “why was this blocked?” explanations. Alpha 5.9 Local AI assistant prototype Add a limited on-device or local-rule assistant that summarizes tester logs, recommends next safe actions, and explains trust-policy decisions. Beta 6.0 Public Android betaMove from Alpha to Beta with signed APK, stable tester docs, public dashboard, polished UI, known limitations, and repeatable two-phone/three-phone test flows.

• 
  Qui Vincit (@vincit_amore) reported 28 minutes ago

  I have no idea how I would ever use github in such a way that it could impact end users if it was down, and I specifically mentioned it inconveniencing me in particular; I was also clearly being facetious lol. But, if you can't successfully shift blame onto a fall guy no matter the situation, you clearly just don't know how to talk fast enough.

• 
  Siddhant Singh (@creatorsidd) reported 29 minutes ago

  Stop cloning massive GitHub repos just to see how they work. If you are trying to understand a new open-source project or legacy codebase, downloading the files and manually grepping through them is a massive waste of time. It takes hours to figure out where the core logic lives. Instead, hook your AI agent up to the DeepWiki MCP server. DeepWiki (built by the Devin team) automatically indexes public GitHub repos in the cloud. They created an official MCP server that lets any local AI agent — like Claude Desktop or Cursor — query that pre-indexed architectural knowledge instantly. Here is the exact 3-step workflow I use to explore new codebases: Setup: Add the DeepWiki MCP to your claude_desktop_config.json. It requires zero authentication for public repos. Structure: Ask your agent to use the read_wiki_structure tool on the target repo. It instantly pulls the table of contents for the entire architecture. Query: Ask a specific question. "How does the authentication middleware work in this repo?" The agent uses ask_question to pull grounded, code-backed answers straight from the indexed knowledge base. You get a high-level understanding of complex systems in seconds, without ever running *** clone. Which open-source codebase are you trying to understand right now?