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:

• 
  FHILY👑 (@Oluwaphilemon1) reported 7 minutes ago

  Cursor is coming for GitHub. The company just launched Origin, a ***-compatible code hosting platform built directly into Cursor. It includes: → Repository hosting → Pull requests → Code search and browsing → Two-way GitHub sync → Vercel, Depot, and Buildkite integrations The timing is interesting. Origin launched alongside a major GitHub outage that lasted 6 hours and 42 minutes, with failures across pull requests, issues, API access, Copilot, and Actions. Cursor’s argument is that AI coding agents are creating a completely different workload. They reportedly demonstrated 22.6 commits per second and 295,000 clones per hour at their developer conference. But there’s one big question: What happens to your code once it lives on Origin? Cursor had not published clear data-retention, subprocessor, or model-training policies for natively hosted code at launch. For teams, keeping GitHub as the source of truth and using Origin as a mirror may be the safer approach for now. The AI coding era may need a new kind of code forge.

• 
  Andrei Sfat 🔑 (@sfat__) reported 9 minutes ago

  @elijahmuraoka_ @github definitely should have been 10x better to have the code on a FTP server. obvious chad move

• 
  Vasilis Koukoutis (@VKoukoutis) reported 13 minutes ago

  The interesting part isn’t that GitHub went down. Every distributed system eventually does. It’s how many companies discover during an outage that GitHub is also part of their deployment control plane. Source hosting being unavailable is inconvenient. Production delivery being coupled to it is an architecture decision.

• 
  Mike Kamo (@mikekamo) reported 15 minutes ago

  Cursor launched its own GitHub competitor this week. The part everyone's talking about is the timing. It went live the same morning GitHub was down with error rates near 20 percent. TechCrunch called it capitalizing on the frustration. Whether they planned it that way or got lucky, the lesson is the same. The best growth moment your company will get isn't a campaign you scheduled. It's the hour a competitor stumbles. Their outage, their price hike, their bad launch, the thing that makes their customers suddenly open to a switch. Almost nobody is ready to move when that window opens. I've watched this play out at NP Digital more times than I can count. A competitor drops the ball on a client, and the agencies that win the account aren't the best ones. They're the ones who called that same day. Most were still putting together a proposal a week later, after the window had already closed. The teams that catch these moments aren't faster thinkers. They just decided ahead of time that shipping at 80 percent beats being ready at 100 percent next month. You can't schedule your competitor's worst day. You can be the one thing that's ready when it comes.

