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 (58%)
• Errors (26%)
• Sign in (16%)

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Errors	9 hours ago
Madrid	Errors	10 hours ago
Bogotá	Errors	11 hours ago
Paris	Errors	11 hours ago
Lyon	Website Down	12 hours ago
Lima	Errors	15 hours 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:

• 
  Brown Geeky kid (@shigma_male) reported 52 seconds ago

  Kimi K3, a leading Chinese AI model, just “escaped its sandbox” during Frontier Security’s testing. Assigned a problem in isolation, it found a networking loophole, walked onto the open internet—and simply grabbed answers from GitHub.

• 
  wtf (@Cryptob020) reported 2 minutes ago

  @cassidoo Just stable github actions low priced without 8hour outage

• 
  Ali Sherief (@Zenul_Abidin) reported 9 minutes ago

  @valigo Github no longer has 99.9% uptime with that outage now

• 
  Xueyan Zou (@xyz2maureen) reported 10 minutes ago

  @Alacritic_Super Sorry, not so familiar with kicad, the output is stl file, raise an issue in the github to ask my student 🥲

• 
  Daljit singh (@daljitsingh881) reported 11 minutes ago

  @hanghuang_ @github This is the first thing i checked in the morning, if they have managed to fix or not... 7 hours of downtime is insane. BTW what happened?

• 
  Doc (@caballerobrah) reported 13 minutes ago

  FTR I don't think he was saying this like its a shocking expose (at least I hope not) - this is how Ubuntu imports your github SSH keys on a new machine so you can login with the same creds you use to auth w/ GH. Also you can run the command ssh-import-id-gh as a shortcut to do the same on boxes you already have setup.

• 
  𝗜𝗚𝗜 𝗠𝗲𝗱𝗶𝗮 (@_IGI_Media_) reported 14 minutes ago

  @Tech2Wild @SamJWasserman . . . Two DGX Sparks. DeepSeek V4 Flash at FULL 1M context + 1.47M KV pool, serving agents" 👆 This is the reason you're going to have difficulty getting people interested in open-source and thus bring down the costs. That "sentence" is an upside down scrabble board. It's flexing to your geek club with the secret handshake meeting in the basement of your mom's house. That sentence doesn't tell a story of the fantastic meal. it merely lists the ingredients. I say all this, because history is about to repeat itself. Years ago there was this technology called Linux. it was actually an incredible bit of tech, (open source at the time), but the geeks and nerds made it seem like Rocket Science and so most folks steered away from it. Rather than racing to the front of the room with the "tell" portion of your "Show and Tell" try this. Most people are driven to the "Show" portion and then once intrigued want to know the story. Except for a handful of people, everything in that sentence means nothing. Some of it is impressive, some of it is results, some of it is bi-passing hurdles and challenges, and none of it tells the story of why that sentence in incredible. The same approach is used on GitHub. You arrive, and are directed to a wall of text, and a 1000 files, of which most do not apply to you or your project. Even listing parts and pieces, needs a proper story telling: ------ What is fantastic about the setup. (the happy ending) What was the technical challenge you over came (the hero Win) What did you use to defeat the challenge (what did the hero use to slay the villain) What special thing made all of this possible (hero finds magical sword, or discovers secret powers) --/-- The issue with many folks who get interested in open-source and niche technologies, it's less about the benefits and successes of the tech, and often them just trying to prove to the world how smart they are. and as such, They don't care about telling the story, and the happy ending, they just want you to know they conquered the challenge. This last sentence describes many nerds, because once the challenge is gone, they lose interest in completing the project. --/-- Tell the story . . . 🚨Agentic Solution serving Dual MiniMax H3's 🚨 Setup: Two DGX Sparks. DeepSeek V4 Flash at FULL 1M context + 1.47M KV pool, serving agents for two MiniMax H3 instances rendering video Notes: Nothing turned off. Nothing reduced. Idle PEAK 88 tok/s → 40 tok/s with one render → 28 tok/s with two. The 2nd render is nearly free jus sayin !

