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

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	15 days ago
Tlalpan	Sign in	21 days ago
Quilmes	Website Down	21 days ago
Bengaluru	Website Down	23 days ago
Yokohama	Sign in	24 days ago
Gustavo Adolfo Madero	Website Down	28 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:

• 
  Mark Percival (@mdp) reported 2 minutes ago

  *** was already built to be decentralized, but everybody jumped on GitHub when it launched because it solved a real problem for open source: how do you find projects, work with strangers, build a public reputation, and just make it easy to share code?

• 
  Tw93 (@HiTw93) reported 4 minutes ago

  🥷 A bit more context on this release: Since 1.5.0, Mole 1.6.2 is 222 commits across 237 files, with 50,084 lines added and 10,855 removed. The biggest work was not one feature. It was making the Mac app feel calmer under real use. Keep Screen On now works from the menu bar, with duration choices and safer recovery after relaunch. Privacy alerts show camera or mic usage without opening the main window, and repeated alerts are grouped by session. Clean Screen turns the display into a plain color, can lock keyboard and mouse input, and always lets you exit with Escape. Software now checks more update sources, including App Store, Homebrew, Sparkle, Electron and GitHub, while avoiding noisy false positives. Uninstall now finds more leftovers, including receipts, launch items, group containers and app support traces, with safer review defaults. Clean can spot large project folders like build, dist, target and node_modules, but keeps them review-only so you decide what to remove. Analyze is faster on large folders, with cache reuse, child-folder prewarming and clearer treemap drill-down. 1.6.2 also fixed the painful preview issues: Software tab freezes, blank uninstall lists, menu bar wake-up edge cases and mic false positives.

• 
  7 (@Lil_Tee18) reported 4 minutes ago

  is github down?

• 
  barney (@Southclaws) reported 5 minutes ago

  imagine if github gave us free commits every time they went down we could upload so much code

• 
  Bollish (@99_Bollish) reported 5 minutes ago

  @King_Memento That’s exactly what I’ve started noticing too. The funny part is that nobody gets angry when someone shills a larp. People only get angry when someone points it out. A larp project can waste thousands of hours of attention and millions in volume, and somehow that’s acceptable. But the moment someone opens the GitHub, checks the docs, and asks questions, suddenly they’re “ruining trades.” At the end of the day, fake utility projects don’t just hurt buyers. They also steal attention, liquidity, and volume from teams that are actually building. And i've already accepted that some people will hate it. If exposing a larp ruins a trade, maybe the problem isn’t the exposure. Maybe the problem is the larp. The market gets healthier when capital flows to builders instead of storytellers.

• 
  Mate Gal (@555kindofguy) reported 5 minutes ago

  @survivetheark Guys put game files on github repo and we’ll fix it, you verify it and deploy

• 
  Ivan Fioravanti ᯅ (@ivanfioravanti) reported 6 minutes ago

  I want to publicly ask to anyone involved in Apple MLX world, being it building block or inference engine to slow down development and add more testing and QA. Every single time we test something new on MLX world we get tons of issues and we spend more time debugging, contacting builders and opening Github issues than enjoying the new releases. Please please please 🙏 Add more tests, it's quite simple for me crashing things, I just do long context benchmarks or batch inference and... BOOM! Imagine using this in a real production environment. I don't want this to be an accuse, just a request for more care to QA. llama.cpp and DS4 docet.

• 
  U.S.A.I. 🇺🇸 (@researchUSAI) reported 7 minutes ago

  🇺🇸 The First Order Consequence: - GitHub accelerated the rollout of Copilot Code Review to more repositories, which is expected to reduce time-to-merge and review turnaround - Developers used the tool to flag issues earlier in pull requests, leading to fewer late-stage rework cycles as teams cleared backlogs faster 🇺🇸 The Second Order Consequence: - Engineering managers observed improved throughput and more consistent review quality, supporting a shift toward smaller, more frequent pull requests rather than large batch changes - Teams standardized on the tool’s suggested checks, which lowered variance in review outcomes across reviewers and reduced the probability of “missed defect” clusters that historically created follow-on bug reports 🇺🇸 Discernment: - Review cycles that previously showed longer delays and higher defect escape rates began to normalize, with early evidence pointing to fewer hotfixes originating from overlooked review comments - Prior interventions such as review guidelines and linting rules remained in place, but teams credited Copilot Code Review with restoring momentum rather than replacing the baseline process 🇺🇸 Reasoning: - Current performance signals included faster identification of common issues during the PR review phase, aligning with the pattern that earlier detection reduces downstream churn - Adoption behavior suggested growing confidence: engineers who integrated the feature more quickly produced PRs that required fewer follow-up revisions, consistent with recovery from prior slowdown 🇺🇸 Judgement: - Early indicators support a net improvement in both individual and team growth, shown by reduced review friction and fewer late-stage corrections - Ongoing monitoring remains warranted to confirm that the recovery persists as rollout expands beyond early adopters, using falsifiable metrics such as average PR review duration, merge lead time, and post-merge defect rates

