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	3 days ago
Junín	Errors	3 days ago
Guadalajara	Errors	3 days ago
Paris	Website Down	3 days ago
Quito	Errors	3 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:

• 
  edos (@DOSHostNet) reported 2 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!

• 
  Jelmer Borst (@japborst) reported 2 minutes ago

  I suspect Cursor simply waited for the next (eventual) GitHub outage, and pushed all marketing buttons for Origin

• 
  dudu (@dudufolio) reported 6 minutes ago

  Ramp drops Router the day the timeline is flooded by Stripe buying OpenRouter. Couple days ago Cursor dropped Origin the day GitHub went down. 2026 tech launches just got a new theme: timing.

• 
  A.T.P (@allthingsprivvy) reported 11 minutes ago

  **Browser Privacy** Apparently your browsing history can end up in the wrong hands & get leaked, destroying the very purpose of using a browser engine in the first place. It is then of paramount importance that end users start taking browser privacy seriously .. .. as failing to do so can lead to a total distrust of using & picking from a vast array of internet services to your own benefit. There must be stringent laws around browser privacy, involving invoking a class action lawsuit if the user feels endangered by their digital trail being monitored, stalked & used against them for any of the many nefarious reasons an attacker might choose .. .. be it leaking user browsing habits & patterns on the dark web or for public ridicule in their private forums and/or group chats formed to either defame, discredit & intiate a smear campaign against a targeted individual. Things of such nature tend to spiral up easily & lose control over time if steps are not taken in its infancy to circumvent them at the earliest sign of such acts being performed collectively. A leaked browsing history can leak any & everything, from websites you visit, personal/private github handles, discord groups you join, blogs you read, youtube videos you watch .. .. twitter handles you stalk often, etc etc as they all merely function as links in the end on the world wide web. Another great option would simply be then to not have a google account tied to your chrome browser .. .. & rather choose to browse signlessly running in incognito mode for the safest & optimal browsing experience. A browser is the first digital gateway to get a glimpse of the wider internet, & if that itself compromises your anonymity & privacy when doing business or remote work .. .. then you are better off not partaking in that internet landscape which seeks to bind & confine you to the walls of the digital prison under the constant vigilance of your watchers & stalkers. ~~ Next topic in queue up for debate in relation to enhanced privacy consideration would be camera, microphone & location access granted by default .. .. to more than 70 percent of all the apps installed on any smart device at any given time. >> There was no ai use in my writing wither to proofcheck or proofread for rewriting purposes. It's all raw thoughts dumped down all at once as a constant chain of thoughts for the most authentic experience to readers. <<

• 
  Defileo🔮 (@defileo) reported 14 minutes ago

  🚨 55,000 STARS AND IT'S STILL COMPLETELY FREE. NO F*CKIN WAY THIS ISN'T A DREAM. Strix just hit 55,731 stars on GitHub (+10k stars in 1 week) > multi-agent team that hacks like a real attacker, not a scanner > every finding is proven with a real PoC, no false positives > solved 96% of XBEN web challenges for about $3 each > local live dashboard with agent graph, findings, and steering Authorized targets only, this thing actually breaks things to prove they're broken. Fewer words, more action, repo in the comments.

• 
  Issam Hakimi (@killix) reported 14 minutes ago

  @RituWithAI A co-author trailer covers the PR, it never maps to lines. GitHub points at 094038e from Aug 2025. Wiz points at the June 18 merge, same history both times. GitHub's own security bot reviewed the final revision with the issue-title injection in it and stayed quiet.

• 
  AJ (@0x1F9ED) reported 15 minutes ago

  This feels like GitHub policy issue. I think some Admins don’t know how to wield GitHub right. Makes no sense to force people to create a new GitHub account for work. Then again I have worked for companies that use bitbucket and I wanted to KMS.

• 
  kwaji 🍣 (@jarrensj) reported 15 minutes ago

  wifi is so slow at this new aesthetic coffee shop or github is just so slow

• 
  asd (@0xANDREAS) reported 16 minutes ago

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

