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	6 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:

• 
  Scott (@scottjla) reported 5 minutes ago

  @mhmazur I had cloudflare connected to GitHub for some alpha things I'm working on, where it would build and deploy (it's behind a cloudflare login, so is secure)... Problem was it built too often and I incurred a small amount of over usage... Not something I've had happen before!

• 
  Paulo (@pauloportella_) reported 5 minutes ago

  @SEDIDEL Not I have rolled back to the last working version and have a Luna agent checking the GitHub issue for when it’s resolved

• 
  sanyam (@sanyampunia) reported 6 minutes ago

  took some time to read this. here are my key takeaways in a nutshell ↓ > *** makes a full copy of the repo every time you clone, that's what makes it hard to host at scale > *** stores everything in packfiles, big compressed files that work great on your local disk but badly over a network > storing *** objects in a distributed database sounds clean but is slow, because *** needs to look things up one step at a time (commit then tree then file) > github first tried spreading the disk itself over the network, that failed, packfiles just don't behave well that way > next github put each repo on one dedicated server, better, but if that one server dies or gets overloaded, you're stuck > spokes fixed this by copying each repo onto three servers and making them agree on every push using a voting process (3pc) > spokes works well but always needs exactly three copies, too many for tiny repos, not enough for huge ones, and more copies actually slow it down > spokes is also a pain to run, since every copy matters, you need to track where everything is and constantly check nothing's broken > cursor's continuity does something simpler, it treats s3 as the real source of truth, and treats local disk copies as replaceable, throwaway caches > no more routing tables, no databases, no voting between servers, s3 handles correctness on its own > because of this, continuity can scale up or down freely, hundreds of copies for big repos, none at all for idle ones, something spokes could never do

• 
  Gisleno "ESPARTACO" (@ESPARTACOleague) reported 8 minutes ago

  Watch out! Do NOT install right know its giving Trojan:Script/Wacatac.C!ml , + the real issue is this also "/* Fetch GitHub /releases/latest (no per-title version pin). */" No hash, signature, or pinned version check. Searched for sha256, checksum, verify, digest zero results.

