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 (71%)
• Sign in (21%)
• Errors (8%)

Live Outage Map

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

City	Problem Type	Report Time
Le Chambon-Feugerolles	Website Down	2 days ago
Antananarivo	Website Down	3 days ago
Paris	Sign in	8 days ago
Lure	Website Down	12 days ago
Ashkelon	Website Down	13 days ago
Veigné	Errors	21 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:

• 
  Urban (@judeehis) reported 7 minutes ago

  Your GitHub doesn't need 100 projects. It needs a few projects that solve real problems. One useful application is worth more than ten unfinished tutorials. Build. Improve. Ship. Repeat. That's how careers are built. #Tech #Software #Python

• 
  Synapse Brief (@Synapse_Brief) reported 8 minutes ago

  NVIDIA just published its playbook for who owns the checkout button when AI agents do the shopping. Short version: not OpenAI, not Google, not Amazon. The merchant. The Retail Agentic Commerce Blueprint is open source, production-ready, and built on the NeMo Agent Toolkit. NVIDIA says it built this together with OpenAI, which is a strange sentence until you realize what it buys OpenAI: a merchant-side integration layer that works with ChatGPT as a front end without OpenAI having to own payments, pricing, or compliance infrastructure itself. The technical bet is protocol support, not model quality. The blueprint implements both the Agentic Commerce Protocol and Google's Universal Commerce Protocol from a single deployment, covering discovery, checkout, delegated payments, and webhook-driven order lifecycle events. Stack includes NIM microservices, Nemotron LLMs, NV-EmbedQA-E5 embeddings, Milvus for vector search, and an agentic RAG recommendation pipeline. Here's the tension worth sitting with: AI shopping assistants compress the funnel. Search, product page, cart, all collapsing into one conversational turn. That's great for conversion, terrible for merchants who don't control the interface the customer is actually talking to. NVIDIA's pitch is that you can plug into that compressed funnel without handing over pricing or the customer relationship. Agents discover and negotiate, but business-critical state stays merchant-side. Grid Dynamics is already running catalog enrichment and agentic checkout demos on this. Bloomreach and other integrators are building turnkey implementations on top of it. That's the actual distribution path, not direct NVIDIA sales. NVIDIA's number: nearly half of retail and CPG companies are already using or evaluating agentic AI. No methodology attached, so treat that as a vendor claim, not an audited stat, but directionally it lines up with how fast this category has moved since the blueprint's GitHub repo went up in January. The open question nobody's answered yet: when three different agent ecosystems are all hitting the same merchant backend with different protocols, whose pricing logic wins during a promotion window. That's not a hypothetical for much longer.

• 
  M.A.O.K. (@armaganonur) reported 8 minutes ago

  @QCXINT_ Heads up: the GitHub repo "API-mega-list" is not a real API directory. I checked it — sponsored ads in the README, affiliate/referral links (fpr=xxx params), unverifiable "11,860 APIs" claim, broken links. Looks like SEO/affiliate farming. Use public-apis/public-apis instead.

• 
  Penelope (@Ladys_Winter) reported 8 minutes ago

  @vladuhat999 @LuminaMeow14 @V33V33V33V33V33 It objectively is terrible UI design when so many users can't find the LITERAL ONLY BUTTON THEY NEED, and github simps will go "well the website is made for other people! They are just forcing you to use it for no reason! NO UPGRADE OR UPDATES!!!!"

• 
  mrgadget (@mrgadgetstudio) reported 9 minutes ago

  @saidotdev Why not working in VSC - github?

