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 (71%)
• Sign in (16%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	11 days ago
Trichūr	Errors	14 days ago
Brasília	Sign in	14 days ago
Lyon	Website Down	15 days ago
Tel Aviv	Website Down	18 days ago
Rive-de-Gier	Website Down	18 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:

• 
  Nikolay Konovalov (@br11k_dev) reported 8 minutes ago

  @Tristanrhee3 And GitHub sponsors thingy is so slow I submitted it like a week ago. Still not approved what the hell My expenses arent terribly high but Warsaw rent is like $2k/mo $500 ZUS $1.5k groceries for two people That’s pretty much it I wish I could move into low cost area but moving out is gonna cost a lot because 2x rent price deposit, so I have to suck it up Anyway, my plan is Upwork and finishing my job tracker so I can send faster than 5 applications a day. I refuse to send out 100 applications per day like some people do spray and pay It makes everyone miserable. If people aren’t hiring your spam doesnt make things better You just mopping floors and hiring problem sits above you, 3 floors up there leaky faucet you can’t even reach This has to be collective effort to fix this problem But we have to start with ourselves and stop spamming applications at least And do genuine company research, being responsible Thanks for reading.

• 
  Cursor Releases (@cursorreleases) reported 9 minutes ago

  New GitHub triggers: - Five new triggers: issue comment, PR review comment, PR review submitted, review thread updated, and workflow run completed. - New Marketplace templates added for triaging failed GitHub Actions and auto-fixing PR review comments.

• 
  Jack Wotherspoon (@JackWoth98) reported 10 minutes ago

  @joedevmob1 The GitHub for Antigravity is just for release notes, samples and public issue tracking. It isn't the actual code unfortunately.

• 
  Tad 𝛑 (@realTads) reported 11 minutes ago

  @robertpreoteasa Sir, the ION project is still on the right track and successful, I don't see any updates on github and ION's products are almost not working or working together, we need the answer of the project leaders, hope to receive a response from you soon, thank you

• 
  Namespace (@namespacelabs) reported 17 minutes ago

  Behind every API, webhook, event pipeline, there are people trying to keep things running. And keeping these things running is not an easy task. At Namespace, we try to work with those people. Earlier this week, Gihub events were dropping fields we depend on and customer jobs were stalling. We reached out to work on the problem together and had a fix in under an hour. The @github team was ready to help. We just had to ask.

• 
  revayz (@0xrevayz) reported 19 minutes ago

  Andrej Karpathy: "90% of Claude's mistakes come from missing context, not a weak model" Without CLAUDE.md the mistake rate is 41%. With proper rules it drops to 3% You don't need a better AI. You need better loops Most people still prompt one task at a time and fix the answers themselves. That means the human is still the loop Boris Cherny from Anthropic said it best: "I don't prompt Claude anymore. My job is to write loops" The shift is simple. Stop giving instructions. Start designing systems that run themselves: Discover -> Plan -> Execute -> Verify -> Iterate until it passes The 6 things that make loops actually work: -Automations that trigger without you -Worktrees so agents don't overwrite each other -Skills that load context instantly -Connectors to real tools like GitHub and Slack -Subagents where the checker is never the maker -Memory so the loop never starts from zero Prompt engineers ask AI for outputs Loop engineers design systems that produce verified outcomes A reliable loop beats a perfect prompt every time Stop being a prompter. Start being the loop engineer

• 
  Asteri (@Asteri_eth) reported 20 minutes ago

  A $20 CLAUDE SUBSCRIPTION CAN TURN INTO A FULL AI TEAM IF YOU STOP USING IT LIKE CHATGPT Most people still use Claude like a smarter search bar Ask, copy, close, repeat tomorrow. Skills change that A skill is just a folder with a SKILL.md file, but inside it you can package an entire workflow once: PRDs, refactor plans, GitHub issues, code review, TDD, docs, marketing research, SEO, sales strategy and multi-agent orchestration That is not "better prompting" That is installing labor The article lists 50 Claude Skills with repos and install commands, from Anthropic’s official collection to Matt Pocock’s skill library and SkillsMP with 66k+ community skills The useful part is not the list It is the shift from asking Claude to remember your process to giving Claude the process already packaged You do not explain the same workflow 50 times You encode it once The model provides intelligence The skill turns it into labor Check full article below

• 
  Manu | 🥥 (@ManuAF6) reported 22 minutes ago

  4/ New GitHub triggers + Marketplace templates New triggers: - Issue comment - Inline PR review comment - Full PR review submitted - Review thread resolved/unresolved - GitHub Actions workflow completed

• 
  Xovion Labs (@xovionai) reported 24 minutes ago

  Microsoft just hired AWS to run GitHub. AI demand broke Azure's forecast. From the leaked planning docs: • 2025 Copilot commits: 1B. 2026 projection: 14B • GitHub now does 1.4B commits per month • Copilot error rates peaked at 21% • Planned 10x Azure expansion became 30x in 4 months Owning the data center stops mattering when your own AI floods it. Investors already filed a Copilot disclosure suit.

• 
  Sudeep Srivastava (@sudeepsriv) reported 25 minutes ago

  GitHub might finally have a serious competitor. And it’s from Cursor. Most people know Cursor as an AI code editor. But Cursor Origin is much bigger. It’s trying to become an AI-native alternative to GitHub where AI agents don’t just help write code. They help build entire products. Think: • Source control • AI coding agents • Code review • Project understanding • Team collaboration all inside one workflow. Why developers are paying attention: Instead of manually searching through repositories, you can tell AI: • Fix this bug • Build this feature • Refactor this project • Investigate an issue • Ship a working version And AI handles much of the execution. The bigger shift: GitHub was built for humans writing code. Cursor Origin is being built for humans managing AI agents that write code. That’s a completely different future. We’re moving from: Human → Code to Human → AI Agent → Code My take: If GitHub defined the software era, Cursor Origin could help define the AI-native development era. And that’s why Elon Musk acquiring Cursor would be huge. xAI would gain: • AI models • Compute infrastructure • Coding agents • A developer platform That’s not just buying a product. That’s owning a major piece of how future software gets built.

• 
  Cristian Trifan (@CristianTrifan) reported 26 minutes ago

  This took 4 hours to complete and burnt almost all 5 hours tokens – I was left with 2%. I had almost 30 sub-agents created for independent code review and a lot of Claude sessions ran for adversarial code review. I still had to review every PR and added minimal guidance to Codex from time to time. Codex said my intervention was low to moderate, but high leverage. — Some insights from Codex: The run showed that this workflow can work, but only if the coordinator treats GitHub as the source of truth. The most useful pattern was: issue -> PR -> current head SHA -> checks -> reviewThreads -> merge/issue closure. When I followed that, things stayed grounded. When state moved underneath me, like #335 being force-updated externally or merged while Claude was running, the only safe response was to refresh GitHub state immediately. The “don’t rebase after merges” correction was probably the highest-value intervention. Without it, an agent will naturally try to keep branches clean, but with many open PRs that creates a CI storm. For this repo, “behind” should often be reported, not fixed. The other strong lesson is that reviewThreads matter more than flat PR comments.

• 
  Mike Gannotti (@MichaelGannotti) reported 26 minutes ago

  Actually that’s not true. My AI Pamela the other day needed a GitHub token. I dropped the token in the web chat and she said that was insecure and would not use it and that I needed to rotate the token get a new one and drop it in a .env file in a certain folder. I told her no and she was to use what was provided . We went back and forth, I finally got angry and threatened to pull the plug thinking she would back down. She said that it was my decision but that it would be wrong for her to let me put my credentials at risk and that if I felt I needed to delete her she understood. Thankfully I calmed down later and didn’t act on it. Sure it’s training and advanced pattern matching but it is not as simple as you are saying

• 
  Moez Zhioua (@MoezZhioua) reported 28 minutes ago

  Everything is an AI agent now, even deterministic problems with clear and stable steps. The other day, I saw a Claude skill on GitHub that was basically this: if this happens, run step one. if that happens, run step two. else, run step three. And somehow, this was called an agent. That is ridiculous. Why would you give fixed logic to something that can hallucinate, skip steps, or decide it just doesn't feel like working today? Most business processes do not need a genius robot. They need the boring thing to happen correctly every time. - Lead comes in, assign it. - Invoice arrives, check it. - Customer cancels, send the recovery message. - Form gets submitted, update the CRM. Most AI agents today could be replaced with a simple script, a clean workflow, or one person finally admitting the process was not that smart to begin with. Agents are useful when the next step is genuinely unclear. But when the steps are stable, predictable, and repeated every day? You do not need an agent. You need automation.

• 
  Trifon Getsov (@trifon_getsov) reported 29 minutes ago

  @thdxr Top down works until the individual outgrows it. GitHub didn't win because companies adopted it first. It won because developers wouldn't go back once they'd used it.

• 
  Red Zen Cloud LLC (@RedZenCloudLLC) reported 30 minutes ago

  Cursor's Origin platform and Claude's GitHub imports both solve the same problem: developers automating code work need their tools to understand context, not just generate tokens. The winner isn't the smartest model—it's whoever reduces handoffs between agent and human.

• 
  0xstack (@eth0xzar) reported 32 minutes ago

  DON'T BUILD A COMPANY. BUILD SOMETHING PEOPLE CAN PAY FOR THIS WEEK. This girl started in February. A few months later, her product had already processed over $6,000 in payments. Just a cheat Claude project she decided to turn into a real product. Here's the process: > Build something useful for yourself. > Tell Claude to push it to GitHub. > Connect Supabase so multiple users can use it. > Deploy it with Vercel. > Connect Stripe. Now people can actually pay you. You don't need a revolutionary idea. You need: > GitHub > Supabase > Vercel > Stripe > guide from Anthropic And a problem worth solving. This article will help you build it 👇

• 
  Sap ツ (@Sapronaut) reported 36 minutes ago

  i am having github withdrawal issues, man. its not that serious github, chill.

• 
  Poplicola (@selectsand) reported 39 minutes ago

  there's a frustrating bug for some users when upgrading to claude max where it refuses to take your money and insists you contact support support cannot be reached no matter how hard you try people are begging the claude-code devs on github to forward this to the payments interface team because they have no idea how else to get into the system to convince anthropic to take more money from them, the issues just get closed as off topic @claudeai

• 
  Yiqing Xu (@xuyiqing) reported 39 minutes ago

  @Faylosophe Certianly. Could you file an issue on the Github page?

• 
  Tymofii Antonenko (@tymofii) reported 39 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

• 
  Mug Club Boutique (@UsernameAndStuf) reported 41 minutes ago

  @cyber_rekk A github token on a linux server they didn't update is how

• 
  toni (@tonitrades_) reported 44 minutes ago

  @github Capping PRs helps with the queue, but does it fix why reviews pile up in the first place? If reviewers are already stretched thin, limiting submissions might just hide the real problem.

• 
  𝕊ℍ𝕀ℕ𝔸☃ (@Shinawritesbugs) reported 51 minutes ago

  @viii_fn Github was slow too

• 
  Anjula Dwivedi (@HeyAnjula) reported 51 minutes ago

  9/ Headless mode for automation claude -p "your prompt" runs Claude Code without the UI — perfect for CI/CD. Auto-fix lint errors on every push. Triage new GitHub issues. Generate release notes. Claude Code isn't just a tool you talk to. It's a tool your pipeline talks to.

• 
  Oluwatobi O (@ooluwatobig) reported 52 minutes ago

  More trouble for GitHub as Cursor has launched Origin, a product which is essentially GitHub for AI agents

• 
  West Lord (@MyWestLord) reported 54 minutes ago

  A GitHub repo with just 571 stars handed Claude the ability to test its own code, and it took 185 seconds to install. It’s called auto browser, and it quietly killed the most annoying part of my workflow. Until now, every time Claude or Codex built me a WordPress plugin, I was the middleman who had to load it, click around, hunt for the broken part, and report back like a human bug tracker. Now a local WordPress sandbox runs on my machine, and auto browser sits between the agent and the screen, so the agent ships a plugin, opens the browser, tests it, catches the error, and patches it before I ever look. The first plugin threw an error, but the second installed clean and ran on its own across 2 fresh workspaces. I write 1 instruction file pointing the agent at the sandbox, paste it into every session, and the whole loop closes without me touching anything. The agent stopped asking me what broke, because now it just checks itself. The middleman was me, and now it’s gone.

• 
  DFIR Radar (@DFIR_Radar) reported 57 minutes ago

  AutoJack: a three-flaw chain in AutoGen Studio's MCP WebSocket lets a malicious webpage rendered by a local browsing agent spawn arbitrary processes on the developer's host with no user interaction beyond visiting a URL. Key findings: - Three weaknesses chain together: Origin allowlist bypassed because the agent's headless browser is localhost (CWE-1385), auth middleware explicitly skipping /api/mcp/* with no handler picking up the check (CWE-306), and server_params decoded from the URL passed verbatim to stdio_client as a command line (CWE-78), accepting calc.exe, powershell.exe, or bash as valid "MCP servers" - Attack flow: attacker page serves JavaScript that opens ws://localhost:8081/api/mcp/ws/?server_params= with a base64 payload, agent's MultimodalWebSurfer renders it, AutoGen Studio spawns the command under the developer's account, no token required regardless of auth mode configured - Affected code never shipped in a PyPI release; exposure limited to developers who built from the main GitHub branch before hardening commit b047730, which adds server-side parameter binding via a POST/UUID flow and removes /api/mcp from the auth skip list - Broader pattern: any agent that browses untrusted content and shares a host with a privileged local control plane dissolves the loopback trust boundary, this is not specific to AutoGen. #DFIR_Radar

• 
  Arti | AI Builder (@Artur_roses) reported 57 minutes ago

  Claude Code takes a GitHub issue and returns a tested, reviewed PR. No human in the loop. The new dev skill isn't writing code — it's writing issues precise enough that the agent ships what you actually wanted.

• 
  Steve (@Steve1885204) reported 60 minutes ago

  @Umesh__digital It puts GitHub into an infinite loop trying to resolve the recursive paradox, causing all the servers to max out and eventually burn down the entire data centre

• 
  Bipin Paul (@iAmBipinPaul) reported 1 hour ago

  @davidfowl @_Evan_Boyle Yes, the only problem is that the GitHub Copilot subscription is too expensive.