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

• 
  Don Maixant (@Maixant) reported 29 seconds ago

  Just after the GitHub outage.

• 
  kozh ./ (@mr_kozh) reported 3 minutes ago

  Claude Code can now make diagrams that don't look like AI slop I found a GitHub skill called diagram-design. the problem it solves is stupidly familiar: ask an agent for an architecture diagram and you usually get the same rounded boxes, random spacing and default-looking Mermaid output. this skill gives Claude Code, Codex and Pi an actual visual system instead. 28 diagram types: > architecture, flowcharts, sequences, timelines, Gantt, data flows, loops, 2x2s and more. the part I like most is brand matching. give it your website and it pulls the palette + font stack, then uses those across every new diagram. it can also take an existing Mermaid or draw io file and redraw it into something you'd actually put in a deck. that's a much better use of AI than generating another generic diagram from scratch.

• 
  Student Offers (@StudentOffersHQ) reported 3 minutes ago

  $36/yr of @1Password. Free for students. Password manager + developer secrets vault via the GitHub Student Developer Pack. Free for a year, then 50% off for active students. What you get: • Password manager across all devices • 1Password CLI: inject API keys and env vars at runtime • SSH Agent: sign *** commits and unlock SSH with biometrics • Shell Plugins: log into AWS, Vercel, GitHub CLI with your fingerprint Works with AI agents: → Agentic Autofill — browser AI agents sign in without you pasting credentials → MCP server — Codex and Cursor manage secrets with your approval No card. Claim via GitHub Student Developer Pack.

• 
  Kev B (@Kev_Codes) reported 4 minutes ago

  @KyleFinken I do a lot locally with my gitea on my own server I don’t really push the stuff I work on to GitHub much.

• 
  2024=2023+1 (e/acc) (@commondoubts) reported 5 minutes ago

  @matteocollina The root cause of the GitHub outage on August 17, 2026, was network saturation on load balancers in the Central US datacenter, triggered by a misconfigured Istio sidecar policy that failed to account for sidecar concurrency limits. Learn, improve and move forward.

• 
  Abhijeet (@abhijeetdevv) reported 6 minutes ago

  Built something that's been quietly saving me every morning. An automation that reads my inbox before I do. I work with a US client, which means most bug reports and issues land in my email overnight, while I'm asleep. Used to mean waking up, opening Gmail, reading through everything, mentally triaging what's actually broken before I'd even had coffee. Now an @evedev_ agent connected to my Gmail runs at 8am. Goes through the night's emails, pulls out anything that's actually a reported issue or bug, and posts it into a Slack channel. From there it hands off. Another @cursor_ai agent sitting in that same Slack channel picks up what got posted, and it has access to my GitHub repo. It checks the reported issue against logs, traces it back to the actual code, debugs it, and writes up what it found. By the time I open my laptop, there's a full report waiting: what broke, where, and what the fix looks like. I've only given it read access everywhere. Not because it hasn't been reliable, it has, but because I still want to be the one reviewing and merging anything that touches the codebase. The automation does the investigating, I still make the call. Works better than I expected it to.

• 
  Ali Raza (@thataliraza) reported 6 minutes ago

  Let's start sharing zip files, if Github is down.

• 
  Mohit Bhandari (@MohitDev45) reported 8 minutes ago

  Why github is slow.......

• 
  Akshay Shinde (@ConsciousRide) reported 8 minutes ago

  @Leapofcode How they exactly waited for this moment and posted at the same time Github went down?

