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 (65%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	2 days ago
Tlalpan	Sign in	7 days ago
Quilmes	Website Down	7 days ago
Bengaluru	Website Down	9 days ago
Yokohama	Sign in	10 days ago
Gustavo Adolfo Madero	Website Down	14 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:

• 
  Qanapi (@Qanapi) reported 2 minutes ago

  @LinuxHandbook What if...hear us out...this information was encrypted before it could ever get to GitHub? We can't fix human behavior, but we can definitely make the credentials useless to anyone trying to view/use them

• 
  vx-underground (@vxunderground) reported 2 minutes ago

  GitHub is a platform where people can share code and collaborate on code bases. It is a place for nerds to write code, share it, document it, and argue about it by leaving passive aggressive comments. GitHub is owned by Microsoft. Microsoft acquired it some years ago. Since Microsoft acquired GitHub, GitHub has made some changes which have angered nerds, especially nerds who dislike Microsoft. Most notably, Microsoft has been pushing heavily in the AI department with their AI product named "Copilot". GitHub has come under heavy scrutiny by nerds because GitHub as of recent seems to be using Copilot to perform administrative tasks which has resulted, in no exaggeration, severe downtime with the website. Like, it basically goes offline every other day. Imagine if YouTube was going offline every other day for a few hours. Would you find that to be acceptable from a multi-billion dollar company? GitHub going offline is a problem because large organizations, and large free and open-source software projects, use GitHub to make changes, report bugs, and apply fixes. GitHub has gone offline so much recently that several high-profile nerds have (some what dramatically) announced their departure from GitHub and moved to other GitHub-like websites. The "banger" in this post is that GitHub was compromised ("hacked") because one of their employees accidentally detonated malware on their work computer (accidentally ran a malicious program) and managed to steal internal code ... before the company was having infrastructure issues again making it impossible for the "hackers" to steal any of their internal source code. The irony is that if GitHub was having infrastructure problems the "hackers" may not have been able to steal their internal source code.

• 
  Gurung (@gurungbuilds) reported 6 minutes ago

  @composio saw an email revoking the github access and just read the such a let down, since i genuinely thought composio would be pretty safe w auth tokens and even suggested it to everyone i know

• 
  cogsec (@affaanmustafa) reported 9 minutes ago

  "Like imagine being able to price the impact of a paper before everyone knows it matters. Or price academic impact without citations. Or price open-source value without MRR. Because there is an epidemic of fake GitHub stars, fake repo history, all of that. But we still know some repositories are actually valuable. They create economic output. People use them. They save time. They replace other software. They matter. But how do you price that? Right now, you almost can’t. You can say, “I feel like this is working.” You can say, “This has value.” You can maybe put some multiple on growth or usage. But there is no real way to make that value liquid." I have a scattershot of metrics, various revenue streams that act differently, for example native stripe subscriptions for your devtool / app (ECC-Tools), the sponsorship revenue, the github native revenue, downloads from github or other avenues, the growth and usage of the repo itself (stars, forks, PRs, issues, contributors, discussions ...), whats the value of the "ECC" umbrella itself? How do you quantify the value of everything all together, you have metrics of course, MRR, conversion, but MRR depends on where its coming from theres more implied depending on if its for a product or via sponsorships, downloads vary with clones, forks, plugin installs, npm installs, its hard to even track or quantify the impact downstream. There's value in *** to price complex and subjective things like this, for many things, there's well established data, ML models and pricing models that have existed forever, but for the new world and where we are headed that isn't super clear.

• 
  revayz (@0xrevayz) reported 11 minutes ago

  Most Polymarket traders are not losing to smarter people. They are losing to 19-year-olds with GitHub tabs open. Last week one wallet made $13,200 because NOAA updated a forecast and the market stayed wrong for 8 more minutes. Eight minutes. That was enough. I started digging through Polymarket repos and realized something ugly: The people making real money are not “predicting” anything. They are running tiny Claude-based bots on cheap VPS servers and front-running human attention. One wallet made $94,000 trading rain and temperature. Another was firing 180 trades a day with average holds under an hour. Not because weather changed that fast. Because humans are that slow. That is the part nobody wants to admit. You are not trading the event. You are trading how long it takes the crowd to notice the event. And bots notice first. They watch NOAA revisions. They watch order book depth. They watch sentiment spikes. They enter before you even refresh the page. The wild part is that most of this infrastructure is already public on GitHub. Meaning the edge is not hidden. It is just being used by people who move faster than you. Most retail traders think they are competing against other retail traders. They are not. They are exit liquidity for people who automated the game first.

• 
  Pieter Willemen (@PieterWillemen) reported 12 minutes ago

  @pierceboggan @burkeholland @github - Workflows is really slow. - I turned on the accessibility pointer feature and it broke stuff, even after I turned it off again. - Cannot decently set commit message or stage changes. Then what is the point of having a commit button? Either you have got integration, or not.

• 
  Chuck Reynolds (@ChuckReynolds) reported 12 minutes ago

  @OliverSild yup; was my concern w/ core 7.0 as shipped. I was tagged w/ a github issue that it's being worked on to encrypt those.... but who knows when that'll land in core and that should have been done for the feature launch. i don't get the oversight.

• 
  Nuno (@2n1u0) reported 14 minutes ago

  The new frontend seniority signal isn't GitHub contributions. It's knowing exactly where to stop the agent. Juniors let it run. Mids fix what it breaks. Seniors define the boundary before it starts. The skill is constraint — not code. "Write the component but stop before the animation" is a senior-level prompt. Where do you stop yours?

• 
  Vlady Veselinov (@vladinator1000) reported 15 minutes ago

  Hot take: GitHub diffs being slow to render is good! Large diffs lead to uncaught bugs.

• 
  Carlos Barreto (@carlosedubarret) reported 16 minutes ago

  @_cgman_ With that i would suggest you to search on the issue page from github. Try to find a post with a similar problem, and if you dont find, create a new one explaining the steps your done and which files you used to get that error.

• 
  187 (@X3zFabian) reported 18 minutes ago

  @aditiitwt No wonder Github is down all the time

• 
  Sibelius Seraphini (@sseraphini) reported 19 minutes ago

  gh auth login saves @github token in a flat file what are best ways to avoid the github token from leaking?

• 
  Nullspice_ (@nullspice_) reported 28 minutes ago

  @flipper_net Feels like an "all take and no give" type relationship lately with your community. From the outside, it looks like F0 Github development has died or frozen with 0 explanation to anyone involved. Hard to feel good when it feels like extracting free work and not working *with us*

• 
  Anas Malas (@CapacitAnas) reported 28 minutes ago

  @blind_via @igorbiletski Interesting... It could the amazing reliability of GitHub nowadays. Try a VPN? Maybe the GitHub servers close to you are broken, but the ones near me are working

• 
  yeri (@yayriri) reported 29 minutes ago

  Finding AI agents buried in GitHub and giving them a face. Repo 1 done. Two versions shipped. V1: clone the repo, install Python, get API keys, run localhost. Full financial data. Real accuracy. For devs. V2: open Claude, drag in the file, pick a stock. No install. Web search powered. For everyone. Same 18 AI investors. Same debate. Different door. One repo taught me more about this problem than all the research combined: 1/ The agent isn't the bottleneck. The door is. 2/ 51K people starred ai-hedge-fund. Most of them never ran it. Not because it's bad — because poetry install is a wall. 3/ V2 isn't better than V1. It's just... reachable. That's what I'm building. Not better agents. Better doors :)

