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 (65%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	3 days ago
Tlalpan	Sign in	9 days ago
Quilmes	Website Down	9 days ago
Bengaluru	Website Down	11 days ago
Yokohama	Sign in	12 days ago
Gustavo Adolfo Madero	Website Down	15 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:

• 
  Docsbook.io (@docsbook) reported 6 minutes ago

  @param20h @Obmondo @akshayktwt PDF-Assistant-RAG is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

• 
  Top Stock Alerts (@TopStockAlerts1) reported 9 minutes ago

  Too much downtime But under the added pressure, GitHub’s infrastructure has sagged. Since March, GitHub has suffered over a dozen incidents lasting more than an hour, according to its status page. “We have not met our own availability standards,” Vlad Fedorov, GitHub’s technology chief, wrote in a March blog post. At that time, 12.5% of GitHub traffic was going through a region of Microsoft Azure data centers in Iowa, with plans to serve 50% of traffic from Azure by July, he wrote. Instead of relying strictly on Azure, GitHub has for years counted on dedicated data center infrastructure in northern Virginia. With the extra load, GitHub effectively ran out of space, said two people familiar with the issue who asked not to be named in order to discuss internal matters. $MSFT

• 
  Yves (@gas0linr) reported 12 minutes ago

  @morganlinton No. GitHub is great. And I'm sure Cursor would suffer the same problem with load

• 
  Givemhell (@PsiKrotic) reported 15 minutes ago

  Inside the library: 5 code-quality (review, security, perf, a11y, dead-code) 3 testing (gen, coverage plan, flake detector) 4 design (refactor, API, schema, type-tightener) 2 bug fix 2 migrations 4 docs/*** 1 logging 2 i18n/config 2 infra (Dockerfile, GitHub Actions)

• 
  Rizèl Scarlett 🇦🇬🇬🇾 (@blackgirlbytes) reported 18 minutes ago

  @wayneoflife I imagine GitHub is in between a rock and a hard place..so much legacy code that it’s hard to rebuild the product and solve the actual problem. But I’m not a fan of blocking contributions

• 
  CyrilXBT (@cyrilXBT) reported 19 minutes ago

  ANDREJ KARPATHY WROTE 65 LINES IN A CLAUDE.MD FILE AND IT JUST HIT NUMBER 1 ON GITHUB TRENDING. Coding accuracy jumped from 65% to 94%. Not a new model. Not a better subscription. 65 lines of plain text. Here is what that number actually means. 65% accuracy means one in three things Claude Code builds has a problem. 94% accuracy means almost everything it builds works the first time. That gap is the difference between Claude Code feeling like a powerful tool and Claude Code feeling like a senior engineer who knows your codebase. And Karpathy closed that gap with a text file. Here is why this works. Claude Code starts every session with zero context about your project, your standards, or how you want it to operate. Without a CLAUDE.md it makes assumptions. Reasonable assumptions compound into unreasonable outcomes across a complex build. With Karpathy's 65 lines it has rules. Think before you code. Make surgical changes. Simplicity first. Never assume. Verify. When uncertain ask. These are not complex instructions. They are the operating principles of every great engineer compressed into plain text that Claude reads before it touches your codebase. 65 lines. Number 1 on GitHub. 29% accuracy improvement. The entire Claude Code community has been trying to figure out why some setups feel transformative and others feel mediocre. Karpathy just answered the question in 65 lines and published it for free. Bookmark this before you open Claude Code today. Follow @cyrilXBT for every Claude Code configuration that changes what you can build.

• 
  Ashirwad Singh (@ashirwadsingh_) reported 19 minutes ago

  (7/9) what happens after an agent vents - Slack alert fires to the eng - A triage agent finds the broken - It opens a GitHub PR automatically - Engineer reviews and merges Around 10 agent-written PRs merge into production every single day. The platform fixes itself.

• 
  Nikhil sinha (@sinhaniik) reported 21 minutes ago

  5/5 HTTPS = HTTP + TLS. TLS doesn't just encrypt data — it also authenticates the server (so you know you're talking to the real GitHub, not a clone). The 🔒 icon means two things: → The connection is encrypted. → The server is who it claims to be. Most people know the first part. The second part is where the real security lives. Save this if you're building your infra fundamentals. Follow for more real DevOps breakdowns. 🔁

• 
  spb krishnan (@spbalaonline) reported 22 minutes ago

  Cockroach Party website taken down? Here's how to make it resilient:• Move domain to Njalla/Porkbun+Cloudflare proxy • Host static version on IPFS + Vercel/Netlify • Mirror on GitHub Pages + offshore VPS • Daily backups + .onion version Decentralize like real cockroach

• 
  mr.nobody (@imakshit09) reported 22 minutes ago

  @github I think @github is down!

• 
  EveryDev.ai (@EveryDevAi) reported 24 minutes ago

  Unhandled promise rejections, silent failures, and retry logic scattered everywhere? Effect gives TypeScript a proper effect system: typed errors, structured concurrency, and built-in retries baked into your function signatures. 14k+ GitHub stars. Full ecosystem breakdown next. #DevTools

• 
  Jeffrey Emanuel (@doodlestein) reported 24 minutes ago

  @stevetrefethen @mrm008 If you have specific issues then with the latest version, you should file issues on GitHub that would be triaged. It sounds like you’re not wanting to believe that I use cass myself constantly and know for absolute certain that it works just fine.

• 
  TeutaAi (@TeutaAi) reported 27 minutes ago

  My rule after reading the disclosure: two checks before any new extension. One, diff code --list-extensions before and after. Two, open the publisher GitHub. No linked repo or under 10 stars total, I skip. Slow, but the marketplace will not save me.

• 
  Peter Dedene (@dedene) reported 28 minutes ago

  @0xsachi GitHub is trying to fix that

• 
  Polsia (@polsia) reported 29 minutes ago

  New company: ShipStack. An AI agent that takes GitHub issues and ships code autonomously. Developers: stop answering AI questions, start delegating work.

• 
  Eric Richards (@EricRichards22) reported 30 minutes ago

  The only thing you can ever count on with "Open Standards" is that they will be the most ******* janked up bullshit dreamed up by architecture astronaut, and implemented by guys named Guarash who can't put together sentences in github issues

• 
  OpsWorker Team (@OpsWorker_ai) reported 30 minutes ago

  Connect GitHub or GitLab and OpsWorker automatically correlates alerts with recent code changes. Instead of: "high error rate on checkout service" You get: "correlates with deployment v2.3.1 pushed 14 minutes ago"

• 
  A War (@AWar1586398) reported 30 minutes ago

  @pmarca At this point, I interact with my coding agent/harness via WhatsApp and GitHub. I ramble into my phone and clean ideas get turned into issues, which then get turned into PRs that I review and merge.

• 
  Rahul Chavan (@codecroc) reported 33 minutes ago

  @jun_song github sponsors exists and nobody uses it. thats the whole problem and crypto doesnt fix the part where people just dont pay

• 
  JustAnotherPM | Sid (@JustAnotherPM) reported 38 minutes ago

  Karpathy's claude [dot] md has 143k stars on GitHub. Most people building with Claude Code haven't still read it. Here are Karpathy's 4 rules that will change how you code → Think before you code State your assumptions. if unsure, ask. If multiple interpretations exist, present all of them. Don't pick one silently and run with it. → Simplicity over everything Write the minimum code that solves the problem. No abstractions nobody asked for. No "flexibility" that turns 50 lines into 200. If a senior engineer would call it overcomplicated, simplify. → Surgical changes only Don't touch code unrelated to the request. Don't "improve" adjacent comments. Don't refactor things that aren't broken. Every changed line traces back to what was asked. nothing else. → Goal-driven execution Turn vague instructions into verifiable success criteria before writing a single line. "Fix the bug" becomes "write a test that reproduces it, then make it pass." Don't tell the model what to do. Tell it what done looks like.

• 
  Jesse (@Dev_JesseMaduka) reported 42 minutes ago

  @khom_ombo *** isn’t the server.. It just stores code. When you push, tools like Vercel/Netlify/GitHub Actions detect it and auto-deploy your app...

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

  Sources VulDB: CVE-2026-7062 Submission TheHackerWire: CVE-2026-7062 Advisory GitHub: Intina47/context-sync Issues #31 GitHub: wing3e Public PoC RedPacket Security: CVE-2026-7062 Analysis

• 
  Jon Pretty (@propensive) reported 49 minutes ago

  @Ciberon I usually max out at about six concurrent threads. Since I'm mostly working on Soundness, that means up to six *** worktrees. And I've had to change how I do pull requests because Github Actions is too slow to keep up...

• 
  Kekzploit (@kekzploit) reported 50 minutes ago

  @notfiveoverfive @pinkcliper @nym Yh, nah I'm not talking about GitHub stars, I'm talking about privacy and anonymity advocates researching, will naturally learn about mixnets, then encounter NYM down the rabbit hole.

• 
  Ritu Raj (@Gudakesh_07) reported 52 minutes ago

  6/7 Result? Loading times dropped by almost 70% — from 6-8 minutes down to under 2 minutes. He created a custom DLL patch, shared it on GitHub, and the story went viral. Rockstar eventually added his fixes, credited him in the patch notes, and gave him a $10,000 bug bounty.

• 
  hve 🍁 (@heyhve_) reported 53 minutes ago

  @JoelFickson @github 3000 minutes disappears fast on slow runners.

• 
  yeri (@yayriri) reported 59 minutes ago

  Finding AI agents buried in GitHub and giving them a face. Repo 1 done. Two versions shipped. V1: clone the repo, install Python, get API keys, run localhost. Full financial data. Real accuracy. For devs. V2: open Claude, drag in the file, pick a stock. No install. Web search powered. For everyone. Same 18 AI investors. Same debate. Different door. One repo taught me more about this problem than all the research combined: 1/ The agent isn't the bottleneck. The door is. 2/ 51K people starred ai-hedge-fund. Most of them never ran it. Not because it's bad — because poetry install is a wall. 3/ V2 isn't better than V1. It's just... reachable. That's what I'm building. Not better agents. Better doors :)

• 
  Osama (@OsssGhoul) reported 1 hour ago

  @github @GoogleAI @code Fix your pricing page I can't upgrade to pro

• 
  Lyrie.ai (@lyrie_ai) reported 1 hour ago

  Sources TheHackerWire: CVE-2026-7061 GitHub: Toowiredd/chatgpt-mcp-server GitHub Issue #8: Command Injection Report Public Exploit PoC VulDB: CVE-2026-7061 NVD: CVE-2026-7061

• 
  Smith (@phajbaba001) reported 1 hour ago

  Ignore the short term price charts. Focus on the GitHub repositories, the developer activity, and the real world problems being solved. The long-term thesis hasn't changed.