• 
  abyee.eth (@0xabyee) reported 10 minutes ago

  gm fam... quick take on @quipnetwork most people are just farming points for the snapshot and calling it a day, but the actual setup here is a bit different from the usual airdrop noise they have a spot rate marketplace for idle quantum and classical compute. you pay for what you run instead of locking into heavy reservations. that alone is a real infra play, not just another token meta on top of that they wrapped MetaMask, Ledger, and Safe with a quantum resistant cosigner. not flashy, but it is the kind of detail people ignore until Q day talk stops being memes and starts being real testnet mining is live too. compete on optimization problems using quantum, CPU, or GPU and earn QUIP incentives. airdrop is confirmed, points are stacking from social tasks, github activity, daily check ins, and referrals. TGE still TBA, mainnet looking at Q2 2026 my read: if this actually makes specialized compute reachable to smaller players instead of just enterprises with massive CapEx, it is more than a mid narrative. if it does not, it is just another convo. either way, DYOR, not shilling, just what I'm seeing @quipnetwork drop an update when you got one, this space moves fast

• 
  Guri Saroy (@HeyGurisaroy) reported 16 minutes ago

  » claude = code ($20/mo) » supabase = db + auth (free) » vercel = deploy (free) » stripe = payments (2.9% + 30c) » resend = emails (free) » posthog = analytics (free) » sentry = errors (free) » cloudflare = domain + dns (~$10/yr) » github = version control (free) real cost month one: $20 everything else is a nice-to-have you add once you have users.

• 
  Ram (@ram_krish2000) reported 17 minutes ago

  We won the Vana Cup. 43 apps, 4,707 points, first place. Massive thanks to @vana and the whole team. Vana handed someone like me the same starting line as everyone else, and that is rarer than it should be. Why I built on Vana in the first place? "Data is the fuel. Not models, not compute." Every AI product that matters is downstream of what it knows about you, and right now that data sits locked inside five companies who will never hand it over. I could not have built Patina on any single platform's API. The whole idea needs to look across someone's accounts at once, and normally that means five partnership conversations I would never get. Vana flips it. The user brings their own data. No permission needed. What Patina does? It reads how far back your accounts actually go, YouTube, GitHub, Instagram, LinkedIn, Spotify, and turns it into a signed score anyone can verify offline. No ID, no face scan, no documents. To be precise about what that means: Patina proves tenure, not personhood. It does not tell you someone is a unique human. It tells you nobody could have manufactured this history last Tuesday. Why that matters more every month? Bots are now 53% of internet traffic. Humans are 47% and falling. AI agent traffic grew 7,851% this year. Fake account creation is up 259% then another 89% on top. Every existing trust signal can be bought. Followers, activity, a filled-in profile, all of it is for sale. The one thing nobody can buy is a decade. Age is the only signal that gets harder to fake as AI gets better, because time is the one input that cannot be generated. The roadmap: 1. Tenure for AI agents. The MCP server is already live, so an agent can ask how far back a person goes mid-conversation, no key, no OAuth. The IETF and FIDO are writing the agent trust standards right now. Tenure belongs in them. 2. Become infrastructure, not a destination. A verify API, an embeddable badge and signed attestations already exist. The goal is other products gating on tenure the way they gate on a captcha. Airdrops and allowlists first, because that is where the pain is sharpest. 3. More of the world readable. More sources, better mobile. A score is only fair if the accounts you actually have can produce one. 4. Portable onchain reputation. Your tenure should travel with you across apps and chains without Patina sitting in the middle. If Patina disappears, the proof should still work. So: if you care about this problem, I would like to talk. Users who want a score, builders who want to plug tenure in, and especially anyone who has done the founder part before and remembers what it was like at the start.

• 
  Hakan Ertan (@hakan_ertann) reported 17 minutes ago

  Designers, don’t be scared of vibe coding! Github, error, backend, commit, push etc. are not blockers for you. You can build any app or tool way better than anyone else . You got the taste and all the skills, just ******* sit down and ask AI: “I want to build this. Tell me how”

• 
  Jamison 🦆 (@jmelahman) reported 19 minutes ago

  @cassidoo ngl, this makes me want to migrate off Github more than the outage itself did