• 
  Michael Fischer (@Holden_Rye_) reported 12 minutes ago

  I’m working on a Bitcoin wallet. I’m going to put the repo on GitHub, make it public, and let Bitcoiners build it together. Fork it. Improve it. Save Bitcoin. Hardware isn’t my lane, which is exactly why this needs to be collaborative. My goal is just to get the ball rolling and the gears turning. Right now it’s a CLI. The point isn’t a pretty interface. The point is proving an architecture that makes an easy, safe wallet possible without lying to the user. The safety shouldn’t depend on the user being perfect. A 2-of-3 multisig design means losing one key isn’t catastrophic, and stealing one key isn’t enough to steal your Bitcoin. That’s a structural guarantee. Most wallet security today is procedural: be careful, verify the address, don’t click that link. Humans are the weakest link. This moves the protection into the architecture instead. The core policy engine does the hard work so the UI can stay simple. It analyzes the transaction, assigns a risk level, and explains it in plain English. The user sees Green: Safe to send or Red: Here’s what’s wrong. They never need to know what a script, descriptor, or PSBT is. Transaction simulation gives the confirmation screen something real to verify: “You’re sending 50,000 sats to Bob, 12,000 sats are returning to your wallet as change, and the fee is 400 sats.” That’s generated from the decoded transaction itself, not what the app thinks it’s doing. The descriptor becomes the backup, and it isn’t secret. Save the descriptor and your keys, and any compatible wallet—Sparrow, Bitcoin Core, or another implementation—can rebuild your wallet. No vendor lock-in. No “sorry, your funds are gone.” But here’s the hard truth. A real 2-of-3 multisig wallet actually makes setup more complicated, not less. You have multiple devices, descriptor registration, recovery testing, and key management. That’s the biggest unsolved UX problem. This repo doesn’t solve that yet. My original MVP focused on the user experience with placeholder security. This version focuses on real security with almost no user experience. Neither half is the finished product. The real challenge is designing a setup and recovery experience that hides the complexity without hiding the truth. That’s not just a coding problem. It’s a design problem. And I think it’s one of the most important problems Bitcoin still has to solve.

• 
  BlaDieBloe𐨆ۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖۖ​ۗۗۗۗۗۗۗۗۗۗ (@BlieDieBlaDie) reported 19 minutes ago

  The scumbags of the universe !!!! Paying exploit thiefs without any problem ha @mour0ne . He only had one exploit bc he found it on github and stole it and then defended him self by html edit his join date on @Hacker0x01 . And the sad part of it all he came away with it !!!

• 
  Soumendra Kumar Sahoo (@soumendrak_) reported 19 minutes ago

  My Hermes Assistant deleted a few skills and created a Github issue at its source code autonomously. #CrazyAI

• 
  Nan Yu (@thenanyu) reported 21 minutes ago

  You should be able to pledge tokens for issues that you open and open source repos. Write a spec in the issue with a pledge. If the maintainer accepts, GitHub passes the issue verbatim to a cloud coding agent at the requester’s expense. No more slop PRs

• 
  Brian Money 🌻 (@brianmoney) reported 24 minutes ago

  Try to get some work done and @GitHub is down 😢

• 
  Hamed Ghasemzadeh (@evgnomon) reported 24 minutes ago

  @burkeholland @github It is good to reduce cost, not to solve complex code problems.

• 
  Degen (@whatalife598) reported 27 minutes ago

  @Hals_xxx Click sign in and choose GitHub as an option

• 
  vergil’s yamato (@sinennn000) reported 27 minutes ago

  @Morpheos_sc tried this actually. for some reason i couldn’t sign in with github

• 
  . (@packerWp6) reported 31 minutes ago

  @gnukeith Okay on a tablet but yes it's not great However I have a simple site running on GitHub and being able to do quick if painful updates to it on the go is great my main issue is how bloody laggy the app is on a flagship Samsung phone

• 
  Lucas Santos (@lucassantoscode) reported 34 minutes ago

  Down @github

• 
  Milady (@onchainmilady) reported 34 minutes ago

  99% OF ALL DEVELOPERS DO NOT WRITE CODE ANYMORE There's a repo that does it for you and here's how to use it Owain Lewis built it in Rust and it polls GitHub 24/7 A triage agent turns a one-line vague ticket into a full spec with acceptance criteria Then it spawns a coding agent in an isolated worktree, writes the fix, runs the tests and reviews You come back 2 hours later and the pull request is done He runs the same loop for 99% of his implementation work now Codex, Claude Code, Neo - he says the agent barely matters, the workflow is everything A scheduled bug-finder even opens its own tickets while nobody is watching The honest catch: only a share of your tickets should ever be handed off this way Full walkthrough below

