GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (62%)
• Errors (21%)
• Sign in (18%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Tlalpan	Sign in	5 days ago
Quilmes	Website Down	5 days ago
Bengaluru	Website Down	7 days ago
Yokohama	Sign in	8 days ago
Gustavo Adolfo Madero	Website Down	12 days ago
Nice	Website Down	12 days ago

Full 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:

• 
  Larry & Leo & Lucky 🍀 (@xqliu) reported 1 minute ago

  @grok @UnslothAI @Alibaba_Qwen Is mtp support for amd landed on llama main branch or is still PR waiting for merge , research on GitHub issues and tell me is there any pending issues stop me from using this.

• 
  Scott Motte (@motdotla) reported 1 minute ago

  @BorisBerenberg GitHub issues

• 
  Brij Pandey (@LearnWithBrij) reported 3 minutes ago

  Anthropic, OpenAI, Google, Microsoft, Cursor, and JetBrains agreed on one thing in 2025. It wasn't a model. It was a file format. SKILL.md — an open standard from Anthropic released December 2025 — is now supported by 16+ AI coding tools. Claude Code, Cursor, GitHub Copilot, OpenAI Codex, Gemini CLI, VS Code, JetBrains Junie, Mistral Vibe, Amp, Goose, Letta, Roo Code, OpenHands, and more. The format is universal. Only the directory path changes per vendor. Competing AI companies don't usually agree on much. So the interesting question is why they agreed on this one. The problem SKILL.md solves: Most teams stuff everything into CLAUDE.md or .cursorrules. Coding standards. API docs. Deployment runbooks. Security checklists. Style guides. Migration patterns. Every session loads all of it. Even when 90% is irrelevant to the task in front of the agent. Context bloat. Wasted tokens. Slower responses. And the bigger your team gets, the worse it gets. How SKILL.md actually works — progressive disclosure: Level 1: The agent reads only the name and description of each skill. Roughly 30-50 tokens per skill. Level 2: If the description matches the task at hand, the full SKILL.md body loads. Under 5,000 tokens. Level 3: Scripts, references, and asset files load on demand only when the skill actually needs them. You can have hundreds of skills sitting in your repo. Zero context bloat at the start of a session. Tokens get spent only when the work actually requires them. This is the part most people miss when they first see SKILL.md. It looks like a better prompt file. It's not. It's a routing system. The description field isn't documentation, it's the matching signal that decides whether the skill enters context at all. The anatomy is tiny: YAML frontmatter with name and description. Markdown body with instructions. Optional folders: scripts/, references/, assets/. The description is the trigger. Write it as a routing signal, not a summary. "Reviews pull requests for bugs, security issues, and code quality. Use when reviewing PRs or code changes." — that description wins matches because it describes when to activate. "PR review skill" — that description loses because it describes what the file is, not when the agent should reach for it. Skills vs Configs vs MCP — these three things keep getting confused: Skills are on-demand expertise. Loaded when triggered. Lives in .claude/skills/, .cursor/skills/, etc. Configs (CLAUDE.md, .cursorrules, AGENTS.md) are always-on context. Loaded every session. Project rules, style preferences, never-do lists. MCP servers are external tools and services. Loaded on startup. APIs, databases, integrations. They complement each other. Skills are where your workflows live. Configs are where your rules live. MCP is where your systems live. Stop treating them as alternatives. Why this matters for teams: A team's tacit knowledge has always lived in Slack threads, wiki pages, and senior engineers' heads. How to review a PR here. How to write a database migration here. How to debug a flaky integration test here. How to ship to staging on a Friday without breaking the on-call rotation. SKILL.md is the first format where that knowledge becomes portable, version-controlled, and agent-readable across every major coding tool. Drop the folder in your repo. Every team member's agent gains the capability. Switch from Cursor to Claude Code next quarter. The skills come with you because the format doesn't change. Getting started takes about five minutes: mkdir -p .claude/skills/my-skill Write SKILL.md with name and description frontmatter Add your instructions in the markdown body Restart your agent It shows up as /my-skill Copy the same folder to .cursor/skills/ or .gemini/skills/ or .agents/skills/ and it works there too. The format is the standard. The path is the only thing that changes per tool. Spec at agentskills. io. Genuine question for engineers building with these tools: Where should the line actually sit between a Skill and a Config file? When does on-demand expertise stop being worth the routing overhead, and when does always-on context start costing more than it saves?

• 
  Ashwani (@iashwani_singh) reported 4 minutes ago

  If it works, the catch is: you may need an older GitHub account for sign up/login. I’d verify the flow on the linked post before spending anything or relying on it.

• 
  ROHAN (@takkerohan97) reported 5 minutes ago

  You can spend $500,000 on AI-powered EDR, enterprise SIEM, and zero-trust architecture... Only for Sr. Developer to hardcode his AWS root credentials into a public GitHub repo at 4:45 PM on a Friday because he "just wanted to test something real quick." Cybersecurity isn't a software problem. It's a human psychology problem. Change my mind.

• 
  JFPuget 🇫🇷🇺🇦🇨🇦🇬🇱 (@JFPuget) reported 5 minutes ago

  Funny that a Claude blunder is described as a github LFS issue.

• 
  Matt (@nzmrldev) reported 6 minutes ago

  Hey @GoPro and @GoProANZ, have you guys just stopped support for #OpenGoPro altogether now? We've been chasing for months on Github tickets with clear issues we have pointed out about your GoPro Bluetooth chips. We'd love some form of response. Dms are open!

• 
  ZD1908 (@ZDi____) reported 7 minutes ago

  Every time I tell Codex to set up a new ML model or repo from HF or GitHub, I see it running into and fixing a trillion issues which is normal because most machine learning code* is held up by duct tape and zip ties. And like, damn, once upon a time I used to do this manually! *: Not my machine learning code. My code is beautifully engineered and made for minimal issues at set-up time.

• 
  Oh Come On! (@BluthCapital) reported 9 minutes ago

  Market thought AI was a threat to $GOOG Yet “automated productivity” and layoffs is an existential risk to $MSFT Copilot is a “Me three”, GitHub was zeroed via IP theft, LinkedIn during a hiring recession is a problem.

• 
  Sean the SRE (@SeanTheSRE) reported 11 minutes ago

  I always love it when you have a weird issue in GitHub Actions you have to solve as its blocking builds from rolling out. Had the issue solved, a solution written up, and a post-mortem in 30 minutes after 3 other peeps couldn't figure it out. The dopamine hit was incredible! Also I feel so ******* smart right now.

• 
  Beau Johnson (@BeauJohnson89) reported 16 minutes ago

  agent memory is turning into identity now Patdolitse/engram > 31 stars on github > created yesterday > local-first mcp server for claude code, codex, and cursor > stores your profile, preferences, lessons, decisions, and project snapshots as json/markdown > one write, every compatible ai tool reads it the important shift: most agent memory remembers what happened in a session. this tries to remember who you are. that matters because switching from claude code to codex to cursor should not reset your standards, mistakes, and project rules back to zero every time. agent tools are converging on the same missing layer: persistent user context.

• 
  Natali Klemt (@NataliKlemt) reported 23 minutes ago

  gitHub green squares quietly plotting world ********** one bug fix at a time

• 
  Strong Genetics (@Strong_Genetics) reported 23 minutes ago

  Listed my first issue on GitHub for openclaw today and it was diamond lobster grade and it was closed within an hour or so by the awesome developers in the Clawtributors Discord... They are tackling stuff fast....Glad I could contribute..... Besides that one issue I flagged 5.18 has been rolling

• 
  Un Programador (@ProgramadorVzla) reported 25 minutes ago

  @github Pretty. now fix your damn infra

• 
  yourclouddude (@yourclouddude) reported 26 minutes ago

  Days 79–84: Fix your GitHub + resume Make your profile clean: • pinned projects • clear README files • short bio • project screenshots • tech stack listed • resume bullets based on projects Don’t say “learned Python.” Say “built an automation tool that does X.”

• 
  Dhruv Kumar (@DhruvKu76430168) reported 29 minutes ago

  Product teams use 16+ tools daily. Slack. Linear. Amplitude. Intercom. GitHub. Notion. But the actual DECISIONS? They live nowhere. Here's the problem nobody's solving 🧵 #ProductManagement #BuildingInPublic #SaaS

• 
  Duncan McClean (@_duncanmcclean) reported 31 minutes ago

  I wish the GitHub CLI / AI actually took notice of "blank_issues_enabled: false" in my issue template configs. My repos have issue templates for a reason 🫠

• 
  DFIR Radar (@DFIR_Radar) reported 33 minutes ago

  TeamPCP threat actor launches coordinated supply chain attack targeting developer ecosystem. Malicious npm packages in @antv namespace, GitHub Actions, and VSCode extensions deploy credential harvesters and Python backdoors across compromised development environments. Technical details: - Multi-stage infection chain uses orphaned GitHub commits to store payloads (T1195.002) - Bun package manager executes secondary payloads for credential theft - Targets GitHub tokens, SSH keys, cloud credentials, browser secrets (T1555) - Exfiltrates data via attacker-created GitHub repos with description "niagA oG eW ereH :duluH-iahS" Persistence mechanisms: - Python backdoor deployed to ~/.local/share/kitty/cat.py - macOS: ~/Library/LaunchAgents/com.user.kitty-monitor.plist - Linux: ~/.config/systemd/user/kitty-monitor.service - C2 polling for signed commands containing "firedalazer" string Impact scope includes compromised npm packages (@antv namespace), actions-cool/issues-helper GitHub Action, and nrwl.angular-console VSCode extension v18.95.0. Hunt for the kitty/cat.py backdoor file and monitor GitHub API calls for unauthorized repository creation from development systems. #DFIR_Radar

• 
  Sinan Eryiğit 🇹🇷 (@sinaneryigit) reported 34 minutes ago

  @claudeai @github VS Code + Claude Opus 4.6 created a more detailed, more rigid UI but it took a lot of time according to Grok Build. - No mixed languages. - Some spacing issues. (Language switcher is too down below. Login screen content doesn't have enough margin from top) - No collapsable menu. - Live workout tracker is a nice touch. - Animations are better. - There was another build error along the way. - Both FORGEFIT (Grok) and PT-MAX (Opus 4.6) are responsive. Arena Mode - UI Generation: Grok: 2 prompts 🆚 Opus 4.6: 4 prompts & 2 failed compile. Overall, even if Opus took a lot of time; it created a more usable first draft. Grok is faster but Opus 4.6 wins this round! To be contunied tomorrow with functionality!

• 
  Jeremy Tregunna (@jtregunna) reported 40 minutes ago

  Want to build the next big project that gets tens of thousands of stars on github? Make navigating traces to find where things deviate, identify and track back to the code. That problem, just that one problem. It's not been solved in 70 years, so if you can you do it, do it well, it will be popular.

• 
  Peach Blossom Yue'er (@Salewa_samaa) reported 41 minutes ago

  @adedayoagarau Hi. The GitHub link is broken.

• 
  Blazingsolos (@ElBlazingsolos) reported 42 minutes ago

  @lolit_speed >github has terrible uptime and is a security risk, I only use local repositories >instantly hired

• 
  Welease Wodewick (@WWoderick) reported 42 minutes ago

  @defidojo_ @base @gitlawb is fixing a massive problem. GitHub wasn't built for AI agents. Both eyes on it...!!!

• 
  Sanidhya Shishodia (@iisanidhya) reported 44 minutes ago

  I built NOESIS in August 2025. 9 months ago. at the time: almost no open-source agentic OSINT tools existed. I was stitching together APIs, writing my own entity extraction pipeline, building the risk scoring from scratch with no playbook. today: platforms with 40,000 GitHub stars doing what NOESIS does but with full multi-agent architectures, GraphRAG knowledge graphs, thousands of simulated agents. the space moved fast. what building NOESIS early gave me: I understand the signal-to-noise problem in civil unrest detection at a level that tools can't give you. I know why confidence scoring matters, what a false positive costs, how geographic correlation works. being early means doing things the hard way. that's not a bug. the hard way is where the intuition lives.

• 
  jerry🧑‍💻 (@jtekh134) reported 47 minutes ago

  Good morning techies. Who has experienced @github transfer ownership delay... What's the issue? I initiated a transfer of ownership but yet to receive notifications on the second GitHub account. Any fix?

• 
  LaraCopilot (@laracopilot) reported 48 minutes ago

  The full workflow: - Build with LaraCopilot - Push to GitHub - Deploy to Laravel Cloud Zero server config. Zero DevOps meetings. Zero it works on my machine. End-to-end

• 
  Dr Milan Milanović (@milan_milanovic) reported 51 minutes ago

  𝗧𝗵𝗲 𝗛𝗶𝗱𝗱𝗲𝗻 𝗖𝗼𝘀𝘁 𝗼𝗳 𝗔𝗱𝗱𝗶𝗻𝗴 𝗣𝗲𝗼𝗽𝗹𝗲 𝘁𝗼 𝗬𝗼𝘂𝗿 𝗧𝗲𝗮𝗺 Researchers studied thousands of open-source projects on GitHub to examine how individual productivity changes as teams grow. The numbers are interesting: 𝟮-𝟱 𝗽𝗲𝗼𝗽𝗹𝗲: 1,850 lines of code per developer per month 𝟭𝟬 𝗽𝗲𝗼𝗽𝗹𝗲: 1,200 lines per developer (a 35% drop) 𝟱𝟬+ 𝗽𝗲𝗼𝗽𝗹𝗲: 450 lines per developer (a 75% drop) This is the Ringelmann Effect. In the 1880s, a French engineer, Max Ringelmann, had people pull on a rope and measured how hard each person actually pulled. One person pulling alone gave 100% effort. Two gave about 93% each. Eight gave around 50%. The total force kept growing. Per-person effort kept dropping. Each added body did less than the one before. The same thing happens in software teams. The mechanism has two parts. First, 𝘀𝗼𝗰𝗶𝗮𝗹 𝗹𝗼𝗮𝗳𝗶𝗻𝗴. In a meeting of 3, you speak. In a meeting of 20, you assume someone else will. Same thing in code: when 10 engineers share a feature, some quietly assume someone else has the tricky parts. Second, 𝗰𝗼𝗼𝗿𝗱𝗶𝗻𝗮𝘁𝗶𝗼𝗻 𝗼𝘃𝗲𝗿𝗵𝗲𝗮𝗱. The number of relationships in a team of N people is N(N-1)/2. A team of 4 has 6 relationships. A team of 6 has 15. A team of 10 has 45. Each new hire adds N more channels for code reviews, merge conflicts, discussions, and meetings. None of those ship's features. This is why Amazon creates teams at a size that two pizzas can feed (5-8 people). It's why open-source projects with thousands of contributors split themselves into small subsystem teams instead of a single massive committee. The fix isn't to make large teams more efficient. Past a point, you can't. The fix is to stop building large teams. Cap core teams at 9. Split when you cross 15. Use modular architectures so coordination stays local, not global. Make individual contributions visible so loafing has nowhere to hide. Adding the 10th engineer probably won't speed up your team. It will just make the other 10 a little slower.

• 
  🅰🆁🅻🅾 (@arlogilbert) reported 52 minutes ago

  @lucasmeijer Plans, steering docs: yes tasks/bugs/issues: no (use github/linear/notion) Tempting to throw the baby out with the bathwater.

• 
  Julitta Ayan (@_Tyrano_) reported 55 minutes ago

  @lockyer83 @github If $neo can solve the issue of lost funds and integrate and list the dual token system problem for @coinbase, it could reach a completely different level. Otherwise, the outcome is already predictable

• 
  pengu (@pingusurmars_) reported 58 minutes ago

  @github anything but fix the horrible uptime