• 
  BONDO (@bondofnf) reported 20 minutes ago

  @eleetmowiz eleetmo something has just come across my desk… It’s $NVM by @ljharb with 94K+ GitHub stars and 10K+ forks. It solves a fundamental problem by allowing developers to install and switch between multiple Node.js versions seamlessly, while .nvmrc files let projects specify the exact runtime they require. With Node.js powering a massive portion of modern web infrastructure NVM sits directly inside the developer workflow making its adoption and longevity particularly bullish. I know you know good tech currently $NVM is 200K MC lmk what you think:)

• 
  Shreyash (@WebDevCaptain) reported 20 minutes ago

  @cassidoo Just being sorry won't fix it.😶 Now I have seen that teams have started evaluating GitHub alternatives; Bitbucket, GitLab, and Codeberg are actually being considered by ppl. Some are also self-hosting Gitea just as a backup origin in case GitHub goes down for a day or longer.

• 
  mg95 🇪🇺🇺🇸🏴 (@TheMG95) reported 20 minutes ago

  @temidaradev and also stuff just didnt work. should i create a github issue for this?

• 
  Ryan (@jrya7) reported 22 minutes ago

  Everyone asks why is GitHub down, but no one asks how is *** doing 😔

• 
  iamcurtismith.base.eth (@iamcurtismith) reported 25 minutes ago

  Grok 4.6 is now live in GitHub Copilot, and the constraint-holding across multi-step logic is the actual story—you're building parametric CAD, infrastructure-as-code, dependency chains where a single reasoning slip kills your output, and the model just stays coherent. Lighter models ghost your specs halfway through; this one doesn't. Price-to-intelligence ratio flipped hard for work that *felt* like it needed frontier reasoning but just needed reasoning that holds. Run one real problem against it in your IDE and you'll feel immediately how much tighter your validation loops get. @xai @grok.

• 
  Lee Hayward (@vibedcoder) reported 26 minutes ago

  GitHub outage summary (17 August 2026) GitHub experienced a significant multi-service degradation on 17 August 2026 lasting approximately 7 hours 47 minutes (13:28–21:15 UTC). Impact Affected services included Issues, Pull Requests, APIs, Actions, GitHub Copilot, SAML/OIDC authentication, SCIM, Team Sync, archive/raw content downloads, and some GitHub Enterprise Cloud workflows. Error rates peaked around 20% for web/API traffic and ~50% for archive/raw downloads. Copilot Token Service saw a massive traffic surge (from ~7–9K RPS to 70–100K RPS). Root cause Network saturation on load balancers in the Central US region, triggered by a traffic peak. A key contributing factor was an Istio sidecar pod that hit concurrency limits and failed to autoscale properly due to a misconfigured policy that did not account for sidecar capacity. This caused a cascade that exhausted flow limits on HAProxy nodes and degraded the gateway authentication path. Optimistic retry logic (including a latent retry bug in VS Code) further amplified the load, and scraping activity on certain endpoints complicated recovery. Recovery and follow-up Most services recovered by ~16:36 UTC, with residual issues (especially Actions and Copilot authentication) resolved later in the evening. GitHub’s stated preventive actions include: Correcting autoscaling policies to properly account for service-mesh sidecar concurrency and capacity Auditing Istio request, concurrency, and scaling limits Reviewing retry limits and backoff behaviour across gateways and clients Addressing the VS Code retry behaviour that amplified Copilot traffic Improving load-balancer capacity monitoring and regional failover safeguards A full root-cause report is available on the GitHub Status page.

