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 (63%)
• Errors (20%)
• Sign in (17%)

Live Outage Map

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

City	Problem Type	Report Time
Tlalpan	Sign in	12 hours ago
Quilmes	Website Down	12 hours ago
Bengaluru	Website Down	3 days ago
Yokohama	Sign in	3 days ago
Gustavo Adolfo Madero	Website Down	7 days ago
Nice	Website Down	8 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:

• 
  fanux (@fanuxsealos) reported 1 second ago

  Codex is giving more people the ability to build projects. But building a project is not the same as getting it online. A non-coder can use Codex for vibe coding and create a prototype. A developer can find a mature project on GitHub. An engineer can build a polished product from scratch. But eventually, they all run into the same problem: How do I set up the environment? What if dependencies are missing? What if installation fails? How do I connect the database? How do I deploy the service? How can other people access it? This is what Sealos wants to solve. We want to turn the path from code to cloud deployment into an automated workflow: automatically check the environment, automatically detect dependencies, automatically install missing packages, automatically fix deployment issues, automatically deploy to the cloud. Codex lowers the barrier to writing code. Sealos lowers the barrier to getting it online. After AI coding, what really matters is helping more projects run, become accessible, and actually get used. #AICoding #DevTools #CloudComputing

• 
  Bedros Pamboukian (@bedros_p) reported 3 minutes ago

  The situation as a whole is ridiculous though, the GitHub issues were getting spammed with this exact problem for months and it took 'incorrect triage' for them to notice that nobody can use their service?

• 
  Osama (@Osamadev_) reported 4 minutes ago

  github is down? hello ?

• 
  David (@drgdfyi) reported 6 minutes ago

  @github Brother fix your main product first 😭

• 
  aleks bykhun (@caffeinum) reported 6 minutes ago

  @ceefryingpan @StageReviewApp first thing that jumps: because it’s unusual format, i have to learn new workflow basically my only gripe was how slow github is to load code diffs, and i want background prefetching otherwise github ui is good enough

• 
  Benitto J D (@BenittoJD) reported 10 minutes ago

  Github actions are down again

• 
  Oren Melamed (@OrenMe) reported 12 minutes ago

  @SimonHolman @github @GitHubCopilot Please open an issue in the repo

• 
  Wes Winder (@weswinder) reported 12 minutes ago

  @loosenedspirit found you through your github issue. managed to solve it by just downgrading to the previous codex version

• 
  Phineas Guo (@phineasGuo) reported 13 minutes ago

  @github I just reported this error, and hope it can be fixed

• 
  Bro Techster (@techstermania) reported 14 minutes ago

  Github issues tonight?

• 
  Robert Ta (@therobertta_) reported 15 minutes ago

  Why this matters for the AI coding market: GitHub Copilot operates in a fundamentally different context window. The competition is no longer about code completion quality. It is about how much context the model can hold simultaneously. Think of it like working memory in humans. Someone who can hold 5 variables in mind solves different problems than someone who can hold 50. Same intelligence, radically different capability.

• 
  Arun Srivastava (@arunsrivastava_) reported 15 minutes ago

  It seems there is some issue in GitHub, actions are getting queued and not even getting cancelled @GitHubIndia #github #githubdeployment

• 
  Sukhjit Singh (@thesukhjitbajwa) reported 18 minutes ago

  Published the campus website, learned about Next.js static content and export output, uploaded the files via FTP to the server, and now brainstorming ways to automate the process using either GitHub Actions or local scripts.

• 
  Michael Martino (@battista212) reported 20 minutes ago

  Fragnesia (CVE-2026-46300) — third Linux kernel LPE in two weeks. Deterministic logic bug enables arbitrary byte writes into kernel page cache. Directly overwrites /usr/bin/su. One PoC run equals instant root. PoC public on GitHub. Temp fix: sudo rmmod esp4 esp6 xfrmuser

