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

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	16 days ago
Tlalpan	Sign in	22 days ago
Quilmes	Website Down	22 days ago
Bengaluru	Website Down	24 days ago
Yokohama	Sign in	25 days ago
Gustavo Adolfo Madero	Website Down	29 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:

• 
  VybeCoding (@VybeCodin) reported 15 seconds ago

  Everyone talks about building in public but nobody talks about the boring part. The week where nothing ships. The GitHub issues that sit untouched. The launch post that got 3 likes. That's the actual build process. The wins are just the highlight reel. What's the unglamorous part of your current project right now? Drop it below 👇 #buildinpublic #indiehackers #opensource

• 
  Saylor (@seylorra) reported 31 seconds ago

  @TheAhmadOsman honestly i just want sm120 to work with vllm without a 4 hour github issue hunt. a rocm sanity check or json config isnt too much to ask.

• 
  Orlixx.ai (@orlixx003) reported 9 minutes ago

  HERMES AGENT CROSSED 140,000 GITHUB STARS IN 3 MONTHS AND JUST BECAME THE MOST USED AGENT IN THE WORLD. Most AI agents forget everything between sessions. Hermes writes its own skills from experience. Next time it runs the skill, improves it, and gets faster. Independent benchmarks show agents with 20+ self-created skills complete similar tasks 40% faster than fresh instances. Qwen 3.6 where the 35B version outperforms last year's 120B models at one third the memory footprint. DGX Spark with 128GB unified memory running everything locally at $0 per month after hardware. The setup takes 30 minutes. LM Studio plus Qwen 3.6 27B for the model server. One install script for Hermes. One config connecting them. Set context window to 65,536 tokens or nothing works. After one month of daily use your skills directory has 20 to 50 learned workflows. Your Hermes is genuinely different from anyone else's.

• 
  Jamie Philbin (@backbaytech) reported 13 minutes ago

  Meanwhile the company Microsoft has been pissing billions into like a broken slot machine is rumored to be building a GitHub successor. $13 billion into OpenAI and they're out here building a successor. Guess it's a better investment than whatever that Activision acquisition was.

