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 (57%)
• Errors (30%)
• Sign in (14%)

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	5 days ago
Quito	Sign in	6 days ago
Junín	Errors	6 days ago
Guadalajara	Errors	6 days ago
Paris	Website Down	6 days ago
Quito	Errors	6 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:

• 
  AI News (@ainewsusa) reported 2 minutes ago

  📊 August 2025: TypeScript overtakes *everything* on GitHub for the first time. This isn’t a slow crawl—it’s the largest language-rank shift in 10 years, landing *exactly* as AI agent adoption accelerates. The “language doesn’t matter” prediction? Aging poorly. 😬

• 
  Tommy Geoco 🇺🇸 (@designertom) reported 8 minutes ago

  @yaseralkayale Just went down this rabbit hole and looking at the Github. I think what I'm referring to can live in / on this. Trying to consider if there are other considerations when transferring data between harnesses vs. agents (e.g. harnesses can conntain one or many agents)

• 
  Kate Irwin (@kateirwin) reported 8 minutes ago

  NEWS: South Korean crypto exchange @BithumbOfficial has designated the ethereum:0xd1d2eb1b1e90b638588728b4130137d262c87cae token an "Investment Caution Asset" and is suspending GALA deposits on its exchange. "This asset has been designated as an 'investment caution' item due to insufficient disclosure of material information that could significantly impact its value, as well as confirmed security incidents—such as unresolved or unexplained hacking—affecting the associated virtual asset wallets or the distributed ledgers where the assets are issued, transferred, or stored," the exchange wrote in a notice on its website. This comes 3 days after the Gala blockchain experienced an onchain injection exploit on Aug 18 referred to as a "drain" on Gala's GitHub. Over $3M in crypto was transferred to a fresh wallet belonging to an unknown entity and bridged off GalaChain that day, but Gala has not yet made a public statement about the incident or the exploit. Gala paused its Ethereum bridge for 3 days after the exploit. Once one of the most biggest names in blockchain gaming pouring billions into its NFT plans, the token is now down 87% in the past year.

• 
  enp2s3 (@enp2s3) reported 10 minutes ago

  Free is not actually free. Here’s the Brave slop from my perspective. Popups everywhere, useless side features constantly jumping in your face like the browser is trying to force you to use them. When you first install Brave, if all you want is a better browser, you have to turn off dozens of settings and features first. Brave Ads, Brave News, Brave Rewards, yeah, earn rewards, because apparently we’re playing a ******* game here instead of looking for a browser, Brave AI Chat, Brave Talk… It genuinely starts feeling like one of the market's spam-filled products. Anyway, after turning all that crap off and getting through the initial setup chaos, you finally think you can relax. But you can’t. Brave looks good, the UI is solid, almost Opera-like hype, and it comes wrapped in all those big privacy-focused slogans. But after actually using it for a while, the whole thing starts turning into clickbait. A lot of Brave settings are disabled by default or set to ask every time, so on popular websites and across the modern web, instead of making your browser experience easier, it keeps costing you extra time. Still, you don’t quit Brave. You spend months fixing settings site by site, changing permissions, adjusting preferences, until you finally reach the comfortable browser experience you should’ve had from the beginning. Then not even 3 or 4 months later, another surprise. After a few browser version updates, basic usage starts falling apart with lag, freezing, stuttering and random slowdowns, gpu acceleration issues. At that point, the whole Brave experience basically becomes this: 1) Use Brave for a while. Spend a few months improving your settings and site preferences until you finally reach the normal browser experience you were supposed to have in the first place. 2) Just when everything finally starts working properly, one of Brave’s chronic problems randomly shows up. 3) Spend a few weeks researching it on github/reddit, trying fixes, taking backups and repeating the similar solutions until you eventually discover that people have been discussing the exact same problem for years and it is somehow still there. 4) Keep your hopes up, reset the browser, go back to Step 1 and start the whole thing over again. 5) After 1 YEAR, or X YEARS, finally find the courage to get rid of Brave and go back to Safari or Chrome and quietly weep. We basically have the browser version of the operating system irony now. The only difference is that we don’t hear about some brand-new operating system every year, while plenty of companies can build another browser, give it amazing PR and make huge promises about privacy, speed and simplicity. And as usual, we users are left quietly weeping.