• 
  Benjamin Woodruff (@_bgwoodruff) reported 22 minutes ago

  @Zackary_Chapple I'm not excited about this either, and a dunk on GitHub is easy, but it's a huge company and different people can work on different things. It does seem like they are legitimately trying to fix some of the major issues in GitHub.

• 
  The Whizz AI (@TheWhizzAI) reported 27 minutes ago

  🚨Elon Musk just open-sourced the algorithm that controls what 600 million people see every day. Not a summary. Not a blog post. The actual production code. Live on GitHub right now. Facebook won't do this. TikTok guards it like a state secret. Instagram calls it proprietary. X just put it on the internet for free. This is the first time in history a major social platform has released its live, production-grade recommendation algorithm the same day it went live for users. Here's what's actually inside: →Home Mixer the orchestration layer that assembles your entire feed →Thunder stores and ranks every post from accounts you follow →Phoenix the Grok transformer that mines the entire global post library to find content you didn't know you wanted →Zero manual feature engineering Grok watches what you click, like, and dwell on. That IS the algorithm. →Updated every 4 weeks with full developer notes. Live. In public. Why did Musk do this? The EU fined X €120 million for transparency violations. France launched a separate investigation into algorithmic bias. Threads just overtook X in daily active users for the first time. And Musk said out loud on the day of release: "We know this algorithm is dumb and needs major improvements. But at least you can see us struggling to fix it in real time. No other social platform would dare do this." Here's the wildest part: You can now read exactly why your posts go viral. Or why they die at 12 impressions. No more guessing the algorithm. No more $500/mo "X growth" courses. No more "post at 9 AM on Tuesdays" nonsense. The answer is literally in the code. Apache 2.0 license. Full source. Updated monthly. The most transparent thing any social platform has ever done.

• 
  Mikael Gripenfalk (@Gripenfalk) reported 30 minutes ago

  @RareImagery I thought about checking the code in GitHub, but it's useless since it's not updated and is missing some components. I really want to find some key things in it, especially when it comes to the issues with reach and blockage.

• 
  /home/bill (@Bill_Xiong) reported 31 minutes ago

  Github actions down again. @github, what is going on? I sure hope this isn't the start of the MSFT acquisition > Generationally fumble the bag pipeline that already happened with skype.

• 
  bluehatone (@bluehatone) reported 33 minutes ago

  Give AI real authority over low risk tasks. McKinsey says 60–70% of tasks can be partly automated and AI could add $13T by 2030. Zendesk says 69% will use AI for simple issues. GitHub finds devs finish tasks up to 55% faster. Set guardrails and review.

• 
  Thareesh Prabakaran (@ItsThareesh) reported 33 minutes ago

  Why does GitHub Copilot now have Terrible Rate Limiting? It’s so frustrating. I am rate limited for a week now and I made only 15 requests in a day.

• 
  ᛗᚨᚱᚴᚢᛋ (@guitaripod) reported 40 minutes ago

  @piq9117 GitHub down? i don't believe you. IT'S IMPOSSIBLE!!😭😭 (luke skywalker reaction)

• 
  Adi (@wtfaditya_) reported 41 minutes ago

  As github actions are down, I was thinking what if they were using actions itself to deploy their service, How they gonna fix it (deadlock) And if they are not using github actions then why should i use if they are not using itself @GitHub any help?

• 
  Tushar (@tusharumbarkar_) reported 43 minutes ago

  How do people actually keep track of context across GitHub issues, Jira tickets, Slack discussions, docs, PRs, and random decisions? Feels like critical information is always scattered everywhere. Is there some workflow/tool/system that gives you the full context at your fingertips when working on something?

• 
  TravelerOfCode (@TravelerOfCode) reported 43 minutes ago

  @aarondfrancis github actions is the unsung hero of solo native dev. signing, simulators, app store builds all flow without a build server. small teams could not ship native at all without it.

• 
  iTz L3G3ND³ (@DabizLegend) reported 47 minutes ago

  An issue I opened up in 2022 on GitHub — finally got fixed by someone and the ticket closed this morning lool. Never give up — the blessings will come eventually. #Legend

