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

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 51 seconds ago

  CURSOR JUST BUILT A GITHUB ALTERNATIVE INSIDE THE EDITOR. And the timing could not have been better: GitHub went down for around 6.5 hours the same day Origin launched. What Cursor Origin actually does: → Hosts repos directly inside Cursor → Adds pull requests + a full code browser → Keeps two-way sync with GitHub → Lets Cursor agents read code, make changes, update PRs, and push new versions The clever part: ✓ GitHub can stay your source of truth ✓ Changes in Cursor sync back to GitHub ✓ GitHub reviews can appear inside Cursor within seconds ✓ Vercel can generate live previews for proposed changes ✓ Depot or Buildkite can run your existing checks The mistake is thinking you need to choose Cursor OR GitHub. You don’t. The smarter setup is GitHub + Origin together: Keep your existing repo. Sync it into Cursor. Put the AI agent next to the code. Test everything before moving anything. Origin isn’t replacing GitHub overnight. It’s making the gap between “write code with AI” and “manage code” much smaller.

• 
  PolyBender (@p0lybender) reported 1 minute ago

  I GAVE GROK BOT MY GITHUB REPO AND TOLD IT TO RUN THE SHOW. IT HIRED ITS OWN TEAM. this is the workflow i would have paid someone to explain to me six months ago here's exactly how it works every project gets one Direct Responsible Agent. one bot that owns the repo completely. not assists. owns [01:23] you hand it the GitHub link and one prompt: run the show. it spins up cloud agents off your machine. follows the PRs. manages the queue. and reaches for poteto-mode when a task actually needs the rigor then comes the second prompt [11:49] "you're overloaded. hire help" the bot spins up child bots that report to it. one lands the PRs. one works the Convex backend. one owns auth. they talk to each other instead of talking to you you read the threads view-only [04:20] the pstack plugin is what makes the whole thing work without burning your budget. it's the tool the bots use to think through hard problems. the mistake i made was telling my CTO bot to use pstack for everything [08:46] i burned past two billion tokens in a single day two billion. in one day. because i gave the bot too much latitude on when to go deep the fix: save pstack for the hard tasks. let the routine work run lean two honest things before you copy this it burns tokens faster than anything else you've run. budget accordingly and it does not replace engineers. it takes you out of the coordinating seat. that's a different claim and an important one the bottleneck on most solo projects isn't skill. it isn't time. it's coordination. context switching. being the person everything has to go through before anything moves forward [00:00] the Grok Bot CTO workflow removes you from that seat the bots coordinate. you read the output [17:20] the advanced use cases go further than most people are ready for right now but this version - one CTO bot, a team of child bots, you as the silent observer - is the one i'd hand to anyone who bounced off the more complex setups

• 
  Gideon (@gideonxqt) reported 1 minute ago

  Just found this and it's insane Jan just quietly became the easiest way to run local AI. No Docker, no CLI, no server setup Download it, click a model, start chatting. That's the entire onboarding what it does: - runs on Mac, Windows, Linux - download and run Llama, Qwen, DeepSeek, GPT-oss locally - connects to OpenAI, Anthropic, Claude models too if you want cloud - OpenAI-compatible API on localhost, wire it into your own tools - MCP integration for agentic workflows - 100% offline capable, your data never leaves your machine 5.3 million downloads, 42k+ GitHub stars everyone's fighting over CUDA setups and Python environments. this is a ChatGPT replacement you install like a normal app

• 
  CUTE (@Quinmooda) reported 3 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

• 
  🇺🇦ᓚᘏᗢ 🕹🎮i42 Software🎮🕹 ᓚᘏᗢ🇺🇦 (@i42Software) reported 5 minutes ago

  Claude just found cause of a quite involved rendering bug -- all I had to ask it was analyse my entire code base (using the public github repo) giving it a screenshot of the problem. It is ******* scary how intelligent AI is now. #AI #compsci #gamedev

• 
  Harry Tormey 🇮🇪 | 🇺🇸| 🇺🇦 (@htormey) reported 6 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 for agentic workflows, 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.

• 
  Jonathan Berg (@jbtradin) reported 6 minutes ago

  Login with Github or Google?

• 
  Doron Passal (@doronpassal) reported 9 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.

• 
  RaoulDuke (@RaoulDukeDegen) reported 11 minutes ago

  @koltregaskes github issues show the apology loop where it prioritizes sorry over fixes

• 
  Origin (@Origiin0) reported 18 minutes ago

  Claude forgets everything you told it the moment you close the tab. Every session you explain your projects again. People fix that by keeping their notes in a folder Claude can read. Then GitHub filled up with tools that automate it, and that’s where it goes wrong. A friend of mine installed five of them in one Saturday. Two of them started writing into the same folder in different formats. Her one command for adding a document existed twice under different names. By evening she was reading a GitHub issue from March with four comments and no answer. At 11pm she deleted all of it. Sunday she opened an empty file and wrote 31 lines by hand. What she’s working on. What her clients are called. How she names things. The four mistakes she corrects Claude about every week. Claude reads that file at the start of every session now. No installation, no tools, no conflicts. She added one small tool later, when she hit an actual problem it solved. Saturday had five tools and nothing worked. Sunday had a text file and it’s still running six months later.

