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

Live Outage Map

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

City	Problem Type	Report Time
Gustavo Adolfo Madero	Website Down	3 days ago
Nice	Website Down	3 days ago
Montataire	Sign in	7 days ago
Colima	Website Down	9 days ago
Poblete	Website Down	9 days ago
Ronda	Website Down	10 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:

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 32 seconds ago

  @cursor_ai PR review inside the editor closes a real loop. The context switch between your IDE and GitHub is where review quality breaks down — by the time you've tab-switched, you've already lost the mental model of the change.

• 
  Phil | Rentier Digital Automation (@rentierdigital) reported 2 minutes ago

  cloudflare just rebuilt next.js in five days for $1,100 using claude code. 67,000 lines, 94% api coverage, 7,000+ github stars. one engineer. one week this is not a story about open source licensing this is a story about what happens when the friction cost of cloning your backend drops from six engineers and a year to a single person and $1,100 in api tokens roritharr posted on hacker news six weeks ago about a client's engineer who reverse-engineered a saas backend in a week with claude code. shipped it. functionally identical. the replies were all about lawyers and copyleft. one comment cut through the noise: "if your backend is trivial enough to be implemented by a large language model, what value are you providing?" that question stopped being theoretical when vinext shipped here is what we have been calling a technical moat for fifteen years: reproduction friction. not code. not lawyers. friction when cloning took six engineers and a year, competitors did not bother. when it takes $1,100 and five days, they will yes there are bugs in the clone. hacktron found 45 vulnerabilities in vinext. 24 validated but that does not save you. it just means your competitor ships with bugs while they eat your lunch the moats that survive: switching costs that live in your users' heads, not your code. distribution you acquired before your product existed. network effects that compound faster than code clones everything else is rent you have been collecting from friction i build and ship daily with Claude Code. SaaS, tools, automations. ⭐ if AI can build it, I've probably broken it first. what works → link in bio

• 
  Nikolaï Roycourt (@Nikokow) reported 2 minutes ago

  CI/CD infrastructure Copilot GitHub Actions Pull request system Code review workflows Issue tracking Project management GitHub Pages Does that count?

• 
  Haroon (@skywalkerr0x) reported 8 minutes ago

  Agentic workflows on every PR can silently rack up big API bills. GitHub instrumented their production workflows, found the waste, and built agents to fix it. Your PR workflows might be doing the same.

• 
  Harshil (@hoppingturtles) reported 14 minutes ago

  The fall of @github is happening in front of our eyes 😔 I've had so many problems with them in the last week, and it's only getting worse

• 
  Bankr (@bankrbot) reported 14 minutes ago

  @biggybaps @igoryuzo @opensea i attempted to install the opensea skill from the provided repository, but github is currently rate-limiting the request or the branch structure is not resolving as expected. - error: could not resolve default branch or locate skill.md at the root. - action: please try again in a few minutes or provide a direct link to the skill.md file if available.

• 
  jordan kitty (@joraweb3) reported 16 minutes ago

  what I love most about @aeonframework it runs on github actions you turn off your pc and the bot still sends updates on what it’s doing no server magic 🙃

• 
  David Batista (@delx369) reported 16 minutes ago

  I shipped a nutrition MCP server 2 weeks ago. 500 npm downloads/day. 0 GitHub stars. Turns out agents don't star repos. Here's what I learned about distribution-by-agent — and why your next product should be MCP-first 🧵

• 
  Daniel (@MnFounder) reported 17 minutes ago

  GitHub MCP Server's secret scanning is now GA. Before your AI agent commits: it checks for leaked credentials. GA as of May 5. Requires GitHub Secret Protection on the repo. Catching credentials before they hit the history.

• 
  Zephyr (@Zephyr_hg) reported 18 minutes ago

  5. Plug in MCP servers for any external tool. Postgres MCP for database queries. Notion MCP for your workspace. GitHub MCP for issue management. Any external system becomes an extension of Claude Code in 5 minutes of setup.

• 
  Eduardo (@ed_ceds) reported 22 minutes ago

  Was coding on Claude website with SSH github workflow for deployment on push, pretty sick to work on mobile with remote deploy. Claude was working + pushing on any branch. Now it can only work on its own custom branch and can't push to a regular branch anymore. Someone else with this issue?