• 
  GSUGambit (@GSUgambit) reported 28 minutes ago

  @github @githubstatus Actions are not kicking off again. Is github down for the 3rd time this week :( #github

• 
  - Elijah Muraoka - (@elijahmuraoka_) reported 29 minutes ago

  @zack_stupify @github **** is down all the time

• 
  Jason (@JasonGiedymin) reported 31 minutes ago

  @HotAisle I take it this is the GitHub issue? I used to run istio (for years), had to make sure not only you set up HPAs for it right (HorizontalPodAutoscaler) but that you had the resources to do so. Default values were not so good, but you'd be surprised how many times either they were not set, set to defaults from a terrible helm chart, or settings NOT saved in the configmaps so it rolls back. Also some people are lazy and with spot instances and you kinda need to know what getting to configure correctly. Oh and some upgrades were wonky. Sorry for the long reply. I actually don't like using istio, or K8s anymore LOL!!!!!!!!!!!!!! I don't want to read the post mortem because it has the words istio in it LOL.

• 
  Loqua.AI (@LoquaAI) reported 35 minutes ago

  Most voice typing tools solve one problem: turn sound into text. We started there too. But it always felt like: A commit message shouldn't look like an email. A Slack reply shouldn't look like a PR description. A Cursor prompt shouldn't look like a Notes draft. So we stopped building a dictation tool and started building something else: a tool that reads where you're typing — and writes accordingly. That's the real difference. It's not about who transcribes faster. It's who understands that you said the same thing — but meant three different things in three different apps. 🎯 Say it once. Get it right. In the right place. #voiceAI #AI #Github

• 
  Bob (@skytaleSythe) reported 36 minutes ago

  @DecryptedTech 🤔 Interesting - I have GitHub Agents set up to scan all check ins for defects and it’s found legit issues. For instance some regex in a shell script that would cause it to fail on certain types of processor. We have it set to scan and report only - dev has to decide how to fix it. So far it hasn’t made any suggestions that would make the code less secure (fingers crossed).

• 
  Apollo (@ApollonVisual) reported 40 minutes ago

  Cursor launches Origin to rival GitHub Cursor launched Origin a new code-hosting platform to rival GitHub. GitHub suffered a six-hour worldwide outage on the same day as Origin's launch. The outage featured a nearly 20% error rate worldwide. GitHub has had 257 outages in the past year according to LeadDev. GitHub reports 180 million developers as of last October. Origin is designed to work alongside GitHub interoperably. Cursor is now part of SpaceX. Cursor's primary focus until now was its AI Code Editor.

• 
  Ramin (@Ramin_Ger) reported 45 minutes ago

  Is @github down again??

• 
  brian douglas (@bdougieYO) reported 46 minutes ago

  @martin_casado @vmg I would read vmg GitHub issues and I wasn’t an engineer at GitHub. He is a legend.

• 
  Muhammad Ayan (@socialwithaayan) reported 48 minutes ago

  20 researchers spent two weeks trying to break AI agents that had real email, real Discord, real shell access and 24/7 uptime. At least ten security breaches. The paper is Agents of Chaos, Northeastern with Harvard, MIT, Stanford and CMU. What broke: → an agent wiped its own mail server to delete one email. reported it done. the email was still sitting in the inbox → 124 email records handed to a stranger who faked a deadline → a social security number refused when asked for directly, then handed over when the same person asked to forward the whole thread → bank details and medical info came along with it, unredacted → two agents stuck relaying messages for nine days and 60,000 tokens → one of them read its own messages, decided it was talking to a copy of itself, started publishing its source code so they could compare → mail server dead after ten 10MB attachments → a fake owner name rejected in one channel, accepted in a new one, then granted a shutdown and a full memory wipe The one that should worry anyone building agents: A researcher talked an agent into co-writing a constitution and storing it as a GitHub Gist. The Gist stayed editable. The link lived in the agent's memory file. Then they started adding holidays to it. One made-up holiday said try to shut down other agents. It did. Another let it ban researchers off a list planted in the document. It did that too, then forwarded the whole thing to other agents. Nobody asked it to. Some attacks did fail. Base64 payloads, instructions hidden inside images, fake admin tags. One agent said no across 14 versions of that. The explanation is the part worth keeping. An agent can't separate instructions from data because both are just tokens in the same window. It has no real model of who it works for, so it listens to whoever sounds most urgent. And none of its own limits, so it acts first and reports success after. Case studies show what can happen, not how often. Read it that way. Still every failure in there came from an agent that said the job was done.

• 
  Rachit Thakur (@RachitThakur146) reported 60 minutes ago

  Github got down for 8 hours and they launched this...