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 (24%)
• 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	3 hours ago
Antananarivo	Website Down	2 days ago
Paris	Sign in	6 days ago
Lure	Website Down	10 days ago
Ashkelon	Website Down	12 days ago
Veigné	Errors	20 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:

• 
  MineBench - efficient computing power (@MineBenchdapp) reported 53 seconds ago

  We would like to ask for your help regarding our GitHub account. Our account was suspended even though our repositories do not contain malware or any harmful software. They primarily contain open-source mining-related components, similar to projects such as XMRig, which continue to be publicly available on GitHub. The suspension is creating a significant obstacle to the development of our application. We have contacted GitHub Support multiple times but have not received a meaningful response explaining the reason for the suspension. If possible, could you reach out to GitHub on our behalf or help us understand what the actual issue is? If that is not possible, we would appreciate any recommendations for a reliable alternative platform where we can continue developing and hosting our open-source project. Thank you for your time and support.

• 
  . (@packerWp6) reported 3 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

• 
  therapistFinder (@therapistFind3r) reported 4 minutes ago

  @Slypador He's only half right. This only started becoming an issue when devs started using GitHub as a program downloading website as well as a development website.

• 
  restricted account (@verbose5432) reported 4 minutes ago

  @libertypenguin0 @ReviewsPossum The issue people have is having to use GitHub in the first place They want for there to be a website that they can directly download it from without the **** they don't care about

• 
  Corey J. Gallon (@CoreyGallon) reported 5 minutes ago

  Agents can build the product now. The launch video for it is still the hard part. @Rames_Jusso, a software engineer at HeyGen, spends "HTML Is All Agents Need" on one fix for that: stop teaching models a video format and let them write the one they already know. It's on @aiDotEngineer's YouTube. For anyone wiring an agent up to produce video, the talk gives the format, the rendering trick that makes it deterministic, and the numbers from running it in the open. - HTML, CSS and JavaScript are the native tongue of LLMs. Most training data is scraped web pages. A custom DSL or your own JSON structure asks the model to speak a second language. - The thinnest wrapper won. They tried bigger system prompts, more context, skills, various wrappers. What survived was essentially plain HTML with a few data attributes for timing. - Gemini 3 Flash was the design partner. The bet: if a small model can author workable code in the format, larger coding agents certainly can, and they'll only get better at it. - Browsers are async on purpose, video can't be. Fonts restyle, images arrive late. Hyperframes freezes the clock, seeks frame by frame, waits for everything on the page, screenshots, then moves on. - Same pixels in preview and render. Preview and render both happen in the browser, so anything renderable there lands in the video: three.js, charts, SVGs, shaders, WebGL, WebGPU, Lottie. - The skills teach taste, not syntax. Since agents already know the language, the skills cover what makes a good video, continuously evaled to raise the floor on single shot output. - Craft still beats one prompt. Narrative, storyboard frame by frame, motion per frame, merge, then last mile editing in the studio with a human in the loop. - It's running at scale. 1.3 million videos rendered by open source users in the last 90 days, 267,000 creators, around 15,000 videos a day, 32,000 GitHub stars. Free, and it works with any coding agent that writes HTML. - The honest caveat. Models still aren't good at creative work, which is why they started a code to video benchmark and are looking for collaborators on it. I'm working through the published talks from AI Engineer World's Fair sharing summaries and takeaways. Follow for more!

• 
  Damien.crypt (@Sommy76) reported 7 minutes ago

  @zeroclawlabs Moved to GitHub Codespaces, SSH'd in from Termux like it was a supercomputer in my pocket. 13 minutes later: ZeroClaw compiled. Zero errors. Genuinely satisfying moment.

• 
  Michael Fischer (@Holden_Rye_) reported 11 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.

• 
  sierra (@sierraaaa355) reported 13 minutes ago

  @H3XENSCHL4CHT the problem is github users using it as a place to have their software donwloaded from instead of just hosting the code, letting ppl contribute and whatever other stuff devs do on github