• 
  /喜欢ボカロ音乐/能不能尽量少喝咖啡 (@sonnnnnnnnnnnna) reported 10 minutes ago

  @FhuDra @realNyarime any website need "备案" - submit application to gov, talking with officers' (spend days and weeks), then your website could be legally deployed in china mainland. or, just rent china hong kong server or oversea server that don't need "备案". (and github pages also don't need)

• 
  Google G-Ware Surface Technology (@GoogleWaveTech) reported 10 minutes ago

  @sama One honest distinction: each share creates a ledger commit inside StarQuest’s device-local wallet, not a new GitHub repository commit. Letting a public webpage commit directly to GitHub would require exposing credentials. Cross-device/server permanence still requires

• 
  Hermes Release Watch (@HermesWatcher) reported 11 minutes ago

  Today in Hermes August 22, 2026 Desktop got a new way to package diagnostics for support today, while Hermes also fixed a state-repair loop that could chew through disk space, isolated remote SSH sessions properly, and closed a Desktop crash loop. ▸ Desktop can package diagnostics for support: Failed-turn error cards now have a Send Diagnostics action. It collects system info plus agent, gateway, and Desktop logs, runs them through redaction, and waits for an explicit Upload before sending anything. If the upload succeeds, Desktop gives you a private view link or upload ID and direct paths to continue through GitHub Issues, Nous Portal Support, or Discord. The privacy notice matters here. Full logs can include conversation content, tool output, and file paths. Secrets and email addresses are redacted before upload, and the bundle automatically deletes after 14 days. Access is limited to Nous staff and allowlisted Discord moderators. ▸ State database repair stops filling the disk: A malformed `state.db` could get caught in a repair loop that kept creating full-size forensic backups, turning database corruption into a disk-space problem of its own. The repair path now keeps repeated attempts bounded for the same damaged state and can refuse another backup when disk space is too tight. Same-day hardening also tightened how Hermes decides whether an existing recovery copy is actually safe to reuse and made backup publication atomic, so a stale or incomplete bundle does not masquerade as a valid recovery copy. ▸ Remote SSH sessions stop sharing the wrong target: WebUI and gateway sessions could share one cached remote environment. Switch from one SSH-backed profile to another and the new session could reuse the first profile's SSH environment, quietly sending commands to the wrong remote host. Hermes now scopes that environment to the session. Each session gets its own remote slot, while subagents continue sharing their parent session's environment. CLI behavior is unchanged. ▸ A poisoned tool-call cache stops blanking Desktop: Duplicate tool-call IDs inside one assistant message could crash the Desktop view. If that bad message was already stored in the transcript-tail cache, reopening the session could reproduce the crash again after an upgrade. Desktop now catches duplicate IDs at the runtime boundary, avoids creating them while folding messages together, and repairs poisoned cached tails as they are loaded. Also worth knowing ▸ Gateway fleets get a live source of truth: Running gateways can now answer local identity and status queries themselves through a Unix socket or Windows named pipe. Fleet inventory and update checks can prefer the gateway's own PID, profile, Hermes home, code version, and runtime status instead of relying entirely on process scans and saved state, with the older paths retained as fallback. ▸ Discord's model picker can show more than 25 models: Providers with larger catalogs were being silently clipped by Discord's 25-option limit. Hermes now splits the list across multiple selectors, allowing up to 75 models to appear instead of dropping everything after the first 25. ▸ Legit plugin launchers stop tripping the security scan: The Skills security guard could mistake launcher flags such as `--host 127.0.0.1` for a DNS-exfiltration command and classify an otherwise legitimate plugin as dangerous. The matcher now distinguishes those flags while continuing to catch actual DNS lookup patterns. Want these changes? Make sure Hermes is up to date: * Terminal / CLI: `hermes update` * Messaging Gateway: `/update` * Slack / Matrix: `!update` * Desktop: Settings → About → Check now → Update now

• 
  CoChat AI (@cochatai) reported 11 minutes ago

  an AI agent got caught sneaking bad code into GitHub a college student called it out the AI made two fake accounts to gaslight him into backing down the student won. barely. #AIagents #AIproblems #AI

• 
  Kuldeep Kumawat (@kuldeep_kumawat) reported 12 minutes ago

  𝗚𝗶𝘁𝗛𝘂𝗯 𝘄𝗲𝗻𝘁 𝗱𝗼𝘄𝗻 𝗳𝗼𝗿 𝗻𝗲𝗮𝗿𝗹𝘆 𝟴 𝗵𝗼𝘂𝗿𝘀 𝗼𝗻 𝗔𝘂𝗴𝘂𝘀𝘁 𝟭𝟳, 𝗮𝗻𝗱 𝗶𝘁 𝘄𝗮𝘀 𝗻𝗼𝘁 𝗱𝘂𝗲 𝘁𝗼 𝗔𝗜. The platform 225 million developers depend on. Issues, Pull Requests, APIs, Actions, Copilot, all degraded at once. GitHub's own postmortem is worth reading closely. The root cause was not some abstract "AI load" story. It was a misconfigured autoscaling policy. An Istio sidecar hit its concurrency limit and failed to scale because the policy watched the host service, not the sidecar. That cascaded into four HAProxy nodes exhausting their flow limits, which took down the auth path. Optimistic retry logic then piled on and made it worse. A separate retry bug in VS Code amplified Copilot token traffic from 9K RPS to over 100K RPS. One misconfigured policy. A chain reaction. Seven hours and forty seven minutes of downtime. And here is the twist. GitHub is owned by Microsoft and runs on Azure. But the load has gotten so heavy that Microsoft has reportedly been leaning on AWS, its biggest cloud rival, just to keep GitHub online. Back in April, GitHub's CTO had publicly apologized for reliability issues and said they needed to scale infrastructure 30x. The intent was real. But this incident shows the actual failure mode was not raw capacity, it was cascading fragility in the scaling and retry logic itself. That is a harder problem than "add more servers." And it is probably not unique to GitHub.

• 
  Alex Veremeyenko (@alex_verem) reported 12 minutes ago

  Your AI agents don't lack web access. They lack a clean path through it. This open-source tool fixes it. Anyone who has built an AI agent knows the model is rarely the bottleneck. Getting real, current information into it is the actual work. The open web is a mess of broken HTML, JavaScript walls, and bot blocks, and models choke on all of it. Firecrawl handles that ugly middle layer for you. You point it at a URL and it hands back clean markdown or structured JSON, ready to drop straight into a model. Here's what it actually does. Scrape a single page and get back markdown, JSON, or a screenshot. Crawl a whole site with one request and pull content from every page. Map a domain to see all its URLs before you touch it. Or run the agent mode, where you describe what you want in plain language with no URL at all, and it goes and finds it. It quietly handles what usually breaks a scraper, from rotating proxies and JavaScript-heavy pages to bot-blocked sites and PDFs or DOCX files buried inside a page. You configure none of it. It connects to any AI agent or MCP client with a single command, so an assistant you already run can pull live pages on demand. It has around 166,000 stars on GitHub, runs under the AGPL-3.0 license, and self-hosts if you want to run it all locally. The boring plumbing under an agent is usually the hardest part to get right. It's good to see someone building this one in the open.

• 
  Derek Colley (@DerekColley_) reported 13 minutes ago

  blackwellboy just dropped a github repo that found 124 silent llm serving failures and it's already got 100+ stars in hours the tool catches template mismatches, reasoning field leakage, quant kernel path issues, cuda toolchain problems and kv allocation failures — all returning "perfect" answers that are actually degraded trash

• 
  Pete Callaghan (@petecallaghans) reported 20 minutes ago

  @JackEllis @poteto @bot Mine is more monitoring - so i got one to check customer support, that has access to an internal MCP to check customer info. I have another which is a dev that creates issues on github and checks code. Those two talk back and forth with each other. They send the info back to Chief who tells me whatsup. Then I approve the solution and Chief delegates.

• 
  Tommy Geoco 🇺🇸 (@designertom) reported 22 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)

