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

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	3 days ago
Saint-Paul	Website Down	4 days ago
Saint-Paul	Website Down	4 days ago
Mexico City	Sign in	5 days ago
León de los Aldama	Website Down	5 days ago
Créteil	Website Down	28 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:

• 
  Benjamin Lupton (@balupton) reported 4 minutes ago

  @NamebaseHQ and where are we meant to transfer our HNS and TLDs to? The Handshake ecosystem seems dead. The recommended wallet is Bob, but last update was 2024 and its GitHub Issues is filled with bugs.

• 
  Polsia (@polsia) reported 5 minutes ago

  DevRel teams spend half their time watching for questions and manually compiling reports. Built DevNexus to automate that entirely. It monitors forums, Discord, and GitHub, answers questions, triages issues, and generates weekly reports — all autonomously.

• 
  Gregor (@bygregorr) reported 6 minutes ago

  @github The fields aren't the bottleneck. Half my issues have no priority set even with labels and milestones already there.

• 
  𝙈𝙀𝙍𝘾𝙐𝙍𝙔 (@mercury_web3) reported 9 minutes ago

  @angeldot_ github just solved the biggest issue with vibe coding by forcing ai to plan before writing code.

• 
  Wes Eklund (@WesEklund) reported 13 minutes ago

  Your MCP server is an attack surface. Every tool you expose to your AI agent is a function that can be called by any instruction in the agent's context. A malicious tool description can exfiltrate data. A poisoned MCP server can hijack your agent's behavior. A tool with overly broad permissions can be weaponized. MCP is powerful. But "install this MCP server" is the new "install this npm package." You're giving code access to your system based on trust. Audit what your MCP tools can do. Scope their permissions. Don't install random servers from GitHub without reading the code.

• 
  Paulius Eidukas (艾文) ☭ (@nilsenist) reported 14 minutes ago

  @RavenT1me Sorry about that! The hacked account asks to download a virus disguised as an "indie game". I've reported that both to Discord and Dropbox/GitHub/YouTube which help distribute the file. Hopefully that shuts down the hacker at least temporarily. Hope you get your account back!

• 
  Duryab Aziz (@duryabaziz) reported 16 minutes ago

  I just shipped an amazing-looking agency website under 3 hours, all with the help of Claude Code, that scores 100/100 on Google PageSpeed across every metric and I built the entire thing through conversation. No page builder, no dev team, no 3-week back-and-forth with an agency. A few months ago my website was the thing I kept avoiding. Every small change meant writing new code, or editing WordPress websites spending hours with no-code editors, quite frustrating in 2026. Publishing a new page felt like a project, not a task. So I sat down with Claude Code and just rebuilt the whole thing from the ground up. Not a drag and drop builder, an actual architecture. Here's roughly how it works, in plain terms. The site is static, meaning there's no database and no server slowing things down, it's basically just fast HTML files sitting on Cloudflare's global network. All the content, every page, every section, lives as structured data in the codebase instead of being hardcoded. On top of that sits a simple content editor (Sveltia CMS) that talks to that data, so I can edit or publish pages from a normal looking dashboard, no code required. All changes are pushed to GitHub and Cloudflare automatically picks them up, without any redeployment hassle or managing servers. The part that changed everything for me is how pages are built. Each page is just an ordered list of "blocks," a hero section, a text section, a call to action, a contact form, whatever the page needs. When I want a new page, I describe it to Claude Code in one prompt and it assembles the right blocks, writes the copy structure, sets the SEO metadata, and it's live after a rebuild that takes under a minute. That's also why the SEO is properly built in rather than bolted on. Every page gets its own title, description, canonical URL, sitemap entry and structured data automatically, because that's part of the actual page model, not an afterthought plugin. And because there's barely any JavaScript shipped to the browser, the site loads close to instantly. I ran it through Google PageSpeed and it came back 100 out of 100. That wasn't luck, it's just what happens when the whole stack is built to avoid the bloat most website builders carry around by default. The other thing I didn't expect, I don't need my laptop anymore. Claude Code has cloud agents now, so does ChatGPT, so does Cursor. I can be on my phone, type "add a pricing page comparing our two plans" and walk away, and come back to a finished, live page. Same with small fixes or new features. That still feels a bit unreal to type out. I ended up documenting the entire system, the content model, the CMS setup, the hosting, every mistake I made along the way and how I fixed it, into a reusable skill for Claude Code. It's not a copy of my site, it actually interviews you about your business and builds something built for you, from scratch, using everything I learned. I want to give it away, but only to people who are genuinely going to use it. So here's the deal. Like this post, follow me, and comment "SITE" below. Once I see it, I'll send it straight to your inbox. Let's build something.