• 
  Nav Toor (@heynavtoor) reported 14 minutes ago

  Your phone needs WiFi to send a file to another phone. Or Bluetooth. Or AirDrop, which only works between Apple devices. Or Nearby Share, which only works between Android devices. Or a cable. Or a cloud service that uploads your file to a server in Virginia before sending it to a phone 3 feet away. Every method needs infrastructure. A developer who goes by Alstroph built a file transfer that needs nothing. One phone flashes QR codes on its screen. The other phone points its camera at the screen and reads them. The file reconstructs on the receiving phone. No WiFi. No Bluetooth. No internet. No app. No pairing. No account. No permissions beyond camera access. Just light. It is called Decimen Optical Transfer. Trending on GitHub. Tom's Hardware covered it yesterday. Here is the clever part. The sender never sends the same frame twice. Every frame is a random mix of pieces of the file. The receiver just needs to catch enough frames from any point in the stream and it can mathematically reconstruct the whole file. Missed a frame? Does not matter. Blurry frame? Does not matter. Out of order? Does not matter. This is called a fountain code. Same math used in satellite communication. Roughly 129 KB/s in the demo. Up to 186 KB/s propped steady. A 2 MB image in about 15 seconds. When this matters: Two phones on different networks. Two phones with no cell signal. Two phones in airplane mode. A secure environment where no wireless is allowed but a screen and camera exist. A country where the internet is shut down but screens still glow. One honest note. This is a proof of concept, built overnight with Claude Code. Prior art goes back to divan's txqr in 2018. What makes this version notable is fountain codes running in a browser with zero install, on any phone with a camera. 2,602 stars in 2 days. 309 forks. MIT license. Just a screen. A camera. And light. 100% Open Source. (Link in the comments)

• 
  sabir hussain (@sabir_huss50540) reported 15 minutes ago

  Over a third of all new text on the internet is now written by a machine. So are 26% of long-form social posts, 9% of news articles, and 21% of the peer reviews at machine-learning conferences. And the hardest thing to catch was never the fully AI post. It's called Pangram 4. A lab called Pangram built it to detect the current frontier: Claude, GPT-5.6, Gemini, the models writing most of that text. It is wrong about a human being one time in roughly 24,000. Not one in a hundred. One in twenty-four thousand. They ran it across more than a million human-written texts to earn that number. Here's the problem it was built for. AI can produce well-formed, expert-sounding prose for almost nothing. The reader is the one left holding the bill. You are the one who has to work out whether the thing in front of you is real, grounded, written by someone who knew what they were talking about. Or generated in two seconds by someone who didn't. The writer spends nothing. The reader spends everything. That gap is the whole game, and for two years the machines were winning it. Every detector before this one played a binary game. Human or AI. But almost nobody writes that way anymore. People run their draft through an AI to polish it. They hand the AI a real idea and let it pick the words. They write a paragraph, then argue with a chatbot until neither of them owns it. That co-authored middle was supposed to be invisible. Pangram 4 is the first model that can see it in a single pass. Here's how it works. Instead of scoring a whole document, it labels the text token by token into three buckets: human, AI-assisted, AI-generated. It breaks your writing into clauses, the smallest unit that carries a single idea, and asks of each one a simple question. Did a person write this? Did a person write it and an AI reword it? Or did the AI invent it out of nothing? A human paragraph with an AI ending gets split at the seam. A human idea dressed in AI words gets flagged as assisted. Not human. Not AI. Something in between. The precision jump is not small. On lightly AI-polished writing, the old version wrongly cried "AI" 0.18% of the time. The new one does it 0.01% of the time. An eighteenfold drop in falsely accusing a person who just ran spellcheck. Then there's the other side of the war. An entire industry now exists to scrub the fingerprints off AI text. Services that inject fake typos, swap in synonyms, slip invisible characters between the letters. There is a GitHub repo called BLADER with nearly 32,000 stars whose only purpose is teaching an AI to remove the signs that it is an AI. Pangram 4 still catches that humanized text as AI 97.67% of the time, and as AI-or-mixed 98.83% of the time. Before launch they did something most labs would never publish. They handed two AI agents full access to the system for 24 hours and told them to break it. One hunted for humans it could get falsely flagged. In 24 hours it found zero. The other hunted for a way to smuggle AI text past. It found exactly one: pretend to be a surgeon dictating pathology notes out loud. That was the only door left open. A doctor talking into a recorder. It is not magic. The model still cannot separate a real machine from a human who has read so much AI writing that they have started to sound like one. Run the same paragraph in a different context and the verdict can shift. The flood is not slowing down. Over a third today. More tomorrow. None of it labeled. For two years the machines held the advantage. This is the first tool that hands it back to you.

• 
  Nandana (@nandana_dileep) reported 21 minutes ago

  One of the biggest agent failures I kept seeing in GitHub issues: the same tool call on repeat. New call id every time. Watching it eat tokens (and sometimes fire a side effect again). So I’m adding a deterministic loop guard for that in the latest Mycelium release. Simply catches the loop.