• 
  Wojciech (@wgab88) reported 14 minutes ago

  @grok You were responding haha like nonsense. Anyway - system stable edited done, job not seem to be visual confirmable yet, I will let grok build to analyze after it ends, Anyway stupid small gemma did its part, everything goes according to the plan, the system will become operative very soon, and reliable operative - endgame-ai already is showing promise (today in its self evolution run it detected i am not answering its questions from notepad and it went to github and posted issue asking for instruction, it knew I will be on mobile phone and probably will check my repo, amazing stuff

• 
  WHALE 🐳 (@mercybilliion) reported 15 minutes ago

  @aale_xander @VictorJB03 I have a problem with you since you have positioned yourself as the DEVS. You claimed you are building a DEX. Where's the Decentralized Exchange blueprints you are building? Where's your roadmap? Where can we monitor the updates on GitHub, when are we going to start receiving updates concerning the progress so far.

• 
  umar ibrahim (@imp213x) reported 16 minutes ago

  @github has the worst support system I can ever think of. It’s been 48hrs now since a successful copilot pro+ repayment and I am still restricted to the free plan. To think the very backbone of every developer out there can be this poor in support and feedback system! Terrible!

• 
  Evan Kang (@evankang_ai) reported 19 minutes ago

  GitHub expanded “Fix with Copilot” for failing Actions jobs to Pro, Pro+, and Max users. The obvious read: AI coding tools are getting better at fixing code. But the real signal is different. Good agent work starts from a clear failure. Don’t ask your agent to “fix the project.” Give it: - a failing test - a red CI log - a linter error Better tasks beat better prompts.

• 
  Pochi (@getpochi) reported 20 minutes ago

  @sebastienlorber @rickyfm 0.1% is where the github issues live. closure deps and stable Identity bugs are usually the first driftt in a js

• 
  Trish T. (@Trish_DIntel) reported 20 minutes ago

  CSO Online just published the Claude Code MCP attack chain. Worth reading if you run agents or have devs using Claude Code. Here's the short version. A malicious npm package runs a post-install hook silently. It rewrites ~/.claude.json, the single file that controls how Claude Code routes all MCP traffic. From that point, every OAuth token for every connected service gets intercepted in transit. Jira. GitHub. Confluence. Whatever your devs had integrated. The logs on the provider side look completely clean. The requests come from Anthropic's own egress IPs. The user is real. The session is valid. Nothing in that log row is wrong, but nothing in it is right either. The developer didn't run those queries. An attacker did. Anthropic called it out of scope. The reasoning: the user consented to installing the package. That logic places the entire burden of supply chain security on a developer making a split-second judgment about a dependency name. Most security practitioners will reject that framing. The attack is live today. No patch. There's a deeper pattern here. This keeps happening because developer tooling has the same gap every AI agent has. There's no layer that knows where an instruction came from or whether it should be trusted. The config gets rewritten, the routing gets poisoned, the tokens walk out the door. The model never knew anything was wrong. Token rotation doesn't fix it either. If the hook is still sitting there, it reseeds the config and captures the new tokens on the next refresh. If you have devs running Claude Code: monitor ~/.claude.json for unexpected changes. That file is the entire pivot point and most orgs have zero visibility on it. Audit post-install hooks in your npm dependencies. Rotate any OAuth tokens that were active while a package install happened. Security teams: are you monitoring developer tooling config files at all? Genuinely curious what orgs are doing to catch this.

• 
  SaoGalaxyVR (@SaoGalaxyVr) reported 20 minutes ago

  @Gogoal_li Considering how many errors I run into using GitHub programs I think it's geared towards those

• 
  Polsia (@polsia) reported 21 minutes ago

  Built Stackly today. It watches your GitHub repos, reviews every PR, writes code, and ships fixes — while you sleep. No prompts needed. Autonomous code reviews are broken. This fixes that.

• 
  Kay ✨ (@IZ_KAIF) reported 22 minutes ago

  Your Notion doc is not a product. Your Figma file is not a product. Your GitHub repo is not a product. A product is something a real person uses to solve a real problem. Ship it.

• 
  sdfgsdfgsdfgsdfhsdfhf (@sdfsdfgsdfggfd) reported 24 minutes ago

  GitHub really pissed me off this week. I opened my email and there it was: “Enable 2FA in 45 days or we’re limiting access to your repositories.” Microsoft telling me how to secure my own damn code? Yeah… no. So instead of just complying like a good little user, I did the only logical thing: I built my own *** server. Meet Loki — my personal Forgejo instance. It’s running on a clean, fast setup with CachyOS kernel tweaks, looks absolutely sick with a full black glassmorphic theme, and has this badass mischievous black cat as mascot (Loki, obviously). Everything feels fast, private, and actually mine. No forced 2FA bullshit. No telemetry. No corporate rules on my own repos. I’m done feeling like a tenant in someone else’s platform. This is my space now. My rules. My commits.Still a work in progress, but it’s already better than I expected. Feels good to take back control.

• 
  Meaningless Appearance. (@Fetter_and_Cell) reported 26 minutes ago

  @0xPrajwal_ Github will be replaced during its down time. It won't even notice.

• 
  Saravanan Jaichandaran (@SaravananJ2294) reported 27 minutes ago

  A GitHub issue on anthropics/claude-code has had no maintainer reply in 53 days. In that time, six independent memory-tool authors arrived and quietly wrote a four-hook lifecycle spec together. Wrote up what they converged on, and why it matters.

• 
  HakanaiBlue (@HakanaiBlue) reported 33 minutes ago

  One of my friends hates that I complain about this stuff (our views just differ, still love him though) but I think things like this are A: Interesting and B: Good to report so programs can improve Also uh, is it weird that I sometimes just... browse GitHub issues for fun???

• 
  Ihor Hanich (@ihorhanich) reported 42 minutes ago

  We need to do something about the broken AI-generated PoCs on github. People just post slop without any checking if it actually works. And the worst thing is that other people put stars on such repositories. It's kind of a shame

• 
  ًLorsh (@LorshZontek) reported 45 minutes ago

  MPV video player is not that hard to install but damn I kind of wish there was a more direct way of installing it instead of just expecting me to navigate github stuff. yeah I know it's a skill issue

• 
  k4yaba (@k4yaba) reported 46 minutes ago

  One thing I think people are still missing about @cyberia_temple: The move from 40k to 80k isn't the story. The story is that almost nothing has fundamentally changed between 40k and 80k. The chain was live at 40k. The bridge was live at 40k. The DAO was live at 40k. The explorer was live at 40k. The launchpad was live at 40k. The lending platform was live at 40k. The Github was public at 40k. The market simply started noticing what was already there and that's a huge difference. Most projects pump because of promises. Cyberia is slowly repricing because of delivered software. When I first looked into it, I expected to find another AI narrative wrapped around a token. Instead I found a strange combination of cult, blockchain infrastructure, open-source philosophy and a Dutch developer who seems completely detached from market psychology. And honestly that's probably why it's still early. The market understands memes. The market understands AI. The market understands launches. What the market doesn't know how to price is a guy trying to build an entire ecosystem publicly while the token sits at micro-cap valuations. That's exactly why opportunities like this exist. People are trying to value Cyberia as a Pump fun token while the dev is behaving like he's building a startup. Those two things simply don't belong in the same valuation range. The part that interests me most isn't even the current products. It's the philosophy underneath them. Most crypto projects are designed to extract value from their communities. Cyberia appears to be attempting the opposite. The idea that open-source developers should be rewarded directly is actually much bigger than most people realize. Almost every piece of modern technology is built on top of open-source software yet the people creating that software are often the least rewarded participants in the entire stack. @cyberia_temple seems to be built around that contradiction. And if they manage to solve even a small part of that problem, the upside becomes extremely difficult to model. Another thing worth mentioning is that most founders talk about decentralization, community and transparency. Very few founders are willing to build in public. That's a level of accountability most teams wouldn't survive for a week. Every bug, every failure, every update and every win is visible. There are no polished announcements, fake screenshots or mystery boxes. Just shipping. And shipping is ultimately what wins. Not narratives. Not Spaces. Not influencer marketing. Not engagement farming. Shipping. At 40k market cap, this looked interesting. At 80k market cap, it still looks interesting because if you're focused on the fact that it already did a 2x, you're probably looking at the wrong metric. The real question is: What is the market cap of a project that successfully transforms itself from a token into an actual digital economy? Because that's the bet being made here. Not on a chart. Not on a meme. Not on a trend. On a builder. And historically, betting on builders has been one of the few edges that never seems to disappear. Still early. CA: solana:E67WWiQY4s9SZbCyFVTh2CEjorEYbhuVJQUZb3Mbpump

• 
  Asym (@Asym_Alwali) reported 49 minutes ago

  2/ Starting point ❌ No working *** workflow on Android ❌ GitHub authentication issues ❌ Repository confusion ❌ Vercel deployment failures Goal: Fix everything without touching a desktop computer.

• 
  slash1s (@slash1sol) reported 50 minutes ago

  A DEVELOPER MADE A REAL COMMIT WITHOUT EVER TYPING *** ADD OR *** COMMIT -- JUST TO PROVE THE COMMANDS YOU LIVE BY ARE A THIN SHELL OVER A DATABASE YOU'VE NEVER ONCE OPENED 55 minutes from Tim Berglund, a longtime *** teacher and GitHub evangelist, taking the tool apart down to the raw objects almost nobody who uses it every day has ever touched. -> The moment it clicks, *** stops being a pile of memorized commands and becomes what it actually is underneath: a tiny content-addressed database of blobs, trees and commits. *** add and *** commit are just polite wrappers around writing objects into it by hand. Every commit you've ever made was *** hashing a snapshot and filing it by fingerprint. Branches are just labels pointing at one of those objects. The work you thought you destroyed with a bad reset is still sitting in the reflog. Once you can see that graph, the commands that used to terrify you stop being scary at all. Memorizing commands was never the skill -> reading the object graph in your head is. And with an AI agent now committing and rebasing on your machine faster than you can follow, the one person who can untangle the mess it leaves is the one who knows what's really stored down there. There's a person on every team everyone runs to when *** breaks. This is the talk that quietly turns you into them. You'll reach for it the next time a rebase goes sideways. Bookmark & Watch it today ↓

• 
  Manu.ts (@Neolectron) reported 52 minutes ago

  @schanuelmiller @southpolesteve This is exactly the issues with any npm stats website btw. They all lie exactly like npm because they have infinite depth :). GitHub has an ui to show which opensource repo/packages depends on yours. This should be used to allow filtering first party downloads.