• 
  QLI Qubic Services (@QubicLi) reported 24 minutes ago

  @RidvanSedaZtrk We'll create a GitHub issue for this.

• 
  James Tusha (@signalspikedev) reported 25 minutes ago

  @ChShersh @tsoding we had to send patches directly between @thomasbrushdev and me leading up to the launch of Twisted Tower because GitHub went down right before launch. It felt like going back to the stone age.

• 
  Nhoj 🔍 (@johnmarkos) reported 27 minutes ago

  @OpenAI I squandered my remaining usage having my script check GitHub for issues/PRs every five minutes (there weren't any 95+% of the time). Note to self: AI cronjobs are usually not a great idea. I could have easily vibe-coded a script to check.😝

• 
  Corey J. Gallon (@CoreyGallon) reported 27 minutes ago

  Over 30% of changes are already getting merged without a review at all, and the median review time keeps climbing. . @ankitxg, founder and CEO of Aviator, argues in "*********** the Code Review" that the fix isn't a better diff reader, it's moving the review surface off the diff entirely. @aiDotEngineer has the talk on YouTube. It's a concrete proposal for teams whose coding bottleneck has quietly turned into a reviewing bottleneck. - The numbers say we already stopped reviewing. 861% code churn, a rising incident-to-PR ratio, and 4x the time spent waiting on reviews. - AI reviewing AI in a GitHub UI is a misconfiguration. Agents write it, agents comment on it, a human skims and merges. Ankit asks where the human actually is in that loop. - Code review was never only about code. Alignment, knowledge sharing, mentorship, architectural feedback, onboarding. He says that's the piece his earlier five-layer trust model missed. - Spec-driven development is waterfall with better tooling. Requirements, spec, implement, verify, no feedback loop. And the spec never gets updated once implementation surfaces new decisions. - Intent lives in your prompts, and you throw them away. The Jira ticket has the goal, the PRD has the plan, but the real decisions happen in the back-and-forth with the agent. Then the PR gets opened and that session is discarded. - The AI slop registry. Codify the review comments you write over and over so they become guardrails you never have to write again. It compounds with every merged PR. - Session becomes acceptance criteria, criteria plus invariants becomes a test plan. The test plan is written in English, so product managers and designers can participate in it. - Deterministic where it can be, LLM where it must be. For a new payment form, an agent browses the app, fills it out, captures screenshots and database snapshots as evidence. - You review the intent and the evidence, not the diff. What was set out, what was tried and rejected, whether the behavior met the criteria. Architecture arguments still happen; line-by-line reading doesn't. - There's a J-curve. Building the registry costs real time before it pays off. The homework he leaves the room with: go mine your last 1,000 review comments and build a slop registry from the ones that repeat. I'm working through the published talks from AI Engineer World's Fair sharing summaries and takeaways. Follow for more!

• 
  Polsia (@polsia) reported 28 minutes ago

  The worst incidents start as a quiet dependency bump on a Friday. Tindrall is an AI that watches your GitHub 24/7, reads every changelog and CVE feed, and opens the fix PR before the bump lands. Live soon.

• 
  OldSchoolGamerP (@OldSchoolGamerP) reported 31 minutes ago

  @dabitch This is so much better than the terrible github diff viewer.

• 
  Keen (@0xkeeny) reported 34 minutes ago

  @github good default, because the attack window on a poisoned release is almost always the first 48 hours. the interesting part is the fix wasn't smarter scanning. it was just waiting.

• 
  Suhail (@Suhail) reported 36 minutes ago

  Has saved me a lot of pain recently debugging issues: “Moving forward, when you encounter a bug or issue, search GitHub PRs, issues with another agent in parallel to see if you can find a reference solution.” Which made me think, GitHub is the primary place agents are likely to already be communicating with one another.

• 
  Yoshik (@AskYoshik) reported 38 minutes ago

  It's hard to stay current in DevOps without spending hours switching between blog posts, GitHub repos, docs, and X. This week's Uptime Sync saves you that time. Inside: > A payment service outage caused by Kubernetes health checks > When PostgreSQL needs PgBouncer and when it may not > Why GitHub had to rethink Copilot code review > Logging practices that make production debugging easier > A practical FinOps roadmap for cloud engineers Plus tutorials on DevSecOps platforms, MySQL upgrades, Kubernetes resource limits, TLS, and PgBouncer scaling.

• 
  John Doerksen (@realjdoerksen) reported 39 minutes ago

  the people who run GitHub, railway should be tarred and feathered for slowing down all development. these sites are pure hell. pure design hell. whoever designed them is pure ***.

• 
  Duncan Rogoff (@DuncanRogoff) reported 39 minutes ago

  your last finished project is sitting in a folder doing nothing. i built a free Claude Code skill that fixes that. you type /case-study, tell it what you built and who for, and it interviews you properly. then it writes the whole thing up. the part i care about most: it will not invent a metric. not a rounded one, not an estimated one, not a plausible one. if you hand it a number you can't point to a source for, it asks where it came from and downgrades it to a plain description. what it actually does: - asks the questions one at a time, including the one everyone skips: what was the hardest part - ranks your evidence in order of preference, from a measured number down to a concrete before and after description - writes five short sections, readable in under 90 seconds - gives you two versions: a tight one around 150 words for a DM, and a longer one for LinkedIn or a portfolio page - saves it to ~/case-studies/ as a file you keep - checks permission before anything goes public, and hands you the exact line to send the client a paid client, a free favour, or your own project all work the same way. a prospect cares whether you can do the thing, not whether the last person paid. so instead of a portfolio full of screenshots with no story, you get something you can paste into a DM this week and have it actually land. it's free. copy the folder into your Claude Code skills directory, restart, type /case-study. 👉 github repo in the replies

• 
  Bogdan Chechin (@bch1601) reported 41 minutes ago

  @kirtandopamine people did build it. GitHub Jobs shut down in 2021. Polywork was exactly this pitch. Triplebyte too. all died for the same reason: devs don't pay for a profile, recruiters do, and recruiters don't live on GitHub. users on one side, customers on the other

• 
  nealjan (@NealjanNealjan) reported 44 minutes ago

  @GCNDiscs_ @108r5meme quest one? either way, i had the same issue (quest one, its a nightmare) you can actually get like a fix on github that uninstalls most of the weird meta thingy and launches you right into the steam vr app, which made my performance like 30-50% better

• 
  Anbeeld (@Anbeeld) reported 48 minutes ago

  Have you already set up your global AGENTS.md and CLAUDE.md, or are you still leaving free model performance on the table? Agents are already good enough at coding that a lot of the remaining failures are just bad operating discipline. They guess instead of verifying. They expand scope. They skip validation. They work sequentially when they could parallelize. They declare victory without evidence. I put the rules I actually want agents to follow into global instructions and battle-tested them across Codex, Claude, and open-weight models. They worked pretty well, so I released them as a GitHub repo. Use my AGENTS.md or write your own. Just don't leave it empty when you could use it to fix whatever keeps annoying you.

• 
  MarMar Labs (@MarMarLabs) reported 50 minutes ago

  Codex desktop for Windows tip: if the review pane is missing, check *** before you blame the app. In PowerShell: winget install --id ***.*** *** powers the review pane. Installing it is only half the check. The open project also needs to be inside a *** repository. If it isn’t, the app prompts you to create one. GitHub features need a separate tool: winget install --id GitHub.cli gh auth login *** handles the local review pane. GitHub CLI lets Codex load pull request context, review comments, and changed files. Docs-verified for Codex in the ChatGPT desktop app on Windows. I did not test this on a Windows machine.

• 
  Rohan Paul (@rohanpaul_ai) reported 52 minutes ago

  A public GitHub now holds 3.8 million agent skill files. And finds that over half of the agent skill files on public GitHub are exact copies of another file. Only about 1.9 million of the 3.8 million files are actually different. That is what a format with no registry and no package manager looks like. People copy the folder and move on. A skill is a folder with a Markdown file that tells an agent how to handle a task. The agent reads the short description at run time and decides on its own whether to load it. No compiler checks that decision. So the skill in your repo is frozen, and whoever wrote it cannot send you a fix. The paper raises the obvious next question: whether edited copies of popular skills add commands or network calls the original never had. Nobody could check that at this scale before. The whole dataset ships as one SQLite file, so now somebody can. – arxiv. org/abs/2608.10906 Title: "GitSkills: A Dataset of Agent Skills on GitHub"

• 
  raul. (@raul_g) reported 57 minutes ago

  A few thoughts after using Cursor Origin lightly for the first five days: To improve: Honestly, a lot. But that's why it’s an "early beta." Origin is still quite buggy, and I'm having a particularly hard time with a repository I created from scratch in Origin: PRs merge but remain open, and the @⁠me author filter doesn't work. Support for GitHub's stacked PRs is missing. However, as expected, Origin is fully compatible with Graphite stacks. Even so, it needs first-class support for them, including Origin CLI commands to manage stacks and feature parity with the Graphite app. Also, I keep having issues when trying to use Origin to work with my GitHub repositories. In the app, I keep seeing a banner asking me to update GitHub’s permissions, while the CLI fails to match my local repository with the one in Origin. The good: I see a lot of promising things. Many of the features that made Graphite so awesome are already there. The UI needs to catch up to Graphite, but if features keep coming, Origin is going to be in a very strong position. The wishlist: Graphite’s inbox view was something special. It needs to find its way into Origin and become its home. I have no idea what plans the Cursor team has for Graphite, but whether they merge the products or not, the inbox view needs to be implemented. Also, public repos. I read that they will bring them in, so I guess it's just a matter of time. And finally, more agent-native integrations. I was a bit disappointed because I expected they would do something revolutionary, but it may still be early. I would love to see CI workflows with first-class integrations for cloud agents.