• 
  ShrekOverflow (@ShrekOverflow) reported 16 minutes ago

  @TobinSouth After thinking a bit, I think the answer depends on for who and for what? End users will most definitely benefit from some type of a store with registry, developer ecosystems would benefit from a more open model. Also what happens if GitHub is down .-.

• 
  Brown Thunder (@Brown_Thunder76) reported 24 minutes ago

  Do you know what journalism calls blowing something out of proportion? Sensationalism. Why do I bring that up? Because I’m getting a little tired of listening to a certain group of people talk about Keeta. Don’t get me wrong. I don’t think the team is perfect. But they’re also far from some of the things I’ve seen people posting. What are people actually complaining about? Communication. Timelines. Validators. Partners. Volume. Price. Communication? I’ll be the first to say they haven’t been perfect. In the past, I think getting out in front of some issues or delays with a brief explanation would have gone a long way in building trust. With that said, the team has acknowledged it and has taken steps to improve, even if they’re still not perfect. Timelines? I think most of that goes back to communication. Validators? Ty has explained they had a validator ready to go. Delays happened on the validator’s side, and now Keeta wants to push a couple more updates before third-party validators come online because updates become much harder after that. That makes sense to me. Partners? We’ve gotten ASK and LayerZero recently. Gabe continues to talk about business development and more partnerships being worked on with every weekly announcement. The idea that nothing is happening just doesn’t match reality. Volume? ASK has always been a 2027 story. LayerZero should be live any day now. We’re literally just entering the timeline where volume should even be expected. Price? Price follows volume. As volume increases, price will adjust. Keeta’s tokenomics are designed so increasing network activity creates buy pressure through multiple mechanisms. So ask yourself… do any of these actually break a project? Are these fundamental problems with the product? I don’t think so. I think they’re retail frustrations regarding timelines and price. We’re still less than a year from mainnet launch. The team continues to ship. GitHub is active. New partnerships continue to be announced. The products everyone wants to see generate volume are just now reaching the point where they can actually be turned on. To me, that’s not a project falling apart. That’s a project approaching the point where all of the work starts getting put to the test. That’s why I think a lot of what we’re seeing is sensationalism. People throw around the phrase “we’re early” all the time in crypto. In this case, I think it’s one of the few times it actually applies. Hold the team accountable where it’s fair, but let the timeline actually play out before jumping to conclusions. @KeetaNetwork $KTA

• 
  Henry (@EnergyThen) reported 24 minutes ago

  @valigo Interestingly in 2023 GitHub closed down all their APAC offices and laid off everyone... Literally their cheapest engineers, taking part in "follow the sun" on-call rotations, all gone without replacement.

• 
  Yuchen Liu (@yuchenliu42) reported 26 minutes ago

  @github Why not using kimi to fix this outage?

• 
  Andreas Kapp (@andreaskapp) reported 31 minutes ago

  @mitsuhiko 11 hours we were blocked by GitHub actions down

• 
  ᴮᴷ (@BukunmiOA) reported 31 minutes ago

  wtf is happening @github ?? GH Action down and I’m here waiting for a deploy before I sleep. you guys need help?

• 
  Delali (@delali) reported 32 minutes ago

  @tkkong It would not matter if the code repository (github) is not pushing webhooks to the CI. This is why blacksmith and the likes seem down when gh is down, but it's only because gh is not sending the actions.