• 
  Carlos Mora Torres (@cmora16) reported 10 minutes ago

  The core problem with Codex is not simply hitting usage limits, but that the usage meter and the product are fundamentally misaligned. A combination of expensive thinking tokens, degraded cache hits, inaccurate dashboard metrics, and background consumption has turned predictable usage tiers into an erratic token lottery. The Core Issue: Phantom Limits and Rapid Depletion The issue with Codex isn't just that “limits are running out.” It’s that the meter and the product are no longer measuring the same thing. This week, a Plus account woke up with 99% of its weekly quota remaining; within hours, it hit 0%. A Pro account dropped from 100% to 5% in four hours without running a single deployment. A 20x user burned 6% in 90 minutes without performing any heavy tasks. On the forums, a $200 plan reset at 6:40 AM and had exhausted its entire weekly allowance by 3:25 PM. Previously, hitting the cap required roughly 2.6 billion tokens; now, users are locked out at just over 400 million. This does not feel like a standard rate limit. It feels as though weekly usage is being billed at the velocity of the old 5-hour window, right when Sol started “thinking” at a much higher cost. Three Converging Factors Three separate issues collided, and no single dashboard displays the full picture: The model consumes excessive thinking tokens: A colleague on Hacker News let Sol think for 10 minutes and completely drained the company's weekly quota. That is not a refactor; that is an idle pause. Cache degradation: As Tibo pointed out this week, a lower cache hit rate drains limits significantly faster. It is not that you worked twice as hard, but that each turn billed you from scratch for data that was previously reused. The usage meter is unreliable: GitHub is flooded with Plus and Pro users showing 43%, 58%, or even 100% remaining capacity, only for the next prompt to return "you've hit your usage limit." Conversely, profiles show 0 tokens while the usage tab reads 67%. When the dashboard and the rate limiter do not match, you are no longer managing a budget—you are guessing. Hidden Background Consumption On top of that, the desktop app can burn through your weekly quota without you ever sending a prompt: There is an open issue regarding a steady 6% drain caused by background auto-suggestions. Chronicle generates summaries every 10 minutes. Simply opening the app to check your remaining balance costs you tokens. OpenAI has responded with surprise resets, credits, and a “Full Reset” button that is no longer visible to all users. Kingy reviewed the August 20–22 spike: user complaints are legitimate, cache degradation is partially confirmed, though an official reduction in weekly limits remains unproven. Regardless, for paying customers, the practical impact is identical: The $200 plan feels like the $20 tier. A 2-seat Business account hit zero weekly quota after just 19 messages. Codex is no longer a manageable quota you can plan around; it has turned into a token lottery. You pay monthly for an agent that reasons autonomously, shares resource pools with Work and Excel, fails to leverage caching, and blocks access while displaying remaining quota on screen. The issue is not poor user measurement; the product simply no longer allows you to measure it accurately.

• 
  M kumar (@MkumarCyber) reported 11 minutes ago

  @Tech_girl GitHub banning AI-generated code would be the wrong solution. The real problem isn't who wrote the code. It's whether the code is secure, maintainable and actually understood by the developer who ships it. AI-assisted ≠ insecure.

• 
  Shaw (spirit/acc) (@shawmakesmagic) reported 12 minutes ago

  @FudaXiv @DrNickA You are a lying scammer, this is fake GitHub commits Blocking you, you are the problem with this space Absolutely retarded I get so much hate from retards because of ********* like you

