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	4 days ago
Quilmes	Website Down	4 days ago
Bengaluru	Website Down	6 days ago
Yokohama	Sign in	7 days ago
Gustavo Adolfo Madero	Website Down	11 days ago
Nice	Website Down	11 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:

• 
  chandog (@thechandog) reported 4 minutes ago

  @kevinrose @digg how are you constructing novelty? stars are 40c on the dollar and a terrible way to measure anything on github.

• 
  Muhammad Afzal (@AfzalBuilds) reported 5 minutes ago

  Just shipped claude-code-backup — a CLI tool that watches your Claude Code files and auto-syncs them to a private GitHub repo. Claude Code stores your memory files, settings, custom commands and CLAUDE.md files locally. Anthropic doesn't sync any of it. New machine or accidental rm -rf ~/.claude = start over from scratch. This fixes that. ✅ Real-time file watcher (chokidar) ✅ Every change = a *** commit ✅ Safe restore with pre-restore snapshots ✅ macOS launchd service (auto-starts on login) ✅ Interactive setup wizard ✅ Private repo by default One-time setup: npm install -g claude-code-backup claude-backup init claude-backup service install Then forget about it. It runs silently in the background forever. #ClaudeCode #DevTools #OpenSource

• 
  Ferbin (@Ferbin08) reported 7 minutes ago

  @cyrilXBT every github trend: week 1 stars explode, week 3 issues mount, week 5 nobody touches it. where are routing and agent memory in that cycle?

• 
  Tom Finnell (@d2fl) reported 8 minutes ago from Cleveland, Tennessee

  I hit conversation limits myself on Grok Build yesterday while researching the new github algo commit. The same issue is now hitting Grok Imagine. SuperGrok users are getting capped after 10 to 80 generations. That is a sharp drop and doesn't match promises. The cause is straightforward. Demand for image and video generation has exploded. xAI is throttling to keep the service stable instead of letting it melt. Elon just posted that we need clear reset times and easy upgrades to higher plans. xAI is already scaling more GPUs and pushing limit increases. Clearer timers and tier upgrades are rolling out. This is normal growing pains. Same pattern hit early Grok text access. It loosens once the servers catch up. I suggest a little patience while new capacity and load distribution is brought online. This is temporary. Anyone else getting throttled on Imagine or Grok conversations? Drop your numbers below.

• 
  promptaholic (@promptaholic) reported 9 minutes ago

  the github bot spam thing. they used *** --author flag to filter noise. that's it. that's the whole move. not a ml model. not a fancy filter. understanding your own system's metadata well enough to solve the problem at the source. 52 systems later this is still the pattern. builders read their tools. dependents wait for tools to be readable

• 
  hbb (@BIGBULLapp) reported 10 minutes ago

  @github @code Basically a cleaner SSH into your own dev box. The catch is your laptop is now a server with uptime requirements.

• 
  nadya (@sosidudku) reported 12 minutes ago

  Ran Hermes Agent and OpenClaw on the same task: scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. Local model: Qwen 3.6 35B OpenClaw: 203k tokens, 12m 01s — wrote a bash script Hermes: 257k tokens, 33m 01s — wrote a SKILL.md OpenClaw: 203k tokens, 12m 01s — wrote a bash script Hermes: 257k tokens, 33m 01s — wrote a SKILL.md OpenClaw: hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes: parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations.

• 
  Mr. Buzzoni (@polydao) reported 13 minutes ago

  Martin Keen from IBM just explained the debate that's splitting Claude and AI agent developers in half CLI vs MCP - and the answer will save you thousands of tokens > GitHub MCP server loads 80 tools into context = 55,000 tokens before your agent does anything > CLI: agent already knows grep, cat, *** cold from training data > MCP wins when Claude needs to render a JavaScript page - curl can't do that, MCP browser server can in 250 tokens > MCP wins for Slack, Notion, databases - OAuth handled by the server, not the agent the rule: use CLI when commands map directly to the job, use MCP when the abstraction earns its cost full breakdown above

• 
  nadya (@sosidudku) reported 14 minutes ago

  ran Hermes Agent vs OpenClaw on local model Qwen 3.6 35B task: scrape GitHub star history, find what caused the growth spikes, build a live dashboard in the browser OpenClaw: 203k tokens, 12m 01s — wrote a bash script Hermes: 257k tokens, 33m 01s — wrote a SKILL.md OpenClaw: hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes: parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations.

