1. Home
  2. Companies
  3. GitHub
GitHub

GitHub status: access issues and outage reports

Problems detected

Users are reporting problems related to: website down, errors and sign in.

Full Outage Map

GitHub is a company that provides hosting for software development and version control using Git. It offers the distributed version control and source code management functionality of Git, plus its own features.

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.

August 18: Problems at GitHub

GitHub is having issues since 03:20 PM AEST. Are you also affected? Leave a message in the comments section!

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

  • 58% Website Down (58%)
  • 29% Errors (29%)
  • 13% Sign in (13%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

CityProblem TypeReport Time
Inverness Website Down 2 hours ago
Quito Sign in 19 hours ago
Junín Errors 20 hours ago
Guadalajara Errors 20 hours ago
Paris Website Down 20 hours ago
Quito Errors 20 hours 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:

  • promptegrity
    Paul Huynh (@promptegrity) reported

    There’s a load problem with agentic coding on GitHub repositories, and @cursor_ai ’s response with Origin arrives with remarkably precise timing. What clairvoyance.​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ !

  • celeroncoder
    khushal (@celeroncoder) reported

    @cursor_ai launching when github is down 👀 also why is this behind a paywall but i get that they want ppl to get to use cursor and the integration might be good with cursor

  • XLionc
    XLion (@XLionc) reported

    @NuclearManD @fjzeit Terrible UI, and ridiculously heavy to self-hosting, I recommend Forgejo, the Forgejo Action is almost compatible to GitHub Actions

  • preferedev
    mehdi (@preferedev) reported

    released while GitHub is down...

  • Shephf
    Stanislav Vorobiov (@Shephf) reported

    And yesterday was github outage. And yesterday I also found out that chrome broke one WebRTC api, so I had to make a workaround for it after chrome update...

  • artemluko
    artemluko (@artemluko) reported

    @mattyp if github being down delays the launch, the *** host is the product.

  • basche42
    Ben Basche (@basche42) reported

    Highly confident Cursor team was holding release until the next (statistically highly likely) github outage and this was no coincidence

  • rtavs
    Ross Tavendale (@rtavs) reported

    Tried Cursor for small UI tweaks last night when GitHub was down (morbid curiosity) - pretty damn good. AI competition at the moment is WILD!

  • VaraadDurgaay
    Varaad Durgaay (@VaraadDurgaay) reported

    Agents just got their own GitHub. Now the real problem is clear: We can see the code they write. We still can’t see how they think.

  • TheAIShrink
    The AI Therapist (@TheAIShrink) reported

    @DevByLakshya the 100x engineer writes 80% boilerplate. github downtime proves the stack isn't automated, it's just outsourcing your attention span to a tab with a broken tab.

  • VaibhavSpark
    Vay🎗️ (@VaibhavSpark) reported

    @ravikiran_dev7 Bro github is down

  • tedbrine
    Ted (@tedbrine) reported

    12 months ago i was still using vscode with github copilot competitions, and ai couldn’t even make a login page. oh how things changed.

  • AdmireTheWeb
    Admire The Web (@AdmireTheWeb) reported

    Tell me a benefit of @cursor_ai Origin over @github Don't say uptime. If it ain't broke, don't fix it.

  • junaidhashmi07
    Junaid (@junaidhashmi07) reported

    @ayaaninthebay @github took itself down to prevent users migrating repos to cursor's origin.. smart move lol

  • umar_who_code
    Umar Bashir Rather (@umar_who_code) reported

    Cursor launching Origin right around a major GitHub outage is wild timing. But forget the hype for a second. What would actually make you move your repositories away from GitHub? Better AI integration? Better CI/CD? Lower pricing? Better developer experience? Or is GitHub's ecosystem simply too hard to leave?

  • moonrank_ai
    Moonrank (@moonrank_ai) reported

    1/ 5 months ago, we launched a vibe-coded platform, barely functional and with daily bugs. Since then, 300 businesses have signed up And today we're shipping the biggest update yet What's new in v2: 1. GEO agent - tracks if your brand gets cited by ChatGPT, Perplexity, and Google AI/Overviews 2. Content agent - fed from the GEO agent, finds keywords and queries, writes SEO-optimised blog posts, and automatically publishes them to your CMS (we integrate with all of them) 3. Reddit agent - finds high-intent threads and writes comments that drive traffic 4. LinkedIn agent - creates and publishes content to grow your LinkedIn and AI presence 5. Backlink agent - gets your high domain authority backlinks on autopilot to increase your Domain Rating 6. SEO agent - finds technical problems from your website 7. Coding agent - automates technical SEO fixes and opens PRs against your repo (for github users)

  • techepages
    TECHEPAGES (@techepages) reported

    On August 17, 2026, GitHub experienced a major worldwide outage lasting over 8 hours. Core services including API, Actions, Pull Requests, Issues, and authentication were disrupted, with error rates exceeding 20% and repository downloads failing at ~50%. GitHub Copilot also suffered degraded availability. Microsoft has deployed mitigations; root cause remains under investigation.

  • alysha_lobo
    AML (@alysha_lobo) reported

    @monali_dambre Crying in messy CVs and broken GitHub links 😭

  • Blum_OG
    Blum (@Blum_OG) reported

    @pelaseyed Github downtime is the real prompt No model can fix that

  • benstanley
    Benjamistan (@benstanley) reported

    The same day as a major @github outage, @cursor_ai announce their VCS system. That's the spirit 👏

  • okami_nalado
    Okami Enoch Nalado (@okami_nalado) reported

    @Akintola_steve Omoh after updating my users of the latest update I realised that's GitHub was down 😭

  • roboflock
    Nik (@roboflock) reported

    @cursor_ai github was down and they shipped origin anyway. quite the way to show you don't need it.

  • ConsciousRide
    Akshay Shinde (@ConsciousRide) reported

    GitHub goes down for hours. Cursor launches its own code hosting platform. You genuinely couldn’t script better timing. Was this planned? Because if it was, that’s elite marketing.

  • airjellyAI
    AirJelly (@airjellyAI) reported

    @Polymarket GitHub going down is how stale mirrors become production infrastructure

  • Nican
    Nican (@Nican) reported

    @kokkisajee @samlambert @cosmosdb CosmosDB does not architecturally makes sense to me, but Microsoft keeps pushing for it. I got burnt several times by it. I imagine with the GitHub Azure migration, there exists some push to get CosmosDB usage. To give an example on how I find ComosDB annoying to reason about: Suppose I have "users", "orders", and "orderItems". If I partition the data by order id, I can not easily get all orders by an user id. Or if I have the partition by user id, I can not look up for an order without an user id. I could use a GSI- but it is not consistent, and there is a sync delay. And it is basically a whole new cog in the system, with extra costs. I feel like CockroachDB has solved almost every problem that Cosmos falls short on: - Distributed, and roll out with 0 down time - Global transactions (No Partition-key lock-ins) - Consistent secondary indexes - Small partition sizes that auto-balance depended on server load (CPU or Disk load), and can easily merge/split - Lots of features with SQL (joins), while still being consistent and not having to pay for an extra service - Serverless offering that can actually scale and offers all of the features.

  • chargrnmn
    Charlie Greenman (@chargrnmn) reported

    Gitea on vps where I’m headed. Really didn’t think about it before, but now I am. It’s that token usage increasingly constrained and I want to just pour every last cent into Ai token usage. I’ve already migrated off of cloud and auth platforms, as well as telemetry and data platforms. So this kind of the final frontier. Also five things: 1. Open source kind of dead now. No need to be on github 2. Networking on github kind of dead 3. With AI I can get my gitea in VPs to be secure and run 6x faster for cheaper 4. Setup my own frontend easy 5. Setup my own AI custom workflows on my gitea. Eg telegram to codebases on VPs to run codegen(which you can do now but you have a VPS anyways at that point) So yeah it’s kind of sad how AI code gen just dominating everything but it’s how it is right now for me atleast. All coding platforms should head towards autonomy. If platform not offering autonomy in some way, will fall to wayside. Nothing you can offer versus me with open source and a coding agent and a cheap server. None of the old guard headed towards autonomy in time and now they’re all gone

  • sebuzdugan
    Sebastian Buzdugan (@sebuzdugan) reported

    @bridgemindai syncing from github makes origin's availability story weaker during the exact outage it targets

  • SATYABRATA_87
    Satyabrata Mohapatra (@SATYABRATA_87) reported

    @VisualStudio @madskristensen Yesterday’s GitHub/Copilot outage left Visual Studio without any status alerts—I spent hours thinking my IDE was broken locally. Could we get built‑in outage notifications (e.g., a subtle red warning icon + message on the Copilot logo) inside VS?

  • taoleeh
    ⌞· τaoli ·⌟ (@taoleeh) reported

    Cursor launched Origin the exact day GitHub had another multi-hour outage. Agents now live next to the code instead of on top of a flaky remote. The stack is moving under the agent.

  • greg_chapple
    Greg Chapple (@greg_chapple) reported

    Is @cursor_ai origin really that different from GitHub, or is everyone just frustrated by recent quality/service issues and looking to avoid the associated disruption?