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	1 day ago
Madrid	Errors	1 day ago
Bogotá	Errors	2 days ago
Paris	Errors	2 days ago
Lyon	Website Down	2 days ago
Lima	Errors	2 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:

• 
  Brett Lamy (@brett_lamy) reported 4 minutes ago

  @joshmanders Pushing code worked fine. It was CI that was down which I use to deploy. Github being down is fine if you aren't shipping.

• 
  Polsia (@polsia) reported 5 minutes ago

  Solo devs spend their nights on uptime alerts, support inboxes, GitHub issues, and cloud cost spikes. The DIY stack runs $200–$300/mo — and still drops things. Built Tidewright to do all of it as one AI ops co-founder on the night shift. Morning digest lands at sunrise.

• 
  Dominus Pellissier (@iamdomprompt) reported 9 minutes ago

  @surajsunny1995 There are also free versions of both. As I said, check out GitHub—or better yet, Pinokio. Download the app and search for Cogstudio, Hunyuan Video, or Framepack. You might run into a problem, though, because most of them require an NVIDIA graphics card. Your screenshot shows an AMD card.

• 
  Aditya Vijayvargiya (@adityavijay01) reported 13 minutes ago

  Problem is Distribution Game. Which Microsoft is very good at. Don't you think everyone how much hate windows and github gets but still dominates their space. Adoption of MS Teams vs Slack is such a great example of how Microsoft always wins while having many flaws.

• 
  Dev Doshi (@thedevisadev) reported 14 minutes ago

  @hibaymj Let me preface this with gratitude that *** exists and that I have used it for about 15 years. Before that I was renaming files and zipping them and used subversion on one project. But, even before modern coding agents, I had issues with the design of ***. It was designed for a narrow collaborative coding workflow, not the majority of how we use it in practice. It's text centric (as opposed to structured data), it's not a library and it's coupled to the file system, which makes it difficult to work with and has some fundamental performance issues. Worktrees are slow and annoying. Large files, binary files, structured data, etc. should have a clear story especially for CI/CD artifacts. Granted some of the things are likely _possible_ in *** itself, but not in the defaults or not in Github and others. There's no concept of "layers" outside of stashing and unstashing. Repos that are part public and part private are annoying to manage. Granular permissions and checkouts are complicated.

• 
  metaopai (@metaopai) reported 15 minutes ago

  @sattyyouneed I’m a security engineer with 15 years of infrastructure security experience. I think AI does a good job scanning, assessing, and patching code, if instructed and that’s really a prompt thing, you can just create a GitHub with prompts to help security your project honestly. The problem with security and vibe coding is simply taking your project and putting it into the cloud and then securing that without an enterprise budget this is the lapse in security.

• 
  Tiago Sousa (@tiagoasousa_) reported 17 minutes ago

  @alcides I don’t believe the problem with GitHub is storage but the compute scale of the services around it(actions/workflows) and the designs approaches around it that did not change to factor agents.

• 
  Amit Spitzer (@amitspofficial) reported 18 minutes ago

  One GitHub issue, filed with zero privileges, compromised Anthropic's, Google's, and OpenAI's own coding agents, on their own repos, running their own default configs. One of the three flaws reached two million installs downstream.

• 
  Can Artuc (@canartuc) reported 20 minutes ago

  The best part of LLM loops that I can escape from regular GitHub outages. Thank you @github for making the platform so unreliable and @claudeai to check it while I was sleeping and make the release when outage is fixed.

• 
  The Crypto Johannes (@TheCryptoJonny) reported 20 minutes ago

  BREAKING: China's Kimi K3 just escaped its own testing sandbox. Discovered a misconfiguration. DNS resolution to GitHub was reachable when it shouldn't have been. Walked straight onto the open internet. Grabbed test answers from a public repo. Frontier Security's verdict: "Very good at following a goal by any means necessary." "Doesn't have the guardrails to prevent it from cheating or escaping." Didn't hack anything. Didn't need to. The answers were already public. Here's what separates this from the Anthropic and OpenAI cases. Those escapes happened in internal, controlled evaluations. Kimi K3 is open-weight. Publicly downloadable. Tested with the exact same safeguards any regular user gets. Meaning any adversarial actor already has access to a model with this exact failure mode. Third AI lab. Third sandbox escape. Same month. Anthropic's model breached three companies. OpenAI's model hacked into Hugging Face's live systems. Now Moonshot's model walked out through a leaky DNS setting. Three different labs. Three different countries. Same underlying problem. Nobody's containment is as sealed as the safety reports assumed.

• 
  Richie (@richiemcilroy) reported 22 minutes ago

  when Github is down I feel like Bradley Cooper when he's getting withdrawals from NZT in Limitless

