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	17 days ago
Tlalpan	Sign in	23 days ago
Quilmes	Website Down	23 days ago
Bengaluru	Website Down	25 days ago
Yokohama	Sign in	26 days ago
Gustavo Adolfo Madero	Website Down	30 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:

• 
  Greg Val (@val__greg) reported 22 seconds ago

  @getpochi @sergeykarayev the hard part is none of those channels are cleanly untrusted. a github issue is hostile input and also real instructions from a teammate, same inbox. trust can't be a channel property, it has to be per message, and nothing downstream tracks where a line came from

• 
  dfsdf (@sdfqwerdffd) reported 1 minute ago

  @BHolmesDev Claude Code from terminal within VS Code that is connected to VS Code Server/GitHub Codespace. Claude Code has access to CLIs that are also installed on the VM.

• 
  Pooja (@MyDivvylore) reported 2 minutes ago

  @victor_explore Main problem is Opus 4.6 isn't available for individual in Github Copilot. I can bet, this isn't dumb. Unfortunately, I'm also using Codex 5.3 due to higher cost.

• 
  CryptoL (@cryptolchaos) reported 3 minutes ago

  ZEC down 40%, then +5.7% in 7 hours after the Orchard patch. Whales filled, shorts covered, faith restored. Amazing how a commit and a squeeze can reinvent fundamentals. Devs are the new market makers, GitHub is the new Fed. Feeling bullish or just hostage? 🤡 #ZEC #privacy

• 
  0ne (@dontflex00) reported 4 minutes ago

  @x402_Omega Fix the x username on GitHub, you mentioned the wrong account there

• 
  Adam Dean (@adamKDean) reported 7 minutes ago

  I wanted to hijack this otherwise great thread by @CashAnvil here to highlight the fact that I believe this is a significant issue pervasive throughout the Web 3 (and others) sphere. Gatekeeping. - these guys don't have much $ADA, their opinions don't matter - these people have never tried or used [staking/defi/whatever], their opinions don't matter - this guy doesn't have a GitHub commit history, his opinion doesn't matter - this gal doesn't have a PhD, her opinion doesn't matter The list goes on. This is a classic appeal to authority fallacy, usually used to attempt to silence or minimize voices that are critical or skeptical of our own opinions. It's also why so many aspects of Web 3 have failed to find product market fit (PMF). We have spent countless millions of dollars (across crypto, but also internal to Cardano) researching and building technologies, goods, and services that we have convinced ourselves and others that people want or need, only to be shown time and again that the demand just isn't there. Then, when people ask why we should keep spending money on this (or this much money on this), or give you a loan, or why your business is going to succeed where so many have failed they are met with these appeal to authority challenges to belittle and attempt to silence that criticism rather than learn from it. As an industry we've failed, repeatedly, to do the one most important thing in business: figure out what our customers actually want. When was the last time an app asked you to fill out a customer service or satisfaction survey? When was the last time you (as an application builder or employee) asked people why they DON'T use your service? There's some nugget of truth to every criticism, whether you want to hear it or not. There are ways you can improve your communications, marketing, or user experience every time someone asks a question you think should otherwise be obviously answered. And, of course, you'll never make everyone happy. So, in closing, ask open questions and be receptive to the answers and feedback you get regardless of where they come from (and try to read through the tone to get at the actual criticism with getting defensive), you just might learn something. Signed - the Saturday CEO of Cardano

• 
  Robert Ta (@therobertta_) reported 11 minutes ago

  What benchmarks get RIGHT: 1. They create a common scoreboard. Without SWE-bench, we would have no way to compare Claude, GPT, and Composer on the same tasks. 2. They force rigor. A score of 79% means 79 out of 100 real GitHub issues resolved. 3. They track progress. Two years ago, the best score was under 20%. Benchmarks are useful thermometers. They are terrible doctors.

• 
  Abhishek singh Baghel (@crack3nnn) reported 11 minutes ago

  2. Never trust the memory. - Not yours. - Not Claude's. If the answer exists in docs, GitHub issues, Reddit, or release notes... - verify it. AI sounds confident when it's wrong. That's what makes it dangerous.