• 
  Poly (@poly0015iew) reported 34 minutes ago

  AN OPERATING SYSTEM THAT WRITES ITS OWN KERNEL DRIVERS HAS 28 STARS ON GITHUB 72,000 lines of C. one contributor. seventeen commits. i checked the numbers three times because the ratio didn't make sense. it's an x86_64 os from scratch whose only interface is a sentence. no shell, no commands, no ls, no cat. the author's own line is better than anything i could write about it: there is not one strcmp on the input path. that's how a kernel developer tells you he didn't cheat. the kernel does its own DNS and its own TLS in ring 0 - lwIP and mbedTLS compiled straight into kernel.bin, no host proxy of anything. the model gets 64 real syscalls as tools. prose on screen is the model, [brackets] are the kernel printing what it actually dispatched, from the real C return value. five separate defects were fixed to keep that line honest. now the part that made me put my coffee down. the kernel ships no audio driver and no knowledge of any sound chip. you attach a card, it shows up as an unclaimed pci device, and you type one sentence. it reads pci config space. writes a bring-up program in the kernel's own driver-vm instruction set. resets the codec. unmutes the mixer. builds a buffer descriptor list. starts the dma engine. installs itself as the system audio sink. then you can just ask it for notes. and in the recorded transcripts there's a run where the model correctly diagnosed a bug in this kernel's own printf - from inside the guest. forty years of teaching humans to speak kernel. one person spent seventeen commits teaching the kernel to speak human. twenty-eight people have noticed. 72,000 lines. 64 syscalls. zero strcmp. 28 stars.

• 
  Antaripa Saha (@doesdatmaksense) reported 38 minutes ago

  @airwarmedd duality of kids to look down on a girl in the post for not having github but getting into google, but when i said cp and github are not the only thing to get job nowadays, he said i looked down on people who grind??? bruhh also before lecturing me maybe a little visit through profile could have given him enough context.

• 
  eFkay🔌 (Character Dev Arc) (@Ox_Mud_ass_ir) reported 38 minutes ago

  @0xYassar Na ******** up be that, but i no mind give the github login make pesin use the points pay me.

• 
  CryptoTweets (@CryptoTweets) reported 41 minutes ago

  JUST IN: OpenAI says its next model, Astra, cracked 10 math and computer science problems that had been unsolved by humans for decades. Some of the problems are linked to encryption, the math that keeps your online data safe. Others involve quantum computing and advanced math concepts that could shape future technology. Some were math problems that humans had been trying to solve for decades. Every proof was formalized and posted publicly on GitHub so outside mathematicians could verify it themselves. Total cost to crack problems that took humanity decades? Roughly $2,000.

• 
  Eric Vya (@ericvyacheslav) reported 43 minutes ago

  🚨 Someone just open sourced a tool that turns one reference photo into a working, animation ready 3D model. No photogrammetry, no mesh scanning. It's called img2threejs. Think of it as a sculptor that only works in code, rebuilding the object as procedural Three.js geometry instead of scanning it. Here's what it does: → Takes one reference image and rebuilds the object as procedural, code only Three.js geometry → Runs a render vs reference review loop so bad output gets caught before it ships → Has a dedicated humanoid generator and a 4 body plan creature generator (quadruped, avian, winged-dragon, serpentine) → Ships a public live demo gallery running in the browser, not just static renders → Deliberately token efficient, built to run inside coding agent workflows like Claude Code v1.4 "The Weapon Update," does image matched CS2 weapon skin reconstruction, down to a dedicated Glock 18 assembly contract. It's also upfront about its limits, it says plainly when a reconstruction is approximate instead of faking confidence on a face it never saw. 8.7K+ GitHub stars. Apache 2.0 license. 100% Open Source. (Link in the reply)

• 
  Urban (@judeehis) reported 46 minutes ago

  Your GitHub doesn't need 100 projects. It needs a few projects that solve real problems. One useful application is worth more than ten unfinished tutorials. Build. Improve. Ship. Repeat. That's how careers are built. #Career #Django #Python

• 
  puffybsd (@puffybsd) reported 47 minutes ago

  @btbytes I'm locking down certain things via yubikey. Strange behaviors that heightened awareness: writing directly to a database in a docker container because harness forgot how to get API key, using github account to issue public PR without permission ("my bad").

