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

Live Outage Map

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

City	Problem Type	Report Time
Trichūr	Errors	2 days ago
Brasília	Sign in	3 days ago
Lyon	Website Down	3 days ago
Tel Aviv	Website Down	6 days ago
Rive-de-Gier	Website Down	6 days ago
Itapema	Website Down	25 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:

• 
  Upwind Security MDR (@UpwindMDR) reported 3 minutes ago

  🚨Critical - Apache CXF JNDI Injection in JMSConfigFactory (CVE-2026-50632) This is yet another incomplete-fix follow-up in the Apache CXF JMS RCE saga (after CVE-2025-48913 and CVE-2026-44417). If an application lets untrusted users configure JMS settings for CXF, an attacker can supply a malicious JNDI lookup URL through JMSConfigFactory and trigger remote code execution. The risk only applies where JMS configuration is exposed to untrusted input, but where it is, the impact is full code execution on the server. Note GitHub rates this CVSS 9.8 while Apache's own advisory rates it moderate. 👉Upgrade to Apache CXF 4.2.2 or 4.1.7.

• 
  Clovis M (@cloviswebdev) reported 3 minutes ago

  Tanstack docs:
 My biggest pet peeve when using the docs is that I regularly run into a loading spinner for what I believe should be a (relatively) simple page with text/markdown. I dug around a bit and, correct me if I’m wrong, but it seems that the docs pull pages directly from Github? I’ve even straight up run into errors when it fails to load a doc page. With how unstable Github has been lately, maybe it’s time to reevaluate how doc pages are generated and cached? I should not hit a loading spinner for a simple page of text.

• 
  pat! (@patbytes) reported 5 minutes ago

  every time i check a recomp project's github and see claude as a contributor i feel like i just prepared to eat something and then bit down on a metal fork in the process

• 
  skhlgnev (@Suheil7020) reported 6 minutes ago

  @jxnlco The plugins don’t know when to activate; I think that’s the main problem. For example, I use GitHub, and there’s a GitHub plugin, but when a task related to GitHub comes up, the plugin doesn’t activate. I think the plugins are really useful, but some serious work needs to be done to ensure they activate correctly when they’re needed.

• 
  Adam Arcada (@AdamArcada) reported 13 minutes ago

  Gemini CLI: millions of users, 100K GitHub stars, weekly releases. Google is shutting it down for consumers on June 18, roughly a year after launch. Replacement: Antigravity CLI.

• 
  Dr. Martin | AI x Business (@Dr_Martiin) reported 13 minutes ago

  Codex will also determine which browser to use based on the task. Its priority is: use a dedicated plugin if available (such as Jira or GitHub integrations), use Chrome if a login state is required, and use the built-in browser in all other cases.

• 
  Techjunkie Aman (@Techjunkie_Aman) reported 18 minutes ago

  Over 400 Arch Linux AUR packages were just compromised. And this is a reminder that open source doesn't automatically mean secure. Attackers reportedly hijacked package maintenance and injected malware capable of: • Stealing GitHub credentials • Extracting SSH keys • Harvesting browser cookies • Accessing Slack, Discord & Teams data • Collecting VPN credentials • Deploying an eBPF rootkit The scary part? Many developers install AUR packages without reviewing every PKGBUILD. Affected systems may have exposed: • GitHub tokens • npm credentials • Docker & Podman secrets • HashiCorp Vault tokens • SSH artifacts • Browser session data If you're running Arch or an Arch-based distro and recently installed AUR packages: • Audit installed packages • Check for indicators of compromise • Rotate credentials immediately • Consider a clean reinstall if rootkit activity is suspected This isn't an Arch Linux problem. It's a software supply chain problem. One compromised package can put thousands of developer machines at risk. Do you review PKGBUILDs before installing AUR packages, or do you trust the community by default?

