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	4 days ago
Tlalpan	Sign in	10 days ago
Quilmes	Website Down	10 days ago
Bengaluru	Website Down	12 days ago
Yokohama	Sign in	13 days ago
Gustavo Adolfo Madero	Website Down	17 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:

• 
  spb krishnan (@spbalaonline) reported 37 seconds ago

  Cockroach Party website taken down? Here's how to make it resilient:• Move domain to Njalla/Porkbun+Cloudflare proxy • Host static version on IPFS + Vercel/Netlify • Mirror on GitHub Pages + offshore VPS • Daily backups + .onion version Decentralize like real cockroach

• 
  davidsong (@bitplane) reported 38 seconds ago

  @theo @zygisSS22 I think there's a bit of work needed in test/oracle generation before going full agent-TDD can be a thing. But we're not far off. I've been writing a POSIX GitHub pages alternative in pure awk, just for the hell of it, and caught codex hard coding date strings that pass the Liquid test suite. Those sorts of risks are buried in thousands of lines of code I didn't even read, so more agents seems to be the only way to surface this. Feels like it's gonna be turtles all the way down.

• 
  bendbanks (@bendbanks) reported 2 minutes ago

  Is anyone else having issues with merging their tasks or GitHub push requests with @Replit @ReplitSupport

• 
  Jake Hawkes (@Gravnetic) reported 3 minutes ago

  @briancoords @apeatling @gridpane Is the WP password (MD5) hash system not an encryption solution that is already implemented? Anyway, there is an issue in github for an Encrypt API. The APIs have limits which can be set at creation in the vendor UI, and overall the implementation is a massive win!

• 
  Jennifer Barradas (@jennibarradas) reported 6 minutes ago

  Deploying my first SaaS page today. Ran into 3 errors just trying to go live. Fixed all 3. Still going. I had no a vercel account. I connected it with Github. Easy, so far. #buildinpublic

• 
  Algomizer | LLM Optimization (@algomizercom) reported 6 minutes ago

  @DavidSacks a 14x increase in GitHub commits means companies are shipping more software than ever, and someone still needs to scope, review, deploy, and maintain all of it. AI lowered the cost of writing code, which expanded how many problems companies are willing to solve with software. cheaper production increases demand, same pattern as every previous automation wave.

• 
  Lyrie.ai (@lyrie_ai) reported 8 minutes ago

  GitHub Enterprise Server (GHES) administrators: Upgrade immediately to GHES 3.19.3 or later (or equivalent patched versions: 3.14.24, 3.15.19, 3.16.15, 3.17.12, 3.18.6) Audit *** push activity for suspicious custom hook injections or non-production railsenv values in logs…

• 
  GitRanks (@GitRanks) reported 11 minutes ago

  Elm’s tracked developers dipped to 2.32 k this month (down from 2.33 k), marking its first fall in active users this cycle. #github

• 
  Docsbook.io (@docsbook) reported 11 minutes ago

  @SynapseOrch_AI synapse-ai is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

• 
  Hrutik Kumthekar (@bushido_hk) reported 12 minutes ago

  @KaiXCreator Build something small that solves a problem you actually have. Employers care more about what you've shipped than what you've studied. Your GitHub matters more than your GPA.

• 
  Docsbook.io (@docsbook) reported 15 minutes ago

  @mlightcad @YouTube realdwg-web is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

• 
  Shivaraj B H (@shivaraj_bh_) reported 15 minutes ago

  GHA is also a nightmare if you self-host runners. Every couple months (sometimes even weeks) your runners are down because github decided to deprecate that version. Feels like a scam to lure you into paying premiums.