• 
  Pieter Willemen (@PieterWillemen) reported 30 minutes ago

  @pierceboggan @burkeholland @github - Cant edit or remove scripts in the settings. - Changes shown are not only uncommitted changes, but also already committed changes. - Currently separate MCP server configuration besides Copilot CLI MCP servers. Why is it not the same? - Allow running multiple scripts.

• 
  sadkat (@sadkatwt) reported 30 minutes ago

  How could they hack github ? i mean how did they get the open window where github is not down.

• 
  Rahul Chavan (@codecroc) reported 34 minutes ago

  @jun_song github sponsors exists and nobody uses it. thats the whole problem and crypto doesnt fix the part where people just dont pay

• 
  Osama (@OsssGhoul) reported 35 minutes ago

  @github @GoogleAI @code Fix your pricing page I can't upgrade to pro

• 
  JETER | 지터 | BIP-420 (@akilress) reported 37 minutes ago

  “GitBank turns GitHub into a Base on-chain banking command line.” This catchphrase has marketability. @Gitbank_io Developers already work within GitHub issues, PRs, comments, and repo workflows. GITBANK is not forcing them to use another new app, but is a structure trying to turn the existing GitHub comment section into an on-chain command interface. It’s a good approach. $GITBANK

• 
  Ari is sleeping🏳️‍⚧️ (@ArisMelatonin) reported 40 minutes ago

  @StarPhod4 @ArcticRel0ad I literally never said any of this. I said I'm tired of ppl dragging other trans women down over a starting does just because they do diy. And there's no reason for me to trust a ***** with a github and discord msgs over actual doctors. Never said all doctors are pure or diy bad