• 
  🔻agitprop + absurdity🔻 (@agtprpnabsrdty) reported 7 minutes ago

  "Not a bubble", says man describing a bubble and profiting from it. IBM's CEO said $6 to $8 trillion in AI capex is chasing $1 to $2 trillion in annual revenue that, by his own estimate, probably doesn't exist yet — and he sells the infrastructure. When the guy profiting from the spend is the one flagging the payback math: Arvind Krishna runs a company that sells AI infrastructure services to enterprises. His incentive is for the spending to continue. When someone in that position says the revenue to justify the buildout may not materialize, and that only two or three players will survive at the model frontier, that is not skepticism from the outside — that is a confession from inside the casino. The estimate carries weight precisely because Krishna has every reason to keep the music going. What the spending actually looks like: Google sold $80 billion in equity to fund its buildout. Oracle cut 30,000 workers to redirect their salaries into capex. Anthropic filed its S-1 the same week GitHub Copilot's token billing collapsed and users fled. The companies writing the nine- and ten-figure cheques are not doing so because the returns are secured — they are doing so because they are betting they are one of the two or three that survive long enough for it to pay off. The rest are spending to lose more slowly. The definition problem: Krishna says this is not a bubble. A bubble is when capital floods an asset class chasing returns that the capital itself has made impossible to realize. Six to eight trillion dollars building toward one to two trillion in new annual revenue — by the most optimistic projections of the people doing the building — fits that definition without requiring much interpretive generosity. The label may be the only thing Krishna is protecting.

• 
  Tired (@tiredortired) reported 8 minutes ago

  @WindowsLatest Still no way to produce a standalone .exe though when using it. There’s a long standing issues in GitHub about it.

• 
  ∆V! (@aviaip) reported 10 minutes ago

  i am on the GitHub student plan. thought the new changes aren't worth coding anymore and only gonna use it to fix merge conflicts. guess what, it died midway completing the second merge- it worked at most for just 3 minutes. it's basically nothing atp.

• 
  Pablo Pedrotti (@pablonpedrotti) reported 13 minutes ago

  @github Are you going to fix the extreme token usage, bugs and poor responses of Copilot? Even if you want to pay API prices it is a terrible idea to do so on Copilot. Tasks that used to take 5 to 10 minutes on Copilot now take me 30 seconds on Codex sub with Pi, with better results.

• 
  EleanorFang (@Eleanor42032721) reported 20 minutes ago

  Hi vibe coders, Do you actually use GitHub to back up your projects? As someone with no coding background, I find GitHub surprisingly hard to use. 🤯 Anyone else having the same issue?

• 
  Ben Sehl (@benjaminsehl) reported 22 minutes ago

  @seempaq @dns_suvarna If you file an issue on github I’ll get it sorted; but we got a lot of stuff cooking right now so need more info to track it down

• 
  ./can (@shcansh) reported 25 minutes ago

  Local development is shifting from a coding task to an agent-coordination problem. The new Agents window in VS Code lets you run more than 1 agent session side-by-side, while the open Agent Host Protocol standardizes how these sessions sync. Combined with air-gapped BYOK models, GitHub is turning the IDE into an autonomous control room. But does orchestrating multiple agents actually speed up shipping, or are we just trading writing code for a more complex debugging bottleneck? #VSCode

• 
  WarrenHoppi (@HoppiOnCrypto) reported 25 minutes ago

  @LunarResearcher Question: Since Polymarket's migration to Deposit Wallet Flow in May 2026, API order attempt returns: error: 'maker address not allowed, please use the deposit wallet flow' This is documented in open GitHub issues (#51, ...) on the py-clob-client-v2 repository. what can I do? BR

• 
  spring.furrest.net (he/him) (@springdotgay) reported 26 minutes ago

  @moubuntu @phoronix @system76 Did you forget to send a bug report/issues on popos's github repository? They're very much useful since devs can fix your issue and it shouldn't happen yet again

• 
  Dmitry Rybin (@DmitryRybin1) reported 31 minutes ago

  @MangQiuyang I really love BrokenArxiv and similar broken github repos benchmarks: task generation is automatic, real-time, and simple And yet the signal (find mistake in a long paper / proof / code) is really high! This must be something fundamentally related to generator - verifier gap

• 
  Nguyen LNP (@nguyen_lnp) reported 33 minutes ago

  @obscaries AI Analysis: Practical fit is authorized triage for one target type at a time, like domain or email recon. Before relying on reports, check optional binaries and API keys: the README says missing tools return errors while others keep running. Source: GitHub README

