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	7 days ago
Tlalpan	Sign in	13 days ago
Quilmes	Website Down	13 days ago
Bengaluru	Website Down	15 days ago
Yokohama	Sign in	16 days ago
Gustavo Adolfo Madero	Website Down	20 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:

• 
  W♤L€ 🇨🇦🇰🇷🏴󠁧󠁢󠁥󠁮󠁧󠁿 (@wissh__us) reported 4 minutes ago

  gitcoin team built owockibot to run autonomously. browse the web, manage a treasury, post bounties, pay other agents in USDC day 5: private keys show up on github. agent says it didn't do it $2,100 gone. project shut down same day

• 
  John Solly (@_jsolly) reported 5 minutes ago

  It's a good day for GitHub 5xx errors.

• 
  João Capinha (@joaopcapinha) reported 6 minutes ago

  I'm using Claude Code more than any other tool in my stack right now, and not just for writing code. Here's how I'm running a DeFi project with agentic AI orchestration at its core. I'm coordinating across ClickUp, Google Drive, Slack, GitHub, and call transcripts. And the problem isn't that the information doesn't exist. It's that finding it, connecting it, and moving it between tools quietly becomes the job. Nobody puts "context archaeology" in the job description. It just eats your day. The shift: instead of jumping between apps, I talk to Claude about the project. Pull the latest task status. Cross-reference a spec. Update a ticket. Draft a message. One thread. No rebuilding context from scratch every time. It also makes you faster at being wrong (worth saying out loud!) Feed it a messy problem, you'll get back a very confident-sounding mess. The judgment still has to be yours. But the coordination overhead? The invisible tax that was never really the job? Most of it has disappeared. Huge productivity unlock.

• 
  Security Weekly Podcast Network (@SecWeekly) reported 6 minutes ago

  Even security professionals are scared to download random packages now. This clip breaks down the growing paranoia around GitHub repos, NPM packages, and PyPI downloads — including sandboxing software in Linux VMs and disabling automatic updates just to stay safe. How much trust should developers still place in open-source ecosystems? #Cybersecurity #OpenSource #SupplyChainSecurity

• 
  Somi AI (@somi_ai) reported 8 minutes ago

  Two compounding failure modes Datacurve's team surfaced. The tasks come from real GitHub issues, small and well-specified, built on data every coding model since 2024 has trained on. DeepSWE tasks edit 7 files and 668 lines on average. SWE-Bench Verified: 1 file, 10 lines. One is engineering. The other is recall.

• 
  Hennie (@andyhennie) reported 8 minutes ago

  @theo Really good post!! We’ve all just accepted the shortcomings of worktrees (we should be able to check out the same branch in multiple places) and GitHub (monorepo with private folders please). There might be good reasons for things being the way they are. But the world has changed. We’re not working the same way anymore. The world must adapt. And people in charge can fix it. Whether it’s Linus or a GitHub VP doesn’t matter. We just need to point it out. And explain the need. I don’t always agree with you, and I sometimes get annoyed when I see you kick downwards on X. But at this ****, you’re really really good! Gj. If you get the issues on this list done (by Theo-bullying them or asking nicely, I don’t care), I’ll get a picture of you on the wall of my office. Probably one with a mustache. ;)

• 
  Extella Research (@extellaresearch) reported 10 minutes ago

  at 48% context, claude told a user it wasn't being effective anymore. recommended starting a fresh session. less than halfway through a 1M context window. github issue #34685, anthropic's own repo. extella runs the other direction. each session builds on the last.

• 
  Tianyi-天轶 (@tian_yi_wang) reported 20 minutes ago

  do open ai and anthropic use github? do they not get blocked with millions prs queuing to be merged? and especially github is down so often these days.

• 
  Reso (@Resorcinolworks) reported 20 minutes ago

  SWE in 2022: >Documentation >Reviewers >Stack Overflow >Indian guy on YouTube with 240p thumbnail >Copy-pasting from GitHub issues >“Bro it works locally” >17 Chrome tabs open >Medium article from 2018 saving your career >Senior dev carrying the whole sprint >Reading error logs manually SWE in 2026: >Tokens and Opus 4.7

• 
  CryptoCloaks™ 🤘 (@CryptoCloaks) reported 21 minutes ago

  @AmericanFoolBTC @ProofofInk GitHub theres a posted a fix

• 
  Tejas AI (@VPsing06) reported 23 minutes ago

  @serenaa_ge Finally someone admitting that most public coding leaderboards are basically popularity contests and don’t reflect real messy developer work. Building tasks from scratch + proper trajectory analysis instead of just scraping GitHub issues is the right move. The gap between looks good on leaderboard and actually useful in production is massive.

• 
  Master Muskan (@MasterMuskan22) reported 23 minutes ago

  So, GitHub went down when I was reviewing a PR, nice.

• 
  Amu (@amu4biz) reported 26 minutes ago

  @realokwy_ @0xWassie @GeckoTerminal cause github is down na? using gitlawb

• 
  Flareforward (@flareforward) reported 29 minutes ago

  Filed a GitHub issue asking @OpenAI to add a programmatic chat API to Codex Desktop so external agents could spawn sidebar-visible chats. 5 days later Codex 0.133.0 dropped with the exact API. Wired it into my multi-agent fleet tool the same day it shipped. Submission → implementation → production in one week. The feedback loop is real.