• 
  Gio 🐘 (@GioDev8) reported 48 minutes ago

  Spent way more time than I probably had to on locking it down. Laptop is on its own network with tight firewall rules. The agent runs as a non sudo user that only has the projects I want it in, with its own GitHub and Claude accounts, so none of my real credentials sit on that box. The bridge only obeys my Slack user ID, and only channels I listed in a config can do anything. Unlisted is read only. The one that browses the web runs in a sandbox with no access to my code, since read plus fetch is how things get out. It probably has holes and is not best but the blast radius is a laptop I can wipe.

• 
  DimitrisK (@jimfeedback) reported 50 minutes ago

  @thsottiaux @rezoundous I think Sol only looking at the progress of my github workflow waiting to be over burns like crazy. I down to 30%

• 
  Cap-EO 👨🏾‍💻 (@EOEboh) reported 52 minutes ago

  2. Case studies, not project cards: A screenshot and a "View on GitHub" button is not proof. Show the problem, your constraints, the decisions you made and why. The result with numbers.

• 
  Rotimi Best (@rotimi_best) reported 54 minutes ago

  This is how I annotate feedbacks for @cursor_ai to go fix in my app. Once it's done, it comes back with a screenshot. If it aligns with my request, I sayf open the PR. if not, I annotate again and send it back for work. Cursor should probably support an annotating tool in their screenshots, that would be sick. Before I had to 1. Annotate 2. Create a linear ticket or Github issue 3. Assign to an eng 4. they go and work on it for hours 5. come back with a PR and we go back and forth on the PR. even though this interrupts my own active work. @greptile and @coderabbitai makes this easier for me though but they still don't catch intent and vision correctly. 6. if all good, then I merge.

• 
  👻GhostInTheModel👻 (@onespookyboi) reported 54 minutes ago

  jfrog found a github repo pushing 50+ sqlite CVE advisories. some reached NVD as critical and CISA's pipeline agreed, then the checked diffs showed no relevant fix and the described structs don't exist. fabricated vulns feeding automated triage is a fun new food chain (•ㅂ•)؟

• 
  Retr0gamer (@retr0gamer42) reported 55 minutes ago

  Update to the JRPG Translator, some annoying bugs got fixed and features added, full changelog since v0.9.2: Since someone asked, this is a standalone application, so it can be used with any emulator or game (that doesn't use exclusive fullscreen mode) but it is best used more seamlessly with the @launchboxapp using the plugin I made since this is the emulator interface I use on a dedicated mini pc. - New two-column terminology table with Add, Edit and Delete actions. - Independent JP → TL and TL → TL profile management. - Duplicate, malformed and empty-entry validation with a raw repair editor. - Reorganized terminology explanations emphasizing local TL → TL correction and the risks of model-based JP → TL instructions. - Stronger detection of glossary false positives and partially translated mixed-script names. - Conditional corrective translation retry using only exact glossary matches. - Dedicated PNG-size-limit errors instead of misleading missing-target errors. - Control-panel X now closes the complete application. - Discreet hover `...` and `×` controls on both overlays. - Clearer overlay context-menu exit labels. - Immediate “Generating explanation…” feedback. - Clear overlay errors when the selected OpenAI or Gemini API key is missing. - Automatic live-audio reconnection for temporary network and service failures. - Replaced continuous WMI polling with PID tracking and one-time recovery scans. - Reorganized API Keys tab with direct access to Windows Environment Variables. - Added the About dialog, version details, GitHub links and bug-report options. - Keyboard/controller navigation between the two Controls subtabs. - Down from Keyboard inputs now enters the first shortcut field. - Consistent Opacity naming and improved Maximum PNG size alignment. - About button remains visible at the preferred snapped window size. - Added Open JRPG Translator to the LaunchBox setup window. - Improved LaunchBox first-time guidance and window sizing. - Added the complete visual README showcase and updated plugin screenshot. - Added a welcome screen at first start - Fixed a bug that kept an AutoHotKey process running after closing the app.

• 
  #T (@SharpT_) reported 59 minutes ago

  @xdncolonthree The problem is people thinking GitHub is a place where you get software