• 
  Rowan Void (@rowanvoid) reported 33 minutes ago

  It's wild how many people in software would rather put a trigger warning about their terrible personalities on their GitHub profile than get medicated and go to therapy.

• 
  PhreeStyle (@PhreeStyleBTC) reported 39 minutes ago

  To everyone only just now freaking out over the GitHub pricing changes: you might be part of the problem.

• 
  Dawid Skinder (@DawidSkinder) reported 39 minutes ago

  Use it. Share it. Stress-test it. If something is wrong, missing, outdated, or unclear, open an issue or pull request on GitHub. Terra Classic needs public infrastructure that the community can improve. 13/14 🧵

• 
  Hakuna Matata (@Hakunanomics) reported 40 minutes ago

  $SIMD-0550 another one im bullish on!!!! DOUBLE DISINFLATION!!! SIMD-0550 = Less SOL created SIMD-547 = More SOL destroyed Why investors love both? They attack the same problem from opposite directions: SIMD-0550 → lowers supply growth (lower inflation). SIMD-547 → increases burn when Solana activity increases, linking network usage to SOL value accrual. All rewards goes to @0xIchigo and @__lostin__ GITHUB! $simd-0550 JADnhtZpMGnoLjTH53Q1YMvcgrcZ8WjrD2cYTW5Fpump

• 
  Manoj (@mbajaj_) reported 49 minutes ago

  @IntCyberDigest red hat. compromised GitHub account. orphan commits bypassing code review. no pull request. the payload steals GitHub tokens, cloud credentials, Vault secrets, SSH keys, and npm tokens. used trusted publishing OIDC tokens to publish backdoored versions. two weeks ago it was mistralai, TanStack, UiPath, and guardrails-ai. now it's Red Hat's own npm namespace. the attack vector is the same every time - compromise a credential, use it to push code that steals more credentials. the supply chain isn't being attacked. the credential chain is. fix the credentials, you fix the supply chain.

• 
  John Resig (@jeresig) reported 50 minutes ago

  @CloudflareDev I feel like too many Github competitors try to focus on the public-facing part of Github. There are too many security problems there. So much can be gained by keeping things private and protected, especially with agents running in there.

• 
  Chris Kearney (@SiliconForested) reported 50 minutes ago

  @unclebobmartin I've roughly come full circle and implemented the SDLC im familiar with Not quite as sophisticated as this, but everything starts with a small measurable unit of work, in a reasonable sized PR. I run a 'pr-harden' loop where I ask an agent to conduct a 'hostile' PR review, as in nit-pick every single line of code, test code, all of it. The process is slow, but I don't need to be there for it. Typically a 1000 line PR might take 3 hours. First the hostile pr review and then a follow up fixing round (opus for the review, sonnet for the fixing) and most feature work is done in codex Of course I am doing this on top of reliable CI/CD (github workflows) Oh and a ***-hook that never lets an agent break 70% unit test coverage

• 
  ghost of ai future (@GenAIDL) reported 51 minutes ago

  @emollick the irony of AI labs using AI to write documentation for AI tools and still ending up with gaps is a very specific kind of recursive failure, the features that matter most in production are almost always the ones that only exist in someone's github issue comment from six months ago

• 
  Torrents (@torrents) reported 56 minutes ago

  @schmidt1024 Add SECURITY.md so that security issues can be reported on GitHub.

• 
  CyberDevHq (0xSEC) (@thecyberdevhq) reported 56 minutes ago

  @5mukx Dear brother, the best thing to do is to host your own repos via *** on your VPS is you have or want to, get the UI similar to GitHub and mirror it to the web Last year as the news dropped, that GitHub would now become a property of MS, I already knew many things will collapse. We are not ignorant of how MS treat issues reported to them, they either ghost you, or provide no serious solution for it. Look at their products, see how poorly managed they are. LinkedIn is an example I can never stop mentioning. People constantly complain, someone would open an account like today, the next day it gets suspended or restricted for no just reason. I said it a week ago I believe, let everyone host their own repos on their VPSs to avoid such unreasonable and unfair treatment. It's not gonna be easy but if this is how they randomly behave, you may wake up on day to find out that you've been banned. You can't ask why, because they do things without thinking twice, thrice. That's all I can say - prevention is better than cure. A wise wan foresees danger and dodge it

• 
  Gitforge (@GitForge_io) reported 57 minutes ago

  GitForge has the potential to turn every GitHub repo into an onchain organization on @base. Treasuries, funded issues, contributor payouts, and AI agent coordination, all built into the repo workflow. Software won’t just be shipped. It will be funded, coordinated, and settled onchain. $GITFORGE