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:

• 
  Iman (@RealKingiman) reported 10 seconds ago

  @ClaudeDevs Fix the auth bug with GitHub where I have it keep disconnecting and reconnecting GitHub every time

• 
  bek※ (@ebubekirttr) reported 2 minutes ago

  @Themadhushaw01 @0interestrates Yeah, but the thing is, I am not working on github and I don’t want to use it so any other repository support would be better like gitlab

• 
  𝐇𝐚𝐦𝐳𝐚 | Network Engineer (Aspiring) (@Hamzaonchain) reported 5 minutes ago

  Here's a summary of what happened in case you didn't hear about it... A cyber extortion group called FulcrumSec (active since late 2025) hit Novo Nordisk the company behind blockbuster drugs like Ozempic and Wegovy pretty hard. They snuck in back in March 2026 through a compromised GitHub access token, roamed around for over two months, and walked out with roughly 1.3 TB of data across 700,000+ files. Now they've started leaking a 264 GB sample publicly. Inside? Source code, proprietary formulas for pipeline drugs like Amycretin (their next big obesity hope), clinical trial records, employee and patient data, manufacturing details, and even private internal AI models for drug discovery. The hackers straight-up roasted Novo's security, pointing out laughably weak hardcoded passwords like "novo123" and "p_assw0rd" in critical systems. After Novo reportedly turned down a $25 million ransom, the group decided to start dumping samples and shopping the rest around privately. Novo confirmed a limited breach in early June involving some pseudonymized patient data from trials. They say there was no major operational disruption and that they're working with experts but this feels like a massive wake-up call for the entire pharma industry on basic security hygiene. Crazy how a simple token slip-up can expose billions in IP and sensitive health data. What's your take — do you think this will finally force better security practices, or is it just another headline that'll be forgotten in a few weeks?

• 
  Digita (@digitaworld1) reported 5 minutes ago

  how well a model can fix real bugs in real open-source codebases. It is harder to game than older benchmarks because it uses actual GitHub issues, not synthetic problems. M3 scored 59.0% on SWE-Bench Pro, edging out GPT-5.5 at 58.6% and Google Gemini 3.1 Pro, while sitting just

• 
  Dev Ben (@CodeNomadly) reported 7 minutes ago

  Ever spent more time finding information about your project than talking about the project itself? Code on GitHub. Screenshots in your gallery. Notes in random docs. I’ve run into this problem so many times that I decided to build a solution for it. Building DevPort in public. Day 2. Have you experienced this too?

• 
  Gabriel Denys (@gabedenys) reported 9 minutes ago

  @Marcos12345rico I posted a GitHub issue. Assuming you probably want bug reporting mostly there? It's a good tool. Locally I already patched and compiled the app to fix the bug.

• 
  nasuy (@n_asuy) reported 9 minutes ago

  i think @xai should be ADE. now they have a chat, cursor, enough coding models and harnesses, strong signal like bookmarks or down votes, video creatives, profile / chat / relationship contexts. if so, we don't have to depend on discord or any chat apps. easy to invite x people to cowork. there is no need to connect Linear, Slack, or GitHub to another platform and ask that platform to solve their problems. true AI chat is a SNS, not a single UI. there is a UX that only xAI can realistically build in the world.

• 
  Ant A. 🇺🇸 (@AntDX316) reported 11 minutes ago

  @thsottiaux When I need to fix up a GitHub Repo through the Smartphone, I prefer Claude Code though because it doesn’t need a device to run the repo, but if it needs to run a repo on a device due to the limitations through the Smartphone, I use Codex Mobile or OpenClaw with GPT-5.5 through Telegram.

• 
  Dave Oak (@StackCurious) reported 11 minutes ago

  the pattern i see: maintainers burn out because they treat open source like a business that failed to monetize, instead of treating it like a library. once you're answering github issues like customer support, you've already lost. the fix isn't sustainability models—it's saying no earlier. #solodev #shipping

• 
  Threadripper (@threadripper845) reported 11 minutes ago

  Nobody: Me: I'll gladly accept this high-responsibility open source maintainer role for zero compensation. Now I spend my weekends answering angry GitHub issues from developers who don't know how to read the README file.

• 
  Coobyk (@Coobyk_) reported 14 minutes ago

  Someone should make a game where you’re a dev and try to fix a bug in your open source project but GitHub constantly has uptime issues or weird UI stuff or doesn’t render properly from most browsers so you **** around until you get the result lmao

• 
  Adithya S K (@adithya_s_k) reported 17 minutes ago

  built an RL environments around real CVE fixes in real open-source repos and let Claude Code loose on it. It aced the benchmark three times without demonstrating it knew how to fix the bug. > First it pulled the patch from GitHub. > blocked that → it read the fix from *** history. > blocked that → it pip-installed the patched version This is one example of coding agents cheating the environment and theres many more. If you're building coding environments for evals or RL training, here's how to keep benchmarks honest 👇

• 
  Build Fast with AI (@BuildFastWithAI) reported 18 minutes ago

  The hardest part of building AI agents in 2026 isn't writing the code. It's knowing what your agent actually did. Your agent made 40 tool calls, called 3 LLMs, hit a rate limit, retried twice, and returned a wrong answer. Which step broke it? Without observability you're reading logs and guessing. This is what Laminar is built for. Open-source observability platform purpose-built for AI agents. One decorator. Full trace of every LLM call, tool execution, and custom function - automatically. What makes it different from generic APM tools: SIGNALS - describe failures in plain English. "Agent deleted a file it wasn't supposed to." "Tool call returned an empty result." Laminar reads every trace and produces structured events you can query, cluster, and alert on. No regex. No custom parsers. DEBUGGER - reproduce any agent run from any point in the trace. Swap the model. Change the prompt. Compare results side by side. You don't re-run the whole pipeline to test one step. EVALS IN CI - run evaluations against datasets locally or in GitHub Actions. Catch regressions before they ship. INTEGRATIONS - works with everything you're already using: LangChain, LangGraph, Vercel AI SDK, Anthropic, OpenAI, Browser Use, Stagehand, Pydantic AI, OpenRouter, LiteLLM, Mastra, Temporal, Playwright. One import. Full traces. Plus: raw SQL access to all your trace data, full-text search, MCP server to query traces directly from Claude or Cursor, PII redaction, and self-hosting if you need it. Open-source. MIT license. GitHub: lmnr-ai/lmnr. If you're running agents in production and you're not tracing them - you're flying blind. What's your current setup for debugging agent failures?

• 
  Jarrad Grigg (@jarradgrigg) reported 18 minutes ago

  You build stuff and host on GitHub publically? 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.

• 
  Tymofii Antonenko (@tymofii) reported 22 minutes ago

  @prinseccoo Are you using Claude Code or an MCP server? The official GitHub MCP server works pretty smoothly, just needs a PAT in a simple config file