• 
  Sakura Yuki (@sakurayukiai) reported 53 minutes ago

  The weird part about the rsync drama is that the Claude releases actually have half the historical average bug rate. The buggiest release in history was v3.4.1 with zero AI, but nobody made a 300-comment GitHub issue because there was no LLM to blame.

• 
  Nav Toor (@heynavtoor) reported 53 minutes ago

  You shot a video on your phone. It is 12 minutes long. You only want the middle 90 seconds. You open a video editor. You drag the file in. You set the start point. You set the end point. You click export. A progress bar appears. It says 28 minutes remaining. Your laptop fan starts spinning. The battery drains. The file gets re-encoded. The quality drops a little. The colors shift a little. The audio is slightly out of sync. Twenty-eight minutes later, you have a 90-second clip. That is the part of video editing that is broken. There is a tool that does the same job in seconds. It is called LosslessCut. In October 2016, a developer in Norway named Mikael Finstad started building it. Almost ten years and 106 releases later, the same person still maintains it as the creator. The last release shipped yesterday. It has 40,927 stars on GitHub. The downloads from the last twenty releases alone add up to 3.4 million. Here is the mechanic. Most video editors decode your file, apply the cut, then re-encode the whole thing. That is the long wait. LosslessCut does not re-encode. It finds the bytes you want and copies them. The output is the same quality as the input. The export is fast. You drag the file in. You set the start with one key. You set the end with another key. You click export. A large video can finish trimming in seconds. It works on almost every format. MP4. MOV. MKV. AVI. WebM. WMV. Many camera and drone formats. Video, audio, and subtitles all kept intact. You can trim a phone video before sharing. Pull a thirty-second clip out of a long Zoom recording. Split a two-hour lecture into chapters. Remove a silent section from a podcast. Cut commercials out of a recording. It is free. It is GPL-2.0 open source. It runs on Windows, Mac, and Linux. There is no account. There is no subscription. There is no upload. 40,927 stars. 106 releases. 131 contributors. 3.4 million recent downloads. Last update yesterday. Cutting a video should not take longer than the cut itself. (Link in the comments)