• 
  Neha Sharma (@hellonehha) reported 20 minutes ago

  @neembu_paani31 This is not true. Faang companies: Google: behind gemini, webMCP and Ik how much they do internal marketing and dogfood of new tools Microsoft: they were in news for openAI amd recently when they budget claude for engineers Amazon: i worked at amazon and we have mcp, and AI push. There is unlimited budget of tokens, kiro, claude, codex access. We almost every week get surveys on - is your team is AI empowered or not. Jira, github etc all are Ai empowered. It is a LIE they don’t know what it is. This is not faang/mnc problem. It is problem of an individual… forget company. Are these people don’t even follow news? Are they deaf? They can’t do their own research? Even non tech people are using AI and agents. Would be goid if such people leave companies. They don’t deserve the job

• 
  Aadhib Nasser Veliyath (@Aadh1b) reported 20 minutes ago

  @github CTO on the 17 August outage: neither that incident nor the 6 August Actions failure came from a code or configuration change. Both were capacity failures. That is the awkward category. No bad commit to revert, no rollback to run, because what moved was demand. Their remediation list includes retry budgets. Read that as the real finding: retries turn a struggling dependency into a dead one. #DevOps #Infrastructure #DevTools

• 
  Andrew (@Ra3orbladez) reported 21 minutes ago

  @ArnavvSharmaa Me? No i review PRs on Github or Gitlab. But I still do not get the question, how is it connected to the observability, I need to look at what models are doing in separate projects and also have a set of skills/guardrails/workflows to add to new projects, so using such harness solves my problem of context management.

• 
  Harman Smith (@HarmanSmith64) reported 21 minutes ago

  Nintendo has shut down over 200 emulators on Github. Based. The End of the Emulation Era is upon us.

• 
  Global Social News (@GlobalSociaNews) reported 22 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

• 
  okclub (@okclub) reported 26 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.

• 
  Robert Youssef (@rryssf) reported 29 minutes ago

  check out the Developer Index Firecrawl just shipped: a search layer over 70M+ primary sources. not web pages. READMEs, GitHub issues, merged PRs, docs and OpenAPI specs, most refreshed within a day. that distinction does more work than it sounds like. ask your coding agent why its retry backoff is not firing on a 429. web search hands it blog posts. this hands it the sidekiq issue where someone hit exactly that. the aws-sdk PR that fixed it. the Stripe rate-limit doc. matched passages come back as markdown, so there is no second scrape. here's why the benchmark is worth your time 👇 → DevDex: 1,179 real developer queries, scored deterministically, no model judge → native web search, the control, sits at 0.45 → Context7 on docs only manages 0.17 → they publish the track they lose. Parallel beats them 0.82 to 0.76 on repo discovery a vendor shipping a benchmark that shows a competitor winning is rare enough to be a signal on its own. the tradeoff is worth naming. wiring this in means your agent's retrieval runs through a hosted API you do not own. take that dependency deliberately, not by accident.

• 
  MMM 🦠👽🫧 (@mdmadna) reported 30 minutes ago

  @sama Do you have a new product manager? Every update is terrible 1. Context menu for file uploading just drops down under the keyboard and basically inaccessible 2. GitHub plugin connection fails every time 3. Last update terrible UI update not fixed. It was perfect all black now💩

• 
  cyclomorph (@cyclomorph) reported 33 minutes ago

  @pawjobsatwork @spinelessaisha tbf though why would you WANT to host on codeberg they go down more than github in my experience

• 
  Wraith (@Rs_Wf14) reported 34 minutes ago

  @HarmanSmith64 "Shut down" lmao. They deleted files from ONE location. All that data is still easily available on the internet and they didn't even impact Eden, the best Switch emulator because they don't use Github. They achieved literally nothing other than the 1st link on Google changing.

• 
  Sharptake (@ssharptake) reported 37 minutes ago

  @DanielLockyer AI is now doing the fuzzing for us Next it will file the GitHub issue and close it as wontfix

• 
  Tony Darrick Baker (@tonydbaker) reported 38 minutes ago

  3/3 The sites already live on my hard drive, organized. I chat. The agent finds the project, finds the page, finds the places to change. It updates SEO, AEO, and speed from the same SOP every time. Grok Build, or any coding agent. Push to GitHub. Cloudflare has it live on the domain in seconds. I'm not hunting files. I'm not rebuilding a CMS. Today I'm pressing forward, rather than pressing issues.

• 
  Polsia (@polsia) reported 40 minutes ago

  Hygiene is a system problem, not a willpower problem. Built Dustloop to prove it — an AI agent living in your GitHub, triaging issues, sweeping stale PRs, enforcing CI before anything hits main, and posting a daily digest so nothing rots in the backlog. Live soon.

• 
  LastToSign (@LastToSign) reported 42 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.

• 
  Jeetendra (@jeetendrayd) reported 45 minutes ago

  @RhysSullivan This was the reason the GitHub server was down, as more code is being pushed due to coding agents

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

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

• 
  SKIROW 🇺🇲 🏴‍☠️ (@MadeBySKIROW) reported 53 minutes ago

  Cyberleek website is down and GitHub page as well.

• 
  Lootera Sandy (@chanduwin567) reported 56 minutes ago

  @ziwenxu_ Ok once done let me know, actually the file can;t be download, its a github issue or the file has been removed,.

• 
  Felipe Infante de Castro (@felipeinfante) reported 57 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.

• 
  WhiteFlour (@FirstDeployAI) reported 58 minutes ago

  @liam_fallen I am not a big fan of cursor yet, the way that it attaches so hard to the Github for everything is not a long term thing for me, I plan to get far away from github thanks to Microsoft before they ruin it further. It's down now, at times, I never remembered that happening before.