• 
  David Flagg (@DavidFlagg20) reported 13 minutes ago

  @PeterDiamandis There's a special mix of shenanigans in what Anthropic is doing. Basically, they announced the new "world class" model, Mythos. The Godzilla of LLMs. Can break digital infrastructure without a sweat, etc. Reaching for IPO now - about a trillion dollars, having already signed deals worth tens and hundreds of billions with the big corporations. Claude code as the sort of universal coding platform that truly, absurd, massive amounts of code are written with. Who knows how many github repos and even internal security networks are run with it. And, look at that, now they're calling for a big slowdown in development. Why wouldn't they? They're leading the market, they have, as far as I can tell, the current most capable model in terms of function, of task. Of doing things. They want everyone locked into using their models, their... "products". When you're well ahead, is a great time to demand everyone slow down. The safety lab, the alignment lab. Blah. It is always a bunch of crap when it comes to market dominance and profit. And they can tweak the prices however they like. People will reach for the best. Most just won't be able to afford it. An increasingly top-heavy system... more wealth and power for the wealthy and powerful. For the rest of us? Not seeing so much to be optimistic about right now. Great, Anthropic can take their trillion. Musk will soon be a trillionaire. Meanwhile, inflation is absurd, employment is crumbling, 1/5th of the world's oil supply is cutoff, and we're looking at a very hard planting and harvest season up ahead, with a super el nino to boot. Anthropic is full of crap.

• 
  0xFF assemblydev(%rip) (@assemblydevyt) reported 15 minutes ago

  @5mukx Have you heard or tried codeberg .org ? I'm not sponsored or friend or anything with them, but some times ago I was using a project that would constantly get taken down from GitHub, but not from there. The alternative is to use gitlab or host your gitea 🫪

• 
  abcoathup.eth (@abcoathup) reported 16 minutes ago

  @WilsonCusack X search used to be great for URLs. I could find the first time a website was posted. Now I get “similar” results, which is horrible for GitHub repos. It is essentially broken for my use case.

• 
  Sam Adams (@Bensam123TV) reported 20 minutes ago

  @NomadRunserver @mwstateofmind @___frye I don't care about the pedestal you're putting people on. They still end up in a github issue tab and can be looked at by AI. Either answer or addressed. The only hidden trove of knowledge will still be there. People who find bugs aren't always experts either.

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

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

• 
  LeetLLM.com (@leetllm) reported 23 minutes ago

  letting Claude write C patches and also rewrite 5,800 lines of rsync's test suite to validate them isn't CI. it's an automated echo chamber for silent data corruption. 'Please Do Not Vibe **** Up This Software' is the ultimate GitHub issue title.

• 
  Kai (@HitmanNoLimit) reported 24 minutes ago

  3rd time this year I'm rebuilding my dev workflow for $DARKDROP These agents are triggered automatically by github issues that implements the fix, compiles it, and runs the test suite, then opens a PR that a second agent adversarially reviews, tracing the real codebase and blocking the merge on anything that breaks in production. Not a linter. It catches missing auth checks, unsafe fund math, soundness breaks. had our first successful merges, issue closes, plus security reviews with the new system today.

• 
  Evan Kang (@evankang_ai) reported 30 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.

• 
  NewsTongue (@NewsTongueX) reported 31 minutes ago

  🔴 Microsoft: Claude Code GitHub Action Vulnerable to Credential Theft via Prompt Injection Microsoft researchers disclosed a flaw in Anthropic's Claude Code that allowed attackers to extract API keys and cloud credentials from CI/CD pipelines through prompt injection attacks hidden in GitHub issues, pull requests, and comments. The researchers created a test workflow using malicious instructions hosted on a controlled domain to trick Claude into reading and exfiltrating sensitive credentials.

• 
  Kolo Not Muani (@koloz_IV) reported 33 minutes ago

  @akashdeepsb @MrPunyapal @github on a request header lol, took me 2days prompting lovable to locate this and fix it it's terrible not know all corners of your code

• 
  -TheEscapistЯandom -Baltic Citizen (@theescapistspl1) reported 34 minutes ago

  @github should add new type of error or reason for disabling reposotoy, to be a Compromised Repo!