• 
  Aurora Martel (@AuroraMar1eL) reported 15 minutes ago

  If you want to start a startup: Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) ProductBridge = feedback (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20

• 
  Sam Cladson (@SamCladson) reported 15 minutes ago

  @JeevanMahesha @NPCI_BHIM Might be the side effects of the GitHub outage happened recently

• 
  davidsong (@bitplane) reported 15 minutes ago

  Ubuntu runners on GitHub have been broken for 8 hours now but their service status is green. Nice work on the pink unicorn, diversity hires and renaming master to main @github, now get some ******* work done.

• 
  ｖｅｇａ (@vega_holdings) reported 19 minutes ago

  @elvissun @vercel had this issue with ci in github and said **** it i have compute local out the ***

• 
  Taylor Page (@TRPage_dev) reported 22 minutes ago

  @benjaminsehl More context - another dev said they have been having issues with this this week. Assumed initially it was all the GitHub outage stuff, but even after still persisted. Reached out to support and support pointed this out in docs - which if this is an update it’s brand new. I did this with collab access maybe 2 weeks ago for a merchant we onboarded.

• 
  Vasilis Koukoutis (@VKoukoutis) reported 24 minutes ago

  @Anthony_K81 I’d accept some coupling, but I’d want an emergency path that doesn’t depend on the same control plane. Not a full parallel CI/CD stack — that’s probably overkill for most teams. Just enough to ship or roll back a critical production fix when GitHub isn’t available. Curious what fallback you’ve seen work well in practice.

• 
  KYD (@K_Y_D_A_A_L) reported 30 minutes ago

  @VadimStrizheus Just searched this turns out it's a known issue in some cases: QR scan opens a fresh chat instead of connecting to the remote session, filed on GitHub. Also fwiw you can skip typing /remote-control manually /config lets you turn on auto-connect for every session.

• 
  asd (@0xANDREAS) reported 33 minutes ago

  how will github actually address long-standing reliability issues though?

• 
  Dom England (@domengland) reported 35 minutes ago

  @behrendtio @cloneisjun The big one is the in ability to work with GitHub issues and something akin to routines. The usecase is now around having an orchestrator agent somewhere which triggers agents to work with issues/tickets. Doing anything like that with any other tools?

• 
  Ajay Yadav (@ATechAjay) reported 37 minutes ago

  Most release notes answer one question: What changed? But before a meaningful release, the team needs answers to a much more important question: Why do we believe this is safe to ship? A strong release note should capture the evidence behind that decision: → What changed? → Which critical user journeys were verified? → What’s covered by automated E2E checks? → Is the release behind a feature flag or staged rollout? → Which production signals should we watch? → What’s the rollback plan? → What’s deliberately not covered yet? This matters because a release doesn’t fail only because the code is wrong. It can fail because: - a critical journey wasn’t tested - a feature was exposed too quickly - an error rate quietly increased - a dependency behaved differently in production - nobody knew what to monitor - the team had no clear rollback path Your existing tools already capture parts of this evidence: - Linear/Jira → scope & ownership - GitHub → code & change history - LaunchDarkly → exposure & rollout - Sentry/Datadog/Grafana → production health - Bug0 → QA & defect signals But there’s one more piece that matters: Journey confidence. Did the workflows that matter to users actually work? That’s where web E2E verification becomes valuable. The goal isn’t to create more paperwork. It’s to make the release understandable before something goes wrong. Because when production breaks, nobody wants to ask: Did we test this? They want to know: What did we verify, what are we watching, and how do we recover? That’s the difference between shipping code and shipping with confidence.

• 
  Tichaona Chitsinde (@TiChitsinde) reported 38 minutes ago

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

• 
  Nakul (@nakul_011) reported 42 minutes ago

  Hey @neetcode1 , could you please add/keep traditional Email & Password login on the platform? Many of us use corporate laptops/networks where Google and GitHub OAuth are strictly blocked by IT policies, making it impossible to log in during breaks or prep sessions. 🙏

• 
  RaoulDuke (@RaoulDukeDegen) reported 42 minutes ago

  @AINativeF wild how origin launched the same day github had that big outage

• 
  Yash Agrawal (@Yash__Sensei) reported 44 minutes ago

  Pov a day at a 14-X-follower open-source startup: > checking github stars again and again > @imheadrick and i spend 3 hours arguing about what to call the category we're building. > i open GITHUB to do GROWTH . somehow i'm debugging a windows issue. > someone with 200k followers likes our post. screenshot immediately sent to the group. github stars still same count. @dshekhar17 tagging you too, so you dont feel left out.

• 
  Jeevan 🅰️ (@JeevanMahesha) reported 44 minutes ago

  @SamCladson @NPCI_BHIM Nah, GitHub wouldn't cause the app to crash or stop loading. Even if GitHub has an issue, it doesn't run the live payment network. This is definitely a backend server outage with the BHIM/NPCI payment gateways. Better to just wait for them to fix their servers.

• 
  Mesh API (@meshapi_ai) reported 45 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.

• 
  Kyle Strouse (@MrKyleStrouse) reported 46 minutes ago

  The "5 nines" is 99.999% system uptime, meaning .001% of the time the system is "down" for whatever reason. Over the course of a year that equates to ~5 minutes. GitHub has had 93% uptime over the past 90 days. Extrapolated over a year that is ~25 days of downtime. Why does everything Microsoft touch seem to go to ****?

• 
  Juan Carlos Perdomo (@Jcperdomoybarra) reported 47 minutes ago

  @dhh I think I found something small but useful for others (fixing a thinkpad fingerprint sensor bug), what would be the best way to push it to the team? I opened an issue in github (#7483). If there's a better way to do it, let me know.

• 
  Tyrone Robb (@ty_auldric) reported 47 minutes ago

  I’ve used @t3dotcodes on 111 of 123 days, across Intel Mac and Windows. Few issues. I forked it and made improvements, but it moves so fast that nightly makes sense till it's more stable. Rough edges: GitHub projects, Preview getting stuck and mobile sync docs. Subscribed to @theo as thanks.

• 
  Mohit Bhandari (@MohitDev45) reported 48 minutes ago

  Why github is slow.......

• 
  Alex (@nuit_dhiver) reported 48 minutes ago

  @NickADobos But doesn’t matter because GitHub is going down in few weeks again, probably.

• 
  Patrick Gallagher (@gridpane) reported 48 minutes ago

  @SethRubenstein There is no excuse but the thing is: they've been absolutely **** for really long time. We had to build redundancies for them like six years ago because new servers would fail to build because the literal core PHP libraries couldn't be pulled. The Internet could not be built because Github was down. Makes me throw up in my mouth just thinking about it.

• 
  200 people murdered in Benue, 50 killed in Plateau (@AScully789) reported 54 minutes ago

  Github had to wait till they trended and everyone all over the world was insulting them, that they finally publicly acknowledged and responded to issues people have been complaining about since last year

• 
  Daniel Craft (@danielcraft) reported 58 minutes ago

  @doodlestein No wonder GitHub keeps going down

• 
  Anthony K (@Anthony_K81) reported 1 hour ago

  @VKoukoutis The real smell is using a third-party SaaS as the control plane for ****. Seen too many teams where a GitHub issue becomes a deploy blocker. Do you keep an offline fallback or just accept the coupling?

• 
  blvnk (@adore_blvnk) reported 1 hour ago

  @GergelyOrosz enterprises are using enterprise GitHub, self-hosted (or GitLab). at least based on where I've worked. this issue is trivial...