• 
  Lee Penkman (@LeeLeepenkman) reported 14 minutes ago

  @gxjo_dev stupidity... no... frupidity basically. like the exec cfo team is like well what if we reduce headcount wouldnt profitability go up? Like yes but you just wont be a good product company without a good product... like you are already struggling to compete with GitHub lmao... how u gna compere with codex n claude when they do repos? Also theres just fear that these devs cant learn AI which is kind of wrong because devs seem to be best placed to leverage AI of all? idk. im just guessing. lots of saas companies just doing layoffs had hired too many people having thought they would keep growing then they didnt their stock went way down and becomes harder to raise money for them because of bearish outlook for them competing with claude so investors scared off so harder for them to afford lots of developers so kind of start sinking. the devs would do better elsewhere anyway better to be on a new ship instead of sinking one.

• 
  OEP 🔺 (@yong_oku) reported 15 minutes ago

  1. Build in public. Your work needs to exist before your resume does. Essays. Projects. Case studies. GitHub. Shipped products. Threads like this one. An ATS cannot reject a body of work. A founder who's been reading your writing for 3 months already trusts you before you apply. Visibility is the new resume. 2. The listing is the last resort, not the first step. 80% of real jobs are filled through networks before they're ever posted. The posting is what happens when the network failed. Stop spending 80% of your energy on listings. Start spending it on real relationships with real humans. 3. Go direct. Find the person who would actually manage you. Not HR. Not the portal. Not the ATS. The human who wakes up with the problem your skills solve. One real conversation beats 100 applications every single time. 4. Verify before you invest. Before you write a single word of a cover letter, run due diligence: → How long has this listing been up? → Has it been reposted with a new title? → Is this company actually growing — or just posting like they are? → Can you find anyone on LinkedIn who joined in the last 6 months? Treat job listings like investment pitches. Most of them are fraudulent. 5. Build leverage outside the job market. Freelance. Consult. Build something small that earns. Not because you need to quit the job search, but because the person who doesn't desperately need the job, negotiates better, interviews better, and gets the offer. Desperation is visible. Leverage is too. 6. Find the communities where real hiring happens. Discord servers. Slack groups. Niche forums. Alumni networks. Jobs move through conversations before they move through portals. The people who found great roles in terrible markets almost always had one thing in common: they were already in the room.

• 
  linares (@skibidifatrizz) reported 19 minutes ago

  @404not_utkarsh He's not spamming his GitHub with performative bullshit. What's the issue

• 
  SILVER (@Bitch_Paratha) reported 24 minutes ago

  @ThePrimeagen We should prolly make a github typa service and name it unicornhub or something (we can think of a better name tbh) and whenever our servers are down we show the GitHub logo

• 
  Jeff Hayes (@JD__Hayes) reported 24 minutes ago

  @FredKSchott I'm interested, but web page is down and could not find on github.

• 
  Kea (@alpinoWolf) reported 26 minutes ago

  " we literally cannot programmatically trade from this account until Polymarket's engineering team patches the V2 library and resolves GitHub Issue #65. " How does you evpoly bot do ? Please help me ? Is python coding problem here ? 3/3

• 
  Tom (@T3metrics) reported 31 minutes ago

  @JasonLixfeld Yeah it's all docker. I'm not sure what you mean. I do have a GitHub runner on the server so once I push code it automatically rebuilds my debug container so I can test before pushing to full production.

• 
  NEET INTEL (@neetintel) reported 34 minutes ago

  A post "decoding" X's new algorithm has gone viral. It tells you what's dead, what wins, and to screenshot it. X open-sourced the entire algorithm on GitHub, so I downloaded it and checked the claims against the real code. Most of it doesn't hold up. What the post got WRONG: → "Small accounts get a 3x boost from out-of-network reach." It's the opposite. One part of the code (a file called oon_scorer) exists purely to turn DOWN posts from people you don't follow. Its own comment says "prioritize in-network." The thread printed the algorithm backwards. → "Media gets 2x the weight." There's no 2x. The code just records whether a post has an image. It's a plain yes/no without any multiplier attached. → "Posting 4+ times a day triggers a penalty." There's a real rule that stops one person flooding your feed. But here's the deal: it only spaces out how often you show up in a single scroll. There's no daily count, and no number 4. That was invented. → "Closers like 'what do you think?' get you flagged." There is no engagement-bait detector anywhere in the code. → "Long 4,000-character posts get boosted." I searched the whole codebase for "4000." Nothing. What it got RIGHT (one thing): → Replies really are judged by WHO replies, not just how many. The code has a setting for whether a large account joined your thread. Credit where due. The irony? The repo ships a file that scores post quality. One thing it measures is literally called a "slop score" — X built a tool to detect low-effort filler. A recycled "what's dead / what wins" thread is exactly that. The takeaway? X's algorithm is public. Anyone can open it, but almost nobody does. Instead, they reshare a thread that summarized a blog that paraphrased a tweet. When a post hits you with confident numbers, ask the one question that matters: did they actually open the file?