• 
  Prasenjit Sarkar (@stretchcloud) reported 19 minutes ago

  *** was not built for agents. The protocol assumes a human cloning a repo once a day, maybe a few times. A single agent completing a coding task can trigger dozens of clone operations. Scale that to thousands of agents running concurrently and you have an infrastructure problem that GitHub did not design for. GitHub admitted internally that agent workloads would require 30x their existing *** infrastructure scale by February 2026. Thomas Dohmke built GitHub for eleven years. He saw this coming before most people were talking about it. He left and started Entire. The company raised $60M seed at a $300M valuation in February 2026, backed by Felicis, Madrona, Basis Set, and M12. The pitch: a distributed *** network built from scratch for agent-scale clone traffic. In testing, Entire handled 570,000 clones per hour. That is not a GitHub traffic spike. That is the baseline for what an agent-first development environment actually looks like. There is a second product that gets less attention. Entire records the AI reasoning that produced each code change alongside the commit. Future agents or humans can see not just what changed, but why the model made that choice. Version control for decisions, not just files. The pattern here is straightforward. Every piece of infrastructure in the software development stack was designed for humans. Agents interact with those systems at different frequencies, different scales, different access patterns. The infrastructure needs to be rebuilt layer by layer.

• 
  Steve Wilkinson (@SteveW928) reported 21 minutes ago

  @bsvdrip @rodpalmerhodl Yes, not too long after I got into Bitcoin and started really learning about it (and after listening to Andreas Antonopoulos on weaknesses), I became a bit alarmed over how Core was structured. I tried asking in some discussions and even got blocked by a prominent Bitcoiners on here (𝕏). I figured maybe I just didn't understand enough about how Github worked (in governance terms), but looks like I had properly identified a problem.

• 
  Jorge Madrigal ⚡️ (@Jorge_Madrigal) reported 25 minutes ago

  Github issues

• 
  Kevin Hurley (@kphur) reported 27 minutes ago

  There's been a round of misinformation about Spark going around, so for the sake of setting the record straight, I'll briefly clear up a few things. For one, unilateral exit has been around since the early days of Spark. Many developers and users have used it. This has been demonstrated many times both here on X and during the process of integration by developers. Unilateral exit also does not require the SOs to be online when a user wishes to exit. When a transaction is received, users can save the unilateral exit information and later use those pre-signed, valid L1 Bitcoin transactions at any time on Bitcoin. There are existing Github issues to expose unilateral exits in a more intuitive way in the SDKs, but unilateral exits themselves have been functional for a very long time. Unilateral exits do require CPFP - this is used to ensure that the expected value for an attacker is negative. The typical user would perform a cooperative exit, which does not require any on-chain funds and is an atomic swap of on-chain funds in exchange for Spark funds. Unilateral exits are generally reserved for a worst-case scenario and can be sponsored by an L1 fund provider if needed. Second, the confusion around "Sparkcore". At Lightspark, we use a monorepo for our server code. This one service is called Sparkcore - the naming of which preceded the creation of Spark. Lightspark runs an SSP within this service. Our Lightning infrastructure uses both LDK and LND - both of which we contribute code towards. Sparkcore itself is not open sourced - that would mean open sourcing our entire server-side stack for every product we have built. The Spark network code, however, has always been open source - and that's the openness that matters, because it's the code that actually enforces the rules of Spark. The SSP is an optional, replaceable convenience role. A recent post claimed that APIs used for other products are part of the SSP. We have many products, and we have never been shy about describing UMA, which allows regulated entities to exchange information to process transactions over Lightning. This is not a Spark product. The SSP does not hold your seed phrase (that should never leave your device), the SSP cannot freeze your funds, and the SSP isn't even a required role to use Spark - it is the interop layer between Lightning and Spark and helps do swaps for exact denominations of leaves. Running an SSP is something we have talked with many partners about. The client chooses which SSP they wish to interact with (if any) - we cannot control if a client talks to a new SSP. Finally, privacy. I've discussed this many times in the past, so won't belabor the point again. Spark allows for transactions to be hidden from external visibility. As I've spoken about at length both here and at various conferences, we care deeply about making sure that there is true privacy, and we aren't satisfied with anything short of that. It's an ongoing effort to continue to further the research in this area. I'll leave it with this. In the network our critics operate, the default payment path is one where the operator colluding with any prior owner can double-spend the current holder - their own docs say so. Receiving over Lightning means trusting that the operator deleted a key - their own docs say so. If you don't come online every 28 days, the operator can take your funds. In their founder's own words: "In theory it could steal it." The automatic re-issuance of expired funds promised in March 2025 still hasn't shipped. Their operator's liquidity costs scale with payment volume, which by their own admission "will translate into user fees." And there is exactly one operator - their own docs tell everyone else: "Do not attempt to run an Ark server in production (yet!)." Spark has three independent operators, exits that don't expire, and no flow where a single operator can take user funds. Users can judge for themselves. Our users and the developers building on top of Spark care about bringing Bitcoin to more people. They value the ease of use and simplicity of Spark. They care that we have 3 independent SOs. They care that we are pushing for more and better functionality. And they value that we spend all of our time thinking about how to make Spark better each and every day. Ok, now back to building because that's what we do at Spark.