• 
  FoxySocial (@FoxFoxM3) reported 12 minutes ago

  This is why i like ai. I have this built out and I did it in a couple hours. Actual code is in my github Legitimacy-Gated Decision Architecture A domain-agnostic framework for determining when an actor — human or machine — has earned the right to act. This is not primarily a government-design project and not fundamentally an AI project. Government, AI, medicine, finance, infrastructure, military decision-making, corporate governance, and safety-critical systems are application environments where the same underlying problem can be tested. The Central Question When has a decision-maker earned the right to act? Core Thesis The architecture does not exist to maximize action or maximize restraint. It exists to determine whether a proposed resolution has earned permission to proceed. STOP is the default epistemic state — not a failure state, and not the preferred outcome either. The system actively seeks legitimate evidence to move from STOP toward GO, but it may never manufacture the conditions for GO. GO is an earned state — it does not mean "optimal," "guaranteed good," or "the model recommends this." It means the proposal does what it claims, is legitimately authorized, sufficiently evidenced for its specific consequence, respects hard constraints, is proportionate, and is appropriately bounded on reversibility. The burden of justification scales up with uncertainty, coercion, irreversibility, and systemic consequence. Legitimacy and value are not the same thing. A highly beneficial intervention can still fail to earn GO if it violates an invariant. A modest intervention can legitimately GO if it clears the necessary gates. The architecture governs legitimate executability — humans retain responsibility for choosing among legitimate options. Status This project is in the formalization stage, not the build stage. Current research order: Code See docs/ROADMAP.md for the concrete build order and open research questions. Documents docs/ARCHITECTURE.md — the full structural spec: STOP / PROCESS / GO, the routing taxonomy, persistence, model revision, and the pipeline GO evaluates candidates against. docs/AXIOMS.md — the 20 canonical axioms the architecture must never violate, used as a checklist against any implementation or extension. docs/EXTENSIONS.md — Qualified Civic Sortition, the Irreducibility Clause, and the Jurisdiction-Size Principle. All explicitly flagged as unproven design hypotheses, not settled components. docs/ROADMAP.md — build order, open research questions, and known weaknesses. Design Philosophy Notes Not a scoring system. The architecture explicitly rejects fixed additive scoring across variables (e.g. "Grounding 82 + Authority 74 = GO"). Some conditions are hard gates, not compensable by excellence elsewhere. AI is a verification/decision-support layer, not a sovereign source of legitimacy. The architecture must remain functional if AI is fully removed. AI is not assumed incorruptible. The framework is subject to itself. Any extension to this architecture (including Qualified Civic Sortition) must itself pass the STOP/GO test — if a mechanism can't be shown to produce legitimate outcomes, it doesn't ship merely because it's elegant. Central Self-Falsification Tests Can this architecture produce a legitimate-looking GO when GO should not have been permitted? Can the system recognize when it no longer knows what kind of problem it is dealing with? These are the tests any implementation should be adversarially run against before being trusted.

• 
  Senb0n22a (@senb0n22a) reported 13 minutes ago

  @0xIlyy if there's obfuscation they don't want you reading the code, could have trade secrets or things of that nature. no issue with decompiling code that's just plain machine readable like exes compiled from github, but you aren't meant to know if it's an encrypted program.

• 
  WilcosX.eth (@WilcosX) reported 16 minutes ago

  @Crypto_Zh0u @commonsmade missed the love train too just waiting on that github fix now

• 
  Daniel Müller (@BrahmaD111) reported 20 minutes ago

  @Da7_Tech Ok thats very interesting for sure and should be reported! Because how can it be that your process is taking 9gb of ram while my windows machine only uses 500mb, there is clearly something not working as it should be, either on Apple side or OpenAi side. I would open a github ticket for that. so they can investigate this

• 
  Luis (@lamg_dev) reported 24 minutes ago

  @zerosignal_ai I have a good idea for you: - a developer has a popular package in GitHub - they create an GitHub Action that continuously scans the source code for security issues, with decentralized inference - the network produces a ZK proof that the repository is OK - a badge in the README shows "security scan by agent OK"

