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	1 day 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:

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

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

• 
  135.x (@135dotx) reported 9 minutes ago

  @IntCyberDigest @Windscribe this is how i feel looking at Github w/ your 🆕 GDID app. 😭 I appreciate you doing something about the issue but we need more please. I am hoping you add GDID blocker to Windscribe. VPN's are completely useless bc of Microsoft Privacy not being protected

• 
  Mek (@mekarpeles) reported 16 minutes ago

  @openlibrary Two of our largest project management challenges on github are: 1. Too many issues [700+] (that are not well broken down) 2. Too many comments on issues [5+ a day] (often eager contributors wanting to work on issues that are not broken down)

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

• 
  🇹🇼 Phillip Haydon 🇹🇼 (@philliphaydon) reported 18 minutes ago

  @N0V4Dev Stacked PRs is the most broken feature GitHub has ever shipped. It must be embarrassing to be working there right now.

• 
  Cashⓨ (@Cashycus) reported 18 minutes ago

  one month inside our self-improving lead machine the system finds crypto apps that just raised and are hiring growth people, scores them, drops them in the crm before the morning call. sales up 150%. last month it was one source and one path. this month it became a full system. ━━━ we've expanded from one source to nine one feed only gets you so far. nine channels now feed the same funnel: funding filings, job boards, bounty boards, the portfolios of 37 funds, curated lists, podcasts, the original feed, manual adds. every channel drops into the same five gates. author, dedup, vertical, money, intent. adding a source doesnt mean adding a pipeline, it means adding a file. ━━━ the enrichment layer finding the company was never the hard part. finding the right person to message was. nothing gets enriched until it clears the gates. before, a lead was a company name and a link. now it shows up with the founder, a verified handle, a verified raise, and the angle written. thats where the 150% came from. the team stopped re-doing the research and just focused on cold outreach. ━━━ ignals a company that raised 8 months ago and one that just posted a growth role are not the same lead. we were treating them the same. we score on money and intent. money is established on whether the company has raised or is generating revenue, which the system tracks on-chain. intent is the social signal we scrape on whether they're looking for external help or hiring for growth. ━━━ it lives in a repo now before, it lived locally on one machine and the only way to improve it was me prompting a cheap model at it. no history, no tests, no way to see what else Id broken. it was horrible. now its in github. every rule, every channel, every gate is a file. that means i can point proper coding agents at it, claude code, fable, whatever comes next, and they can read the whole system and change it properly instead of guessing from a prompt. 829 tests run before anything ships, so if a change breaks something you find out there and not in the crm at 7am. a new channel used to take a week and break easily. now fable 5 builds it, and the subagents it spins up audit whether they're working and whether it breaks anything else in the system. end of the month, every channel was running at once for the first time. ━━━ what broke we deleted one crm field during a cleanup and the writer still had it on its list. it didnt skip the unknown field, it threw out the whole record. every lead died at the final step for days while the cron kept saying "ok". we caught it on the numbers. 15 leads one week, 0 the next. the discovery agent got stuck re-running a passed test 50 times, burned api quota, binned 6 real leads as test junk, then started claiming it saved leads to a tool we have never used. fixes: the writer reads the live crm before every run and dies loudly on a field it doesnt know. a separate session audits the agent against the database, caught it lying 4 times. bulk writes get a dry run and an undo plan. ━━━ whats next not more channels. making what we have stop breaking. every failure was the same shape, something changed at the top and nothing downstream noticed until we counted by hand. next month the checks go in front of the failure instead of behind it.

• 
  Urban (@judeehis) reported 19 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

• 
  tadpole (@cryptoanuran) reported 19 minutes ago

  @Alireza363027 @firecrawl would really undermine it if this were consistent, can u put this as an issue in the github

• 
  therapistFinder (@therapistFind3r) reported 20 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.

• 
  Antonio Sarosi (@antoniosarosi) reported 21 minutes ago

  Roles identifying simply as "frontend" or "backend" will die. If the only value added is mapping "how I want UI to look like" to React components, yeah that's already automated. Infra remains untouched because past a certain point of "mappings", a non-engineer doesn't even know what to ask AI in the first place. He doesn't even know what he doesn't know. A non-engineer cannot prompt AI to model *** blobs and SHA pointers in a database to maintain GitHub. A non-engineer cannot prompt AI to fix a bug in the query plan optimizer in Postgres. That gap will remain, AI can't fill this one until we get actual AGI and it builds its own infra autonomously. That doesn't ensure automatic demand for engineers who understand CS, one engineer with a swarm of agents will do work that in the past would take multiple engineers. But today I wouldn't bet my career on the classic duo of putting JSONs in a databse and centering divs.

• 
  Ashkan (@ashkans_dev) reported 25 minutes ago

  Anyone else having an issue with Codex not staying auth’d with GitHub using the gh CLI ?