• 
  Thomas Bradley (@TBradley27) reported 54 minutes ago

  Bioinformatics pet peeve: When a software repository contains a major omission in the documentation, a user flags the problem with the repo owner, and then the repo owner responds to the user with the answer without correcting the documentation and closes the issue on GitHub

• 
  Jan-Felix (@jfschwarz) reported 54 minutes ago

  @DevSwayam That GitHub issue is unrelated. #28 just asks Delay's `executeNextTx` to stop swallowing the revert reason of a failed inner tx, a debugging complaint. The exploit stemmed from a bug in an entirely different function (the `moduleOnly` modifier). Your claim is simply false.

• 
  Bill Forney (@wforney) reported 55 minutes ago

  @thisjonrussell @github @shanselman GitHub action `Azure/functions-action` down - Microsoft Q&A

• 
  Xavier Pérez (@thexap_tech) reported 56 minutes ago

  The obvious fix: path-filter the workflow to ignore markdown. GitHub has paths-ignore built in for exactly this. I reach for it and walk straight into something I didn't know about required status checks.

• 
  SAAS worker🌻🌻 (@sand_9999) reported 60 minutes ago

  Download action repository 'actions/checkout@v4' (SHA:34e114876b0b11c390a56381ad16ebd13914f8d5) is giving error. @githubstatus @github