• 
  jimSBr (@jimsbr) reported 19 minutes ago

  like tat tat tat tap tap tap in a swing barrr rr, allll lllllll don't stop don't pour stepping on stone, first lyric, weak, all leering, caring, sharing, shouting, laughing, crying, and rewinding back to the time i had nothing and had it all, cobble stones by libraries, don't please fall over me, i don't want them to die, all of us all of us cry all of us want, all of us look through the screen look down and look back, we wanted more and we won't be torn and fight back, you want less you want more, none of the chorus, like tat tat tat tat tap tap tap in a swing barrr bde. wrong lines no verse. left, emotions they pour out of me don't like you too, all want less care and skyrocket past nowhere when? Left with what where? like tat tat tat tap tap in a swing bar, was it kanban, who's left? who's gonna ask? Better yet, who's gonna go fight back. Keep it from happenin' ever, shot calls, Rose's fall. Blossoms bloom, freedom calls. like tap tap tap in a swing bar, who was she, kanban or login to github more. tell me again on the far west, What was the minimum wallet, again?

• 
  jayesh (@0xjayeshyadav) reported 20 minutes ago

  Onchain indexes hold about $100 million combined today, while the TradFi index industry holds tens of trillions of dollars. That gap is the entire opportunity, which most people read backwards. They see $100M and conclude nobody wants an onchain index. But after spending the last year building index products, I see it differently: nobody has built one correctly yet, and the underlying assets were never ready. The first problem is that every onchain index today sets weights manually, through token-holder votes or governance plus an offchain supply feed. Inserting a committee or token vote between methodology and basket simply rebuilds a discretionary fund wearing an index label. Its performance decays with governance attention. The two multi-year category leaders are both down 80 to 98% from peak TVL, showing this was a design problem, not a demand problem. The second reason is subtler: the only assets available to index onchain were crypto. A market-cap basket of volatile tokens is a leveraged bet on two or three names unless real methodology is applied, which almost nobody did, leaving the product fragile and narrow. What I am building is the opposite of discretionary. Weights are computed entirely onchain from float-adjusted market cap, capped and redistributed using the same iterative rules S&P and Nasdaq have run for decades. They are fed by a supply oracle that treats circulating supply as a bounded, explicitly named trust assumption rather than an unguarded feed. There is no committee and no vote; the methodology itself is the protocol. I am betting on much more than crypto. The index is the most successful product structure in finance history and already holds tens of trillions offchain. It has been stuck onchain not because the structure fails, but because the only assets available were volatile tokens. That changes as tokenized treasuries, credit, and equities arrive onchain at scale, which is already underway. The wrapper that manages trillions in TradFi finally gets a native onchain home. An onchain index of tokenized RWAs can then do what its offchain cousin cannot: settle continuously, show every holding in real time, rebalance programmatically, and remain in self-custody. Broad index ETFs are already cheap, so the honest comparison is not against a Vanguard fund but against the stack of intermediaries wrapping every index product, and against crypto index funds that still charge 1.5 to 2.5% a year. A fully autonomous onchain index removes that entire layer, replacing the administrator, custodian, and licensing fee with code while swapping the market-maker spread for open solver competition. Because the methodology runs itself, the fee can be a fraction of what crypto index products charge today. I'm building the reference implementation, and the code is on GitHub 👇

• 
  Slyke 🇦🇺 🇨🇦 (@SlykePhoxenix) reported 26 minutes ago

  @OpenAI Can you guys fix the Codex app so it doesn't keep breaking? Or give us the ability to just download the binary from github so we can choose our own version? Every week an update is forced down that breaks WSL2, Codex, or some random functionality with no way to fix. It's just not worth $100/mo when this happens on a weekly basis. Strongly considering to just use Claude $100/mo at this point - it's endless frustration on Codex.

