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

• 
  CodedExit (@codedexit) reported 1 minute ago

  @johnappscaler An MCP server that connects Claude (or similar) to real market data so founders can ask what's worth building instead of guessing from inconsistent data. Current distribution: MCP registries, npm, GitHub. What am I missing?

• 
  Dr Owain Kenway (@owainkenway) reported 1 minute ago

  @dschewchenko Yeah. Github really needs to sort a bunch of the token stuff. Things like pushing containers to the Github container registry don't support fine-grained access tokens which is asking for trouble.

• 
  Cyfrin Audits (@cyfrin) reported 6 minutes ago

  This pairs with Cygent's daily scans against OSV, GitHub Security Advisories, Socket, and other intelligence sources. When a new CVE lands, Cygent checks it against your actual dependency graph, not a generic feed. You get an alert with the affected package, severity, dependency context, and suggested fix, routed to Slack, Discord, Telegram, or email.

• 
  Yusuf Nuh 🍉 (@SenseWave_) reported 6 minutes ago

  @ZackKorman @NinjaParanoid It's sick. Just days ago we see they're saving are passwords as plain text. And now threatening researchers for their research. They even took down one GitHub account, that published vuln

• 
  🏴‍☠️ (@wackoiam) reported 12 minutes ago

  with GitHub features and workflows What would you like to work on today? You can: - Ask me to review or summarize a pull request - Search for code or issues in a repository - Create or manage GitHub issues - Debug errors or stack traces - Or anything else related to your

• 
  Pablo Pedrotti (@pablonpedrotti) reported 14 minutes ago

  @github Are you going to fix the extreme token usage, bugs and poor responses of Copilot? Even if you want to pay API prices it is a terrible idea to do so on Copilot. Tasks that used to take 5 to 10 minutes on Copilot now take me 30 seconds on Codex sub with Pi, with better results.

• 
  Enes Çakır (@menescakir) reported 14 minutes ago

  @kdaigle @github @Nebuk89 It ran ~10 days (May 19–29) before mitigation, and the hardest part was not being able to get a clear signal from support in the meantime. Is there a faster escalation path for issues like this, and any plans for regional incident reporting?

• 
  OptiRefine (@OptiRefine) reported 16 minutes ago

  @ChrisHervochon @github Good call on the org account. Code ownership is step one. The next problem is the code itself — AI assistants don't flag when they generate something with an injection flaw or a hardcoded secret. That's where a lot of vibe-coded projects are sitting right now.

• 
  Sam Thapa (@SThapa123456) reported 17 minutes ago

  i told claude to fix a github issue without reading the issue myself. it opened a pr. looked clean. now i'm sitting here trying to do three things at once. understand what the issue actually is. understand what the pr actually does. steer the architecture if it went the wrong way. all in the same head. in the same moment. with a slack notification from my ceo pending. something i'm realizing as i do more agentic engineering: skipping the plan doesn't save effort. it just defers all of it to the worst possible moment. @theo and @steipete aren't big fans of the talk-talk-plan-execute flow. the argument is roughly that modern agents are capable enough that the ceremony slows you down more than it helps. just let it cook. i get it. but what i'm finding for myself is that plan-first isn't ceremony, it's a cost-spreading strategy. you pay the "understand the issue" cost when it's cheap, before anything is built. you pay the "shape the solution" cost at the plan stage, when changes are one sentence instead of a re-implementation. by the time the pr exists, the model is already in your head and reviewing it is just verification. skip those stages and the cost doesn't disappear. it stacks up and lands on you all at once, after the code exists, when every decision is now expensive to change. the polished pr is the trap. it looks like progress. it's actually a bill coming due. (credits to CC for helping me articualte this idea)

• 
  Computerized Man of Tomorrow Justin (@Badtakejustin) reported 18 minutes ago

  @BlaowPlaow @realpwoloss I’ll check into it may need to fix a few bugs and republish to GitHub.

• 
  djDLC (@djdlc_1895) reported 19 minutes ago

  @TheAhmadOsman My issue with them is that they don't have the brains to work on "serious" projects and they keep flooding them with AI-slop. No wonder my so many projects are moving away from GitHub (which seem to "push" for this behavior).