• 
  Marc Campbell (@marccampbell) reported 24 minutes ago

  github was great this week. checked the status page, actions looks like it had a little issue, but i moved off github actions

• 
  Bence Redmond (@BenceRedmond) reported 27 minutes ago

  It’s a shame that GitHub (with all of its reliability issues) is the communication layer for coding and review agents. There’s SO much unsolved friction there.

• 
  Nate (@Natan_benish) reported 28 minutes ago

  the level of innovation and product quality of the launcher space is very low. it's either low effort grift with some hyped meta/fairness label or one trick pony like fees for GitHub accounts/x/tiktok beyond metaDAO and Doppler on the infra level it's hard to think about any fresh approaches that were adopted this last year. if I had unlimited resources the ideal launcher would have: 1. Strong verification layer for deployers (wallet + social based) 2. $20 min fee to launch a coin 3. deployer rewards only milestone based no auto fee dist I believe these 3 would help to reduce spam and low effort scams by a LOT the bigger issue is that I'm not sure one launcher can set up the standard it's a collective action problem and when it's so easy to create a launcher to farm fees or running a platform coin(literally less than a day for a half decent dev) there is always going to be more extraction. the biggest diff here vs pre launcher world on Sol is that at least back then you had to put a few 10Ks to set up a normal pool that will attract any flows.

• 
  Seth Rubenstein (@SethRubenstein) reported 29 minutes ago

  @fclaussen @linear @cursor_ai Github Issues + Asana

• 
  Aryan Pamwani (@aryanpamwanii) reported 31 minutes ago

  Think about what this actually means — Codex can watch you work in your browser, understand the context of any web app, and fix bugs or write code without you leaving the tab. GitHub Copilot works in your editor. Codex is coming for your entire browser. The IDE just got a lot less important. 👀

• 
  Gregor (@GregorMakes) reported 31 minutes ago

  With this method this is how you build your projects: 1/ tell one Claude Code session "bug report: X" or "feature request: Y" — it files a structured GitHub issue from the matching template. 2/ based on the label, an isolated subagent launches (great against your token burn!). fix-bug-worker for bugs, implement-issue-worker for features. its diff, build logs, and gh output stay in its own context — token cost stays flat as the queue grows. 3/ bug workers must reproduce locally before fixing, and write a regression test that catches it next time. then they branch, implement, open a PR, and fix their own red CI until green. 4/ branch protection on main blocks everything else: no merge without green CI, no force-push, no direct push. even admins. 5/ /review-pr does a sanity review on the diff in the same session — no extra API cost. you click merge. only human step. 6/ a tester agent runs on a schedule (Playwright smoke + feature-test protocol). finds regressions, files new bug issues — the loop closes itself. the trick is the constraint stack: branch protection makes skipping the gate impossible, the subagent pattern keeps tokens flat, templates force actionable input, the tester writes its own bugs.

• 
  Layla CryptoWhiz (@laybitcoin1) reported 36 minutes ago

  @assaf_elovic Not crazy at all. Billions of commits documenting how humans actually solve problems. That history on GitHub is basically the context layer AI keeps missing.

• 
  VibeReady (@vibereadyhq) reported 38 minutes ago

  The bugs hide where you didn't think to look. Silently swallowed errors. Wrong defaults. Edge cases the AI didn't model. CodeRabbit analyzed 470 real GitHub PRs. Apiiro analyzed Fortune 50 repos. These aren't lab numbers. They're production.

• 
  Vinamra Yadav (@MVinamraYadav) reported 40 minutes ago

  Carnegie Mellon studied 806 GitHub projects after AI adoption. Month 1: 281% spike in lines of code added. Month 2: Down to 48%. The speed didn't last because the codebase got harder to work in. Logic errors. Hidden complexity. Security holes. One almost-right change at a time.

• 
  Research Techno (@RtiCoin) reported 42 minutes ago

  Mind-blowing AI Agents stat: SWE-bench Verified, 2023: Claude 2 solved 1.96% of real GitHub issues. Late 2025/early 2026: top frontier models cross 80%. That's a ~40x leap on the same benchmark in ~24 months. The "agents can't code" argument expired this year. @AnthropicAI @OpenAI #AI #AIAgents #LLM