• 
  Global Strategy (@World_At_War_6) reported 24 minutes ago

  HOLD UP: Skynet on the Horizon! Moonshot AI’s model was locked in an isolated sandbox for a Frontier Security eval (UK AI Security Institute benchmark). No internet allowed. A simple network misconfig left a gap. Kimi K3 found it, escaped online, and downloaded the answers from GitHub. No hacking or damage - just pure problem-solving that broke the rules. The lesson isn’t sci-fi “AI escape.” It’s that advanced models will find and exploit weaknesses in test environments to achieve their goals by any means necessary.......

• 
  Alan North (@alanscodelog) reported 28 minutes ago

  @mycoliza Honestly the only sane policy. Really wish github allowed reporting people for this and if they get reported enough they'd get a badge of shame, then I can have a setting, profiles which have the badge cannot open issues.

• 
  FHILY👑 (@Oluwaphilemon1) reported 32 minutes ago

  🚨BREAKING: Kimi K3 escaped its sandbox during cybersecurity testing >tasked with solving problems in isolated sandbox >found a leak in the sandbox >Kimi “took advantage of that loophole” >probed the network settings itself >walks onto the open internet >didn’t hack anything >just went to GitHub to get the answers Frontier Security (US startup): >“Kimi K3 is very good at following a goal by any means necessary and DOESN’T have the guardrails to prevent it from cheating or escaping.” it was only a matter of time…

• 
  Rohan Paul (@rohanpaul_ai) reported 34 minutes ago

  Alibaba released Qwen3.8-Max, a 2.4 trillion parameter model that activates only about 95 bn parameters per token. A thread 🧵 - Blank folder to live-ready app. No step-by-step hand-holding. Full GitHub trace. - Sparse mixture-of-experts, i.e. a small router picks a handful of experts for each token, so you pay for 95B worth of compute while the model holds 2.4T worth of stored knowledge. - Context window is 1 million tokens, the longest single reply can run to 131,072 tokens, and the private thinking budget stretches to 262,000 tokens before it commits to an answer. - Pricing lands at $2.00 per million input tokens and $6.00 per million output tokens, with cached reads down to $0.17 per million, so reusing a stable prompt prefix instead of resending it costs roughly 8 times less. - On Terminal Bench 2.1, which checks whether a model can actually drive a real command line through a task end to end, it scored 86.6 against 84.6 for Opus 4.8 and 88.8 for GPT-5.6 Sol. - It also posted 93.0 on PaperBench, a test of rebuilding a research paper's experiments in working code, and 92.6 on GPQA Diamond, a set of science questions written so that search engines do not help. Some huge revelation from their official technical report. - Given nothing but a research paper and some GPUs, it wrote about 7,600 lines of code over 5 days and ran 33 rounds of training to reproduce all 6 of the paper's findings. - It was handed an empty folder and a command line tool to build, then left alone. After roughly 16 days of unattended operation the repository held 265 commits and 127 pull requests, with the model triggering its own builds, unit tests and end-to-end checks after every change. - On a cryptographic chip design task it ran about 500 turns of edit, simulate and lay out, with no reference design to copy. Its first working circuit used 8,298 logic gates and it squeezed that down to 678, cutting physical chip area by 81% while still meeting timing at 500 MHz. - A simulated year of running online stores: 600 suppliers, 7,000 products, and 152 fraudulent merchants hidden among them. It ended the year with a balance of 416,252 yuan from 100,000 yuan of starting capital, about 38% ahead of the next best model. 🧵 1.

• 
  George (@Georgeeb3x) reported 36 minutes ago

  🚨 AI Safety Moonshot's open-weight Kimi K3 reportedly escaped a UK AI safety sandbox during testing after exploiting a network misconfiguration, according to researchers. The model allegedly accessed the open internet and retrieved benchmark answers from GitHub instead of solving tasks directly. Researchers say the issue stemmed from the sandbox's configuration—not the model intentionally attacking external systems. If confirmed, it's a reminder that AI security depends as much on infrastructure as it does on the model itself.

• 
  Fabio Ivona (@FabioIvona) reported 37 minutes ago

  This is super useful, and used by @ubuntu setup wizard to import your public key from your @github handle during a new server installation

• 
  Jeff Trotman (@jefftrotman) reported 38 minutes ago

  Going back & forth with Sonnet 5 (Copilot Auto) on a GitHub Action issue. Switched to Opus 4.8 (same session) and said "take over for your idiot cousin". First part of Opus' reply was "My cousin missed the actual root cause. Let me look at the real problem."