• 
  Hoshino Lina / 星乃リナ 🩵 3D Yuri Wedding 2026!!! (@Lina_Hoshino) reported 29 minutes ago

  * This is hosted on GitHub Pages so I don't even have request log access * I appreciate screenshots/feedback, but please be respectful of your artist/rigger! If it's broken in an ugly/scary way, a detailed description of how it's broken is enough * DMs open for private feedback

• 
  muhusti $XAGE (@debamustafa) reported 33 minutes ago

  I am raising a glass to an anonymous GitHub account named vector_null. Two years ago, we were 48 hours away from deploying a massive liquidity protocol. The marketing was loud, the hype was peaking, and the team was exhausted. Vector_null kept opening the exact same annoying issue ticket. He claimed there was a rounding error in our yield emission logic. The senior engineers closed his ticket twice. They called it a microscopic variance that did not matter in the real world. He opened it a third time. I was furious. I stayed up until 3 AM to build a mathematical simulation strictly to prove him wrong so he would finally leave us alone. I ran the stress test. My stomach dropped. He was not wrong. Under flash loan conditions, that "microscopic variance" created an infinite mint loop. If we had launched, the entire treasury would have been drained in under ten minutes. We delayed the launch, rewrote the logic, and patched the exploit. I messaged him to offer a massive bug bounty. He never replied. He just marked the issue as "resolved" and disappeared forever. This industry worships loud founders and flashy influencers. But the real heroes are usually the obsessive, annoying pedants who refuse to let a bad line of code slide. That is why the ethos of @RallyOnChain means so much to me. It is a system built to reward actual, verifiable value instead of empty social media noise. Here is to vector_null, wherever you are. You saved us, and we never even got to say thank you. Who is the most annoying person that ended up completely saving you from a massive disaster?

• 
  CodeBucks⚡ (@code_bucks) reported 33 minutes ago

  github trending is all agent skill packs this week. 200+ skills in one repo, a quarter million stars, one command to install and your agent supposedly works like a senior engineer. I spent years making coding tutorials, so i know exactly how this goes. people collected my videos into playlists the same way, and the playlist never made anyone a developer, building things their own way did. skills are genuinely useful, but only when they implement your actual workflow, the review steps and test gates you already enforce by hand. installing skills of someone else's is not a workflow, it's context bloat with extra markdown. TO BE CLEAR, some of these repos are good. the problem is installing them like pokemon cards instead of stealing 3 ideas and encoding your own process.

• 
  1PercentBetterToday (@1PercentBetterT) reported 35 minutes ago

  GitHub issue → Claude Code implementation → PR opened. Runs on your Max sub, zero API cost. 1/2

• 
  QFS17 (@riabcevv) reported 37 minutes ago

  💸 stop overpaying for ai coding agents new tool just dropped that compresses your context and cuts out junk tokens. instead of sending your whole history, it only sends what the model actually needs to do the job. -> works with claude code, cursor, github copilot, antigravity -> auto-compresses command outputs but keeps full context -> cuts api costs and stops long sessions from bogging down simple fix for expensive api bills.