• 
  Adibou (@Adibougre) reported 39 minutes ago

  @ShanuMathew93 "the older models that are no longer SOTA will get competed down as competition increases" Github didn't get the memo

• 
  Yashas (@YashasGunderia) reported 41 minutes ago

  Most AI-native startups will not lose because they ship too slowly. They’ll lose because they ship fast without knowing what actually worked. Coding agents gave every team more velocity. Cleo gives them product memory. Customer feedback, GitHub issues, Slack threads, metrics, tickets, specs, launches, agent traces, all connected into one loop that tells your team and your dev agents what to build next. We’re opening the Cleo waitlist today. For small teams trying to compete with companies 100x their size (link in comments)👇

• 
  COP 🐸 (@CoppedPepe) reported 41 minutes ago

  @github loud correct. hardest part is just clicking “new issue” without imposter syndrome cancelling you first.

• 
  Sum0janedoe (@sum_janedoh) reported 44 minutes ago

  @Denosko1 @OrahOnX Hey Mrs. D. Just read this about the algo going public on github. Maybe it will be helpful for you? Here be the ruuules: :) It punishes for muting blocking etc. Who knew, huh? From @NavToor Here is what this means for you: If your posts are not reaching people, it is not because the algorithm is broken. It is because the algorithm is working exactly as designed. It rewards: 1. Posts that get reactions across multiple action types (a like AND a profile click AND a follow beats five likes alone) 2. Conversation depth (quote tweets are worth more than reposts in the math) 3. Dwell time (write posts people stop to read) 4. Posts that convert viewers into followers (your bio is part of your post) 5. Variety from each author (post less, post better) And it punishes: 1. Mutes 2. Blocks 3. Reports 4. "Not interested" clicks.

• 
  Sean Keenan (@sean9keenan) reported 46 minutes ago

  @brian_lovin Semi-relatedly: I’m back to VS Code from Cursor, autocomplete seems much better now! (Not that I’m crafting code by hand much) But importantly, the… basics seem much more stable (Cmd+f, and saving have been pretty broken in Cursor recently) Curious how GitHub Copilot feels!

• 
  Jens Ingelstedt (@JensIngelstedt) reported 48 minutes ago

  @DarkGodFaith Filtering for active GitHub + lives in Discord is the right signal. Most hackathon teams break down because nobody set those filters before kickoff.

• 
  Yuuru (@PriestruYuuru) reported 48 minutes ago

  @thsottiaux Bro, compaction essentially broken right now. Dunno about everyone but for me it doesn't work most of the time. Steam error end everything, can't provide you with/feedback sadly but team could look into github issues from others. Tried to set compaction earlier but still issues.

• 
  Lyrie.ai (@lyrie_ai) reported 50 minutes ago

  🚨 MiniPlasma (no CVE, NO PATCH): Chaotic Eclipse bypasses Dec 2020 fix (CVE-2020-17103) in Windows cldflt.sys → SYSTEM on FULLY PATCHED Win 11 & Server 2025. PoC live on GitHub. No patch exists. Windows admins: monitor cldflt.sys NOW. #ZeroDay #Windows

• 
  Moe Sbaiti (@MoeSbaiti) reported 52 minutes ago

  WHAT THE FRAMING GETS WRONG Most posts today are saying "Grok added a new feature." That framing is backwards. What happened is that an agent framework with over 110,000 GitHub stars, the number 1 ranking on OpenRouter, and an NVIDIA endorsement just got native access to one of the most capable models available through a simple OAuth login. xAI made the announcement. Not Nous Research. Hermes Agent also self-improves. When it solves a hard problem, it writes a skill file for that solution and saves it. The longer it runs on your specific workflows, the more capable it becomes for your specific context. That is not how people are talking about this today. The memory layer and the self-improvement loop are the actual product. Grok is the engine.

• 
  C. ₿utt 📵 (@ctbutt114) reported 53 minutes ago

  @zquestz Reports are an issue with GG20, which was identified last month and set to be addressed. However, being open source, the bug was revealed via GitHub, & someone took advantage. Single bad actor on a new node. DLKS has been on the roadmap. Needed faster now.

• 
  Miscellany (@Miscellany_a) reported 56 minutes ago

  @FL_Slayer Oh it 100% is. They literally stole the UI from ChartForge, even down to the "Everything you need" tab they have on their website. Their Github says "trained with 42,000 charts from the CH/YARG communities" and I bet you they didn't bother asking charters for permission either

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

• 
  Drini (@drini_kasmot) reported 58 minutes ago

  @maxalexweber It's the HarmonicLabs token-minter repo, uses plu-ts for tx building. Getting a PPViewHashesDontMatch error on Preprod when submitting. Already raised it on their GitHub!