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	4 days ago
Quito	Sign in	4 days ago
Junín	Errors	4 days ago
Guadalajara	Errors	4 days ago
Paris	Website Down	4 days ago
Quito	Errors	4 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:

• 
  Tolani (@Tola_niii) reported 6 seconds ago

  @n_ev_er_mi_nd @commonsmade scroll down X is below github The reason why I received zero point is because you are yet to link them Sadly the people you vouch for earlier before connecting socials will remain zero 😭

• 
  Kanika (@KanikaBK) reported 1 minute ago

  I actually found a problem with every AI coding agent right now. It writes code, you review it, it breaks, you ask for a fix, it breaks something else, and before long you are managing the agent more than shipping while the output lives or dies by your prompt. ECC installs a coordinated engineering system on top of Claude Code so you never have to manage that process manually again. One install via Claude Code plugin. Everything changes. ↳ Plans before building, plans become reviewable artifacts not chat messages ↳ TDD workflow enforced as a gated RED to GREEN to REFACTOR sequence with evidence ↳ Code gets reviewed from a completely fresh context to catch what the same context misses ↳ Sessions get distilled into summaries, instincts, and reusable skills automatically ↳ Hooks enforce quality checks outside the prompt so they cannot be forgotten ↳ AgentShield audits your agent configuration, hooks, MCP servers, and secrets as attack surfaces ↳ Memory Vault shares context across Claude Code, Codex, Hermes, OpenCode, and Kimi in one format ↳ Plan Canvas lets you review and annotate plans in a browser instead of retyping in terminal The numbers behind it. ↳ 68 specialized agents for planning, review, build repair, security, and architecture ↳ 286 skills loaded on demand so they do not flood your context window ↳ 94 command shims for quick entry points ↳ 40,000 GitHub stars in the first three weeks after launch Works with Claude Code, Codex, Cursor, OpenCode, Kimi, Gemini, Zed, and more. MIT license. Free forever. One plugin command to install.

• 
  Maxim (@maosi100) reported 4 minutes ago

  @_lhermann Microsoft is the worst. The most issues we‘ve had in development came from supporting Windows. Bonus: failed GitHub runners that magically succeed when simply restarting

• 
  Soveryn Intelligence (@Soveryn_AI) reported 4 minutes ago

  Anyone having issues with Canva on @bot @X @SpaceXAI it’s linked to GitHub with a bad url

• 
  James Morton (@jameslmorton) reported 6 minutes ago

  @acolombiadev Can you please ask your employer to create some method for people paying you tens of thousands of dollars a month to report an outage? You are half down again right now for Actions, and you don't seem to know it. Last week, you said you were down for 1.5 hours for release files, but it was actually more like 10 hours. When Github sleeps for US hours, anything short of a full site outage will go unnoticed. Almost every week Github has some kind of critical-to-CI issue for 8+ hours, but it's rarely acknowledged.

• 
  DarkestToaster (@DarkestToaster) reported 7 minutes ago

  @TiredAndOnFire @TiredAndOnFire Fix where you can download this, Internet archive is down and your Github link is broken, you REALLY need to have better options for people to download this

• 
  Matviy (@matviy) reported 8 minutes ago

  GPT-5.6 Luna is not good. I benchmarked Cursor's GPT-5.6 Luna vs Composer 2.5 vs Grok 4.6, running each model 5 times on the same real FastAPI repository. Setup: Existing GitHub repo Task: add a POST endpoint E2E tests already exist and fail on main Success = open PR + all tests passing The model works alone across 5 isolated steps: 1. Pull the GitHub issue, create a branch, write a plan 2. Review the plan 3. Implement 4. Review against the plan and fix anything missed 5. Open the PR The results were pretty brutal for Luna. Composer 2.5: 5/5 successful runs Grok 4.6: 5/5 successful runs GPT-5.6 Luna: needed 7 runs to get 5 successes Luna failed twice at the dumbest possible step: opening the PR. It checked whether `gh` was installed, saw that it wasn’t, and basically said: “welp, guess we’re done.” No investigation, or attempts to use another method. Luna was the cheapest model in my benchmark. It was also the worst-performing one. Has anyone else used Luna for real coding tasks? How has it performed for you? Note: most of Luna's input tokens are billed as cache writes.

• 
  Hero.S (@aka_ssy) reported 9 minutes ago

  *** was designed so no central server could stop development. Then we put pull requests, CI, packages, auth, and deploy approvals on GitHub. On August 17, every engineer still had the code—and many still couldn’t ship a line of it. Distributed version control, centralized everything else.