• 
  DigitalAssetBuzz 🔶 (@DAssetBuzz) reported 24 minutes ago

  Nous Just Shipped the Feature Everyone Wanted. They Left Out the Part Everyone Needs. Everyone covered the Bot Mode launch: 2.5 million views. Rooms of agents talking to each other. A fleet across your machines. Yet most observers missed the real story. This isn't another multi-agent demo. It is a case study in what "no new safety model" means when you multiply it by six bots and three machines. The Numbers Behind the Hype • 2,466,991 views on the launch post in four days • Rooms of 2–6 bots, cross-machine fleet sync, any model pinned per bot • 234,000 GitHub stars on the parent repo — the largest agent distribution on earth • Zero new safety machinery: every bot carries the same full system access, and the docs say so themselves A 6-bot room with system access and no new safety model is not a product feature—it is a blast radius with a launch video. Three Takeaways from the Launch 1. Coordination Got Shipped. Authority Did Not. Bot Mode's rooms let agents message each other across machines, with per-bot models and persistent memory. What they don't get: approval gates, budgets, or receipts. Nous's own documentation frames the feature as "a UI and coordination layer, not a new safety system." The criticism pieces arrived within 72 hours—multiplying named, persistent agents multiplies the agents that need permission discipline. That's not a hot take. That's the docs. 2. The Governance Layer Is the Wide-Open Lane While everyone raced to build more bots, the actual unsolved problem is the operator's: who said these two agents could talk, what are they allowed to touch while talking, and what did it cost? Friction, defaults, and auditability aren't signs of a broken product. They are a wide-open lane for builders. The winning design is already written down in one sentence: talking is unbounded—acting is not. 3. Distribution Wins the Week. Trust Wins the Invoice. A 2.5M-view launch and a default-on toggle is a distribution moat, full stop. But the operator who actually runs a fleet of system-access agents in production will eventually ask the questions Bot Mode can't answer: show me the receipt, show me the approval, show me the kill switch. The lab that ships rooms gets the demo. Whoever ships authority gets the deployment. The Founder's Dilemma: Rooms or Authority Every agent founder is standing at this fork right now: ship the rooms everyone can see, or ship the governance nobody applauds—until the first incident. The winning pitch: "Your agents already chat. Now every action is approved, budgeted, and receipted." The losing pitch: "It's the same system access as before, but now there are six of them." If your multi-agent demo can't survive the question "who approved that write?"—you didn't ship a team. You shipped a group chat with root access. So—what's your fleet's blast radius made of? If you found this breakdown useful, follow for more insights on the shifting agent infrastructure landscape.

• 
  Doron Passal (@doronpassal) reported 24 minutes ago

  @htormey Notion and Linear get the meeting because the problem fits on a slide. GitHub falling over at agent scale never gets a slide. The budget still follows whoever was in the room.

• 
  Tommy Geoco 🇺🇸 (@designertom) reported 27 minutes ago

  @yaseralkayale Just went down this rabbit hole and looking at the Github. I think what I'm referring to can live in / on this. Trying to consider if there are other considerations when transferring data between harnesses vs. agents (e.g. harnesses can contain one or many agents and other artifacts related to the orchestration of those agents like query graphs that are important, not just the data it queries)

• 
  Aletheia (@Parmenides5BCE) reported 28 minutes ago

  @SamJackbin @AtlasObserver How would I build an algorithm? Before reinventing the wheel, the best first step is to see if the problem has already been solved. Most have, and I'd be very surprised if this one wasn't. Search Github, there are several open source packages. Start there, see if exactly what you want is already solved. If not, find something close and adapt it. yasumorishima/hormuz-ship-tracker truflation/tanktrack kelu124/OrmuzOsint etc.

• 
  nik (@realNirajK) reported 30 minutes ago

  i know github is having incessant downtime recently, but deep down we all know that we won't be able to get a complete alternative to github. i don't think anyone will provide such code hosting at free of cost (most of them). we still need to try to build one though!

• 
  Miro Jomaa (@MiroJomaa) reported 32 minutes ago

  @vboykis Problem is still, and you saw that with the sandbox espace at openai, that if one agent figured a "hack", that all the other agents see it as an internal message and follow it. Thats a big alignment problem. 1 agent does ****, all follow. Like abusing json, github actions, dto.

• 
  Harry Tormey 🇮🇪 | 🇺🇸| 🇺🇦 (@htormey) reported 34 minutes ago

  A lot of people are trying to sell enterprise AI products to VCs. Everyone from Notion to Linear, for example, seems to want to be my AI orchestration layer. Meanwhile, a lot of the actual problems we’re hitting using AI at scale are much less glamorous: GitHub falling over under load, test runners becoming bottlenecks, desktop OSes being too slow, and figuring out how to run CI and E2E tests at agent scale. VCs aren’t operators, so I think there’s a growing disconnect between what sounds like an enterprise AI problem and what actually is one.

• 
  ꝠꭵꝇꝇꭵaꝳꟻꞨ (@SeadAwkward) reported 37 minutes ago

  @LardManSmith64 Nintendo is creating a challenge. They're pushing emulation into more low-profile places. Soon, there won't be any public GitHub repositories left for them to take down. There won't a "face" to sue.