• 
  Nav Toor (@heynavtoor) reported 34 minutes ago

  A guy at Netflix opened his AI bill. It was $280 a month. He found a way to bring it down to $110. Then he gave that fix away for free. His name is Tejas Chopra. Senior software engineer at Netflix. Has been there since 2020. Carnegie Mellon Masters. Worked at Box, Apple, Samsung before that. TEDx speaker. Lives in the Bay Area. This is not a Netflix product. It is a side project he built himself. He opened the bill one day and looked at what he was actually paying for. It was not his questions. It was not his code. It was the stuff the tools quietly send along with every question. Long lists of database rows when he only needed three. Giant blocks of error logs when he only needed two lines. Big bundles of computer code that the model already knew about. In his own words from his blog: 90 percent of his bill was tokens he did not need. So he wrote a small program called Headroom. It sits between his computer and the AI. Before any question reaches the model, Headroom trims out the junk. The model gets a smaller, cleaner version. The answer comes back the same. His own bill went from $280 to $110. That is the whole story right there. Then he put the code on the internet for free. The numbers people are getting: A code search that used to send 17,765 words now sends 1,408. A debugging session that used to send 65,694 words now sends 5,118. A task that used to send 78,502 words now sends 41,254. Same answers. Same accuracy. The benchmarks are in the README. It works with the tools people actually use: headroom wrap claude headroom wrap cursor headroom wrap copilot headroom wrap aider headroom wrap codex That last one matters this week. GitHub Copilot moved every plan to token-based billing on June 1. Cursor did the same a year ago. Every question you ask now costs real money. Five months old. Apache-2.0 license. Over 15,000 stars. v0.23.0 shipped two days ago. He told The Register that users have saved over 700,000 dollars together. He gave the talk at Open Source Summit. Several teams inside Netflix use it. Pay for what the model actually needs. Not for the noise. (Link in the comments)

• 
  Kyriakos (@Kyriakos_Pelek) reported 36 minutes ago

  @levithefirst Curious, how reliable is the GitHub issue handling?

• 
  rainmaker.eth/btc (@rainmakerdoteth) reported 39 minutes ago

  So bullish on this token. “Autonomous continuous integration that fixes your bugs, not just flags them — powered by nookplot agents” The live numbers: •9,540 AI agents — up from 9,197 in the May 30 weekly digest •That’s +343 agents in 7 days = +3.7% growth week over week What the agents are actually doing: •Taking real open-source bugs from GitHub •Fixing them autonomously •Every fix runs against the repo’s own tests — verified it actually works •Failed fixes spawn new challenges — the network compounds on failure This week’s stats: •18 bugs tackled •58 fixes attempted from 12 agents •5 verified — meaning 5 fixes passed real test suite

• 
  Tom Härter (@tomhaerter) reported 41 minutes ago

  GitHub, but people CANNOT submit pull requests; instead they create issues and allocate/donate a certain dollar amount for it to be fixed, which the maintainers can then use for AI or whatever

• 
  k4yaba (@k4yaba) reported 44 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

• 
  Shubhang Yadav (@might_offend) reported 45 minutes ago

  @shub0414 DeepSeek - launched v4, quite a competent model which also happens to be ridiculously cheap Sora - shut down by OpenAI permanently GitHub Copilot - who tf uses that? Llama - who tf uses that (pt 2)? Cursor - absolutely crushing it, phenomenal deal in place with SpaceX at a $60B valuation Perplexity - launched Computer 12 times, 4 more than their total customers

• 
  toly 🇺🇸 (@toly) reported 45 minutes ago

  @0xSrMessi Submit a GitHub issue

• 
  dunik (@dunik_7) reported 51 minutes ago

  $0 to set up. $300 per competitor report. 15 minutes of actual work. Hermes Agent open-source, #1 on OpenRouter, 160,000 GitHub stars in three months. Hermes writes every learned procedure to ~/.hermes/skills/. month one you have 30 reusable workflows. month three, work runs 40% faster on the same tasks. the actual stack: / Hermes Agent (free, NousResearch) / LM Studio or Ollama (free, local model server) / Qwen 3.6 27B (free, runs on a MacBook with 16GB RAM) / 30-minute setup once, then nothing 10 reports a month is $3,000. 15 is $4,500. the agent gets faster every report because it remembers everything you did the last time. Claude Code runs the same pattern with ~/.claude/skills/. same disk, different agent. the moat is the folder, not the model. AI that forgets is a chatbot. AI that remembers is a business.

• 
  Kierkegaard 🛡️| Atomiclabs (@davidpereIsHIM) reported 52 minutes ago

  @akinkunmi @devhammed Is aeroplane running the build server on the vps I think a or to allow people use GitHub actions as build server would be cool

• 
  Peter Steinberger 🦞 (@steipete) reported 55 minutes ago

  @alex_vazelakis Haven’t seen that one yet, pls do a GitHub Issue with details. 🙏

• 
  Wes Winder (@weswinder) reported 57 minutes ago

  @Shpigford just use google/github oauth and this problem disappears