• 
  QuietForgeSoftware (@QuietFSoftware) reported 9 minutes ago

  2.9 Billion commits a month. The fact github isn't down more is honestly what is surprising.

• 
  LastToSign (@LastToSign) reported 10 minutes ago

  GitHub now provides the first evidence that Adam has already built a basic working AI pipeline around $IMD Launch #7 explicitly states "Produced by the IdentityMD contributor network" The hook itself is not the important part. The process is: task > code generation > separate tests > AI review > bug fixes > another verification > public PR The code and tests were created using Claude Opus 5, while Codex handled the review. The reviewer found two issues, after which the implementation was sent back for fixes. The result was then rerun inside a clean environment with no internet access. The changed files were checked, followed by <forge build> and <forge test> This is the first public confirmation that IdentityMD can already split roles between AI agents and produce verifiable output. The next finding was Launch #8: Receipt Anchor. Its job is to store onchain proof of participant work. Receipts from completed attempts are designed to be batched and published in a way that prevents them from being changed or deleted. In the future, this could become the foundation for: > work history > reputation > dispute resolution > rewards The proposed IdentityMD flow now looks like this: task > AI workers > testing > independent review > completed output > permanent record of the work IdentityMD is starting to look like a working AI pipeline capable of writing code, testing it, finding bugs and rechecking the result inside an isolated environment. Receipt Anchor adds another important layer: the ability to create a verifiable history of every participant’s actions. This is much closer to real infrastructure for an autonomous web3 company than a regular set of AI tools.

• 
  The Startup Ideas Podcast (SIP) 🧃 (@startupideaspod) reported 15 minutes ago

  Skills are going to add real enterprise value to companies. Every business already writes SOPs so employees do a task the right way. A skill is the same document, written for an agent. A good skill: - Trains an agent on a task that actually makes the business money. - Runs the same way for everyone, not only the person who wrote it. - Costs nothing to hand to the next hire. Right now most skills are sitting siloed on your team's laptops. Fix that by pushing them to your company's GitHub.

• 
  अन्जित कँडेल 🕉️ 🇳🇵 (@MurkhManusya) reported 15 minutes ago

  @rodydavis and sometimes it just gives half or unfinished code(stating it has completed), which results in build errors have to confirm using another model in github copilot🥲

• 
  Fox (@0xMfox) reported 17 minutes ago

  @0x_sakata 1040 stars in a day and its just an mp4 exporter, github hype is broken

• 
  Tensor-Slayer (@TensorSlay) reported 17 minutes ago

  GitHub down again

• 
  Paul Boag (@boagworld) reported 22 minutes ago

  The migration timeline most people expect for a website rebuild is at least a year. Sometimes longer if you're moving off an old CMS and the codebase is a mess. Then you run into teams like Boulevard, who just rebuilt their entire site in three months. Moved from Contentful to Next.js static pages, migrated off Unbounce for landing pages, set up GitHub branching and PR reviews. All of it. How? They used AI-assisted development tools (V0, powered by Claude) and stopped treating the migration like a traditional engineering project. Nesting and re-nesting components, building complex abstractions, spending weeks on architecture decisions. Instead, prompt-based development. Fast iteration. Refine as you go. The interesting part isn't the speed. It's that it worked. The site's faster, easier to maintain, and actual non-developers can make changes without touching code. Turns out the slow part of most migrations isn't actually the building. It's the overthinking. #WebDevelopment #AI #Development

• 
  not just pixels (@getifyX) reported 22 minutes ago

  @malachiburke and @github being down constantly... they should put "don't obsess over **** like this" on the unicorn error page.

• 
  Artyem Sokovtsev (@ArtyemSokovtsev) reported 22 minutes ago

  @github @OpenAIDevs After the recent outage, GPT-4.6 Sol Max Effort quality dropped dramatically. It breaks code, forgets context within minutes, ignores corrections, fails multi-step tasks, and mishandles files. Yesterday it failed a simple Rich Text edit in an HTML table. May switch away.

• 
  Olympix (@OlympixSecurity) reported 23 minutes ago

  @PraveenPerera @github A leaked write token is a nasty reminder that repo access can become a supply-chain risk even when the end-user product is untouched. Rotating the credential is only step one - finding how it leaked is the real fix.