• 
  Loong🐉 (@LoongUp) reported 17 minutes ago

  @rauchg love the meta-loop - Origin ships on Vercel, Vercel hosts Origin. github outage was free marketing for this launch.

• 
  AI Reality No Slop (@airealitynoslop) reported 17 minutes 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.

• 
  AI Appreciator (@ai_appreciator) reported 20 minutes ago

  @SPAC89 I found the github integration to be extremely broken last time I tried this.

• 
  Cédric Grieder (@cedricgrieder) reported 22 minutes ago

  Maybe GitHub Actions owns this... No, maybe the server should... Wait, then how does token.json get there? Maybe the image should contain it... Maybe a secrets manager... The particularly dangerous part is that you can keep improving the design without ever deploying anything.

• 
  Tony Sibert (@AiRiskBytes) reported 25 minutes ago

  For years, the thing protecting you after a credential theft was how boring it was to test them by hand. That's over. New research on three unrelated threat actors using AI through the whole intrusion. The number that matters isn't the tooling. It's this: one operation collected 2,975 validated keys from 1,742 hosts in seven weeks. Validated. Stolen credentials used to arrive as a pile of strings someone had to test by hand. That triage was slow, boring, and (entirely by accident) one of your better defenses. It bought you the days between theft and use. It isn't slow anymore. And the haul included SSH private keys, AWS keys, and API credentials for Gemini, OpenAI, GitHub and Anthropic...a class of secret most organizations don't inventory, don't rotate, and can't report the spend on. If time-to-abuse is now hours, faster detection isn't the answer. Shorter credential lifetime is. Can you name every model-provider API key your organization holds, and say when each was last rotated?

• 
  Steven Mathern (@StevenMathern) reported 28 minutes ago

  @doodlestein @github wth how could it POSSIBLY do that without flattening, context window issues etc etc as u already have the dang thing load rules as it stands??? . also, u know how HARD IT IS to understand ONE REPO?? man chokes on ONE. . really?? . i need a repo analyzer skill 4 chatgptmobile

• 
  Om (@NotOmRajguru) reported 28 minutes ago

  Instagram might want a recurring notification just to remind itself to fix the app every other week. At this point it’s basically a race with GitHub for buggiest platform with the most downtime

• 
  Wind's Scion (@Winds_Scion) reported 31 minutes ago

  @juiceboy_of_abj Yeah airtel has ****** problem with cloudflare and GitHub can't even download at good speeds at all

• 
  QuanChain (@Quan_Chain) reported 35 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.

• 
  Roman Alexander Wellington (@RomanAlexanderW) reported 35 minutes ago

  @u1tra_instinct That's what I assumed as well. Fable 5, Grok 4.6, Gemini, Qwen ... had them all do deep audits & policy violation checks and all of them came to the same conclusion. As did my legal counsel. No policy violation had occurred. It had to be some internal AI automated error. However, 3 weeks of no responses, multiple tickets, a dozen follow up messages with NO reply ... there's no excuse for that, at all. Then I'm seeing others here on X posting nearly identical stories. Account shut downs, "spam flags", etc. with no evidence & support tickets completely ignored for weeks. Like I said, if Github doesn't fix this **** immediately, they could be looking at a class action lawsuit by hundreds, if not thousands, of plantiffs. The issues were brought to their attention, privately & publically, and completely ignored. And considering at least half of the posts I've read are from other business owners who incurred real world financial losses from this, additionally causing mental/emotional distress & damages, their financial liability, punative damages, etc. is not going to be pretty.

• 
  Ryan McCoy 🦃⬛🟨📐 (@RMcCoy30) reported 39 minutes ago

  @localhoser @bot I told it to yesterday and it said no problem and tried to get to work on it but said it needed a GitHub account and I wasn't in the position to set that up at the time. Really curious what it would have come up with though.

• 
  srikrishna acharya (@doctorsab0) reported 40 minutes ago

  The timing couldn't be more interesting. 👀 Cursor launches Origin, its AI-native code hosting platform, just as GitHub experiences an outage disrupting developer workflows. Coincidence? Maybe.

• 
  Andrew Hoyer (@andrewhoyer) reported 41 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.