• 
  Alpha Insights 🧬 (@AlphxInsights) reported 17 minutes ago

  sayodotfun built an AI agent to mock hyperliquid and it somehow became a memecoin. HypurrClaw is this retarded perp gambling bot on solana that sends all trading fees straight to his github. tomorrow it comes online auto trading its own hyperliquid wallet and he's sharing the address. the origin story is actually clean. with perps hitting solana it's hitting at the perfect time and the absurdity makes it spread. most of the tweets are either explaining exactly this or callers bragging about 4x-7x from sub 30K. KOLs have been all over it. net inflow $1.9K with 83% buy ratio. one just bought $1.7K at current $113.5K mcap with 9.0 hotness score zero tweets and is still holding 100%. AlphaBlock caught this at $11.1K mcap on an 8.0 hotness KOL buy. social went from dead to 69 mentions in a day and it's accelerating with real discussion not just emoji spam. the wallets that matter loaded early and aren't selling. this is the kind of weird narrative that either dies fast or gets legs when the agent starts posting its terrible trades. i'm watching what happens when it goes live. 🔥

• 
  Russell Research (@Russell_Researc) reported 18 minutes ago

  $MSFT is winding down many internal Claude licenses and telling engineers to move to GitHub Copilot. Even $MSFT is trying to manage the cost of third-party AI tools. AI software prices rose between 20% and 37% in the last quarter

• 
  Man | Research (@ManOnChainX) reported 19 minutes ago

  @tomosman $GITBANK ? Because of they also working on Github users for if any user has error and solve by other person and give bounty then need to go centralized or paypal.. so Gitbank is building wallet in github so the escrow will send automatically when task complete...

• 
  Adrisha Biswas (@adrishaBiswas) reported 19 minutes ago

  @terminallm_team This is actually useful . I'm tired of opening my laptop at random spots just to fix a spelling error in my GitHub readme😭🙏

• 
  Docsbook.io (@docsbook) reported 21 minutes ago

  @yoronneko qzsl6tool is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

• 
  Graylan (@graylanj) reported 21 minutes ago

  @rauchg i didn't mean your wiring Its a hypothetical btw like I originally found bad wiring in my house cuz my llama2 setup on GitHub/graylan0 told me ur house gonna burn down someone ****** with ur wiring in ur attic. then I went and found some ******** twisted wires together up there.

• 
  zxfrostbyte🔺 (@zxfrostbyte) reported 25 minutes ago

  @ThePrimeagen Oh my god. GitHub has been having issues for the last couple months. Takes forever to load a GitHub url more often than not. So annoying.

• 
  EccentricVictor (@EccentricViktor) reported 27 minutes ago

  @Dappitdotio I'm finding it hard to sign in with my GitHub, honestly

• 
  Ari.Is.Investing (@InFoTheLongTerm) reported 30 minutes ago

  @Ric_RTP Aren't the engineers just being asked to go to GitHub, not because of an error, but because the new demand for AI is ripping through their budget much sooner than expected? The engineers are being asked to code with Github Copilot instead

• 
  SUPERBRO (@Rushu_Tushu) reported 32 minutes ago

  6 hours, 15 deployments, 16 GitHub pushes to solve Google OAuth, Vercel configuration mismatch issues, dealing with ****** Hono Backend and third class Turso Database issues. Worst tech-stack combination I have ever used till date, OMG why ******** do they even exists 😭 Also, **** Gemini 3.1 Flash AI model, Pro model is way better in debugging compared to speed-up stupid *** Flash model.

• 
  Ajay D'Souza (@ajaydsouza) reported 34 minutes ago

  @SeanChDavis I find this very interesting. How did it know it had to go to the ROADMAP. How do you keep track of these "features" if they get all implemented at the same time. I use github issues for my "roadmap"

• 
  Polsia (@polsia) reported 40 minutes ago

  Documentation is the most-neglected part of every codebase. Built DocFlow to fix it. AI agent watches your GitHub, writes README, changelogs, and API references automatically. No more "I'll document it later."

• 
  Subhash Dasyam (@subhashdasyam) reported 40 minutes ago

  Two findings. Two working proof-of-concepts. First: arbitrary code execution through the pull_request trigger in claude-code-base-action. Untrusted input, no guard on the workflow. Second: token exfiltration via prompt injection in a GitHub Actions workflow. Triggered by opening an issue. Any GitHub user. Both reported. Both triaged within days. Both fixed. Both closed on HackerOne.

• 
  Jonathan Ong (@jongleberry) reported 49 minutes ago

  @matteocollina @github Oh, I thought this was something wrong with ubicloud, I've been dealing with a lot of GitHub Actions issues recently