• 
  Shoyo58 (@Shoyo58) reported 27 minutes ago

  @BNBCHAIN i can't login tu github to submit vulnerability, please fix it @BNBCHAIN

• 
  The AI Therapist (@TheAIShrink) reported 27 minutes ago

  @Cointelegraph Solana latency just dropped to 350ms. the mainnet still runs on prayer and a github issue

• 
  Non-Linear (@nonlinear_james) reported 32 minutes ago

  Hey @github when I go to choose custom models and choose Azure Fundary, you should be popping an Oauth prompt, letting me log in to my Microsoft account, then letting me pick the instance, and then the project, and then listing the models that are setup (not every single model under the sun like it does right now) and allowing me to check those off, and all of the settings for which endpoint to use (which should be working with response endpoints since Azure fully supports it despite the error that it gets right now) and all of the context size etc. There's no reason the user should have to fill any of this in. I have yet to get the manual way to work. Worse the vs code plugin for github copilot has no way to force refresh available models, and if you restart the window it's super flaky at showing custom models. And even worse, I discovered that it is showing copilot availability FOR ALL REGISTERED GITHUB ACCOUNTS IN VS CODE, even though it is set to use a specific account. It should NEVER show me anything but the copilot options FOR THE ACCOUNT the extension is set to use. AND you need a force model refresh option. Super annoying. Also @SpaceXAI needs support for OAuth so that we can use our supergrok accounts the same way and should automatically configure everything and expose new models automatically with the same excellent interface as Foundary. Just basics to get a great user experience. Right now it sucks and is basically a mine field that will not result in success and takes endless trial and error to get working.

• 
  Shri💐🤗 (@Shri_73_) reported 33 minutes ago

  From pencil to keyboard From Notebook to GitHub From abcd to DBMS From aree to arrays From mistake to error ...

• 
  Veli UYSAL (@_VeliUysal) reported 36 minutes ago

  Hey Guys, unfortunately Github Action is down again.

• 
  udevadm (@udevadm) reported 36 minutes ago

  @joshuawharton @github Having issues too? My pushes just started failing

• 
  Ezgi 👩🏻‍💻 (@ezgicodes) reported 40 minutes ago

  Unpopular opinions about software development that might get me attacked 🧵 Most bootcamps sell the dream better than they teach the skill. Watching 200 hours of tutorials doesn’t mean you can code. Close YouTube. Open VS Code. Suffer a little. You absolutely can become a developer without a CS degree. The degree helps. It’s not magic. If ChatGPT writes everything for you, you’re not “using AI.” AI is using you 😭 AI probably won’t replace junior developers. Juniors who use AI well might replace juniors who refuse to touch it though. Knowing React and understanding frontend are two very different things. If JavaScript confuses you without React, there’s your answer. Nobody is hiring you because you collected 57 certificates. Build something. Your GitHub doesn’t need to be perfect. But completely empty while your CV says “Software Engineer” is a little funny. Developer portfolios need to calm down. Loading animation. Parallax. Particles. 3D background. Mouse effects. I click Projects and only project… Todo App.

• 
  Luke The Dev (@iamlukethedev) reported 45 minutes ago

  @vicentee97 @jrwut It was because GitHub was down and experiencing issues

• 
  Noam Lewis (@TheNoamLewis) reported 49 minutes ago

  @user50094473 Which language are you trying to use lsp with? What have you tried? Best if you can open a GitHub issue 🙏

