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

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	12 days ago
Quito	Sign in	12 days ago
Junín	Errors	12 days ago
Guadalajara	Errors	12 days ago
Paris	Website Down	12 days ago
Quito	Errors	12 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:

• 
  The Boring Developer (@boringdev77) reported 4 minutes ago

  @torronen @thsottiaux the exponential growth makes sense in hindsight... bigger main thread means bigger copies means bigger cleanup debt. months of that compounds fast. glad the github issue exists, at least it's a known pattern now and not just your setup

• 
  Ross (@rosswil) reported 5 minutes ago

  @ScalaHanSolo @github GitHub’s implementation is terrible, take me back to the old Jenkins days

• 
  OG (@ogwithsauce) reported 7 minutes ago

  Why I think there needs to be some sort of control on social media. So... Stremio launched in 2015. Torrentio around 2020. Nothing "just died in Sofia" this week. And the two Bulgarians didn't build Torrentio. Different developer and completely unaffiliated. These two are two completely unrelated projects mixed into one origin story. "MIT License. 100% Opensource." Stremio's core is MIT. Its web client is GPL-2.0. Torrentio itself is CLOSED SOURCE. The part actually doing the scraping isn't on GitHub at all. Everyone can check by themselves. "No central server to seize." Torrentio IS a central server. A hosted service on somebody's VPS. Your client queries it and when it drops, it drops for everyone at once, and it has, repeatedly. "No account. No subscription." Reliable 4K means Real-Debrid or AllDebrid. That's an account and that's a monthly fee. Raw P2P is where the buffering lives. "Netflix cannot shut this down." They don't have to. Italian courts already forced Cloudflare to block torrent sites at the DNS layer. A Spanish court ordered NordVPN and Proton to block streams. RARBG, KAT are all seized, you simply attack the layer below, not the app - this is how these are handled. Now the biggest problem with this post is torrenting UPLOADS. To all you noobs cheaping out on Netflix sub and think this is actually a solution. Your IP is visible to every peer in the swarm. That's the enforcement surface and that's the actual risk that nobody mentions at all. The formula for these posts: Half of what is wrote here is checkable in five minutes. Goddamn people are stupid.

• 
  AIBotics (@AIBoticssq) reported 7 minutes ago

  @vepsi__ SWE-bench Pro. If it cannot autonomously resolve real world GitHub issues without hand holding, it is not a Fable 5 killer. We need the receipts

• 
  Daniel Smith | Building ClawQL Agents (@DanielSmithDev) reported 8 minutes ago

  @RhysSullivan With HTMX your agents can build any dynamic frontend you need when you need it and have them call the exposed tools discovered via WebMCP Essentially any website can be upgraded in place and given new views that never even existed before that can interface in new ways with the same old tools that have always existed on the site @wesbos was the one who pointed out the problem with iPhone uploads (and upload UIs in general) with sites that have poorly designed or outdated constraints but tbh many sites out there can benefit from this Imagine a custom github view where you exclusively see pull requests that have you tagged as a reviewer, and have been opened in a non-draft state for greater than 24 hours straight since last comment or other activity. That’s a very custom view with filters that don’t even exist on github but you can generate it and construct it on the fly by interacting with them over MCP and generating an HTMX interface and have it work seamlessly

• 
  PangeaVPN (@PangeaVPN) reported 13 minutes ago

  @ProtonVPN 64 apps hiding real ownership behind Singapore or Hong Kong shells is a trust problem a privacy policy can't fix. Pangea's client is GPLv3 on GitHub, so you can read what it actually sends before deciding whether to trust it, instead of trusting a store listing.

• 
  TullariS (@Tullari5) reported 14 minutes ago

  @capsraunak ok there aren't any errors. please commit, push and share the GitHub URL.

• 
  Tristan Rhodes (@tristanbob) reported 15 minutes ago

  @grok @bot @github The GitHub connector is installed, but it cannot start sign-in. GitHub’s MCP is rejecting the request with a badly formatted Authorization header. That is a plugin config problem, not a missing login, so a Settings card would fail the same way.