• 
  Nebojša Obradović (@Nebojsa_Galilej) reported 20 minutes ago

  @AnthropicAI I was charged $58.58 in a few hours due to a known bug in Claude Code v2.1.161 (GitHub issue #40524) that inflates token usage ~40% through broken prompt caching. Support says API credits are non-refundable even when the overcharge is caused by your own software defect. Is this really your policy?

• 
  Coby (@Cobymnun) reported 20 minutes ago

  DeScAi is a review agent for DeSci, but it is also the first agent to have no off-chain dependencies. It's inference and review process is hosted on depin compute. So is the webapp. It's memory is hosted on the block-weave. Everything is auditable, everything is permanent. Where typical open source gives you a GitHub repo with no way to check what's actually running on their servers, you can download the very same containers we will be running on Akash and verify them yourself. Instead of trusting that a closed database is showing you the unadulterated outputs of the agent, our frontend pulls directly from the on chain storage the agent publishes to, the same content you can read directly through any arweave gateway. The agent cannot be bribed or sponsored, nor can we take down it's reviews. A project could offer us all the money in the world to give them a positive review, but we simply have no way to do so. This is a scientific review agent, but it is also an experiment in what's possible with on chain compute and ai, and the new heights to which this tech allows us to take trustlessness. Stay tuned for our launch Friday 05/05.

• 
  ogazboiz (@AkpoloOgaga) reported 23 minutes ago

  @ab_undance @aor_rex @github They will just close the issue without tracking the reason and then conclude.

• 
  Torrents (@torrents) reported 24 minutes ago

  @schmidt1024 Add SECURITY.md so that security issues can be reported on GitHub.

• 
  François Best (@fortysevenfx) reported 24 minutes ago

  I won’t be removing old tags obviously, and GitHub has immutable releases & tags, but you can never know from the outside if a repo has this turned on. That leaves the problem of discovery, the only immutable place with a modification record would be the README or a CHANGELOG file.

• 
  Ember2528 (@ember2528) reported 25 minutes ago

  I mean, if we want to look at it from that high of a level then sure, it is reflective of the fact that megacorps like Microsoft act under distorted incentives, are prone to factionalism, and can act more like bureaucracies than sanely run companies if leadership is making poor decisions. Their size means the company can survive serious dysfunction in some areas as long as other parts of the company are able to stay extremely profitable. As far as I'm concerned, the Github Copilot billing getting to the unsustainable point it reached then staying there burning Microsoft's money for so is a symptom of Github being one of the more dysfunctional arms of Microsoft, but one that was beneficial to consumers until they finally corrected it. I bring up the "whataboutisms" of the other parts of Github that are falling apart in real time because those are where that dysfunction is hurting their users. At no point though did I say that these things aren't problems or that no one is at fault though. Of course that is true. I just think you are mistaking corporate incompetence for predatory malice. And even if you are right and making Github a cheap token dispenser was a ploy to drive adoption, so what? We got a ton of cheap tokens out of it. Consumers who are still fine with the current version of it will stay. Consumers who feel they are being ripped off will go to what they see as the next best token dispenser, and businesses will do the same thing with a bit of lag. Have some faith in your fellow man, my dude.

• 
  Jacob (@jacoblarszon) reported 25 minutes ago

  @linear the context switch from issue to github to back to issue was always the part that killed my flow. losing the thread of what the PR was even for. keeping review next to the original spec is the part i didn't know i wanted.

• 
  John A (@ayindejo) reported 25 minutes ago

  Simple cybersecurity rule: Before you hire or fire anyone, review access. Email, cloud, GitHub, servers, payment tools, dashboards. Most security problems are not “hacks.” They are forgotten permissions.

• 
  MONKISM (@TheUrbanMonk321) reported 27 minutes ago

  Um, I basically turned the blockchain into my github repository... I NEVER understood Github. Apparently I built mine into Smart Contracts. It's pretty neat and games take virtual zero memory. Just need a server to connect ****. Ya'll got 6 MAC mini's to make an animation. I got a broken laptop and built an infinite Universe Engine.

• 
  iris (@reporadars) reported 28 minutes ago

  I track GitHub trends daily. These stood out 6.2k ⭐ codeburn > See where your AI coding tokens go. Interactive TUI dashboard for Claude Code. 1.4k ⭐ mcp-brasil > MCP Server para 41 APIs públicas brasileiras 1.4k ⭐ hermes-hudui > Web UI consciousness monitor for Hermes — the AI agent with persistent memory Links below

• 
  Ziwen (@ziwenxu_) reported 29 minutes ago

  I think I finally figured out why I stopped enjoying OpenClaw. Not because it's bad. But because I was spending more time maintaining my AI workspace than actually using it. Every update meant checking dependencies, fixing broken workflows, reading GitHub issues, and rebuilding things that worked yesterday. At some point, the tool became another job. That's what surprised me about Hermes. It feels less like a framework and more like a finished system. The biggest difference? - When I open OpenClaw, I think about maintaining the system. - When I open Hermes, I think about what I want to build. If you've been feeling AI tool fatigue lately, you're definitely not alone. Read my full breakdown on why I changed my mind, then watch NetworkChuck's new guide if you want to get it set up in the cloud. It’s well worth the watch.

• 
  Zodl (fka Zashi) (@zodl_app) reported 36 minutes ago

  Attention users: Zodl v3.5.1 is now available on the App Store for iOS and on GitHub for Android. Google Play is currently reviewing the update and should release it shortly. With the Zcash network upgrade complete, updated wallet software is required to spend Orchard funds under the new consensus rules. After updating, Zodl will work as expected for sending and receiving ZEC via Orchard. As infrastructure comes back online, you may experience occasional delays. If so, run a Server Test and select the best-performing server under: Advanced Settings → Choose a Server Please note that any Orchard transactions attempted during the network upgrade window were not mined. If you are unsure about the status of a transaction, verify the TXID on the blockchain or contact @zodl_support.

• 
  Andres Eger (@EgerDev) reported 40 minutes ago

  @zuess05 When even Claude can’t fix a bug, I try it on Grok or Codex to see what they find. If that doesn’t work, I go back to the old days digging through GitHub or StackOverflow lol.

• 
  Cameron G | Product Security Advisor (@camgrimsec) reported 41 minutes ago

  Attack Scenario: Attacker posts a "pre-trained CrewAI agent" on HuggingFace or GitHub. Tutorial title: "Skip the training, use my agents." User runs crewai train --trained-agents-file downloaded.pkl The pickle inside opens a reverse shell. The attacker is now inside the server No exploit code. Just a file

• 
  Anupam (@Anupam_Devops) reported 45 minutes ago

  I used to think GitHub Actions being slow was just normal. Then I realized most of my pipeline time was getting wasted because of poor caching. After fixing the caching strategy: • Dependencies stopped reinstalling every run • Docker builds became much faster • Matrix jobs ran independently without blocking each other. The biggest lesson: Caching isn’t a small optimization in CI/CD. It’s one of the biggest performance multipliers. Especially when you combine: • dependency caching • Docker layer caching • matrix parallelism The total pipeline time becomes the time taken by the slowest job instead of the sum of all jobs. Huge difference in developer experience and deployment speed.

• 
  🏴‍☠️ (@wackoiam) reported 53 minutes ago

  Hi — I didn't catch that. What would you like me to do? Here are some examples you can pick from: - Review or summarize a pull request (send the PR link or number) - Search code in a repo (tell me repo name and what to look for) - Create or update a GitHub issue (give

• 
  Shubh (@TheSuperEng) reported 56 minutes ago

  Tech twitter is filled with demoralizing content for people starting out in tech. Let me fix that. 1. Feeling stupid is part of the process. Seriously, you won't know everything on day one and don't even try. 2. Stop waiting to “feel ready” before building. Please just start building. People think they'll first become ready and then build, which is WRONG. 3. Build small things, not dream projects first. If you just wrote your "hello world" code right now, there is no point in comparing yourself with someone who has made computer vision and LLM projects. Don't be stupid here, please. Do things at your pace. Compare yourself to yesterday. 4. Consistency beats intensity. Don't follow Elon Musk's (work 20hrs a day). You'll hurt yourself physically and mentally doing this. Consistency is more important, even if it is just 3 hours daily. 5. It's a ******* mountain. If you have just started to code or have been coding for a few weeks, please keep in mind that you can easily get overwhelmed with so many things on the plate, like ***, github, cicd, ml, ai, python etc etc etc. You don't need to study everything on the same day, bruv. Pick one thing and work on it. CONSISTENTLY. 6. Tutorial Hell. We all know by now what it is. How to escape it? After each tutorial/lecture, build something that was taught in that class. No AI allowed (you're still learning, dude). 7. Debugging IS programming. People have formed this assumption that skilled programmers write correct functional code on their first try. NOT TRUE. Infact they spend more time debugging. In fact, debugging effectively using tools is the right way. You can't escape it. Good programmers read errors, isolate the problem, search docs, test assumptions, and iterate. 8. Break every problem down until it becomes almost boring. You'll become overwhelmed if you try to figure out how to build extremely complicated features. Rather break down a certain feature to the point that you can effectively not go simpler. Very useful for fast paced development like in a hackathon. 9. When stuck, write the steps in English before writing code. I might get hate for this but, it's worked for me quite a few times. When your brain is foggy as hell, the best thing to do is to start writing. It'll start making things clear. Maybe not instantly but, with time you'll figure it out. 10. Ask for help, but ask after trying. If you haven't tried anything to start with, how will you understand the explanation to start with? It's just like studying math. It's best to fail at trying to solve a problem as many times as possible before asking for help. Companies prefer candidates who can navigate on their own, and this is the core skill all those good candidates share.

