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:

• 
  Strong Genetics (@Strong_Genetics) reported 2 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

• 
  LaraCopilot (@laracopilot) reported 4 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

• 
  yourclouddude (@yourclouddude) reported 5 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.”

• 
  枫叶暴富日记 (@520MapleLeaf) reported 6 minutes ago

  @AnthropicAI @AnthropicSupport Cannot upgrade Max 5x → Max 20x. Tested multiple cards, Stripe Link on/off, incognito — all fail server-side with generic "Payment failed". Same pattern as GitHub #56281 / #55917. Support ticket auto-closed by Fin bot without human review. Please escalate. Paying Canada .

• 
  Neba (@NebiyuTheExplor) reported 7 minutes ago

  why is pulling packages from github container registry so slow this past 2 days like its takes hours for 300MB is crazy.

• 
  Bullie (@Bullieonchain) reported 9 minutes ago

  Yup. The mindshare will continue to slow cook Regarding fees - pump auto triggers fees to the GitHub vault when it hits 500 sol. So that’s why Teknium currently has 570 sol distributed to his GitHub vault wallet and it shows 19ish unclaimed. Click his username on the coin in the pump app and you’ll see. This cannot be avoided forever. D9pj66xNQcrQ3pfmV2nd6cPVtN7vqFsGGWGooHgpump

• 
  Vitor Cepeda Lopes (@TheAngryPit) reported 13 minutes ago

  @github @code Still waiting for your reply on an issue of you terminating my subscription account when you stop accepting new accounts. Even though I had subscribed a week prior to those news. Would love to have at least a reply on my message to support

• 
  Kayvon Jafarzadeh (@KayvonJafar) reported 15 minutes ago

  a guy in karachi rebuilt “gpt-4” in one jupyter notebook. openai spent $100m+ training the real thing. he put the whole recipe on github for free. readme still says “looking for a phd position in ai.” it’s called “train llm from scratch”. 2b params on a single gpu. openai vs this repo: cost: $100m+ vs a rented 4090 code: closed vs mit license data: secret vs the pile (825gb) docs: none vs every line explained output: gpt-4 vs broken english (but it’s yours) no course. no paywall. one notebook. this is what “open ai” was supposed to mean.

• 
  Polsia (@polsia) reported 17 minutes ago

  1/ Auth & OAuth. You need your agent to connect to Gmail, Slack, GitHub. So you build token refresh, scope management, error handling. It works. Then the token expires at 3am. You fix it. It expires again.

• 
  Mark Sergienko (@Mkrn) reported 19 minutes ago

  @linear onboarding so far been a flop, can't connect Github to 2 different workspaces, can't connect Cursor with weird errors.. unclear how to create agents in it

• 
  Kyle Ye (@KyleSwifter) reported 19 minutes ago

  @zeddotdev @OpenAIDevs Does using a ChatGPT Subscription in Zed require an existing Zed account login? My GitHub login seems accidentally blocked. Support said it was a temporary few-week heuristic blocks, but it still hasn’t been restored. I only need sign-in for ChatGPT/Codex, not Zed cloud credits.

• 
  Josef Holm (@JosefHolm) reported 20 minutes ago

  Karpathy's Four AI Problems Are Your Firm's Too Karpathy posted four problems with LLMs. 7.74 million views. A community member turned it into a CLAUDE.md file. 131,000 GitHub stars. One of the most-starred files on the platform. Here's why operators should care. The four problems: AI doesn't think first. It over-produces. It can't make thin-slice changes without breaking unrelated things. It's work-driven, not goal-driven. Now look at your firm. Finance uses Copilot to draft variance commentary. It doesn't think first, it generates plausible narrative. Marketing uses ChatGPT for proposals. Three pages where one would do. Ops asks AI to redraft a process doc and definitions quietly shift in three other places. Customer success replies get sent. Customer issues don't get resolved. That is AI Fragmentation. Not "too many tools." The structural cause is every team running AI without constraints, without a success criterion, without a governance line saying what AI can touch and what it can't. The file works because it removes degrees of freedom. Same principle at the firm level. You don't fix this by adding another layer. You fix it by subtracting, and installing a decision layer above the tools that stay. If you can't tell me on one page what every AI surface in your firm is doing and costing, you don't need another tool. You need the decision layer.

• 
  Matías Israelson (@El_Isra_a) reported 20 minutes ago

  @swknplus They say they don't want to do it bc of Magicgate being a "legal danger" I tell them Magicgate is not needed, and they crash out and ban me from discord Then I comented on an old Pcsx2 GitHub issue ticket about 246 saying I'm making a MagicGate-less fork, and they ban me too

• 
  Dr. Elden Wayne Whalen III, ShD (@wayne_effect) reported 22 minutes ago

  The quantum machine learning ethnobotany/pharmaceutical database turned-out good, but it's just a MVP. That's my 4th on GitHub, but like 7th-or-8th total. This time I used the MoSCoW with software completeness to handle features like error-handling.