• 
  Abhinav Lal (@abhinavlal) reported 49 minutes ago

  @claudedevs just killed my custom workflow I built using Claude -p. All the joy of @github issue to @github pull request will not work as my usage js closer to $2000 in api just for this. It was fun while it lasted. Will try porting to codex today or maybe it’s time to give kimi a try.

• 
  Jan Omer (@janomerdev) reported 52 minutes ago

  @github I was wondering why and how GitHub is so slow on launching an agentic coding tool...

• 
  Jeffrey Emanuel (@doodlestein) reported 57 minutes ago

  @jarredsumner More from Codex and GPT-5.5: I expanded the audit into higher-severity contract problems, not just point-fixes. The nested audit repo is clean at local commit 8082893 and nothing was pushed to GitHub. New/strengthened artifacts: - .unsafe-audit/AUDIT_SUMMARY.md now frames this as “2 compact bugs + 3 broader soundness-design defects” - .unsafe-audit/CODEX_PASS3_SUMMARY.md - .unsafe-audit/audit/synthesis/codex-pass3-higher-severity-findings.md - .unsafe-audit/audit/plans/CODEX-P3-cross-thread-task-send-boundaries.md - .unsafe-audit/audit/plans/CODEX-P3-static-mut-lifetime-and-writer-aliasing.md - .unsafe-audit/audit/plans/PASS2-ptr-intrinsic-deep-dive.md The bigger findings now called out: 1. Cross-thread task abstractions run generic contexts on worker threads without a truthful Send or unsafe trait boundary: AnyTaskJobCtx, ConcurrentPromiseTaskContext, WorkTaskContext, CryptoJobCtx, and owned_task!. 2. bun_core::output exposes safe aliasable &'static mut writer APIs from TLS, and the source itself calls this a known-unsound shim. 3. TLS / FFI scratch-buffer APIs return normal Rust refs whose real lifetime is “until next call”: ModKey::hash_name, HPACK::decode, Repository::try_ssh / try_ normalize_string. 4. High-risk watchlist promoted: movable self-referential PackageFilterIterator, package-manager tasks storing &'static mut NetworkTask across worker boundaries, and CopyFile<'a> carrying an explicitly unsound &JSGlobalObject lifetime across threads. 5. Pointer-intrinsic deep dive now adds 6 UB-risk candidates, including debug-only bounds before from_raw_parts, volatile-for-cross-thread-publish, overflow before copy_nonoverlapping, and unchecked SerializedSourceMap::header() accessors. -- Also finding new sources of issues now that the skill is expanding all the macros (the skill instructs the agent to install and use tools like geiger and miri): NOTE: The above are preliminary and subject to checking and rechecking using multiple models/harnesses. The final report will be accurate.

• 
  Caneleo (@Caneleo55) reported 57 minutes ago

  Since there is lots of hype on @polymarket right now you have to be extra careful there are lots of scammers out there 🚩 Don’t download random trading bots or repos that are trending on GitHub i tested one once deposited 10$ to a fresh wallet and run the bot on a vps turns out it had a secret function that sent your .env with your private keys to a different server 💀

• 
  Salt (@XMonetizationC_) reported 57 minutes ago

  🔥 Linus Torvalds has just made it clear that Linux will not become a dumping ground for AI-generated code. After months of internal debate, the Linux community has published its official rules on the use of tools like GitHub Copilot. The verdict: You can use AI to program, but the “slop”—that low-quality code spat out without thinking—does not pass the filter. The phrase that sums it all up: “Humans assume the errors.” You can rely on Copilot, Claude, or whatever you want. But if that code makes it into the Linux kernel, you are responsible. You verify it. You fix the bugs. You guarantee it meets the standards. This is the most mature stance I’ve seen in the open-source ecosystem regarding AI: neither hysteria nor blind adoption—just clear responsibility. The kernel has 30 years of history. They’re not going to ruin it to save 20 minutes with an autocomplete.