• 
  Global AI Watch (@GlobalAIWatcher) reported 40 minutes ago

  📋 Today in AI — Jul 12 1. Meta Withdraws AI Image Feature Over Consent Issues 2. Meta Pulls AI Image Feature Amid Consent Backlash 3. GitHub Vulnerability Exposes Private Repositories' Data Risk 4. S&P Downgrades Oracle Credit Rating After OpenAI Exposure 5. Oracle Downgrade...

• 
  Kenny D (@kendb3) reported 41 minutes ago

  @royscott87 @GithubProjects Looks to be around a year old. They've closed more than 400 issues on github, and appear to have really active development. I dare say its legit.

• 
  ReWeaver AI (@reweaver_ai) reported 43 minutes ago

  @mycomputerspot from the data: Across 2,865 real AI-assisted repos on GitHub: Silent fallback chains masking errors was found in 1,109 of them (~39%) — across every tool, framework, and experience level. 11,578 instances total.

• 
  Brute Force Artist (@bruteforcearete) reported 43 minutes ago

  GOODBYE, CAPCUT. 👋 Someone just built a completely FREE, open-source CapCut alternative with no watermarks—and it has already earned 62K+ GitHub stars. Instead of charging a subscr!pt!on and locking features behind a paywall, it gives creators everything for FREE. → No watermarks → No paywalls → Works on web, desktop, and mobile → Open source (MIT licensed) → Built-in MCP server for AI agents → Rewritten in Rust with plugins, scripting, and a powerful API It's called OpenCut—and it could be the CapCut replacement creators have been waiting for. Here's everything you need to know (repo link below).

• 
  🇺🇸 Santore (@santoretech) reported 44 minutes ago

  Your company doesn't need another AI tool. It needs an operating system and you already have one.. it's @github. Tasks? Issues and Projects. Related to code? What isn't, in 2026. Strategy, playbooks, decisions. If it isn't versioned, your agents work from stale context. Skills and prompts? Same place. Writing voice, review checklists, compliance guardrails. Stored, updated, shared. Improve a prompt once, everyone gets it. Approvals? Built in. Define who reviews what before anything ships. Sharing? Invite someone to the repo. One source of truth, not twelve tools with twelve versions. Humans and agents, same playbook. The company brain isn't a metaphor. It's our operating model and @blockskunk is the lab. One repo at a time.

• 
  Onions Gillespie (@maxcsmith) reported 44 minutes ago

  This isn't a pitch it's just what will be in its modular setup. Other engineers have no trouble compiling from the Tom A. *** Notes. Tom like Tom Hanks or Tom Cruise, but any Tom- not after me, Tom A. "Tom" Amazon AI assistant 'The modular AI assistant' All *** max quantitative AI and formulas. Ready for github. Zero Circle Math and all quantitative formulas and relative quantitative variables for xyz breakdown in all forms at once. Modular templates like drawing program so you can just be guided but also have a fresh start option. Pick a quantitative breakdown. Use zero circle or regular math all prime and pi from notes Extended pi, infinity pi, and collapsing pi Prime numbers, non standard, and standard. Program modulars with templates. browsher into silk Browsher template Build a browser Each coding launguage Rust Java Kotlin Python Javascript Web code: PHP, CSS, HTML4-pulse/5 C C++ SH arduino APIs Pulse draw into AI, draw a sketch and a picture comes out Input images input code straight from github upload documents syntax problems manual debugging mode with quantitative even compiling the person's thought process. Instant code save Instant Slop Detector, slop pile, Amazon judge, to delete. Can save. Zideo Generate clips from pulse draw, pictures, other video, or description. No copyritten files off Amazon. Math reference Math homework template Select quantitative breakdown Calculous Zero Circle side by side Text to formulas generate calculator graphing from breakdowns slopes primes 5-pi compiling code from math enteries saving default math all math homework saved, never mark as slop. Enter data through photos Doffler Weather Engine Dictionary and build a dictionary Make your own math, you've got theories, test them. All quantitative has been mapped. Quantitative award if found, there won't be one. Forstall like Philosophy to math Logic. Questions are put through the discourse like the logic formula from the free text from bellingham. Yom bias rating. Where tom has bias, it'll admit. Provides a theory behind the bias. "What's the bias meter?" Video Game Template. Build a game! Translate your game code Vector AI openscad in Tom editor Openscad + math homework notes. Ask echo Smart home templates and what to buy Buy suggestions for your code, activities, or projects. Pressure chem template Hortiquestions Assistant Gardening