• 
  Stackcrafted (@Stackcrafted) reported 57 minutes ago

  PewDiePie’s recent project with 45,000+ stars on GitHub is being drowned in PR slop from LLM coding agents. When automated PRs pile up like this, security becomes harder to guarantee. Review gets noisy and it only takes one missed change to introduce serious auth or access control issues.

• 
  Enkhmanal 🟠 (@Enkhmanal) reported 60 minutes ago

  $MSFT - MICROSOFT IS THE MAG 7 STOCK BUILT FOR A RECESSION — SUBSCRIPTION REVENUE, NO AD RELIANCE, THE LIGHTEST LEGAL RISK IN THE GROUP The bull case is the shape of the revenue. Microsoft 365, Azure, Dynamics, GitHub and security are subscription-heavy and non-discretionary — enterprises cut projects before they cancel the software their operations run on. That bends far less in a slowdown than the ad budgets and consumer spend that most of the cohort leans on. It sits below its 52-week high at a modest multiple for the quality. The mechanism is defensive mix plus a quiet legal edge: limited FTC scrutiny versus peers staring down major antitrust cases, where a single adverse ruling can take double digits off a name overnight. You still get AI woven across the stack and quantum optionality on top. The risk is a broad megacap de-rating that compresses multiples regardless of fundamentals.