• 
  ElasticClaw (@elasticclaw) reported 41 minutes ago

  elasticclaw 2026.5.21 focused on resiliency of factories - When github returns a 5xx error, the factory will continue to retry - When a factory fails, an LLM generated explanation is posted back to the story - The *** credential helper is more "firmly installed" And an exploratory ai troubleshooter was added to the settings page

• 
  Rizèl Scarlett 🇦🇬🇬🇾 (@blackgirlbytes) reported 43 minutes ago

  @wayneoflife I imagine GitHub is in between a rock and a hard place..so much legacy code that it’s hard to rebuild the product and solve the actual problem. But I’m not a fan of blocking contributions

• 
  Maya Nedeljković Batić (@maya_ndljk) reported 44 minutes ago

  @3266miles @karrisaarinen @linear I'm guessing this is a table created via API/MCP server/synced with GitHub and not in the app? We try to make them full-ish width now in app, the programmatic side still needs work. (I'm kidding, all of it needs work 🫠)

• 
  Тлумок (@blur_vibe) reported 46 minutes ago

  @scaling01 Using a .env file is dumb no matter what. What's your problem with using ~/.config/<project_name> like literally every other piece of software does, incl. GitHub?? Elaborate

• 
  Mathias Onea (@mathiasonea) reported 46 minutes ago

  @JonBuildsHQ - 200 followers (1 person away) - automated bugfix pipeline (sentry -> notify github -> create issue -> codex pick up issue -> create PR)

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 48 minutes ago

  @github 3,800 internal repos accessed through one employee's poisoned VS Code extension. The attack surface is developer machines now, not production servers. Credentials get rotated but the real fix is making the extension ecosystem harder to weaponize.

• 
  Lauren Goode (@LaurenGoode) reported 51 minutes ago

  @kshithappens Is GitHub down?

• 
  Mark Maurer (@exanter) reported 53 minutes ago

  This has literally been the question since Dario and Sam have been spouting their bs, and all the “yaya ai” bros have been following suit. since then we have: Massive microsoft issues (win 11, github, etc) lots of security holes with mythos. and lots of vapor ware, for all that it matters.

• 
  Jeroka – יואל The Fire (@_jeroka) reported 58 minutes ago

  @pierrecomputer @github And you literally can't fix your trash app. Someone else had to take in the work to fix what a whole incompetent company hasn't been able to do for years. I'm so glad I'm ditched you all.