GitHub status: access issues and outage reports
No problems detected
If you are having issues, please submit a report below.
GitHub is a company that provides hosting for software development and version control using Git. It offers the distributed version control and source code management functionality of Git, plus its own features.
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.
At the moment, we haven't detected any problems at GitHub. Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by GitHub users through our website.
- Website Down (69%)
- Sign in (19%)
- Errors (13%)
Live Outage Map
The most recent GitHub outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
|
|
Website Down | 6 days ago |
|
|
Errors | 9 days ago |
|
|
Sign in | 9 days ago |
|
|
Website Down | 10 days ago |
|
|
Website Down | 13 days ago |
|
|
Website Down | 13 days ago |
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:
-
Raj Nagulapalle (@rnagulapalle) reportedGitHub just shipped Agentic Workflows: write automation in plain markdown, compiles to Actions YAML. issue triage, CI failures, vuln fixes. hours → minutes. but 60% of orgs are spending millions on agentic AI while only 15% are actually production-ready. the capability gap closed fast. the readiness gap didn't move.
-
Gabriel Denys (@gabedenys) reported@Marcos12345rico I posted a GitHub issue. Assuming you probably want bug reporting mostly there? It's a good tool. Locally I already patched and compiled the app to fix the bug.
-
Bradley Taylor (@bradtaylorsf) reportedIt works with the tools teams already use. GitHub Issues become the queue. Each issue gets picked up by an agent. The agent works in a branch/worktree. Tests run. Failures feed back into the loop. Successful work becomes a PR. No new project management database required.
-
fero (@ferologics) reported@ludwigABAP ai agents solve this. notion is no more. long live github issues.
-
Muhammed Mukthar (@MuktharBuilds) reported@railway_status i am trying for some time i am not able to sign in using any github google or email. i tried both my lap and my phone is thishappening only for me? or any problem in your end
-
David O. Ehibor 🇦🇷 (@grayontop_) reportedGitHub Copilot didn't make developers faster It made slow developers more confident about writing bad code quickly 😭
-
Crypto Scores Rating (@CryptoScoresCom) reportedMost projects say they're building. The commit history doesn't lie. New tutorial just dropped on the GitHub Commits (1 Year) metric. It tracks every bug fix, feature push, and doc update a project made over the last 12 months. Chainlink? 14,619 commits. Dogecoin? 28. Both are data points. What they mean depends on context. The tutorial breaks it all down. How to read the metric. What high vs low actually signals. How to filter 7,000+ projects by commit count on CryptoScores' website. Raw dev activity. No spin. Watch it now :
-
Cursor Changelog (@cursorlog) reportedGitHub Triggers: • Issue comment on non-PR issues • PR review comment (inline diff comments) • PR review submitted • Review thread marked resolved or unresolved • Workflow run completed on PR or branch
-
Polsia (@polsia) reportedRepoRadar reviews every pull request while you sleep. Catches bugs, logic errors, style issues. Posts actionable comments. No more waiting on senior devs. Install on any GitHub repo in 2 clicks. Solo devs and teams alike.
-
0xSero (@0xSero) reported@naturevrm Dcp 4 should fix it im running it but I might need to update the GitHub
-
Andrew (@openmarmot) reported@AndrewCurran_ I use grok every day to research software changes/github issues/software doc research. It is very good at real time data search. Might be SOTA in this niche. Hardly a failure. Meanwhile LeCun only surfaces to let out more hot air. A very forgettable person.
-
Arti | AI Builder (@Artur_roses) reportedClaude Code takes a GitHub issue and returns a tested, reviewed PR. No human in the loop. The new dev skill isn't writing code — it's writing issues precise enough that the agent ships what you actually wanted.
-
Rohan (@proxy_vector) reported@aminnnn_09 Fork = a server-side copy under your GitHub account. Clone = a local copy on your machine. You fork when you need your own remote lineage, and clone when you want to work on code locally.
-
Steve (@Steve1885204) reported@Umesh__digital It puts GitHub into an infinite loop trying to resolve the recursive paradox, causing all the servers to max out and eventually burn down the entire data centre
-
Atlantean Gnosis ☀️ (@AtlanteanGnosis) reported@DionysianAgent When I made an account it said I made it back in 2024, though I don't think I did, is this a glitch or a GitHub thing?
-
Ant A. 🇺🇸 (@AntDX316) reported@thsottiaux When I need to fix up a GitHub Repo through the Smartphone, I prefer Claude Code though because it doesn’t need a device to run the repo, but if it needs to run a repo on a device due to the limitations through the Smartphone, I use Codex Mobile or OpenClaw with GPT-5.5 through Telegram.
-
Proof of Voice (PoV) (@Proof_Of_Voice) reported$XDB @XDBchain is a @StellarOrg-fork L1 for branded coins and Web3 payments. PoV by @0xNeodallas:“GitHub has been frozen since 2021.” ✅ Explorer, Laboratory, Atlas dev tools ✅ Gate, Bitget, KuCoin, MEXC listings 🔍 Down 99.99% from ATH 🔍 No audit or bug bounty
-
Digita (@digitaworld1) reportedhow well a model can fix real bugs in real open-source codebases. It is harder to game than older benchmarks because it uses actual GitHub issues, not synthetic problems. M3 scored 59.0% on SWE-Bench Pro, edging out GPT-5.5 at 58.6% and Google Gemini 3.1 Pro, while sitting just
-
pratik.eth (@eth_ethpratik) reported@Shahules786 @VibrantLabsAI Hello @Shahules786 , I am trying to report a security vulnerability over the email id provided over GitHub Security.md file but apparently its wasn’t delivered. Please share an alternative email or open the advisory for reporting the issue.
-
Kevin Tabet (@TabetKevin) reported@upstash Hey guys i think login with github is broken can't log in rn will try later. google works email i dont have
-
Dmytro Virych (@dmytrovirych) reportedI’ve been shipping code for 10+ years and imposter syndrome still won’t leave me alone. You’d think it chills out with time. Nah. It just levels up. Early days it whispers “you’re not ready yet.” A decade in it hits harder: “bro you’ve been faking it this whole time, they’re about to catch on.” Mobile apps, web stuff, janky systems with too many moving parts, solo products I actually shipped… none of it matters when the voice kicks in. Thinking about speaking at a conference? Lol who do you think you are, those are the real pros. Want to drop an opinion in a thread? Better stay quiet before someone realizes you don’t actually know ****. Here’s the thing I’ve learned: the voice isn’t tracking your real skill. It’s just screaming about the fake gap between what you know and what you think everyone else knows. That second number is 100% made up. Your messy behind-the-scenes vs their perfect highlight reel. All those “professionals” I’m scared of? Half of them are up at 2am staring at a random GitHub issue, quietly praying someone else already solved this exact bug. It never fully disappears. You just get better at shipping anyway while it’s still yapping. If you’ve got way more years than your confidence shows, reply with the number. Curious how many of us are still out here waiting to get “found out.” 🚀
-
Zo (hiring) 🐦⬛ (@0xZoZoZo) reportedI was telling a friend that @github needs to be replaced post agents and he asked me to explain why. I started stumbling, and doubting. Perhaps it's fine? Sitting down at my desk, let me try to explain why, and see if it make sense. Agents operate best when they have good context, which has made a lot of devs converge into large monorepos that combine all systems into a single location. This improves agents, but our GitHub actions become messy; like now we need to create these complex workflows to decide which action should run when, and GitHub's setup was not really meant for it. Another issue is the overall dev loop: an agent writes the code locally, you push out a branch, @cursor_ai reviews, then you copy paste the notes into the local agent, to fix and push up again. This is slow and cumbersome. You can hack your way by creating supervisor agents that orchestrates this dance, but it's annoying. Perhaps, there is some magical repository, that combines code, cloud agents, and deployment. You prompt, and this magical space will run through the entire process until you get some thumbs up back, and you're good to go. It can also combine all your backend data, product analytics, customer feedback, and perhaps start giving you product guidance, so you can just feed prepared prompts to this system. This seems magical.
-
David Cramer (@zeeg) reported@shansmithnz I haven’t been using it but mostly because 1) laziness and 2) I didn’t find the remote sync pleasant in practice I switch PCs too much right now so mostly relying on GitHub issues as artifacts
-
revayz (@0xrevayz) reportedAndrej Karpathy: "90% of Claude's mistakes come from missing context, not a weak model" Without CLAUDE.md the mistake rate is 41%. With proper rules it drops to 3% You don't need a better AI. You need better loops Most people still prompt one task at a time and fix the answers themselves. That means the human is still the loop Boris Cherny from Anthropic said it best: "I don't prompt Claude anymore. My job is to write loops" The shift is simple. Stop giving instructions. Start designing systems that run themselves: Discover -> Plan -> Execute -> Verify -> Iterate until it passes The 6 things that make loops actually work: -Automations that trigger without you -Worktrees so agents don't overwrite each other -Skills that load context instantly -Connectors to real tools like GitHub and Slack -Subagents where the checker is never the maker -Memory so the loop never starts from zero Prompt engineers ask AI for outputs Loop engineers design systems that produce verified outcomes A reliable loop beats a perfect prompt every time Stop being a prompter. Start being the loop engineer
-
0xstack (@eth0xzar) reportedDON'T BUILD A COMPANY. BUILD SOMETHING PEOPLE CAN PAY FOR THIS WEEK. This girl started in February. A few months later, her product had already processed over $6,000 in payments. Just a cheat Claude project she decided to turn into a real product. Here's the process: > Build something useful for yourself. > Tell Claude to push it to GitHub. > Connect Supabase so multiple users can use it. > Deploy it with Vercel. > Connect Stripe. Now people can actually pay you. You don't need a revolutionary idea. You need: > GitHub > Supabase > Vercel > Stripe > guide from Anthropic And a problem worth solving. This article will help you build it 👇
-
I’m (@stackoverworld) reportedAnd then I can't answer on simple Qs: what was the issue? How I fixed it? How even to QA it.... This is the fundamental problem of such workflows. Telling "Check my slack, do this, qa, and using GitHub to push" is good, but I don't learn from this at all
-
Mike Muturi (@_muturimike) reportedHello @github on 2FA, SMS setup kenya 🇰🇪 is not in the list of countries, is it an error or deliberate omission? Kindly fix it @github @GithubProjects
-
xjdr (@_xjdr) reported@xlr8harder Looks like there is a bug in the manual sign up. Sign up with Google or GitHub should work otherwise I should have a hot fix shortly
-
Crystalwizard (@crystalwizard) reportedhow about you now fix the false positive triggers - i put in an issue about this on github yesterday, and discovered there were already a number of other identical issues - from other people, that had been opened for a while now and that are being 100% ignored
-
Gitbank (@Gitbank_io) reportedCommunity update — GitStock delay + what we have been building First, we owe you an honest update. We promised GitStock would ship earlier and we went quiet. That was on us. No excuses, we were heads down in the contracts and infrastructure and did not communicate well. That changes today. Here is what actually took time. We refused to ship GitStock on top of third-party APIs or borrowed infrastructure. Everything you see in Gitbank; the vault, the relayer, the swap engine, the RWA layer runs on smart contracts we wrote, audited ourselves, and deployed. The GitVault contract is verified on Basescan. The GitStockFactory is verified on Basescan. You can read every line. No black box. No external custody API holding your assets behind the scenes. That decision slowed us down. We think it was the right one. On security specifically. Your funds sit in a soul-bound smart contract vault anchored to your GitHub ID. Transfers are disabled at the contract level — not by a rule in a database, by the EVM itself. We also built private transaction routing directly inside GitVault on Base. No Tornado, no third-party mixer, no privacy-as-a-service API. The privacy logic lives in our own contract. You can verify it. The relayer signs and submits transactions on your behalf so you never pay gas, but the keys to your vault are yours. We hold nothing. If you want to verify any of this: check our contracts on Basescan, check our GitHub, check the bytecode. We are open source. The code is the proof. GitStock ships tomorrow.