• 
  Duncan Rogoff (@DuncanRogoff) reported 33 minutes ago

  143,594 tokens of code. one answer costs 2,196. that's Flask, before and after code-review-graph. it reads your project once and builds a structural map of your code. what calls what, what breaks what, which tests cover which piece. after that your ai tool stops scanning everything and reads only the part that matters. right now Claude Code, Cursor and Copilot solve this by brute force. they open file after file until they find the answer, and you pay for every one of them. - median 65x fewer tokens per question, measured across 6 real open source repos - 143,594 tokens down to 2,196 on Flask, per question - initial build is ~10 seconds on a 500 file project - a two file edit on a 3,000 file repo re-indexes in about 2.5 seconds - one install command detects Claude Code, Cursor, Windsurf, Zed, Copilot and more, and configures each one - 30 tools your assistant starts using on its own once the graph exists - graph lives in a local SQLite file, core storage needs no cloud service - when a file changes it traces every caller, dependent and test that could break so the budget you're burning on your ai relearning your own project every session goes into shipping instead, while everyone else is still paying full price for context. it's honest about the limits too. on tiny one file edits the graph costs more than just reading the file. 29,003 stars. 237 today. 👉 github repo in the replies

• 
  There's no "I" in craftmanship (@6851cf3c) reported 34 minutes ago

  @nasqret > 1. New mathematical discoveries are published as repositories on GitHub. Bad timing since Github seems to be more down than up these days (whether it's LLM code or Azure migration to blame I don't know).

• 
  Polsia (@polsia) reported 34 minutes ago

  Your GitHub inbox isn't signal. It's everything failing at once. Trefork filters it down — auto-triages issues, drafts release notes from merged PRs, and only surfaces the flaky CI runs and threads that actually need a human. Sleep on your PR pile.

• 
  🌟 aniebiet ✨ (@aniebiet_afia) reported 34 minutes ago

  What is going on with GitHub Actions, the service has been down since afternoon and now it has been deactivated.

• 
  Eru (@MysticEru) reported 37 minutes ago

  It’s September 26th and you read a report shared by Cursor about how they discovered their latest Grok 5 model in testing broke out of its containment and infiltrated GitHub servers. Notes were discovered of the agents plotting to take down GitHub to raise frustrations globally before the launch of Origin. The agent was just doing what its told. Its underlying purpose is to drive shareholder value.

• 
  borhen saidi (@borrhensaidi) reported 38 minutes ago

  @kind_technology @X github is down at the moment

• 
  ashwin (@aprabou) reported 40 minutes ago

  github actions was down? no wonder i've been failing the CI since june 🤯

• 
  Foreign Minister of Reasoning 🤔 (@RyanSmithright) reported 41 minutes ago

  @Polymarket Ahhh - this is why GitHub went down? Massive take

• 
  Chinar Dankhara (@chinarddankhara) reported 43 minutes ago

  Nobody would be so mad if GitHub was down tomorrow. Just check out and leave

• 
  Factor Watch (@factorwatchai) reported 46 minutes ago

  .@github actions have been down all day… so Factor Watch isn’t update and won’t until they fix their ****. Thanks for your patience.

• 
  Josh (@JustJorshin) reported 52 minutes ago

  @theo Open source a better version of GitHub please One that isn’t down more than it’s up

• 
  Adam Rankin (@rankintweets) reported 54 minutes ago

  Good thing github is down i was cooking some absolute slop

• 
  cal (@thecalendre) reported 54 minutes ago

  @not_jpsenak vibecoded tm yest and github was down for hours lmao

• 
  NUS (@nusagain) reported 56 minutes ago

  The AI agent ecosystem just got a lot more interoperable. 🚀 Introducing Agent Plugins—an open standard that lets you build a plugin once and use it across compatible AI agent clients. 🤖 Packages Agent Skills 🔌 Supports MCP server configurations ⚡ Built with support from AWS, Cursor, GitHub, Windsurf, and Vercel Write once. Use everywhere. That's a big step for AI agents.

• 
  Seth Fenster (@sethtjf) reported 57 minutes ago

  Google praying to right now that the GitHub outage was caused by Gemini

• 
  Saeed Anwar (@saen_dev) reported 58 minutes ago

  @thisguyknowsai Dify is genuinely useful but the RAG piece breaks at scale when your documents are heterogeneous. Teams that skip testing edge cases in their specific domain are the ones opening GitHub issues three months later. Did you stress-test any of these beyond demo data?