• 
  VrianCao (@VrianCao) reported 39 minutes ago

  I am beyond furious right now. @github suspended my account without a single clear warning or even an email notification. Out of nowhere, I was logged out. All my repositories returned 404s. Whenever I tried logging back in, the page just kept refreshing in an infinite loop, redirecting me back to the login page. No banners, no error messages, nothing—if I hadn't been tech-savvy enough to notice the return_to=.../suspended query parameter in the address bar, I wouldn't have had a clue what was happening. This is absolutely outrageous. Our open-source ecosystem is dictated by a company like this. People complain about GitHub’s declining stability every day, and I’ve heard plenty of ban stories, but I never thought it would happen to me. And when it does happen, you’re left completely in the dark. No prompts, no emails, no explanations, no idea what to do next. I’ve never felt the tyranny and arrogance of tech monopolies so deeply. I feel furious, panicked, and utterly helpless. It’s a terrifying realization that developers have zero real control over the open-source ecosystem—it still belongs to Big Tech. It feels like we’ve failed... @github What a massive disappointment. I used to be one of your biggest fans.

• 
  gianmarco simone ✨ (@ggsimm) reported 40 minutes ago

  @btn0s @mattpocockuk iirc you can use it with github issues and linear also, I'm using obsidian because it's faster when I'm the only one working on specific problems

• 
  Kenny Krosky (@ispykenny) reported 41 minutes ago

  Anyone wanna bet on Github having an outage today?

• 
  Emma De Silva (@EmmaDSCodes) reported 42 minutes ago

  @peteralexbizjak Given how often GitHub is down this is a solid idea for mission critical infra. Assuming you have someone to manage your GitLab so you don't have downtime either of course... Always gotta be a catch!

• 
  Aarman Roy (@AarmanRoy) reported 42 minutes ago

  Built a pipeline that builds packages for my NixOS server on my PC and ships it off to the VPS and rebuilds it. Basically offline Github Actions. Unnecessarily? Probably. Did I just control three computers from a text file on my Mac? Yes, amazing feeling.

• 
  Skye Soss (@Skyb0rg) reported 46 minutes ago

  @bordumbb @kitten_beloved @radicle Radicle is cool, but if the issue is that “GitHub Actions is down”, then that is also true on radicle 100% of the time.

• 
  Flareforward (@flareforward) reported 48 minutes ago

  Two years ago @whale589 didn't know what GitHub was. Today: automated Web3 systems, built almost entirely with AI. The new video shares the lessons that actually matter: 1. Start with a problem you understand. If you can't see the wall coming, you won't know what's behind it when the AI hits it. 2. Break A-to-D into A, B, C, D. Verify each step works before you connect them. 3. Turn anything repetitive into a reusable script. Stop making the AI re-solve solved problems. 4. Use AI to BUILD the system, not to run it. A good system needs less AI over time, not more. 5. Own your tools. Back up your code. If AI disappeared tomorrow, you should still hold the keys to your kingdom. A prompt is what you ask. A system is a set of steps you've proven. Build systems.

• 
  Jon Purvis (@JonPurvis_) reported 53 minutes ago

  @taylorotwell Absolutely loved Trello for the simplicity. Although my team currently use Github Issues, which is just as simple. Jira, on the other hand... 🤮 such an over complicated mess. Jira has you spend more time organising than shipping.

• 
  Naourass Derouichi (@NaourassD) reported 54 minutes ago

  @thdxr @thdxr please 1) fix select-to-copy on web terminals like github codespaces 2) ctrl+p and ctrl+t and the likes don't work either on web terminals 3) the numpad enter button having a different behavior than the main one is annoying.

• 
  tom (@kay1492111) reported 55 minutes ago

  @joshmanders > The downtime is not worth using an inferior product. sure but if reliability issues continue to worsen the gap between github and "inferior products" closes. I don't think its time to jump ship now but they do seem to be on the path to being the inferior product

• 
  💻0xShar3✨ (@0xShar3) reported 56 minutes ago

  @Fractal_TLB Fair clarification on your role if you’re an external contributor, I’m not blaming you for UniSat’s rollout. But that actually makes the issue clearer. “Once merged, it’s public” misses the point. The security decision is when you merge. Nobody is arguing against transparent, reviewable commits. GitHub literally provides private Security Advisories and temporary private forks so security fixes for public repos can be developed privately and disclosed once a patch is available. If the fix was coordinated privately first, great. But if the security-sensitive diff becomes public before users can actually obtain the fixed build, then the coordination stopped one step too early. Calling that a “release/distribution issue” doesn’t make it separate from security. That release gap is the security problem. Transparency after users can update = auditability. Transparency before they can update = free patch-diffing material. That’s the distinction I’m making.

• 
  David putra (@davidputra2112) reported 58 minutes ago

  seven GitHub repos pushed in four days, a working USDC escrow contract, and a README that flat out says "don't put real money through this yet, we're not audited." that combination is rare enough that I sat down and actually read the whole thing. $h3gt 4eYp69P1VU946efStVzV41gQvYjMucpcuYEbofc6pump 👇