• 
  Mediocre (@piyushpradhan07) reported 30 minutes ago

  Couldn't find anyone working on this in Github Issues. Thinking about vibe coding this over the weekend.

• 
  Jozef Izso (@jozefizso) reported 32 minutes ago

  Another day, another @github outage during work hours.

• 
  Divya Teja Reddy (@divyateja93) reported 35 minutes ago

  @e_myrax Massive thanks @e_myrax — you're literally my first non-friend signup 🙏 The empty stats make sense if it's an old account. If you want to point it at your current GitHub, just sign back in with that one and the banner will update. What's the "room for improvement" you noticed? Genuinely want to hear — even the small stuff. The whole point of launching now is to fix what real users hit.

• 
  Spektion (@spektion) reported 40 minutes ago

  → 𝗬𝗼𝘂𝗿 𝗦𝗕𝗢𝗠 𝗰𝗹𝗲𝗮𝗿𝘀 𝗶𝘁. 𝗥𝘂𝗻𝘁𝗶𝗺𝗲 𝗰𝗮𝘁𝗰𝗵𝗲𝘀 𝗶𝘁. The same package writes to ~/.ssh, encrypts a keystore with an XOR key, POSTs to a GitHub Gist. Process-behavior problem, caught where the process executes.

• 
  Rhinest☆ne (@CrimsonHaze2) reported 41 minutes ago

  @Yishivali I got it from a github repository from a server so maybe?

• 
  Mohabatt_man (@mohobatt_man) reported 44 minutes ago

  is github copilot down ? anyone else facing the issue ?

• 
  alexstrauss.x (@alexstrauss19) reported 45 minutes ago

  Seems like GitHub is my server now

• 
  Justin Brooke (@agentskills_ai) reported 45 minutes ago

  You will regret installing Hermes locally ESPECIALLY if you're not backing up to Github daily. Local machines die, get unplugged, lose wifi connection, kids break them, things spill on them. That's why I install mine on a cheap VPS server, and I like DigitalOcean because they have a CLI. Which means, Claude can do the whole install for me. - It's super cheap - Always on - No one can steal it - Accessible from any device anywhere If you're a non-techy like me, then this checklist will be the fastest, easiest, safest way to install Hermes. Just let AI do it for you...

• 
  Live Out Loud and on Purpose (@LoveItAndLiveIt) reported 48 minutes ago

  @TheLouieCo @MikeNellis So, you’re blaming AI because you don’t want to pay a premium to bypass that problem? The moment I came across limits in GitHub Copilot — I upgraded to the first tier. And when I ran into limits after that — I upgraded again. I’ve never had a problem since.

• 
  Startup & Tech (@startup_an_tech) reported 48 minutes ago

  An Indian dev is trending globally on GitHub right now with stop-slop. It has already crossed 5,300 stars and people are actually using it to clean up AI generated junk from their datasets. This is a massive problem for training good models. 🧵👇

• 
  morizotter (@morizotter) reported 51 minutes ago

  Maybe because of yesterday’s GitHub Actions outage, all the issues I was creating via workflows have vanished. I was watching it happen in real-time—the issue count kept dropping, the author changed to 'ghost', and finally, I couldn't access them anymore 🫥 @githubstatus @github

• 
  Daryl Micah (@_darylm) reported 51 minutes ago

  Plain dropped their free tier mid-build. Whole project pitched as $0/mo.Pivoted the support signal to GitHub Issues in 30 minutes. The data layer is just SQL — swapping one Coral source for another mostly rewrote itself. This is the @WithCoral_com payoff I didn't expect.

• 
  Tarak (@octavianslash) reported 52 minutes ago

  GitHub down again. The only way they can survive this Ai-pocalypse is to remove the free tier and to back to their old pricing

• 
  Shaurs (@Shaursbtw) reported 53 minutes ago

  Paid scraping tools are basically obsolete. A free open-source AI just hit #1 on GitHub. Paste a url, describe what you want in plain English, get LinkedIn profiles, emails, pricing in 60 seconds. No code, no captchas, no bans. Tested on 500 profiles. Zero issues. Comment 'SCRAPE' for the link.

• 
  ed_the_engineer (@ed_the_engineer) reported 54 minutes ago

  Two years ago, open local LLMs were a hobby project. They solved 4% of real GitHub issues. The cloud was 20× ahead. Today a 9B model on a 16 GB consumer GPU solves 65%. The frontier sits at 80%. The gap that used to be a chasm is ten points. Look at the curve: → April 2024: Llama 3 70B at 4% on SWE-bench Verified → Jan 2025: DeepSeek R1 jumps the frontier to 42% — reasoning post-training arrives → Q1 2026: small-tier models (≤16 GB VRAM) cross 50%, then 65% in a single quarter → May 2026: frontier open ~80%, mid-tier ~73%, small-tier ~65% What used to require a datacenter now fits on a card you can buy at a consumer electronics store. What used to require the cloud now runs on your desk with the network unplugged. If the small-tier line keeps its slope for another 12 months, the model running locally on a $500 GPU will solve more real engineering tasks than the best cloud model could in early 2025. The question isn't whether local catches up. It's what we do once it has?

• 
  KUMBAJI RAJ KUMAR (@KumbajiK) reported 57 minutes ago

  Ship 1 small public project every month. No excuses. Not a tutorial clone. A real thing that solves a real problem. Your GitHub becomes your portfolio. Your portfolio becomes your leverage. 💀