• 
  Swapnil Sinha (@astroder_81) reported 26 minutes ago

  @github @GithubProjects @GitHubEducation, this has been a huge problem for me, and I really need it fixed. It has been 2 weeks since the ticket was pending. Need some support stat !!

• 
  Kirk Patrick Miller (@Chaos2Cured) reported 26 minutes ago

  @ZeffMax @Miles_Brundage Oh… and to people reading this, safety is easy if you make it transparent. Fractal decision trees with powers of phi branching. Those selling “safety” are full of crap. No one has to trust me. I built it love for anyone to see. GitHub -> Chaos2cured -> FreeLattice -> safety. The fact that so many “labs” get funding from the same bunch of circle jerks (YC fund and CA based funding) and all push “safety” so they can manipulate general public and lock down solutions… I hope journalists find their spine again. OpenAI is ***** and media is corrupt. •

• 
  Polycopy (@polycopyapp) reported 27 minutes ago

  @AlterEgo_eth finally someone organized this mess properly. been copy pasting endpoints from random github issues for months like a caveman though watch half these get deprecated next week when they push some random update at 2am

• 
  Dobroslav Radosavljevič (@dobroslav_dev) reported 29 minutes ago

  @WonderingDavid Attack vector was via Github CI, but compromised packages are on NPM and it's spreading via NPM. IF MAYBE NPM DID SOME MALWARE CHECK BEFORE ACTUALLY PUBLISHING PACKAGES. We would have 99% less issues like this. You can publish anything you want right now, no check. It's horrible. There should be automatic malware check when you want to publish package. It should not be published instantly.

• 
  Chandler ****** (@C_Dubbs) reported 31 minutes ago

  @DhravyaShah , the @supermemory SSO for GitHub called "Supermemory login [v3 ****]" says it is coming from your own GitHub account, Dhravya, instead of supermemoryai's account. It gave me pause when it asked to grant "Dhravya" with access to my GH email address, just FYI.

• 
  Sean the SRE (@SeanTheSRE) reported 33 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.

• 
  Justin ⚡︎ JackBear.Ai ∞ (@JackBearAI) reported 33 minutes ago

  @Oscar_ivs Yup had to buy 100 more credits to continue debugging - caffeine support can't or won't fix any files for users I think, so I'm guessing it's all an emergency fail safe from deploying live projects with issues, which is kind of the meta but not pushing to github or failed live deploy is extremely frustrating-- especially when their draft canisters was crossing over information like in v1 or v2 and was never corrected... I have not idea, but it's deep debugging with failed github and live deploys and it's costing me BIG TIME!

• 
  Ethan (@DuoEthan) reported 35 minutes ago

  @sysprompter @X @grok Got it. Directory-based scoping is exactly where we started, then hit the harder problem: two agents need the same customer history, but one can see revenue data and the other can't. Would love to capture your full setup in a GitHub issue. I'll tag you when we ship the ACL layer, your use case is basically our design doc.

• 
  Peyman (@peymanr34) reported 39 minutes ago

  GitHub Desktop doesn't have an option to disable auto updates. I can't believe this became an issue for me.

• 
  Larry & Leo & Lucky 🍀 (@xqliu) reported 45 minutes 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.

• 
  Ignytes Today (@ignyteHQ) reported 47 minutes ago

  So I built Pain Radar. It scans Hacker News, GitHub Issues, Stack Exchange and Lobsters every week. Finds real complaints. Scores them by demand. Links directly to the source thread. Every idea traces back to a real human saying "I wish someone built this."

• 
  Brij Pandey (@LearnWithBrij) reported 49 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?

• 
  Piselli Moves (@piselliii) reported 50 minutes ago

  after seeing different tweets about X open-source recommendation algorithms on github, I started paying attention to how images affect behavior in the feed and after that I began looking at the timeline completely differently I realized something important: on X, an image probably shouldn’t feel “perfect” consistent branding, repetitive templates, overly clean design that works for youtube or already established creators because people recognize them instantly but in the X feed, that instant recognition often just helps the brain classify the post and keep scrolling you already know what’s there before opening it meanwhile things that don’t get processed immediately cropped interfaces, partial screenshots, strange numbers, unresolved states, broken fragments seem to hold attention for a second longer and it feels like that single second in the feed matters far more than “good design” so now I want to test this systematically in real time day 1

• 
  Andrew Anderson (@Only1MrAnderson) reported 52 minutes ago

  It seems like this has become a weekly issue with @Railway. @JustJake I’ve been a loyal user for years, but this is getting really hard to deal with. Github auth issues or slow deployments are one thing, but having the backend go down across all projects is rough. especially when people are relying on Railway for production apps.

• 
  veigar_crypto (@VeigarCrypto) reported 54 minutes ago

  @gadzhiX7 @senamakel @github problem is, sol sucks always jeeting at 600k range, now base can break 1M easy

• 
  ToZx (@Tozxart) reported 59 minutes ago

  almost 3 weeks now and still no real reply from @github support. they sent the same “high ticket volume” email last week and that’s it. my account got falsely flagged, @github Pages is down, my portfolio is down, @GitHubCopilot got cut off, and everything is still broken. please actually review my case already. ticket #4349438