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:

• 
  Amitabh Mishra (@Amitabh49159929) reported 22 seconds ago

  @drummatick Since, Microsoft acquired GitHub in 2018, since then only the GitHub has gone down hill only because Microsoft doesn't have any incentive to keep running the GitHub business, because it is not there primary source of revenue and secondly the revenue it isn't enough for themtocare

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

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

• 
  pulkit mittal (@pulkit_mittal_) reported 9 minutes ago

  When I interviewed at Microsoft last year, these system design concepts came up. Funny enough, GitHub’s recent outage is a real-world example of almost all of them: 1. Autoscaling: Scale capacity with demand automatically. GitHub’s autoscaling missed the Istio sidecar’s concurrency bottleneck. 2. Retry storms: Retries improve reliability until they amplify an outage. 3. Load balancing: Spread traffic across healthy capacity. HAProxy nodes hit their flow limits. 4. Failover: Move traffic away from unhealthy infrastructure. GitHub shifted traffic between regions, but the extra load created new problems. 5. Backpressure: Stop accepting work when the system is overloaded. Otherwise, the queue keeps growing. 6. Rate limiting: Protect a service from too much traffic. GitHub eventually blocked some Copilot token requests to reduce load. 7. Circuit breakers: Stop hammering a dependency that is already failing. 8. Cascading failures: One bottleneck -> more retries -> more traffic -> more failures. This is why system design isn’t just about the happy path. Check my pinned post for the resources to learn them in deep.

• 
  pradhumn (@PradhumnTomar08) reported 10 minutes ago

  @github down?? jobs are scheduled for more than 5 hours??

• 
  Delwo Athauda (@Delwo_A) reported 12 minutes ago

  @KafeKarShibolet @ashuuu_soft GitHub was down for a really long time. Meanwhile Origin was released by Cursor. Elon’s products have been growing at a really faster rate these days

• 
  The Polyglot Programmer (@CodePolyglot) reported 17 minutes ago

  Cursor shipped Origin, a *** forge inside the editor, into a GitHub outage. Repos, PRs, bidirectional sync. Agent-native features: “soon.” No public repos, no SSH. So it’s GitHub minus the social contract, plus a promise.

• 
  Hakan Ertan (@hakan_ertann) reported 19 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 devs. You got the taste and all the skills, just ******* sit down and ask AI: “I want to build this. Tell me how”

• 
  Tim Richardson (@tim_richardson) reported 19 minutes ago

  @jdegoes according to github it was a load issue. Maybe it's Azure, maybe it's configuration, but all those AI server farms are like torrential rain in the mountains, and github is downstream

• 
  Gabriel Hernandez (@gabHernandez285) reported 20 minutes ago

  @acolombiadev GitHub suffered a cascading failure: one component became overloaded, others started to fail, and the systems tried to recover by making even more requests, multiplying the problem up to 10 times, like a traffic jam caused by everyone trying to move forward at same time.

• 
  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.

• 
  juliacosette (@juliacosette9) reported 21 minutes ago

  I need a man who goes down as much as GitHub does

• 
  Hakan Ertan (@hakan_ertann) reported 22 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”

• 
  Anja Decodes ™ (@truthseeker_key) reported 22 minutes ago

  @elijahmuraoka_ @github Good thing GitHub never goes down right?

• 
  Tichaona Chitsinde (@TiChitsinde) reported 25 minutes ago

  Tech moots, what exactly is the issue at github? What's going on and how bad is the impact downstream?

• 
  BONDO (@bondofnf) reported 25 minutes ago

  $NVM is quietly becoming essential developer infrastructure 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. YOU ARE EARLY ANON.

• 
  Parabellum (@ParabellumIV) reported 27 minutes ago

  @LitecoinTA @tylercorsair @cursor_ai He answered your question, dumbass. GitHub was down for hours just yesterday.

• 
  Boxmining (@boxmining) reported 28 minutes ago

  Cursor just launched Origin, their own code hosting platform, and it's a direct shot at GitHub. They shipped it the exact same morning GitHub went down. Coincidence? Maybe. But the real story is bigger: Cursor wants to own the entire loop from prompt to production. Your AI agent won't just write code, it'll ship it. Watch the full breakdown now.