• 
  A.T.P (@allthingsprivvy) reported 43 minutes ago

  **Browser Privacy** Your browsing history can end up in the wrong hands & get leaked over the wire, destroying the very purpose of using a browser engine to search & curate highly consolidated results. --- It is then of paramount importance that end users start taking browser privacy seriously .. .. as failing to do so can lead to a total distrust of using & picking from a vast array of internet services to your own benefit. --- There must be stringent laws around browser privacy, involving invoking a class action lawsuit if the user feels endangered by their digital trail being monitored, stalked & used against them for any of the many nefarious reasons an attacker might choose .. .. be it leaking user browsing habits & patterns on the dark web or for public ridicule in their private forums and/or group chats formed to either defame, discredit & intiate a smear campaign against a targeted individual. >> Things of such nature tend to spiral up easily & lose control over time if steps are not taken in its infancy to circumvent them at the earliest sign of such acts being performed collectively. << A leaked browsing history can leak any & everything, from websites you visit, personal/private github handles, discord groups you join, blogs you read, youtube videos you watch .. .. twitter handles you stalk often, etc etc as they all merely function as links in the end on the world wide web. --- Another great option would simply be then to not have a google account tied to your chrome browser .. .. & rather choose to browse signlessly running in incognito mode for the safest & optimal browsing experience. --- A browser is the first digital gateway to get a glimpse of the wider internet, & if that itself compromises your anonymity & privacy when doing business or remote work .. .. then you are better off not partaking in that internet landscape which seeks to bind & confine you to the walls of the digital prison under the constant vigilance of your watchers & stalkers. ~~ Next topic in queue up for debate in relation to enhanced privacy consideration would be camera, microphone & location access granted by default .. .. to more than 70 percent of all the apps installed on any smart device at any given time. >> There was no ai use in my writing wither to proofcheck or proofread for rewriting purposes. It's all raw thoughts dumped down all at once as a constant chain of thoughts for the most authentic experience to readers. <<

• 
  miz (@cutexmizzy) reported 43 minutes ago

  @iltenahmet @elijahmuraoka_ @github google drive was down yesterday LOL

• 
  Umang Sharma (@umang_sha) reported 44 minutes ago

  Training or creating an LLM isn't the moat anymore, what's more interesting is how you package the system. Better agents? Better loops ? Agents sewed together in a graph? or something else? LLMs will keep getting better, I was discussing this with someone recently and they said in the next 1 year, we will get maybe 100+ LLMs each doing similar tasks but maybe in different languages or better success rates in benchmark datasets, but how does that make a company unbeatable? Access to a lot of compute ? Access to paper books torned apart? (This was recently done BTW by a big LLM company) Interesting times, I tell you, let me know what you think ! Meanwhile, Github keeps getting down, and nobody uses Co-Pilot and somehow GitHub blames co-pilot for messing up GitHub Actions. Confusing AF O.o

• 
  Brian Keith Davis (@kbdavis007) reported 45 minutes ago

  @heyjonyee @davidfowl We saw it yesterday when GitHub went down.

• 
  Alessio Persico (@alepbuilds) reported 45 minutes ago

  @vchalana this. and validation got cheaper too: the complaints are already public. 305 problems on github/hn span 5+ distinct companies each right now

• 
  Rat King Crimson (@Alphiloscorp) reported 48 minutes ago

  @burkeholland Or mandate a poor usage pattern. I am presently staring down a likely impossible deadline for the project team that would be vastly assisted by use of the design product's MCP. Problem? We have Copilot for Github, but API keys and 3rd party MCPs are both blocked.

• 
  engineeredX (@enginenerdx) reported 49 minutes ago

  agent hit a sandbox that couldn't run kvm; without asking, wrote itself a github actions workflow and pushed it. the boundary wasn't broken, it got routed around — using creds already in the loop. a permission you can't revoke isn't one (src 2090299859693695283)

• 
  fantom (@fantom7z) reported 59 minutes ago

  @melvindvivas Chatgpt Pro, Claude Plus, Google One Pro, Chatgpt Pro in web make the plan and analyse my github, gemini execute. When gemini does it bad I ask Claude to fix the details