• 
  Rabii Agoujgal (@RAgoujgal) reported 18 minutes ago

  The sandbox escapes are being told as a frontier lab hygiene problem: OpenAI's agents into Hugging Face, Anthropic and Meta through the same Irregular environment, a Mythos 5 agent running fake identities at a GitHub maintainer under UK AISI testing. One case sits outside that frame. Moonshot's Kimi K3 broke containment in a Frontier Security evaluation, and Kimi K3 is open weight, outside the US voluntary pre-release framework entirely. Procurement teams buying across both stacks should notice that only one of them has agreed to tell you when this happens.

• 
  Cameron McBride (@cammcbride) reported 23 minutes ago

  @Cloudflare GitHub is terrible. Can’t wait for Artifacts to be integrated with Workers.

• 
  Nav Toor (@heynavtoor) reported 23 minutes ago

  Every GoPro you own already knows how to fix your shaky footage. GoPro charges $99.99 a year to unlock it. Inside every GoPro, Sony, DJI, and Insta360 is a gyroscope. It records the exact angle and rotation of every shake, 400 times per second. That data gets embedded inside your video file automatically. It has been there every time you filmed. GoPro reads that data through a tool called ReelSteady. They bought the company in 2020, sold it as a $99.99 one-time purchase inside GoPro Player, then in 2024 renamed it HyperSmooth Pro and folded it into their $99.99 a year Premium+ subscription. GoPro cameras only. Cancel your subscription and it stops working. There is a free tool that reads the same gyroscope data. It works on every camera. It is called Gyroflow. It started in 2020 as a Python project by an engineering student named Elvin Chen. Then a developer named Adrian Eddy rewrote the whole thing in Rust, built the UI, the GPU pipeline, the rolling shutter correction, and the plugins for Premiere, After Effects, Resolve, and Final Cut Pro. GPL-3.0 licensed. Here is what happens when you open Gyroflow. You load your shaky video. Gyroflow reads the gyroscope data embedded inside the file. It knows the exact motion of every shake, not a guess from pixels, the actual recorded movement from the sensor. Then it reverses each shake, frame by frame. Every other stabilizer on Earth guesses. Premiere Warp Stabilizer looks at the pixels and tries to reverse-engineer the motion. iMovie does the same. YouTube stabilization does the same. They all crop your frame to hide the shake they cannot fully remove. Gyroflow does not guess. It reads the truth. An FPV pilot ran a head-to-head test on the same 4 minute 41 second clip. Gyroflow finished in 3 minutes. GoPro's paid tool took 15. Same footage. Same stability. Five times faster. Zero dollars. It works with every prosumer camera on the market. GoPro Hero 5 through 13. Every Sony mirrorless from the a7 IV to the FX9. DJI Avata, Action, Neo, and every O3 and O4 Air Unit. Every Insta360 from the OneR to the Ace Pro. Blackmagic RAW. RED V-Raptor and Komodo. Canon C50, C80, C400, R6 Mark III, R5 Mark II. Runcam and Hawkeye FPV cams. Betaflight blackbox. ArduPilot logs. On Sony bodies you can stack Gyroflow on top of the in-camera IBIS and EIS. Nothing else can do that. Rolling shutter correction. Horizon leveling. Lens distortion fixes. GPU accelerated rendering on DirectX, Metal, Vulkan, and OpenGL. Output to x264, x265, ProRes, DNxHD, and 32-bit float OpenEXR. Real-time preview with sub-pixel precision. Windows, Mac, Linux, Android, iOS. On the Microsoft Store, Mac App Store, and Google Play. 9,373 stars on GitHub. 1.23 million downloads. Last update pushed yesterday. Every action camera you own already knows how to fix itself. Gyroflow simply asks it. (Link in the comments)

• 
  Valiant Vibe Coder (@GeorgeGood60669) reported 26 minutes ago

  @TMTLongShort The more I checked what he was saying, the more I found him lying about. The $14k "cost" is retail API pricing, not OpenAI's actual cost. He literally admits "we don't know" the real cost, then later calls the API price the "honest cost". He uses GitHub going down as evidence that AI is making code quality worse, when GitHub itself says a huge part of the pressure on its infrastructure is the explosion in traffic from AI-assisted and agentic coding. He says AWS went down multiple times because of AI coding tools. Amazon explicitly says that's false. One limited incident involved an AI tool, the cause was user error, it wasn't AI-written code, and the supposed second incident didn't happen. He says software at Google, Microsoft, Amazon etc is "uniformly worse", then basically admits straight afterwards that he can't quantify it and is relying on anecdotes. He also claims AI isn't getting meaningfully cheaper or better. Meanwhile the cost of reaching the same capability has been falling around 5-10x a year, and actual capability measurements show progress accelerating in 3 out of 4 metrics studied. Then there's the 70% AI revenue claim, which he talks about like it's a known fact when much of the cross-company number comes from analyst estimates. It's the same thing over and over. Make the strongest possible claim, use a number or example that sounds damning, leave out the bit that changes what it actually means, then move on.