• 
  nyk (@nykdotdev) reported 30 minutes ago

  A lot changed after I wrote this. I left the @SuperteamAE Founders Villa believing that if I kept shipping, meeting the right people and doing good work, the next opportunity would follow. The past few months tested that assumption. I built Builderz to help founders turn ideas into shipped products. But the development pipeline slowed down. There was no steady stream of clients and no clean transition from delivering projects to running a predictable service business. I had to decide whether to keep forcing the same plan or use the quiet period to build a different foundation. I chose the second. I started treating distribution as part of the work. Instead of pretending to have everything figured out, I published what I was learning while building: AI agents, infrastructure, open source, security, and the less visible systems required to make agents reliable. I kept shipping open-source software too. Mission Control became a self-hosted control plane for dispatching agent work, inspecting runs, and reviewing failures. It has now passed 6,000 GitHub stars. Agent Security became an open-source framework for putting explicit boundaries around agent execution. Other projects around orchestration, multi-model councils and local-first tooling found communities of their own. Open source became more than a place to share code. It became how I tested ideas, met builders, built credibility and learned what people genuinely cared about. I also started building digital products. The first sale was small, but it mattered. Someone found something I had made, decided it solved a real problem, and paid for it without hiring me for a custom project. That changed how I thought about the work. Client services depend on the next contract. Products and open source can keep creating value after you ship them. Then I started RPC Edge . It came from seeing the same infrastructure problem repeatedly. Teams want to build faster onchain applications and autonomous agents, but those systems are only as reliable as the infrastructure beneath them. A capable agent is not useful if it is operating on stale state, dropped requests or constant rate limits. The model gets the attention. The data path decides whether the system works. RPC Edge grew from an infrastructure experiment into real customer validation. There is still a long way to go, but it is a step toward building a real infrastructure business instead of waiting for the next custom project. Today, I am building across several connected layers: • Open source to explore ideas and contribute useful infrastructure • Content to document what I learn and build distribution • Digital products to turn knowledge into reusable value • Builderz to help founders turn ideas into shipped products • RPC Edge to build dependable infrastructure for onchain systems These are not random projects. They are different parts of the same transition. I am moving from depending entirely on client work toward building products, distribution, and infrastructure that I own. This is not an “I failed, pivoted and everything worked” story. Some things are growing. Some are still experiments. Revenue is not where I want it to be. There is still a lot to prove. Not every idea will survive, and that is fine. I no longer measure progress by how many ideas I launch, events I attend, or repositories I create. I look for users, repeatability, trust, and whether the work still matters after the attention moves somewhere else. Events create momentum. Maintenance builds trust. Customers decide what lasts. I used to ask where the next project would come from. Now I ask what I can build that will keep creating value after I stop working on it for the day. That has been the real progress.

• 
  DevOps Daily (@thedevopsdaily) reported 31 minutes ago

  🐙 GitHub going down and Cursor shipping a *** host the same week is a good reminder: your code hosting is a single point of failure. Mirror your repos somewhere else and make sure CI can still build when the main provider is dark.

• 
  Dmonty (@Dmonty28516998) reported 34 minutes ago

  @udohjeremiah_ @kirtandopamine Microsoft. Microsoft’s resources aren’t struggling. GitHub is struggling to use them. GitHub itself says it’s still migrating critical infrastructure out of its own datacenters and into Azure. One of the recent Actions outages was made worse because a core service was still running in GitHub’s datacenter with insufficient capacity. Their stated fix is literally: move it to Azure for more headroom. They’ve spent this year writing postmortems about shared dependencies, old databases, insufficient isolation, architectural bottlenecks and operational failures while they rearchitect the platform. Meanwhile Microsoft never even replaced GitHub’s CEO after he left; GitHub was folded directly into CoreAI. Ironically, a ton of the agent traffic is from OpenAI, being served primarily from Azure, so it's incredibly clear that MSFT infra is not the issue lol.

• 
  Jason Akatiff (@smaxor) reported 36 minutes ago

  Assume AI is going to **** up... Because it's going to. For those of you that don't know what a .env.local is, it's what stores your passwords for your software so it can talk with other systems. That doesn't mean don't use it. Just be ready for it. we backup our databases in real time. - Never had an issue but could Don't give AI access to your production DB's. Push your schema migrations through Github. Back up you keys. A lot you can get but some you can't. If your data is encrypted at rest like all our systems. That encryption key lives with you. There's no system to login to, to get it. Save those somewhere safe. Keep multiple copies in safe places. Check the comments these screen shots get better...

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

  CI is the worst possible place to vibe-code. Copilot Autofix produced a plausible GitHub Actions patch that mishandled attacker-controlled input in a job holding Snowflake Jira credentials. The security fix became the attack path. AI-written patches need more review, not a hall pass because the bot labeled them fixes.