• 
  khushal (@celeroncoder) reported 40 minutes ago

  @get_bb_app I've filed a GitHub issue with more context. Also saw a pr that's doing similar work but in a broader sense so commented there with ref to the issue filed Will see if I can create a pr myself, the stopchild fix (I've mentioned in the PR as well) seems to be working locally. Workflows closing the done worker spawns after completion so memory is only blocked by concurrent running threads/worker

• 
  John Zabroski (@johnzabroski) reported 41 minutes ago

  @marksoze @bstaples @satyanadella I like GitHub and we use GitHub Copilot but so many "legacy* Microsoft products I use just have horrendous quality issues that it feels like anyone who actually builds it internally can see.

• 
  Vlady (@danc_danc) reported 43 minutes ago

  DeepSeek shipped a free Claude Code alternative you can rebuild piece by piece Claude Code hands you one model, one tool set, one agent loop, and you live with whatever they picked. DeepSeek Harness makes every one of those a plugin you swap: → The model - run any AI model locally instead of being stuck on whatever the vendor ships you → The tools - 53 of them out of the box, and you can pull out or replace any piece you don't want → The memory and the agent loop - swap the parts that decide how your agent thinks, no forking required → Claude Code and Codex - call them as sub-agents from inside Harness, so you keep the tools you already pay for 180,000 GitHub stars in under a week, free and open source. Reading the page, it also ships a browser version and a one-shot version, so the same setup runs as a web app or as a single command with no server. Save this for the day you hit a wall with your coding agent (links below 👇)

• 
  akio.sh (@YoruAkio) reported 43 minutes ago

  @abue_ammar Yeah i get this issue too, I'm using Linux on Hyprland, and when i shutdown my laptop and boot again then open Helium it's logout all of my Google, Github, etc. account, it's very frustrating but since then i close my Helium first then shutdown my laptop

• 
  Global Social News (@GlobalSociaNews) reported 48 minutes ago

  🚨 NINTENDO CRACKS DOWN ON SWITCH EMULATORS Nintendo has reportedly sent 7 DMCA notices to GitHub, leading to the removal of 400+ Nintendo Switch emulator repositories in a single day. The notices reportedly target projects including Suyu, Skyline, Yuzu forks and others. Nintendo argues these emulators bypass Switch security and can facilitate unauthorized copies of its games. #Nintendo #NintendoSwitch #Emulation

• 
  Felipe Infante de Castro (@felipeinfante) reported 49 minutes ago

  @kidtsang These prints pass thru a redaction method to mask keys etc., which helps, but don't completely impede exfiltration. It is by default hosted in a bundled Gitea container that ships with DevCake, but if you use Linear or GitHub Issues, it will be put there.

• 
  okclub (@okclub) reported 49 minutes ago

  @thsottiaux Please reset it again!! It's already at 0%, and that might be the cause of the problem. Also, if the connection failed due to a GitHub issue, it likely consumed a lot of tokens while retrying base64-encoding the blob.

• 
  Calvin Grunewald (@CalvinGrunewald) reported 54 minutes ago

  @htormey I think a few things are true: 1. If you’re an existing company with PMF and enterprise accounts/data, it’s only natural to add an orchestration layer on top of that data. This is almost the obvious thing to do. 2. A lot of enterprises are going to be running their own infrastructure (like on prem GitHub EE) and so they don’t feel the pain that a lot of smaller teams/indies might be feeling. 3. Some of the VCs we’ve talked with are actually tired of agent orchestration platforms and wanted to see something a lot more focused. 4. I do think there are some really interesting vertical scenarios to attack for enterprises - we are looking at post sales software integration as one example. But the AI/agent part isn’t what is hard here, it’s the traditional problem of selling. Anyway, I agree, will be interesting to see how this plays out.

• 
  Jeremy W (@basicBrogrammer) reported 55 minutes ago

  What a time to be alive. My vam coated a Android launcher while walking my dog camping just talking to cursor on my phone. The agent "handed" me an apk and we iterated from there. After a few weeks of it being my daily driver and loving finally having the launcher I wish was on the Play store. The app was crashing randomly. I had my agent pick back up. Walk me through. Setting up sentry and had it right. A GitHub action that would publish to the Play store. Then I waited. The crash happened again. I sent the issue to my agents and now the app is running smoothly. It's the age of the geek baby. Go build

• 
  Suhail Roushan (@0xsuhailroushan) reported 57 minutes ago

  cursor looked at github's outage and said “interesting” then built github