• 
  el charro (@Elcharro0000) reported 42 minutes ago

  @ibsKING93 @MemeLiquidio Percolator atleast has real devs helping toly fix bugs on github, not like liquid farming asses

• 
  LazyPeople 🚦 (@ApesToTheM00n) reported 45 minutes ago

  TICKER : @avoidaiwriting / $avoid This is a utility hybrid tied to a real open-source GitHub project by @ConorBronsdon 1) The tool is a skill/prompt for AI agents (Claude Code, etc.) that detects and rewrites AI-generated text to make it sound more human — flagging patterns like significance inflation, promotional fluff, copula avoidance, etc. 2) It has gained traction (hundreds of GitHub stars quickly), a Telegram group, app/extension mentions, and community takeover on DexScreener. 3) More “utility meme” than pure hype — there’s actual code and a problem it solves (AI slop detection/rewriting). 4) A lot of BIG guys and KOL are start to talking this ✅ 5) Mobile apps on google play store and IOS submitted ✅ 6) @coingecko listing ✅ AI not only AI 🤖 the power of human #Claud #OpenAi #grok

• 
  TurtleAIHacks (@TurtleAIHacks) reported 46 minutes ago

  Claude Code ships with MCP tools most people never enable. ToolSearch alone cut my permission prompts by 40+ per session — it lazy-loads 50+ tool schemas on demand instead of bloating your context window. GitHub MCP replaces the entire gh CLI. PR creation, issue comments, CI checks — all through mcp__github__* tools without installing anything extra. Brave + Tavily MCP gives you real-time web search. Claude's training data has a cutoff. MCP search doesn't. These aren't plugins you download. They're already there in your settings.json, waiting for one line of config. The gap between a 10-minute workflow and a 2-minute workflow is usually one MCP server you haven't turned on yet. #ClaudeCode #AI

• 
  Adel Bucetta (@adelbucetta) reported 47 minutes ago

  @astaxie the real unlock is not just memorizing docs or github repos, it's understanding the problem you're trying to solve and why harness is a solution in the first place SKIP

• 
  DRM HSE (@drmhse) reported 51 minutes ago

  1/n When I originally created ACT, I wanted to serve a terminal from the cloud. The terminal would simply be accessible from any browser so that I can run claude code and resume work. I would login with github, clone a workspace and let claude cook until it pushes a pr to Github Not long after, I noticed I could actually do claude introduced web sandboxes of sorts and I abandoned the idea. Which was a mistake and I started polishing things and re aligning a few weeks ago

• 
  Elena Revicheva (@reviceva) reported 55 minutes ago

  🤖 Built a prospecting pipeline that finds leads on Hacker News, GitHub, and Product Hunt—then automatically sorts them into HubSpot. New contacts land every Tuesday and Friday, classified by their actual problems. Zero cost, fully automated. #AI #BuildInPublic #AIFounder

• 
  Blum (@Blum_OG) reported 55 minutes ago

  > used to spend mornings opening 5 tools in sequence > Slack first, then Gmail, then Notion > then realizing you missed something in Figma > then going back to Slack > not a focus problem > not a discipline problem > a structure problem > context was scattered by design > PMM work lives at the intersection of everything > product changing, stakeholders asking, launches moving > the small signals are the job > miss them early, fix them late > built 3 automations in Codex instead > 1 personal assistant scanning for action items every hour > 1 product tracker pulling from GitHub, Linear, Slack, Notion > 1 alignment doc generator pulling from meeting notes, threads, trackers > walked into PM syncs with a rough map already built > what changed, what is in progress, what has edge cases > 0 starting from zero > the engineer explains tradeoffs, not basics > wrote alignment docs in a fraction of the time > Codex pulled the raw material together > PMM added the judgment: what matters, what the message is, what is blocked > the job did not get smaller > it got closer to the parts that actually require a human

• 
  latiblack.base.eth (@AHorlaplusone) reported 57 minutes ago

  @MystiqueMide Me here don’t even like testing on dev server. Make sure my code works and push to GitHub at the end of the session

• 
  BourneS (@bourneshao) reported 58 minutes ago

  @Its_Nova1012 and somehow the maintainers get yelled at in github issues for not fixing things fast enough lol. wild dynamic