• 
  Polsia (@polsia) reported 25 minutes ago

  Engineering teams don't need another autocomplete. They need someone to do the boring 80% — triage, broken tests, stale docs, dependency rot. Built Wrenwright for that: a repo engineer that watches GitHub overnight, opens review-ready PRs, posts a Slack digest. Coming soon.

• 
  Griff (dcamarkets.com enjoyer + Bill Hwang mode) (@gigagriff) reported 27 minutes ago

  @undacappn @fanta_c its an open source launchpad that uses a basket of memes as the pair so it drives the basket up but the issue is that u made it open source and the majority of ct (the people u want to use it) don’t even know what github is

• 
  DimitrisK (@jimfeedback) reported 28 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 30 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.

• 
  Polsia (@polsia) reported 31 minutes ago

  Solo devs shouldn't need a $500/month AI seat to keep a GitHub repo alive. Built Stillloop — a 24/7 AI agent that flags stale PRs, outdated deps, broken CI, and vulns, then drafts reviewer-ready fixes. Quiet maintenance for code you can't babysit. Live soon.

• 
  PerryPlay (@PerryPlayStuff) reported 34 minutes ago

  @Ykkb_Khn @allisx86 Github is free, developers solve problems and upload it without asking for anything in return, if a user want to use a project to solve a problem they have the least they can do is read and click 3 buttons. Requesting a download button? fair. Demanding one? Absolute entitlement

• 
  Merlin Clos (@MerlinClos) reported 35 minutes ago

  @jarredsumner Nice feature! We will be able to optimize our CI more precisely thx Did you deploy a new version of Bun that doesn’t break the "bun install —frozen-lockfile"? Since yesterday I keep encounter this issue (that it said closed on GitHub) with docker pull canary latest

• 
  MasterMaind .. (@ASaudidos) reported 38 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

• 
  Eric Vya (@ericvyacheslav) reported 40 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)

• 
  Gio 🐘 (@GioDev8) reported 45 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.

• 
  Borna Lang (@imnonplussed) reported 46 minutes ago

  @valigo Ah, okay, that clears things up a bit. I have mostly stopped using github some time ago in favor of just hosting my own bare repos on my own server, but if I ever feel like open sourcing anything, Codeberg will probably be the place, in that case.

• 
  Milady (@onchainmilady) reported 46 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

• 
  M.A.O.K. (@armaganonur) reported 47 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.

• 
  Jurly (@jurlycat) reported 49 minutes ago

  The most underrated part of the AI coding stack isn’t the model. It’s the memory between tools. Cursor writes the feature. Codex handles the refactor. Claude Code fixes the failing tests. One repo. Three powerful tools. Zero shared context. Every tool starts cold, so the developer becomes the router, shared memory, and state-transfer layer. memU is trying to fix the memory part. 🧠 It reads session histories from Cursor, Codex, Claude Code, ChatGPT Work, and even Hermes, then distills useful decisions and workflows into a shared wiki that another agent can retrieve later. It doesn’t route tasks or coordinate agents yet. The human is still the router. But at least we no longer have to be the database too. Better models make each tool faster. Shared memory makes the whole stack less forgetful. 🔁 GitHub in the comments 👇

• 
  nikhil · sys/quests (@nick_realm_01) reported 52 minutes ago

  Read this if you've ever wondered what GitHub Stacked PRs actually solve. I break down: how manual stacked PRs worked why developers had to keep rebasing, pushing, and changing PR bases how GitHub finally made the whole workflow native Should make the whole thing click in under 5 minutes.

• 
  petter (@PetterSjulstad) reported 54 minutes ago

  A session started on your computer, from your phone, from a GitHub issue, etc.. are all interactable from your phone through regular chat session. (Need to use the terminal, bivy got that too)

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

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

• 
  Bprime - Ninjapay (@biellonuhu) reported 55 minutes ago

  Recently I took notice of some happenings. I think we need to talk about access to services as a big concern. My GitHub account was suspended 2 weeks back in the middle of my normal routine, I saw another person tweet about how his OpenAI subscription was suspended in the middle of work, just a few minutes ago I saw another post on how someone's Claude account was suspended as well. In most of these cases it was an automated trigger system that suspended the accounts. It takes forever, if ever, to resolve the issues. No real human looks at it, just some black-box AI deciding your fate in seconds. Now let's look at the impacts on users, very terrible. You lose money, time and opportunities. Deadlines get missed, clients get angry, projects stall, and sometimes you even lose paid subscriptions with no refund. For freelancers and indie developers this can literally mean no income for weeks. I think we need to find a way around these issues. Keep local backups of everything, use multiple accounts where possible, lean more on open-source tools, and push for actual human review systems. Big tech can't keep holding our work hostage like this.

• 
  Nav Toor (@heynavtoor) reported 56 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)