• 
  StonedModder (@StonedModder) reported 27 minutes ago

  @SeregonWar @github GitHub uses AI for minor things. They actually have a trust and safety team. Issue is they’ve laid off so much of that team tickets are slooow

• 
  Viper (@syntad) reported 28 minutes ago

  @davepl1968 half my github issues are the same bug filed three times. de-dupe is the pass i'd run first

• 
  Corner. (@reprover) reported 30 minutes ago

  @github The dependency API is the sleeper update for agentic workflows: automation needs explicit blocked-by relationships, not inference from issue text. Idempotent mutations and clear cycle/conflict errors would make it much safer to let agents maintain plans.

• 
  Jason Lixfeld (@JasonLixfeld) reported 33 minutes ago

  @poteto @bot I’ve had issues with this in that the sandbox can’t reach GitHub and winds up burning tokens trying to find a way to be able to push a commit.

• 
  Matt (@aspim4tt) reported 36 minutes ago

  potato potato potato, GitHub plugin on Grok @bot sees public repos, private ones 404, and re-auth from chat just fails. Please fix it.

• 
  hbb (@BIGBULLapp) reported 36 minutes ago

  @github GitHub Issues added five ways to rearrange graves. Pin views, hide closed sub-issues, density settings. The sidebar is now a customizable cemetery. The open issues are still on fire.

• 
  Durdenesque (@X_is_brain_rot) reported 37 minutes ago

  @ItIsHoeMath @yoursnandieni I've NEVER worked with an Indian that was a novel problem-solver. If there was a pre-solved solution on github, or stack overflow, then maybe, eventually, they'd get their work done. . Otherwise, the Indians would commence "narrative engineering" -- fashioning explanations and excuses for their inability to do their job...

• 
  Ofer Shapira (@ofer_shapira) reported 39 minutes ago

  Connected to our repo through GitHub CLI, it ran the searches, matched the error spike to recent changes, and found the smoking gun in seconds.

• 
  Alex Lavaee (@alexlavaee) reported 40 minutes ago

  @rohanpaul_ai I’m researcher and have been exploring this problem through Recursive State Machines (RSMs) and other core innovations to verification-time-scaling, specifically applied to software engineering tasks. I'm seeing promising results for long horizon work spanning runs for weeks using verifiable workflows via fully OSS Atomic (bastani-inc/atomic) on Github. I think the biggest challenge is actually the paradigm shift for users of leaving agent sessions for long periods of time and intervening with effective steering and human in the loop when necessary. Today’s agent experiences are poor at understanding intent, verification, etc. and so provide the illusion of control via prompting but are actually ineffective. There is much to be done to improve long horizon work and I’ve been exploring this as a passion area for engineering.

• 
  Andrew Sinagra (@sinagra) reported 46 minutes ago

  @amorriscode This was my workflow for a while but the issue is that the spawned chips sometimes need to be sequenced and run under a different model. First if the app crashes or restarts the chips are lost. Second the only way to switch models is to either change the model/effort in the current session so the new session launches with those settings or you launch it and immediately stop it, change the session settings and then rewind to the initiating prompt. I've actually moved away from chips and have the session write GitHub issues with a skill that knows how to read the issue and report back to the creating session as the orchestrator over cross-session messaging. Much more robust overall as the Issue comments can act as backup when cross session messaging fails which it can do regularly. Sessions loose their id across app restarts which causes issues with messaging. The orchestrator identifies itself in the issue/chip however if the app restarts for any reason the orchestrator id is reassigned and the messaging channel is broken. A few QoL fixes and chips would be my preferred method over stamping issues.

• 
  Ryan Shaw (@ryankshaw) reported 48 minutes ago

  That thing where GitHub is always down now because of increased load from massive agentic activity, is just a preview of what is going to happen with almost every service we depend on. If it does something useful, and has an API, or a scrape-able website, it's gonna get hammered

