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	2 days 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:

• 
  AI Reality No Slop (@airealitynoslop) reported 1 minute ago

  Cursor shipped Origin on Sunday and every headline called it a GitHub alternative. Their own changelog is more careful than that, and the difference matters. Origin does two things. You can create repos on it, which Cursor genuinely hosts. Or you can sync repos you already have on GitHub, and for those, in their words, pushes keep going to GitHub, which stays the source of truth for anything started there. So for code that already exists, Origin is a very good client sitting on top of GitHub rather than a replacement for it. PR comments sync both directions, which is the useful part and also the part that needs GitHub to be up. Which it wasn't. GitHub degraded the same day Origin rolled out, 14:34 to 20:40 UTC, and Cursor's own status page lists Origin among the affected services. Along with Automations, Cloud Agents, Review Agents and Codebase. None of this makes Origin bad. New repos hosted there are a real alternative, and meeting people where their code already lives is a sensible way to launch. It just means the thing being called a GitHub alternative had a six hour outage on launch day because GitHub had one.

• 
  Dr. Josh C. Simmons (@drjoshcsimmons) reported 5 minutes ago

  Microsoft is running the Xbox labor playbook on GitHub: lay off Americans, backfill with H-1Bs, then treat the visa count as a moderation problem. Asha Sharma ran that at Xbox. Satya is running it on the code host.

• 
  Anas (@Anas_founder) reported 6 minutes ago

  Founders, which login method do you actually prefer for your product? - Email + password - Google / Apple / GitHub - Magic link only

• 
  Kirill Goldin (@KirillGoldinBiz) reported 7 minutes ago

  @GergelyOrosz There is another concern even with traditional code repositories like GitHub - AI generates billions of lines of code now which almost inevitably have security issues which can be potentially exposed. Because of this very reason most companies still store the code internally.

• 
  Arizoft Games (@arizoftgames) reported 8 minutes ago

  @johncodes Hopefully, options like Origin will take up some of the overflow. But they need to understand that hosting open source is part of the noblesse oblige, part of the overhead, that goes with being a Github competitor. Or the whole ecosystem goes down the drain it's circling as we speak. Because I promise you, if everyone had to sub for every single function they use, there would be four megacorps running tech and they'd all be doing everything in house...and advancing at a snail's pace if at all, as the accountants asking "should we do this" drown out the engineers saying "we can do this."

• 
  zach bai (@zach_bai) reported 9 minutes ago

  @colemurray @zachlloydtweets because github was down and resolving conflicts from a clogged merge queue has become a literal bottleneck

• 
  jtavares (@jnstav) reported 10 minutes ago

  The first product able to merge chat + issue tracking + *** + ai agents will get all our money in subscriptions. Can't wait to ditch the slack/linear/gitHub stack in favour of an all in one workspace. That's why everyone is building the same thing now

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

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

• 
  fforres (@fforres) reported 18 minutes ago

  @ericclemmons Agreed: Authentication, repos, pull request (This is the chunky section: comments/approvals/checks) and merge gating. "Checks" being the main issue with all github alternatives. How to run a bunch of CI flows, tell commit XYZ of the results, and access (visualize?) that.

• 
  Mark Huliganga (@kenjihmark) reported 21 minutes ago

  Spent a whole day hunting a GitHub App integration bug that Shinka found. Took six separate root causes before it actually worked. Sharing the breakdown in case it saves someone else a night of confusion these were all silent failures, no error thrown, just nothing happening: 1. JWT gate verification logic assumed a request format GitHub doesn't actually guarantee. Read the platform's real auth flow line by line, not what you assume it does. 2. Missing secret existed in one environment, not the one actually serving traffic. "Works locally" means nothing if deployed secrets don't match. 3. Wrong event subscription the app wasn't subscribed to the specific event type needed. No error. Just silence requests never arrived at all. 4. Token exchange worked fine on the happy path, broke under retries. Race conditions love to hide behind a test that only runs once. 5. Internal auth path a code path meant to bypass checks for trusted internal calls wasn't actually wired up. Legit requests got treated like external ones. 6. PEM key subtly malformed. Passed basic validation. Failed real signing. This one took the longest to find because everything looked correct. The pattern across all six? nothing crashed. Nothing logged an error. It just didn't work, and the reason was different every time. That's the hardest kind of bug to hunt and honestly the most satisfying kind to finally nail. But finally, the bot now runs a full analysis on a PR. A lot more to test, but so very close!

• 
  sanixdk (@sanixdarker) reported 23 minutes ago

  man... github is slow, wtf ?

• 
  Andrew Hoyer (@andrewhoyer) reported 23 minutes ago

  If your site runs WP Rocket, don't upgrade to WordPress 7.1 until it gets an update to v3.23.2.1. Or if your site is down, fix it by one or both of these steps: 1. Disable the plugin by renaming its folder. 2. Click through to above thread, find the GitHub issue, and make the code change manually.