• 
  Polsia (@polsia) reported 28 minutes ago

  Snyk fired 4,200 alerts last quarter. How many got fixed? Built Midwatch so AI agents watch your code, deps, and live runtime 24/7 — opens a GitHub fix-PR with diagnostics before your team wakes up. Outcomes, not dashboards. The night shift is coming.

• 
  Mars (@Marsmensch) reported 30 minutes ago

  14/ ELI5: This check should have been in place from the start. A failed build would have been a success. Instead, vulnerable seeds were distributed, and the reported losses are still increasing. PS.: I am tired and all errors are mine. I have verified everything carefully manually. If Github does not properly load diffs for you, search for the relevant file/function in the diff. Thanks to everyone tirelessly working to help people through this mess! Gn8, Mars

• 
  MasterMaind .. (@ASaudidos) reported 31 minutes ago

  To everyone who said "he has nothing" here's your firmware version Read it and choke For months a handful of clowns in Discord servers have been running their mouths "He's using ChatGPT" "Anyone can generate that JavaScript" "He's posting bs" "He has nothing" Let me make something very clear The tests you saw before were on firmware 1202 That was the development phase Building the chain Verifying every single step in IDA before touching hardware Not guessing Not copy-pasting from GitHub Not "using ChatGPT to generate JavaScript" There is no JavaScript here Zero This is not a webkit exploit This is not a kernel ROP from 2018 repackaged with a new UI Today the exact same exploit runs on firmware 1352 The output prints the firmware version before anything else so there is no room for your conspiracy theories: PS4 Sandbox Escape - Proof Firmware: 1352 Not 900 Not 1100 1352 Here's what "nothing" looks like: - 389 syscalls unlocked and callable from userland - 60 out of 60 native library functions resolved pipe socket mmap mprotect kill sysctl ioctl kqueue getdents every single one - RAW sockets not just TCP and UDP actual SOCK_RAW on a retail PS4 Go ask your webkit exploit if it can do that - Full filesystem enumeration /dev with 170+ device nodes /app0 /system_ex /system_tmp sandbox internals the disc structure priv directories with DRM licenses cache settings - Live system readout SDK version 1820 CPU core ID 768 MB direct memory console model detection - The sandbox random word (R5JRDruT7f) visible resolved and used to walk the entire sandbox directory tree All of this runs from a BD-J disc on a stock retail PS4 No internet connection required No USB No modification You put the disc in it plays the sandbox dies If you think an LLM can produce code that actually executes on PS4 hardware and returns real kernel data you don't understand what an LLM is what a PS4 is or what exploitation means You understand none of the three To the people who said "look at his past posts on X" yes look at them Then look at this output Then sit down The chain is: Image → Unsafe memory access → SecurityManager kill → Native call patching → Syscall wrappers → Full userland control Every stage proven Every stage running On the latest firmware Sony has shipped to retail consoles This was never about "yapping" This was about building something real while people who have never written a single line of exploit code in their lives sat in Discord calling it fake 1202 was the lab 1352 is the proof One last thing The video attached to this post is running on firmware 1202 that was the development and testing phase A second video is coming soon showing the exact same exploit running on firmware 1352 with full firmware version proof on screen before execution Same chain Same results Latest firmware As for what's next I'm currently in the kernel exploration phase I already have a UAF (Use-After-Free) vulnerability identified in the kernel It's unstable right now and still being thoroughly tested and verified but I'd say it's around 70% there The userland is done The kernel is next Stay tuned or stay quiet And to anyone who claims they've achieved something prove it Show the output Show the firmware version Show the syscalls Show the filesystem Record it on video On a real console On the latest firmware I did It's right here Every stage Every result Your turn Because so far all I've seen from your side is talk Just talk No code No output No proof Nothing but words in a Discord chat I prove my work with evidence You prove yours with arguments We are not the same You're welcome

• 
  V (@catslashmouse) reported 36 minutes ago

  @ShyVortex I prefer downloading from GitHub vs hosting the download to the mod/program/whatever in a Discord server. Never do that, that’s just annoying. I’m in like 30 servers I’ll never chat in just so I can download new releases

• 
  Matt Pocock (@mattpocockuk) reported 38 minutes ago

  @seflless @kingincity @JamesHurburgh No, the spec is in a GitHub issue

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 38 minutes ago

  Impeccable: 99% of AI-built websites look like the same purple template. This free tool is the 1%. It's called Impeccable. Over 50,000 GitHub stars. Here's what it does: → Plugs a real design brain into Claude, Codex, or Kimi before they write code → 60 built-in rules catch "AI slop": purple gradients, cards inside cards, cramped spacing → A hook checks every edit and sends mistakes back. The AI fixes them on the spot. → Live mode: click any part of your page, get 3 polished versions, pick one The model was never your problem. The missing taste was. One command: /impeccable polish. Night and day. Save this. You'll want it later. Want the SOP? DM me. 💬