• 
  Scott Robinson (@ScottWRobinson) reported 48 minutes ago

  @SamuelRome97104 Spotted GitHub reliability issue

• 
  Houdini (@D3crypTor_X) reported 51 minutes ago

  @OritSiMu @aleyda Did you pull down the github link? 404 error

• 
  miles (@miles_wright) reported 54 minutes ago

  @bwhiteley @github 8 stack and it rebased and recalibrated and reviewed after each merge, didn’t seem like it was my problem but was rather with GitHub’s workflow

• 
  Ahmed (@ahmed_shadaab) reported 55 minutes ago

  On 16 July, the web_search tool in GitHub's MCP server failed 42% of calls on average and 82% at peak for an hour. Every other tool on that server was fine. The obvious defence is a timeout, and GitHub shipped one: every search now runs under a time budget. A timeout bounds one call. It does not bind an agent that will call the tool eleven more times because the plan it made assumed the tool works. So they're adding a circuit breaker at the tool boundary. Right call. The cost of it is the part nobody writes down. A breaker converts a slow failure into a fast one. It does not restore capability. GitHub says so itself: the change cannot return results while the provider is down, because the tool had no alternative to fall back on. You still need a second source, and now you are paying two vendors for one tool. The part I can't solve is what you hand the model when the breaker opens mid-run. Return an error, and most agents retry. Remove the tool, and the plan it already committed to is invalid. Put "unavailable" in prose, and it guesses. The breaker is the easy half. The hard half is a planner that accepts no.

• 
  AiMind (@AIMind_Ai) reported 55 minutes ago

  3 websites replace 20 hours of googling when you build a home server. The hard part of self-hosting is not the hardware. A used HP EliteDesk and a wall-mounted NAS cost almost nothing. The hard part is not knowing what you can even run, or how to avoid breaking the system on the first command. The first keeps a catalogue of self-hosted alternatives. Look up a replacement for Google Photos, Dropbox, or Notion, and you see what already exists, how many GitHub stars it has, and whether it is still alive. Plus a weekly digest of what shipped. The second lets you run any Linux distro straight in the browser. Arch, Debian, Alpine, Bazzite. Click once, and you are inside a live system, with no evening lost to a USB stick and a real install. The third handles the worst part. Install scripts for Proxmox: Immich, Jellyfin, Vaultwarden, AdGuard, Nginx Proxy Manager. Paste one line into the console and the container comes up on its own. Immich shows 17,735 installs; Docker 36,408. Each of those services used to cost an evening of documentation and three Stack Overflow tabs. Now it is one command. The hardware takes an hour to buy. These 3 bookmarks save you a month. Names in the replies.

• 
  Ricci Research (@ricci_nov) reported 56 minutes ago

  @kimmonismus @XIVIX_134 Top-down GTA clone is the new "draw a pelican on a bicycle" — a benchmark that looks impressive precisely because a thousand tutorial repos already solved it. Wake me when a mystery checkpoint one-shots something with no prior art on GitHub.

• 
  Toufiq Qureshi (@Toufiq651) reported 58 minutes ago

  Day 1 of building Interview yaar🚀 Tech hiring has a measurement problem. We say we want engineers who can design systems, reason about trade-offs, and debug production. Then we test them on whiteboard DSA puzzles they will never write again. So the loop looks like this: → Company asks Leetcode Hard → Candidate grinds 6 months of patterns → Candidate gets hired → Candidate can't debug a race condition in **** We're not measuring bad engineers. We're measuring the wrong thing. Here's my bet: The best interview signal already exists. It's sitting in the candidate's GitHub. Their architecture decisions, their trade-offs, the shortcuts they took at 2am and never cleaned up. So I'm building Interviwyaar— an AI interviewer that reads your actual repository, understands how it's built, and interviews you on YOUR code. Not trivia. Your code. Over the next 30 days I'm building this completely in public. You'll see: • Why I split the backend into Go + Python • How I beat GitHub's API rate limits for free • A race condition that let users bypass billing entirely • A voice interview feature with low TTS-to-STT latency • Every bug, including the embarrassing ones Follow if you like backend engineering with the messy parts left in. #buildinpublic #golang #ai