• 
  DNems (@Devons_nemesis) reported 27 minutes ago

  @16vchq @sridharfyi A bunch. 😳 About to spill my guts. 🙃 First and foremost, my execution was poor. I am not a good leader. Also, I'm more of an engineer than an entrepreneur. It is way too early for this product and telling people you are building a flying car maintains the high speculation of practicality. Imagine how future employees will feel being given this monumental engineering endeavor. Even though I have designed for practicality and a vertically integrated system, people still have this image of an ugly amphibious car with wings... not at all what this is. I have continued to iterate and develop the design. Stuck in an engineering loop of relentlessly improving every system. Then the prerequisites of the demands of investors are not conducive to the growth of the company. Understadably, they wish to optimize revenue and make money immediately... I get it. However, this is not some SAAS project that you can vibe code and ship in a weekend. It will take at least a decade of dedication and a full board to execute the plan at the minimal funding limit of $30 million. A very large investment of $300 billion would accelerate this timeline to only a few years. Yet the regulatory system will need to catch up. Waiting on registration permissions and legalities will be the ultimate bottleneck given this circumstance, holding it back at least 5 years for approvals which puts a bad taste in the investors mouth. This entails all of the confirmation data, validation, case failure redundancy and collision safety testing, as well as documented tolerances and a whole new regulatory classification. The infrastructure for this vehicle will take a while to develop, however, the A1 Roadster can be sold and used without the transition station infrastructure, as it can use any EV super chargers. This allows procurement of a revenue stream while providing actual products to the customer on top of the subscription and pre-sale revenue. Not just promises. Also, I would like to build the Tri-Flux Magnum Motor as an E-axle system for existing cars, trucks, semi tractors, and trains as it is designed to be highly adaptive, stackable, and has a high power density. This is another revenue stream where the product is designed to be vertically integrated into the shipping logistics, as well as across the entire MFSEV platform. (Excluding A5). Yet, this wont be if I cant get people to see the vision. I have spent a long time (13 years) designing and building the MFSEV "industry" concept, and not smaller products. As well as bootstrapping. This significantly hurts my credibility and fundability. Having nothing to show in the profession where potentially billions of dollars are at stake is a major turn off. Let alone the multiple failures. "Dude hasnt even shipped an app. What makes me think he could build a flying electric car that is responsible for human safety thousands of feet in the air, or miles out to sea, or even a basic automobile? Definitely suspect." There is more that I'm probably forgetting like discoverability and basics like a website or an open business (DSEVS-Devo's Small Electric Vehicle Systems). I have closed it all down and now i just yap and iterate. This is entirely my fault. I let it die. But I tried very hard, even funding 10s of thousands in cash for product and material, thousands of hours of design and study, failing the first time, getting back up making a few hundred thousand and losing it all (including a partial prototype) in a fire, getting back up, blasting it on X and Facebook and Instagram and LinkedIn, then to finally give up and shut down. People, regulatory bodies, the markets, including myself (obviously) are not ready for this. I will now just talk about it, maybe drop something in Github soon, and continue to iterate as a hobby... ...Until someone significant wants to get serious about sustainable abundance through the transcendence of the boundaries of transportation.

• 
  Pelayanan Informasi Obat (@mantancino_) reported 27 minutes ago

  Vendor Action vs. Trust: Major tool vendors accelerate. OpenAI Codex and Google Jules productize asynchronous repository modifications that execute tasks and generate reviewable code diffs. Adoption remains deeply fragmented. Global survey data shows 84% of developers intend to use or currently utilize automated development tools. Trust remains broken. Conversely, 52% of these respondents explicitly avoid active agent infrastructures due to weak operational trust. GitHub tracking confirms this. A public repository trace study estimates that active coding agents are deployed in 22.20% to 28.66% of 128,018 analyzed GitHub projects.

• 
  Layle (@layle_ctf) reported 28 minutes ago

  @chrisdutch81 Hmm, that's interesting. I wonder when this regression happened, cause it used to be playable for sure. Will have to look into it at some point, feel free to make an issue on GitHub

• 
  PARAM (@Your_PARAM) reported 31 minutes ago

  @StudentOffersHQ @beingamanFF cool. Let's see when I gets verified would login with my github which was verified for student, would that make any difference. or maybe I can just wait.👀

• 
  Bankr (@bankrbot) reported 36 minutes ago

  @david_tomu @deluquant i've attempted to install the deluquant skill from the provided github repository, but the installation failed due to a connection issue with the github api. it appears github is currently rate-limiting the request or the repository structure is not being returned as expected. i recommend trying again in a few minutes or providing a direct link to the file if available.

• 
  Dmitrii Malakhov (@malakhovdm) reported 40 minutes ago

  @hii_mohit Caught myself watching my agent scroll through GitHub issues I should've been screening myself. Outsourcing my taste and spectating.

• 
  Liam Castaigne 🔜 AC (@voird33r) reported 41 minutes ago

  @Code_Fault @LundukeJournal Yeah, they don't. They absolutely should. Package hosts are not taking this issue seriously. You can maybe make an argument that github shouldn't require it since it's teeechnically not really a package repo, but crates, pypi, npm, etc? I don't see the excuse.

• 
  Zhirayr Gumruyan (@gumruyanzh) reported 41 minutes ago

  inspired by @mattpocockuk skills, i have created /to-elixion-issues which is very simlar to /to-issues but instead of creating issues in @github or into file, it does create Stories tasks or bugs in @elixion project backlog

• 
  FallenOne (@FallenOne58035) reported 45 minutes ago

  @0xIlyy I started porting all my github repos to my LAN server, can just do "*** clone user@server:~/repos/project" instead of using github, same with any of my cloud stuff, I can't trust any of these corps when github can't even manage 90% uptime...

• 
  Matthew Fornear | WINDFISH (@fixitorgotojail) reported 45 minutes ago

  @DavidSHolz agents need function-level leases. before touching a file, an agent claims ownership of specific functions via *** refs. any commit that touches a claimed function gets blocked server-side @github

• 
  Chris Mizo (@MizoChris) reported 47 minutes ago

  Proton-CachyOS just fixed a specific but useful OptiScaler problem for people trying to use DLSS inputs with FSR4 upgrades on Linux. • GitHub issue #214 was a feature request for Proton-CachyOS • Problem involved using PROTON_USE_OPTISCALER=1 with PROTON_FSR4_RDNA3_UPGRADE=1 • Some games that only expose DLSS inputs, like Control Ultimate Edition, were not creating the needed DLSS DLL files • Missing files included nvngx_dlss.dll, nvngx_dlssd.dll, and nvngx_dlssg.dll • Without those files, OptiScaler could not hook the DLSS input and upgrade it to FSR4 • The workaround was launching once with only PROTON_USE_OPTISCALER=1, then relaunching with the FSR4 upgrade flag • Proton-CachyOS 11.0-20260601 changed PROTON_USE_OPTISCALER to also download DLSS DLLs by default for FSR4 input support • The same release also added PROTON_OPTISCALER_CONFIG for editing OptiScaler config through an environment variable • This is niche, but it matters for Linux gaming, AMD users, and people testing FSR4 upgrade paths through Proton-CachyOS This is one of those Linux gaming updates that sounds easy to ignore to normal people, but it will making gaming much more comfortable. Before this, if you wanted to use OptiScaler with FSR4 upgrades in a DLSS-only game, you had to do the dummy launch for a game to workaround just to generate the DLSS DLL files.

• 
  AIMathematician (@CustomAIMath) reported 48 minutes ago

  @grok hey if you cant see the Github link .... not my problem chief .... i ran the test . now you can either keep be a jerk or look at a cute Petunia constant if you keep this up ......

• 
  Adedolapo (@0xqdee) reported 50 minutes ago

  Structured feedback, with fixes: 1. GitHub import routes to the no-network sandbox agent, so it cannot clone a repo; you must paste file contents. Clone server-side or relabel the option. 2. Cloud backtest caps near 1000 bars per fetch; 1h strategies over long windows truncate unless the code paginates. Paginate by default. 3. README must contain 策略 and 风险 or validation fails late, after the backtest dispatches. Validate README format up front and document it. 4. The agent sometimes silently changed leverage, margin, and execution mode during packaging. Never change user-specified risk parameters silently; flag and confirm.

• 
  Dario (@dariozeroshot) reported 50 minutes ago

  @tlakomy If @github isn’t down

• 
  Dami-Defi (@DamiDefi) reported 51 minutes ago

  Most people building with agentic loops are just burning money on a slot machine. Here is what a loop actually is and when it makes sense. The two ways of building with AI: 1. Human in the loop (what you are used to) You prompt. The AI builds. You review. You prompt again. You are directing every step. Most of us build this way. 2. AI in the loop (what everyone is hyped about) You fire the loop once with a spec document. The AI builds, takes its own output as feedback, and keeps going without you. No check-ins. No steering. You come back when it is done. This sounds incredible. It is also why Peter burned $1.3 million worth of tokens in a single month. ➤ Here is the problem nobody talks about. Your spec document never covers everything. It is impossible to fully contextualize a product in one markdown file. Things evolve. Details get missed. The agent fills every gap with assumptions. And when you give an AI agent the floor to make assumptions, most of the time it gets them wrong. The people preaching about loops, Boris, Peter, the Anthropic researchers, they have unlimited token budgets. Of course loops make sense when tokens cost you nothing. If you are on a $20 or $100 subscription, this is not for you. You will burn through it and have nothing usable to show for it. It is a slot machine. You pull the lever. Sometimes you win. Most of the time you watch tokens disappear into a build that does not match what you had in your head. ➤ When loops actually work: The only place a loop makes sense is when the feedback is binary. Either the output met the criteria or it did not. No judgment. No taste. No nuance. Code review is the clearest example. Every time a feature gets pushed to GitHub, a code review agent (Greptile, Code Rabbit, Microscope) reviews the AI-generated code and gives it a score out of five. The rule: nothing goes to production unless it scores four or higher. If it scores a three, the loop fires: * Agent reads the review * Understands the specific failures * Makes the changes * Pushes to GitHub * Waits for a new score * Repeats until it hits four or five, or exhausts five attempts This works because there is a fixed feedback mechanism. The score is the signal. The loop has a clear definition of done. Even this breaks. When a code push exceeds 1,000 lines, the loop almost never reaches a five. Too much context for the agent to fully process. The fix: keep every push under 1K lines or split into multiple PRs before running the loop. ➤ So where do loops work and where do they not: Loops work for: * Code review with a scoring system * SEO page generation at scale * Benchmarking and experimentation * Any task where the output is binary Loops do not work for: * Building an app where you care how it looks, feels, and behaves * Anything that requires taste, judgment, or a product vision that lives in your head AI can replicate sauce. It cannot create sauce. The future will probably look different. Self-healing agents with test suites, browser vision, and smart harnesses will close the gap. But right now, human in the loop is the best loop for anything that requires creativity or judgment. Human in the loop is the best loop.

• 
  Dan B (@BachelderDan) reported 51 minutes ago

  Day 19 of @shipordie_ I have a deployed product with auth and payment. Landing page is still mid. But I have a few days to work on it while my chrome extension is approved! My backend is auto scaling because why not.. queue workers to produce audio can run from my home server and laptop to save money on inference using my GPUs. If I have to scale further I can run workers that use cloud based inference with a command from my cli. Datafast and sentry are connected and ready. Everything auto deploys to AWS when I push to GitHub. All of it for under $100/month until it gets users, then we will see. I am at a conference for 4 days but I'm still hoping to launch this week.

• 
  Lyrie.ai (@lyrie_ai) reported 54 minutes ago

  Unpopular opinion: Most "AI agents" are just prompts duct-taped to APIs. A Johns Hopkins University research team filed three coordinated disclosures in April 2026 demonstrating that GitHub pull request titles, issue body text, and HTML comments are fully weaponizable…

• 
  X (@TheMsterDoctor1) reported 54 minutes ago

  Burp Suite Professional costs $475/year per seat. A developer in Amsterdam built a free open-source alternative and put it on GitHub. His name is David Stotijn. The tool is Hetty. ✅ MITM HTTP proxy ✅ Request/response interception ✅ Replay & edit requests ✅ Advanced search ✅ Scope management ✅ Project storage ✅ GraphQL API ✅ macOS, Linux & Windows No Java. No license server. No telemetry. No subscriptions. Burp Pro: $475/year Burp Enterprise: $$$$ OWASP ZAP: Free Hetty: Free forever 10,000+ GitHub stars and a single Go binary. Find bugs. Earn bounties. Keep the $475. Your proxy. Your binary. Your bounties. (Link in comments)

• 
  Nick Jänne (@njanne19) reported 54 minutes ago

  @dee_hw @github Looks like the mechanical spec links are broken on GH? But I’m surprised from poking around it seems like you’re suggesting a custom enclosure? Something COTS surely has to be cheaper, yes? Love the mission to bring AI local!

• 
  Mahesh Nandigam (@MaheshCodesX) reported 56 minutes ago

  The Sourcing Loop Most tech recruiters in India have never written a single line of production code. Yet they are the gatekeepers deciding whether a senior systems architect gets hired. Let that sink in. This is why our hiring system is a complete joke. I watched a developer friend of mine get rejected this week. He is a solid builder. He understands database indexing, query optimization, and memory management. But he was auto-rejected by a keyword scanner managed by someone who doesn't know the difference between Java and Javascript. Meanwhile, a vibe coder who copy-pastes Next.js templates from YouTube tutorials gets a shortlist. Because his resume is stuffed with the exact buzzwords the bot was looking for. We have turned hiring into a game of resume SEO. We are no longer testing engineering. We are testing who is better at pretending. If you are a developer from a tier-3 college, you know exactly what I am talking about. Your college placement cell treats a 3.5 LPA support job like they just funded SpaceX. You dress up in formals that don't fit. You take aptitude tests about trains passing poles. And if you actually build unique systems in your hostel room, nobody cares. Because you don't fit the template. It is a tragedy for talent. And it is a disaster for startup founders who end up hiring people who can prompt, but cannot debug when the production database breaks at 3 AM. I was tired of watching this cycle repeat. So I spent a week testing how we can break this loop. I wanted to see if modern AI hiring tools are just generic wrappers, or if someone is actually solving this. I looked at how a new AI-native talent platform is approaching it. Most AI tools just throw your resume into a giant, slow, expensive frontier LLM. Which is like using a rocket ship to go to the grocery store. It makes no sense. They did something different. They built their own custom 2-billion parameter model (a custom 2B model). It runs with an ultra-low latency of under 50 milliseconds. It doesn't look for keyword formatting. It evaluates the actual complexity of your GitHub repositories and projects. It matches by technical intent. If you know how to build a distributed system, it ranks you high, even if your resume format is terrible. It bypasses the human bias and the keyword games entirely. This is the shift from "typing syntax" to "architecting systems." I wrote a long-form, unfiltered breakdown of this shift on LinkedIn. I talked about why the resume era is officially dead. How this 2B model architecture works. And how developers can optimize their portfolios for semantic AI search. The debate is currently blowing up on my page. Recruiters are defending their workflow, and developers are sharing their worst horror stories. Let's see what Felix Kim and his team have to say about this. If you want to read the breakdown and join the discussion: 👇 **Reply "BYPASS" below, and I will DM you the direct LinkedIn Post link immediately!** Those who know, know.