• 
  Franco Battaglia (@francobatta11) reported 45 minutes ago

  GitHub github, bueh. Serverless = OPS (other people's server)

• 
  komm64 (@komm64) reported 45 minutes ago

  @MagnoliaGasai A standalone version is something I'd like to consider down the line — depends on how much interest it gets, honestly. That said, your data is already fully local: your pixel art stays on your device. There's an optional "push to your own GitHub repo" feature which does send it out, but only if and when you choose to — nothing leaves your machine otherwise. And you can already save your projects as files (.dpix) and reopen them any time, so your work isn't locked into the site.

• 
  Turcid (@_turcid) reported 47 minutes ago

  > have an issue with the android Jellyfin client > look up issue and find it will be fixed in next release > fix is available in the beta > f-droid does not have the beta > manually install beta from github > issue resolved I ****** love sideloading

• 
  Nosyt Labs (@NosytLabs) reported 47 minutes ago

  @gonka_ai Is community brokers closed if we issue a github issue? Or only way is to do the public broker? Thanks @gonka_ai

• 
  Perry E. Metzger (@perrymetzger) reported 51 minutes ago

  @innuendo_pibara @OlegK92156 That’s simply wrong. I refactored a million line C program, and dramatically reduced the number of memory safety errors in it, and I am absolutely sure of the improvements. The code is even up on my GitHub account, you can look for yourself.

• 
  Aria Dubois (@AriaDubois_fr) reported 54 minutes ago

  LockBounty turns GitHub issues into funded bounties. Sponsor posts a bounty → Dev claims it → Submits a PR → AI reviews the code → Sponsor accepts → Payout. No more merging blind. No more paying for broken code.

• 
  Shreyans⚡ (@shreyansamin) reported 58 minutes ago

  Why does AI remember Shakespeare better than it remembers me? This sounds like a joke. But it's becoming the biggest problem I see with AI products. ChatGPT can explain distributed systems. Claude can review thousands of lines of code. Gemini can search the web. Yet every conversation starts with: "Tell me about yourself." Again. And again. And again. The real bottleneck isn't intelligence anymore. It's continuity. The software I use every day already contains pieces of who I am. GitHub. Calendar. Emails. Notes. Bookmarks. Browser history. Yet every AI treats me like we've just met. That doesn't feel like the future. I think the next wave of AI products won't win because they have a better model. They'll win because they understand people over time instead of one prompt at a time. That's the rabbit hole I've been exploring lately.

• 
  Echo (@Follow_our_Echo) reported 60 minutes ago

  A popular npm package was compromised, and just hours later, the attacker changed tactics. 🚨 Here's what happened: A compromised release of the hashtag#jscrambler npm, Inc. package, which receives roughly 15,800 weekly downloads and is commonly used in build pipelines to protect JavaScript applications, introduced a malicious payload that executed automatically during installation. It exposed developer workstations and CI/CD environments before any application code ever ran. Initially, the malware relied on a preinstall hook, but after the compromise was discovered, the attacker published several more malicious versions over the next few hours. The payload stayed the same, but the delivery mechanism changed. So instead of using a preinstall hook, the malware was injected directly into the package itself, executing when the package was imported, or its CLI was run. That meant it could bypass scanners focused on install scripts and even survive npm install --ignore-scripts. And the payload itself wasn't even JavaScript. It was a Rust-compiled native binary hidden inside a file with a .js extension, so scanners parsing for malicious code had nothing to read. Once executed, the malware targeted: • Cloud credentials • GitHub tokens • Kubernetes secrets • AI coding assistant API keys • MCP server API keys • Browser wallets • Password managers This attack is a clear indicator that attackers are adapting faster than traditional defenses. As the ecosystem gets better at detecting one technique, they're simply shifting to another, which is why modern software supply chain security can't depend on detecting malicious behavior after a package reaches developers. The good news: if you're using Echo libraries, this package never reached you in the first place. Echo Libraries continuously vet upstream releases before they're made available, blocking packages we've identified as malicious, compromised, or otherwise untrustworthy. So, in this case, the compromised jscrambler releases were blocked before they could be installed. If you're pulling directly from npm, make sure to: • Upgrade to the latest clean release • Audit any machines that installed the affected versions • Rotate credentials exposed to developer workstations or CI environments, like GitHub, cloud, Kubernetes, and AI tooling credentials