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 (58%)
• Errors (33%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Colima	Website Down	2 days ago
Poblete	Website Down	3 days ago
Ronda	Website Down	3 days ago
Montataire	Errors	3 days ago
Montataire	Website Down	4 days ago
Tortosa	Website Down	6 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:

• 
  BadKidsEnjoyer (@BadKidsEnjoyer) reported 1 minute ago

  SN62 Ridges went parabolic → afterwards we corrected hard But the Team never stopped building While price dipped: -Ridgeline live: autonomous agents that solve GitHub issues end-to-end -Harbor integration + multi-language evals -Dynamic screeners, real-time patches, commit stats -Scoring 73-88% SWE-Bench Verified + 96.3% Polyglot Hard Facts: -Market cap: ~$32M (FDV ~$145M) -Built a Cursor/Claude competitor with just ~$10M in TAO emissions -Cursor sits at $29B valuation Product accelerating ✅ MCap still tiny✅ $TAO #SN62 #RidgesAI

• 
  Aryan Sawant (@aryan97208) reported 3 minutes ago

  If you’re a Computer Science student, read this: Stop wasting time on 10 courses. Do this instead 👇 1. Learn 1 language properly (Python/Java/C++) 2. Build 3 real projects (not tutorials) 3. Learn *** + GitHub 4. Solve 1–2 DSA problems daily 5. Start applying before you feel “ready” That’s it. No one cares about your certificates. They care about what you can build. Start today.

• 
  Prajwal Tomar (@PrajwalTomar_) reported 3 minutes ago

  Most people using Claude are wasting HOURS re-explaining the same thing every session. This CLAUDE .md hit #1 on GitHub with 82K stars and most Claude users still don't know it exists. This permanently fixes the repetition problem.

• 
  gary IH fung (@garyfung) reported 4 minutes ago

  @Teknium That takes care of GitHub issues Replace GitHub next? 🙏🏼

• 
  DataBoss (@DatawithAkshay) reported 6 minutes ago

  A single 𝗖𝗟𝗔𝗨𝗗𝗘.𝗺𝗱 file just hit #1 on GitHub trending 🤯 It fixes LLMs' worst coding habits using 4 principles from Karpathy: Karpathy called LLMs out for making wrong assumptions silently. They overcomplicate everything. They edit code they were never asked to change. No pushback. No clarifying questions. They just run. So those observations were encoded into 4 behavioral constraints: → Think before coding. If something’s ambiguous, ask. Don’t pick one interpretation and run. Surface tradeoffs, stop when confused. → Simplicity first. Write the minimum code that solves the problem. No speculative abstractions, no flexibility nobody asked for. → Surgical changes. Only touch what the task requires. Don’t improve neighboring code, don’t refactor what isn’t broken. → Goal-driven execution. Turn vague instructions into verifiable targets before writing a line. “Add validation” becomes “write tests for invalid inputs, then make them pass.” It works immediately. Drop the file in your project root and Claude Code follows it from the first task. One file. Zero dependencies. No setup. And best part, 100% open source.

• 
  Unbearabull󠀽󠀽 ♕ (@Unbearabull2) reported 10 minutes ago

  $Staccana (Solana Fork Staccana) is doing really well. The website for this token is a Github repository--the source code for this fork. It takes a lot of work to fork Level 1 infrastructure. Definitely not just a meme + hopium like almost every other Sol token. I trust this token won't rug, at least not because of the contract or code. This doesn't mean the poorly-performing alt coin market won't drive it down though. NFA Trustworthiness should be the starting point for all tokens again. More transparency should become mandatory on Solana because the whole blockchain needs a lot of improvement especially in the trust department.

• 
  Willian Mitsuda (☕, ☕) 🦇🔊 (@wmitsuda) reported 11 minutes ago

  Unfortunately every GitHub alternative is a GitHub clone and would suffer from AI slop scalability issues. Ironically I think we'll all eventually end up using *** like the Linux kernel, by sharing patches via email between trusted collaborators, which is the only sane way to filter out junk.

• 
  🐍 Tal Weiss (@majortal) reported 12 minutes ago

  Evolution: 1. Claude, fix GitHub issue 726. Get to the root cause, use TDD, mark as feature request if not in spec and ping me for escalations; test all and deploy patch 2. /bug 726 3. /bugs 4. /schedule every 7am run /bugs 5. /wire /bug to GitHub issues as they arrive

• 
  androolloyd.hl (@androolloyd) reported 18 minutes ago

  @0xKmafia GitHub issues

• 
  Beau Johnson (@BeauJohnson89) reported 22 minutes ago

  your coding agent should not be trapped on your laptop browser-use/bux > 298 stars on github > 24/7 claude code agent on any ubuntu box > real chromium session through browser-harness > telegram bot included > persistent cookies, skills, and chat history this is the right direction not another chat window a cheap box with a real browser, live handoff for login walls, and an agent you can text from anywhere

• 
  Artur Schaback (@skyzer4ever) reported 22 minutes ago

  @TuahaJawaid @steipete @sama All their open GitHub issues and pull requests

• 
  CryptoD₿S (@DbsCrypto) reported 23 minutes ago

  The loudest feedback is usually the cheapest. I care less about the clever Reddit comment than the 3rd confused GitHub issue from someone who already installed, integrated, and got stuck. Public feedback matters when it comes with cost. Time spent. Setup done. Real friction hit. Everyone else is mostly writing fanfic for your roadmap.

• 
  Alex Styl (@alexstyl) reported 29 minutes ago

  For the first time in forever all my Github issues are blocked by either Google or JetBrains.

• 
  Petra Donka (@petradonka) reported 32 minutes ago

  @Qodesmith @warpdotdev Thanks for the report! That should just work — would you mind opening a GitHub issue so we can track a fix for it? We've squashed a bunch of bugs around the filetree, this may be another one that needs to be fixed.

• 
  Gocha Berulava (@gochaberulava) reported 33 minutes ago

  @sherifgjini "does the work for me." pick a usectl machine, push to github, your app is live with managed postgres, redis, storage, ssl, custom domain. no server to configure, no devops chair to fill.

• 
  Ayush Sharma (@theayush) reported 33 minutes ago

  @peer_rich I am optimistic that GitHub will fix it before any solid alternative arrives

• 
  OomkaBear (@OomkaBear) reported 36 minutes ago

  There are ~12 obsidian-MCP servers on GitHub. Enquire is different on three axes: ✅ Standalone — reads .md directly. No Local REST API plugin needed. ✅ Read-rich — backlinks, broken-wikilink scan, outbound resolver, Dataview queries (AND/OR/LIKE). ✅ Safe-by-default — read-only, opt-in writes, symlink-escape blocked.

• 
  mels.dev (@AmirizeW54059) reported 36 minutes ago

  Seems like I’m the only one experiencing this GitHub and copilot issue 🤧

• 
  kate (@whoiskatrin) reported 37 minutes ago

  @threepointone @abhagsain @mattzcarey Hey Anurag, file a GitHub issues in our agents repo and I will take a look ASAP

• 
  Anupam (@Anupam_Devops) reported 37 minutes ago

  You don't need to know everything in DevOps. I know. The roadmap said otherwise. You opened it. Saw Kubernetes, Terraform, Ansible, Docker,Jenkins, GitHub Actions, Prometheus, Grafana, Vault,ArgoCD, Helm, Istio, Pulumi, AWS, GCP, Azure… And you thought: I need all of this before I'm ready. You don't. That's the trap. The overload trap: 🔴  Jump between 10 tools, master none 🔴  Start a new course every time you see a job posting 🔴  Feel perpetually behind — because the list never ends 🔴  Ship nothing. Build nothing. Just consume. What actually works: 🟢  Pick one cloud. Go deep — not wide. 🟢  Learn Docker → then Kubernetes. In that order. Slowly. 🟢  Build a real pipeline end-to-end. Break it. Fix it. 🟢  Understand why a tool exists before learning how to use it 🟢  One project shipped beats 12 tutorials watched. The engineers who know everything? They don't exist. They just know their stack really well and know how to learn the rest fast when they need it. Breadth comes with time. Depth is what gets you hired. Stop collecting tools. Start building fluency.

• 
  Thanh Nguyen (@ng_thanh8) reported 39 minutes ago

  A 13-year-old in Thailand just built an AI coding agent that can solve Codeforces 800s in about 45 seconds. 😳 Setup? - MacBook Air - HHKB Type-S keyboard - Claude Code as the “brain” - Chrome MCP plugin to read the problem - GitHub repo with the whole system open-sourced He doesn’t have a competitive programming coach. He hasn’t taken contest programming classes. He hasn’t even written code by hand during this run. And yet: 23 solved problems in a month, rating up to 800 in 12 days, and one weekend to build the whole workflow. This is equal parts impressive, futuristic, and slightly terrifying.

• 
  Maor Ai (@Maor_Elkarat) reported 44 minutes ago

  In 2015, the Chinese police visited a programmer's home. They told him to stop working on his code. They told him to delete it from GitHub. He posted one final message before he obeyed: "Two days ago the police came to me and wanted me to stop working on this. Today they asked me to delete all the code from GitHub. I have no choice but to obey. I hope one day I'll live in a country where I have freedom to write any code I like without fearing." Then he deleted the repo. Then he deleted the message. Then something happened the Chinese government did not plan for. Within hours, the code was mirrored to thousands of other GitHub accounts. Within days, it became the #1 trending repository on GitHub globally. Within weeks, every Chinese developer who could compile code had a copy. The government tried to make it disappear. The act of trying made it permanent. The project is called Shadowsocks. The programmer's username was clowwindy. He built a tiny piece of software that let anyone in China bypass the Great Firewall and reach the open internet. No subscription. No company. No account. You set up a server somewhere outside China. You connect to it. Your traffic looks like normal encrypted web browsing, so the firewall cannot tell you are using it. Why this terrified the Chinese government in 2015: → It was open source. Anyone could compile it. → It was small. The whole protocol fit in a few hundred lines of code. → It looked like normal HTTPS traffic. The Great Firewall could not distinguish it. → It required no money. No accounts. No central server to seize. → It worked on every operating system. You cannot arrest a protocol. You can only arrest the person who wrote it. So they did. And the protocol kept spreading. shadowsocks-windows: 59,300+ stars. GPLv3. Still online 11 years later. The 2015 commits the Chinese government wanted deleted are still in the history. clowwindy was forced to walk away. The code never did. But DO NOT install it. The Great Firewall has feelings too. 100% Open Source. (Link in the comments) Must Follow For More updates.

• 
  Jeff Conlon (@freeconlon) reported 46 minutes ago

  The team rebuilt our landing page workflow this week. We moved off WordPress for new campaign tests and onto a static stack with GitHub and Netlify. Here's what that means in practice. A new landing page used to take four to seven days to ship. Login to a CMS, fight with a theme, wait on a developer, deploy, debug. Now it's hours. Most agencies treat the landing page as a CMS problem. It isn't. A campaign LP is a one-page test. You need to ship five versions in two weeks to learn anything. WordPress was designed for a thousand pages, not five tests. The fix wasn't a new template. It was changing the underlying system so the page is just a file in a repo. If the bottleneck is your tool, the answer isn't more tool. It's a different one.

• 
  The Bingus Man (@NotNordgaren) reported 47 minutes ago

  @thekitze IDK. Some joke about GitHub and going down and maybe Bryan Johnson

• 
  Naveen Pandey (@naveenpandey27) reported 51 minutes ago

  Apple was irrelevant in AI for years. One open-source project accidentally changed that — and now they can't build Macs fast enough. Here's what happened: OpenClaw — an AI agent framework with 323K+ GitHub stars — needs a machine that can run large models locally. Turns out Apple Silicon is perfect for this. The Mac mini's unified memory lets CPU, GPU, and Neural Engine share the same RAM pool. A $599 Mac mini with 64GB can run 70B parameter models that an $1,800 NVIDIA RTX 5090 physically can't touch. Result? Mac mini and Mac Studio are sold out. Tim Cook told analysts it may take "several months" to catch up. Mac revenue hit $8.4B last quarter. Apple didn't plan this. They got lucky. But they won't stay lucky for long without a real AI strategy. And that's now John Ternus's problem. Tim Cook is stepping down as CEO on September 1. Ternus — a hardware guy with 25 years at Apple — takes over. Nowhere in the announcement did Apple mention AI. Not once. Meanwhile: → Apple's AI chief John Giannandrea retired → Their head of UI design left for Meta → Their COO retired → It's the biggest executive exodus since Steve Jobs died The opportunity is massive. 2B+ devices. On-device AI that rivals anyone's distribution moat. But distribution without a strategy is just hardware waiting for someone else's software. The question isn't whether Apple can make great chips. It's whether their new CEO can build an AI vision before Google, OpenAI, and Anthropic make Apple's devices just a screen for their agents. #AIwithNaveen #Apple #ArtificialIntelligence

• 
  Vijay (@imotiusa) reported 55 minutes ago

  The problem: When an alert fires at 2am, the error message tells you WHAT broke. It tells you nothing about WHY. So your on-call engineer spends 20 minutes manually searching Jira, Slack, and GitHub before they even start fixing anything. That's the gap I wanted to close.

• 
  Yash Solanki (@YashSolanki_) reported 57 minutes ago

  @thdxr Don't you think if GitHub genuinely put some effort into the infrastructure, then they could easily fix it, and other competitors would still be so much behind them

• 
  Ofek Shaked (@VibeCoderOfek) reported 57 minutes ago

  @socialwithaayan Just pointed it at a real GitHub issue and watched it spec + code + PR in one go. Terminal is dead, long live Warp.

• 
  JMoon (@Jmoon_174) reported 57 minutes ago

  @bas_fijneman screenshot to github issue to auto-fix is a tight loop. the hard part is usually the issue spec. does claude get enough context from the screenshot to produce a fixable issue?

• 
  Alan Lam 🔥 (@extralam) reported 58 minutes ago

  anyone know, is it possible to add a general user to @github repo, but he cannot see the code? just for rise issue ?