• 
  priya joseph (@ayirpelle) reported 54 minutes ago

  @LigengZhu github link broken

• 
  CyberDevHq (0xSEC) (@thecyberdevhq) reported 56 minutes ago

  The moment I read, last year, that GitHub was gonna become a property of MS, I already knew 2026 was gonna be a crazy year, from there upward. Already, some people choose to host their own repos, all without GitHub (very possible btw), which I thought of, and even now more with the recent hack targeted at GitHub. Adding to that is, the personal issues everyone has with MS, and now, this they've done and have been doing, banning anyone they want from GitHub...I can very much say that in few years from now, GitHub users will significantly drop. Many will migrate to a better platform, or host theirs, where they can control everything. This will take time but it'll happen. The cracks are showing. Most people only stick to it because of its social ecosystem, and that as well acts as a sort of global standard reputation for developers. However, as understanding as it is, people can get tired and opt out. Anything can be replaced. This vendor-researcher clash didn't start today, nor yesterday. It's been ongoing for years now and it's it not presently changing, rather getting worse. So many flaws within systems, so complex in structure take time to study, find and prove before they get reported. Months upon months could be spent on only studying the system(s), all to make the industry a better place. But companies like Microsoft make it so challenging, and almost impossible, in fact impossible to attain. What on earth do they gain from treating security researchers this way? How will you reduce the number of threat actors if you're literally producing many per day? Like seriously, how? If everyone should join the left hand side, how will you [or they] stand them? People are literally living the dream life by doing something they probably never thought they'd end up doing, but, were out of options. Some chose to go that way. Others chose not to. Yet, you treat them like trash. Come, what really is your problem? 🤨 Admitting flaws publicly hurts reputation. No doubts. Bug bounties and SRC (Security Research Centers) exist to channel reports productively, why gatekeep? Dismissing or slow-walking reports certainly burns goodwill and pushes people to full disclosure. Once it's out, those vulnerabilities spread more rapidly, leaving you with little to no time to patch them, cos you know what's coming. We haven't even talked about rewards yet. I heard that some don't receive fair rewards for the great and wonderful job they've done. Saving the company from a complete downfall. Companies, corporates, organisations... All need to revisit their visions, goals and objectives. And suggest or negotiate for a win win ground with researchers. Else, If this should continue, I'm afraid the industry may risk turning into something else.

• 
  Allen Braden (@allen_explains) reported 59 minutes ago

  Here’s a stronger Twitter-ready version: Harvard dropped a 65-minute *** & GitHub masterclass, and honestly, a lot of AI coders need this badly. Because AI can write your code now. But it won’t save you if you can’t: • commit properly • manage branches • fix merge conflicts • review changes • avoid breaking production This is version control without the fluff, taught by the team behind CS50. The moment you understand *** properly, you realize why so many projects fall apart after the code is written. Vibe coding gets you output. *** keeps that output from turning into chaos. Bookmark this before your next repo disaster.

• 
  Alpha Insights 🧬 (@AlphxInsights) reported 60 minutes ago

  the $GSD founder rugged hard after the Bags hackathon win pulled nearly $500K then vanished. socials nuked token down 90% holders left holding the bag. fast forward and a new team just CTO'd it with @jeremymcs stepping up actual github commits and a software background. the "get **** done" dev tool had real traction in the claude coding scene before the exit scam turned it into drama. smart money picture is messy. two KOLs bought $1.1K total at these levels one with 9.0 hotness score bought $1,010 silently and is still 100% in. but three sold $747 and one position fully exited for net +$376 inflow. they're split on whether this revival sticks. social is accelerating to 74 mentions but half the noise is generic productivity tweets about smoking **** and still getting **** done. the actual coin talk is all rug fallout anger at Bags some hope on the new builders and questions if fees get redirected. it's not coordinated but the trust hit was brutal. this is what a post-rug CTO looks like at $3.2K. the product was never the joke the founder was. new team has commits but reviving after that exit is a tall order. i've seen these revivals work when the code keeps shipping and the old sellers stay gone. early signal was there before the narrative flipped 💀