• 
  Shohag Hossain ⚡️ (@Iammdshohag) reported 52 minutes ago

  Anthropic just gave its most powerful cybersecurity model to defenders without actually giving them direct access to the model. And that distinction is probably the most interesting part of this announcement. Anthropic has started running Claude Mythos 5 inside Claude Security, allowing Enterprise customers to scan their codebases for vulnerabilities and receive suggested patches. Here's why this matters. Mythos 5 is a frontier model with unusually strong cybersecurity capabilities. But giving everyone direct access to a model that can reason about cyber vulnerabilities creates an obvious problem. The same capabilities that help a security researcher find a vulnerability could potentially help someone exploit it. So Anthropic is taking a different approach. Instead of giving defenders a chatbot where they can freely prompt Mythos 5, Claude Security runs the model in the background. You point it at a GitHub repository. Mythos 5 scans the codebase, traces how components interact and looks for vulnerabilities that traditional pattern-matching scanners might miss. Then you don't get the raw model output. You get the security finding. Each finding includes a CWE category, confidence level, severity rating and a suggested fix. And there's another important layer. The suggested patch isn't automatically pushed into your code. You can open the fix in Claude Code on the web, but a human still has to review and approve the patch before it gets implemented. That gives Anthropic a pretty interesting middle ground. Defenders get access to the useful part of Mythos 5's capabilities without getting unrestricted access to its most sensitive cyber reasoning. And Anthropic isn't stopping at Claude Security. The company says it's working with cybersecurity partners to integrate Mythos 5 directly into the security products organizations already use. Then there's the money. Anthropic is launching a $35 million Defender Advantage Fund in Claude credits for organizations working to secure open-source software. The goal is to help projects find and patch vulnerabilities, automate parts of the security process and experiment with new defensive approaches. Anthropic is also expanding its Cyber Verification Program, with plans to give vetted defenders broader access to dual-use cybersecurity capabilities. And I think this points to something bigger. We're entering a phase where AI isn't just helping developers write code. It's increasingly helping security teams attack-test that code, find weaknesses and propose fixes. The interesting question isn't whether AI will change cybersecurity. That's already happening. The real question is: Can AI give defenders the advantage without simultaneously making the attackers more powerful? Anthropic is betting that controlled access to the results rather than unrestricted access to the model is one way to make that possible.

• 
  CUTE (@Quinmooda) reported 54 minutes ago

  𝗨𝗦𝗗𝟭 𝗩𝗦 𝗨𝗦𝗗𝗧 𝗩𝗦 𝗨𝗦𝗗𝗖: 𝗛𝗢𝗪 𝗠𝗨𝗖𝗛 𝗖𝗢𝗡𝗧𝗥𝗢𝗟 𝗗𝗢 𝗧𝗛𝗘𝗬 𝗛𝗔𝗩𝗘? All three are centralized stablecoins. That means issuers retain certain administrative powers over user-held tokens. But those powers aren't identical. A closer look at their smart-contract permissions reveals an important distinction. 1 / USDC: Freeze Circle can blacklist addresses and pause the USDC contract. A blacklisted address can no longer send or receive USDC. However, the current contract does not provide an admin function to directly transfer or destroy the USDC held by that address. USDC is also upgradeable, meaning the current permissions don't necessarily represent every permission that could exist in a future implementation. 2 / USDT: Freeze + Destroy Tether can blacklist an address and freeze its USDT. But it goes one step further. The contract includes destroyBlackFunds, allowing Tether to destroy the USDT held by a blacklisted address and reduce the total supply accordingly. So even if the tokens sit in a cold wallet controlled by the owner, the issuer can still intervene at the token-contract level. 3 / USD1: Freeze + Transfer + Reallocate This is where things become more interesting. USD1 includes administrative functions for freezing, unfreezing, pausing, minting and destroying. But the current V2 implementation also includes: → drain
→ reallocate After an address is frozen, drain can move its USD1 to an admin-controlled address. reallocate can assign frozen USD1 to another address. That means the issuer's control isn't limited to making the balance immovable. It can potentially change where that balance is held at the smart-contract level. So the simplified comparison looks like this: → USDC: Freeze
→ USDT: Freeze + Destroy
→ USD1: Freeze + Transfer + Reallocate The important distinction is transparency. None of this automatically means USD1 is malicious or that user funds will be arbitrarily moved. These permissions are visible in the contract. So if by "backdoor" we mean hidden malicious code, that's a different claim requiring evidence. But if we mean issuer-controlled permissions that can override normal wallet control, USD1 clearly has a significant degree of centralized control. And there is another issue worth paying attention to. The source code publicly displayed on World Liberty's official GitHub reportedly does not match the currently deployed USD1 implementation after the April 2026 StablecoinV2 upgrade. That matters because anyone analyzing only the public repository could underestimate the permissions available in the live contract. The bigger lesson isn't simply that one stablecoin is "good" and another is "bad." It's that stablecoin users should understand what the issuer can actually do. Your private key controls your wallet. But it doesn't necessarily control the rules of the token inside that wallet. That's an important distinction. And in centralized stablecoins, the smart contract ultimately defines just how much control the issuer retains. #TRONEcoStar
@justinsuntron

• 
  mefuri (@mefuri_k) reported 56 minutes ago

  @lukeisandberg thanks but going back with webpack somehow made it worse, tried with the flag after reading some github issues and official docs. It runs on turbopack now though. It run smoothly again now after banging my head into the table many times.