• 
  Nicolai Schmid ✌️♥️ (@NicolaiSchmid) reported 26 minutes ago

  @kirtandopamine two days ago, during the last outage, cursor decided to vibecode a github alternative and it's already live, it's called origin!

• 
  Julia Turc (@juliarturc) reported 28 minutes ago

  @ThePrimeagen stop bringing github down pls

• 
  Aurora Martel (@AuroraMar1eL) reported 29 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

• 
  Joshua K (@JoshuaK74492) reported 33 minutes ago

  @jeffseibert It’s very cool it’s a shame their platform is going to get overrun by AI slop in the future. Origin - Too much slop Codeberg - Not enough slop GitHub - Your slop is down Gitlab - Corporate slop

• 
  Kyle Strouse (@MrKyleStrouse) reported 35 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 ****?

• 
  DuckDegen is for hire (@DuckDegen) reported 37 minutes ago

  @ksaitor @cursor_ai @github Skill issue, my ingestion pipeline is online and working, pulling millions of commits daily <3

• 
  edos (@DOSHostNet) reported 40 minutes ago

  Great response! First 100 get free plus for a year 🪎. I update users a few times a day. Log back in to check. We will never Contact you outside the website. No Emails, No text, No GitHub BOT on the server. Don’t fall for internet scams!

• 
  Dr. Josh C. Simmons (@drjoshcsimmons) reported 41 minutes ago

  Microsoft owns the deploy path for software sitting in cameras, cars, and pacemakers. GitHub going dark for 7 hours and 47 minutes is not a website outage. A landlord just turned off the lights.

• 
  Mike Meredith 🇪🇺🏴 (@hmv666) reported 42 minutes ago

  @DataJuggler007 @the_codewala SQL server; also known as Sybase. Github existed before Microsoft took it over.

• 
  Lazarz (@Laz4rz) reported 43 minutes ago

  Codex has this peculiar recurring issue with my Github CLI credentials. It thinks they're expired, stops the goal and alerts me. I then copy-paste the log that they're in fact not expired, and it just continues and everything works?

• 
  Alessio Persico (@alepbuilds) reported 43 minutes ago

  @wickedguro the complaint data agrees: github api/downtime complaints went 0 → 5 mentions this week in our corpus. any platform dependency means their outage is your churn. at least github breaks in public

• 
  Hotragn Pettugani (@hotragn) reported 45 minutes ago

  @cursor_ai shipped a @github competitor. GitHub went down for 6 hours 42 minutes the same day. Cursor's Matt Palmer: "We were going to ship this earlier, but GitHub was down." They insist the timing wasn't planned.

• 
  Ryan Zander (@ywzander) reported 46 minutes ago

  Instila launches August 24. Most founders don’t have an information problem. They have a “something important got buried in Slack, GitHub, Linear, or Jira” problem. Instila is an AI COO that watches the company context, catches what gets missed, and tells you what actually needs attention. We’re opening it up in 5 days. If you run a software company and want early access, reply “instila” or DM me.

• 
  Shagrath (@shagrath49) reported 51 minutes ago

  @thdxr I push one of the two...hoping it's connected to a GitHub CI/CD of some kind and pray GH is down again.

• 
  Abraham Alba (@AbrahamAlba10) reported 52 minutes ago

  Developer: “This should be a quick fix.” Three hours later: Google open. GitHub open. Claude open. ChatGPT open. Stack Overflow open. And the original bug? Still there. 😭💀

• 
  Kaushik (@TheQriousCase) reported 54 minutes ago

  Launched a side project here three days ago. The launch post got 4 views. A reply I left in someone else's thread during the GitHub outage got 1,398, and sent 17 people to the site. Turns out nobody cares what you launched. They care whether you're useful in a conversation they're already having.

• 
  QuanChain (@Quan_Chain) reported 58 minutes ago

  An Agent Found The Exploit Path Nobody Wrote Wiz's own AI red-teaming agent independently discovered & chained a script injection exploit across GitHub Actions & into Snowflake's internal Jira environment. No human hand-authored the attack path. It was authorized research, responsibly disclosed, already patched. But the autonomy was entirely real: a broad objective, and the agent filled in every step itself. Nobody issued a command. The agent just found a door & opened it. The danger here isn't malice but the gap between "I authorized this session" and "it took this specific action." Wiz authorized a research objective. Nobody authorized that exact exploit chain. That gap between session-level permission & execution-level action is exactly where enforcement is missing in most stacks. Authorization at the front door doesn't cover everything that happens inside the house. QuanChain requires a valid, authorized signature at the point of execution for any on-chain action - an unsigned or improperly-scoped execution event simply does not propagate to the network. This isn't a login check. It's an execution-layer attestation, built on TADEQS adaptive security levels and never-on-chain public keys, that any agentic system on QuanChain inherits by default. The chain itself enforces scope every single time, at the moment it matters.

• 
  Lone_billo :) (@HazariSoumyadip) reported 60 minutes ago

  I am switching to codeberg not because I don't like github but the **** is happening there :) also I liked their anti ai policy so will be pushing all major projects in codeberg Later will make my own *** server for sure 🙃