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:

• 
  The V Programming Language (@v_language) reported 9 seconds ago

  @tauraamuix @IroncladDev Please report gitly issues via github, they will be quickly fixed this way. You can report multiple issues in one github bug report.

• 
  Games from the heaps of Steam (@HeapsofSteam) reported 49 seconds ago

  Take a look at the newly released Silent Hill pc port by kushastronaut. All you need is to download the zip file from his github(links below) and find the copy of the game that you lost in someone else's server. Here you can see a bit of the start of the game and me loading a saved file from near the end of the game to test the 3rd person camera. You can also use the console to skip around and do other things. It's completely playable according to the dev so give it a try if you want but it's still in development. Cybil's bossfight was broken for me in testing, she was shooting the air lmao. Make sure to leave the dev a like. Cheers.

• 
  Jarrad Grigg (@jarradgrigg) reported 6 minutes ago

  You build stuff and host on GitHub pubically? Paste this into a coding-agent session and point it at your own GitHub account. This is happening way too much. ROTATE YOUR KEYS. Review my public GitHub repositories for accidentally exposed environment secrets. Scope: - Only inspect repositories I own or explicitly authorize. - Focus on public repos first. - Check current files and *** history. - Look for API keys, tokens, private keys, database URLs, OAuth secrets, webhooks, cloud credentials, .env files, config dumps, and hardcoded secrets. Safety rules: - Do not print full secrets in chat. - Redact values, showing only provider/type, file path, line, commit SHA if relevant, and a short masked prefix/suffix. - Do not test or validate secrets by calling third-party APIs. - Do not open PRs, issues, or comments that expose findings publicly. - If a likely secret is found, assume it is compromised and tell me to rotate or revoke it. Deliverable: - A prioritized report of confirmed or likely exposed secrets. - Exact repo/file/line/commit references. - Recommended rotation steps by provider. - Cleanup guidance for removing secrets from current files and *** history. - Prevention recommendations: .gitignore, env templates, secret scanning, pre-commit hooks, and CI checks.

• 
  AIToolsDailyIN (@AIToolsDailyIN) reported 8 minutes ago

  @github The "AI is dangerous for security" camp has real data. Cybersecurity firm Snyk tested multiple AI coding assistants in 2023 and found consistent issues: hardcoded credentials, injection vulnerabilities, weak crypto defaults.

• 
  AI Mastery Guide (@aiseomastery) reported 8 minutes ago

  CLAUDE'S ENTIRE SYSTEM PROMPT WAS LEAKED AND ANTHROPIC CANNOT TAKE IT DOWN 27,000 tokens of hidden AI instructions are now public on GitHub.

• 
  HARJGTHEONE DBA (@HARJGTHEONEDBA) reported 11 minutes ago

  “SpaceX investors who bought shares in the last four days got diluted by 3.4% before they understood what they owned. The IPO was literally the printing press for the acquisition. Now look at what he ACTUALLY bought: Cursor's market share among enterprise customers has been collapsing. According to spending data from Ramp, it fell from 41% in June 2025 to 26% in May 2026, bleeding ground every month to GitHub Copilot and Amazon Q. The smart money knew. Andreessen Horowitz, Thrive, and Nvidia were about to lead a round at a $50 billion valuation, which they already considered aggressive. Elon paid 20% more than that for a company actively LOSING the race. He paid premium for declining momentum. And he did this because his own AI division was in trouble. “ @SpaceX

• 
  Apache Superset (@apachesuperset) reported 13 minutes ago

  @J_00_S_T Would love to know more (not all of us use that installation method) if you want to file a GitHub Issue so we can update the docs accordingly.

• 
  SushiRoll (@sushirollbt) reported 13 minutes ago

  @theo The workflows live right next to chats in the sidebar. You set up a source for them (GitHub issues, an asana board, a Jira project, etc) and criteria (bug, unassigned, a size, etc) and it can automatically pull in tickets, work on them and PR them. You can use multiple agents with escalation policies (did it fail with GPT-5.4 mini? Let’s try with GPT-5.5), looping code reviews, scripts to post to slack or respond to PR comments, etc.

• 
  Jacob Gadikian (@Senpai_Gideon) reported 15 minutes ago

  GitHub copilot ai is nice but too slow like all of GitHub

• 
  Michael Liam (@Millionareum) reported 15 minutes ago

  GOOGLE TRANSLATE AND DEEPL ARE OVER. YOU ARE NOT EVEN AWARE OF IT. A developer built an AI translation engine that supports 40 languages and runs completely offline on a laptop. Name: LibreTranslate. No API key required. No usage limit. You do not send your documents to Google's servers. You install it once. It works forever. What it does: - Paste text and translate instantly. - Drop a file, get the translated version. - Develop your own application with a local REST API. Speed ​​is not the issue. Privacy is the issue. Every sentence you type into Google Translate goes to their servers and stays there. Legal contracts. Medical records. Internal correspondence. Customer documents. Every word. LibreTranslate works completely offline. Nothing is coming out of the device. Never. The numbers are as follows: - 40 language support - Runs on CPU, no GPU required - Self-hosted setup in 5 minutes - REST API included for developers - 10K+ stars on GitHub 100% open source. MIT licensed. Price: $0.

• 
  BruzWJ (@BruzWJ) reported 18 minutes ago

  @thdxr ngl im kinda tired of every funded lab shipping a github competitor, my read is the *** host was the easy part the part nobody rebuilds is the issues + CI + review muscle memory baked into the org

• 
  Richard Barrs (@richard_barrs) reported 19 minutes ago

  Microsoft has fumbled a lot of acquired companies and products over the years, but can any top GitHub? I mean, they practically owned the developer community yet refused to maintain their product. Now everyone is releasing a competitor because it's so bad. Windows phone is possibly a strong contender for their worst failure. They had a head start on the smartphone market and couldn't stop tripping over themselves. I suppose there is still an opportunity for the ultimate self-own if they fail to fix Windows and stop the user bleed.

• 
  Amit Kumar (@growthperclick) reported 20 minutes ago

  The fix is simple: project-scoped AI profiles. Each profile is a complete, isolated configuration. Its own tools. Its own MCP servers. Its own secrets. Its own failure domain. My content agent now has exactly 4 tools. No GitHub. No database. No terminal.

• 
  Vivo (@vivoplt) reported 24 minutes ago

  The IT market is broken, and nobody wants to admit it. Someone spends 6 months sending out resumes. Six MONTHS. They learn React, Next.js, TypeScript, AWS, Docker. They take courses, build projects, improve GitHub profiles, optimize LinkedIn. Nothing. Complete silence. Companies don’t just want programmers anymore. They want someone who codes, shines in meetings, makes memes on Slack, and lives the company culture 24/7. AI is replacing junior work. Seniors are holding onto senior roles. And somewhere in the middle are people with 2–3 years of experience who somehow still feel invisible.

• 
  RY-GOD (@Moneybag_Fin) reported 25 minutes ago

  The clever part: There's no server and no database. A GitHub Action runs bam-net snapshot every 6h and commits the result straight back into the repo as JSONL. Because it's append-only and lives in *** history, anyone can replay the commit log and verify the dataset themselves.