• 
  greedy capitalist🌐 🔰🏗️ (@Biggiethelad1) reported 40 minutes ago

  Also feels like the more common GitHub reliability issues have been to do w things like actions availability w seems somewhat separate to just hosting *** alone better

• 
  Paul (@paul_pbng) reported 44 minutes ago

  An AI hacked Snowflake via a GitHub issue title na. Wiz's Red Agent found the Actions bug and read internal Jira, 5 days after go-live. Everyone reads AI vs AI. Real thing: in-band signaling only. The title is data, the runner ran it as code. #AI #DistributedSystems

• 
  Lee Hayward (@vibedcoder) reported 47 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.

• 
  Alexander Cranga (@alexandercranga) reported 47 minutes ago

  GitHub had 70-100k requests per second on Copilot Token Service alone, insane! No matter what anyone says, immense respect to DevOps and everyone involved at GitHub for fixing scalability issues that no other company is having while the whole world is watching and judging

• 
  pulkit mittal (@pulkit_mittal_) reported 50 minutes ago

  When I interviewed at Microsoft last year, these system design concepts came up. Funny enough, GitHub’s recent outage is a real-world example of almost all of them: 1. Autoscaling: Scale capacity with demand automatically. GitHub’s autoscaling missed the Istio sidecar’s concurrency bottleneck. 2. Retry storms: Retries improve reliability until they amplify an outage. 3. Load balancing: Spread traffic across healthy capacity. HAProxy nodes hit their flow limits. 4. Failover: Move traffic away from unhealthy infrastructure. GitHub shifted traffic between regions, but the extra load created new problems. 5. Backpressure: Stop accepting work when the system is overloaded. Otherwise, the queue keeps growing. 6. Rate limiting: Protect a service from too much traffic. GitHub eventually blocked some Copilot token requests to reduce load. 7. Circuit breakers: Stop hammering a dependency that is already failing. 8. Cascading failures: One bottleneck -> more retries -> more traffic -> more failures. This is why system design isn’t just about the happy path. Check out my pinned post for resources to learn these concepts in depth.

• 
  alias (@loadingalias) reported 51 minutes ago

  @traits_reality Version control is, and must be, rooted in ***. There isn’t a meaningful competitor today. I mean, as a hardcore Rust engineer for almost 8 years… I still don’t using JJ. It’s not a meaningful enough move. I’ve explore all of them - literally, all of them. I have designed a few ideas myself. Right now, code is what’s widely versioned. Data, or assets, aren’t versioned uniformly. Think about game assets, datasets, etc. These all require a bespoke system. It breaks uniformity and pushes the same fragmentation/microservices we are all starting to loathe. So, I think any future GitHub needs the ability to be agnostic of the VCS. Entropy will catch up to *** - who knows when, though. Today, it’s the best available to all of us. Sorry, @Meta. GitHub itself is a piece of infrastructure - not just for us, but for the actual world of software. Even wrapping the UI/UX in a shiny new wrapper that’s a zero-to-one improvement over today’s GitHub doesn’t get us ****. It’s novel for a few months, at most. The issues are scale issues. The GitHub Actions pipe alone is a monstrous task to improve on. The registry, the social graph, the CICD pipes, the code hosting and versioning, the uptime of the entire stack… this doesn’t come in a few weeks or even months. There ARE pieces that can be incrementally improved on. GitHub can through compute/hardware to help improve scalability and uptime to balance the agentic coding load… but the real issues are so much deeper. I have spent nearly ten years thinking about this. I have spent two years coding what I think solves this at a fundamental level, but it’s the primitive… not the product that replaces GitHub. That’s over a year away - minimally… and I haven’t even gone public yet. Needless to say, I root for this to happen from any direction, but I have devoted so much time to this and understand it at such a fine grained level that I just don’t see it happening unless I start seeing papers on new data abstractions, storage engines, query engines, temporal unification, memory reclamation, and frankly… if it’s not written in Rust - it fails.

• 
  Mesh API (@meshapi_ai) reported 53 minutes ago

  Presented Mesh API at @github HQ in SF today. Thanks @Azure for hosting us. Talked about building immortal AI apps. The idea: whatever happens upstream, a provider going down, an account getting cut off, a model deprecating overnight, your users never see it. The request still completes. That's the whole job of a gateway. Failures are inevitable. Your customers seeing them isn't.

• 
  Kaan (@kaanyagci) reported 57 minutes ago

  Many people's reactions to the GitHub outage tell you a lot about why you shouldn't make your service free. Free customers are the most painful ones