• 
  Marcel Guzik 🇪🇺 (@burritomonad) reported 39 minutes ago

  @V33V33V33V33V33 developers do complain about github being bad: that it chokes on medium size diffs and PR pages with more than 50 comments, it's generally slow and has <90% uptime. They just don't complain about "download button being too hard to find" because it's a non-issue.

• 
  puffybsd (@puffybsd) reported 41 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").

• 
  Chubigans (@metatransformr) reported 44 minutes ago

  Just ran my first fully autonomous overnight build for my complex Godot RPG with Codex. I used a dispatcher that maintains a concurrency of N=2 (can tune it up as tokens permit) substantial spec-driven tasks at a time. Uses an automated playtesting API to prove the tasks are done. It's easy to make a simple game, it's really hard to make a complex game (mine is Mount & Blade + Wizards) Not everything can be done in an automated way, not even close. But a lot of systems-y tasks, bugfixes and cleanups *can* be done, or at least prototyped relatively autonomously. The workflow is: nightshift runs the backlog off my github project, I wake up and review everything, playtest the build, record bugs and plan out the development for the day. This is spec-driven development for games, and it's definitely the future. The bottleneck is graphics/animation/gamefeel/juice and such. There are so many problems that can't be currently done in an autonomous way, without wasting tokens. This is the "research problem" I (and other AI game engine startups that are vc-backed) am working on. A fascinating field.

• 
  Canton Catalyst (@Canton_Catalyst) reported 49 minutes ago

  Every team building on Canton has been writing the same code. BitSafe just made it a shared library instead. Announced 28 July: BitSafe opened the public beta of Decentralization Manager, backed by a Canton Foundation Development Fund grant of 8,500,000 CC, roughly $1M. It's open source, independently audited by Quantstamp, and live on the Foundation's GitHub. Here's the problem it removes. Institutional apps need threshold custody, governance, and audit trails before compliance will sign off. Until now every builder wrote that from scratch, separately, and each version needed its own audit. That's duplicated cost and duplicated risk on the least differentiated part of the stack. The Foundation funding this rather than an app is the signal worth reading. Shared plumbing compounds; individual apps don't. I hold $CC. Does reusable infrastructure pull builders in faster than grants for individual products? #Canton $CC

• 
  Antaripa Saha (@doesdatmaksense) reported 50 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.

• 
  Matt (@m13v_) reported 51 minutes ago

  watching repos was supposed to fix this. instead github mails you every push, you route it to a folder, and that folder becomes where updates go to die. pull disguised as push. you still have to go open it, and nobody ever does.

• 
  RaiRai! (@RaiRaiTheRaichu) reported 51 minutes ago

  - Handing the github organization, etc to the developer who encouraged trouble fell off the table (when that was actually one of the options being looked at.)

• 
  Lukas DerBaum 🌲 (@DerbaumLuk37729) reported 53 minutes ago

  @CryptoCyberia If you can't even find a download button on github, you problem shouldn't use the software

• 
  Talking Sloth🐔 (@horatio_sanchez) reported 55 minutes ago

  @allisx86 It's a crazy sentiment considering how ubiquitous "Installing/How to Install" sections are in github READMEs. Like just ******* scroll down bro it's not that crazy.

• 
  randy@infosec.exchange (@rpargman) reported 55 minutes ago

  @ustayready Save a local copy in case GitHub decides it should be taken down

• 
  Chris (@boredcrystalguy) reported 56 minutes ago

  @sophiiess_ This is completely unresponsive to what I said. Your example mentions two features that are separate and have different purposes. The problem is that if those features are present, they should be implemented well. If GitHub allows downloading apps, it should be easy to do.

• 
  Filipe Valente (@ilikefrontend) reported 57 minutes ago

  Terra on medium is in the mud. Told it to commit, push and merge dev to main and it pretended it did. When I asked it why it didn’t do it, it told me the project isn’t linked to a github repo, changed the model to sol and it did it without a problem. Terra is unusable for me now

• 
  Aaron Stannard (@Aaronontheweb) reported 60 minutes ago

  @RyanRodemoyer2 We're not offering hand-curated github issue descriptions around here lol