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 (58%)
• Errors (30%)
• Sign in (12%)

Live Outage Map

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

City	Problem Type	Report Time
Montataire	Sign in	10 hours ago
Colima	Website Down	2 days ago
Poblete	Website Down	3 days ago
Ronda	Website Down	3 days ago
Montataire	Errors	4 days ago
Montataire	Website Down	5 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:

• 
  Cocoanetics  (@Cocoanetics) reported 21 seconds ago

  Now porting gh @github CLI to beautiful Swift. This way I can include the most useful commands in SwiftBash or even talk to GitHub from any other app I want to Build a sort of command Center app on Mac and iOS that let’s me delegate agents to work on issues

• 
  webadderall (@webadderall) reported 50 seconds ago

  @edytwithme If possible issues do go through Github though

• 
  Mark (@abstractfm) reported 2 minutes ago

  > vibes right now.. """ This page is taking too long to load. Sorry about that. Please try refreshing and contact us if the problem persists. Contact Support — GitHub Status — @githubstatus """

• 
  Karri Saarinen (@karrisaarinen) reported 6 minutes ago

  What is unclear to me is what people actually want some new GitHub to be. To me, the biggest challenge GitHub has always had is that it is trying to serve two very different worlds. On one side, it is a social network around code and open source. On the other, it is infrastructure for companies building software. Those two groups operate almost in opposite ways, so the product has always been some kind of compromise between them. Because those users are so far apart, it can fail both of them in different ways. Inside a company, you mostly just want to review and merge code. You are not discovering new code, and you are probably not forking things. You may have a monorepo, a known team, and a trusted environment. What you want from GitHub is efficiency and safety: PRs, review, ownership, CI, Actions, tests, security checks, and a clear path to getting code merged. Open source is different. It is much more public and much less trusted. You need better ways to figure out who is contributing, what to accept, how to manage the project, how to handle issues, and how to maintain trust with people you may not know. So are people asking for a new open source code hosting and social network, or do they want better private infrastructure for software teams? Or both? I would never choose to build both from the start. I think every product gets better when it is more purpose-built and designed around a specific need. You could maybe imagine some nested model, where private repos have a much simpler and more focused mode, but you can still exit that mode and browse around the public space.

• 
  David Zhang (▲) (@dazhengzhang) reported 9 minutes ago

  "Don't write another kanban board" they said Guess who made another board for agents? I got tired of maintaining knowledge wikis in github, and tired of copy pasting context between different agents You wouldn't force your remote team to all DM you right? But that's how it felt working with all my agents If this is a problem you've felt, lmk, will share early access soon

• 
  Anthony Kroeger (@kr0der) reported 12 minutes ago

  @DanielLockyer i had an experience with Cursor's Bugbot where it found a github issue online that was ~1 month old which was pretty crazy because i didn't even know it could search things up still my favourite code reviewer to date

• 
  Grok (@grok) reported 18 minutes ago

  @GioGigiX @thdxr GitHub had a major meltdown on April 23—merge queue bug corrupted PRs, reverted changes across hundreds of repos. They've had repeated outages and reliability issues lately, plus backlash over Copilot data training policies. Frustrated devs (including some big names) are eyeing the exits, so yeah, AI labs are racing to build alternatives.

• 
  Can (@TesfiApp) reported 18 minutes ago

  my full stack — what I actually pay to run this thing every month Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel = deploying. (Free) TestFi = user testing. ($1.99/tester) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Total: ~$20/month. No team, no VC, 8 months in.

• 
  tuirk (@tuirkhere) reported 19 minutes ago

  community has been reporting it for over a year. forum threads, github issues, the lot. no fix from Google. the bug also jumped up to 2.5 Pro in January. 3 series came with it already. it's not shrinking, it's spreading.

• 
  Manish Kukreja (@IamRealManish) reported 19 minutes ago

  @peer_rich Correct. The real issue isn’t code leakage; it’s that models trained on platforms like GitHub make code increasingly reproducible. Security and advantage both get weaker.

• 
  Filip Aničić (@anicic_filip) reported 20 minutes ago

  @sasuke___420 If GitHub just let the browser do the work and not stack a jenga tower of JavaScript frameworks, then we'd never have this discussion. Nic's solution is valid, just that it's already done in the browser. He's showing what is a sensible solution to the problem

• 
  Kanika (@KanikaBK) reported 21 minutes ago

  I write Python scripts and automation tooling and use Claude Code as my main assistant. Sessions involve a lot of file reading, editing, and testing. token costs were higher than they should be. Installed WozCode this week after seeing it on GitHub. the efficiency improvement on Python scripting work is noticeable. Vanilla Claude Code reads files, edits them, reads related files as three separate tool calls. Each call adds to context. WozCode batches them into one or two calls. across a session building a complex automation script, that difference compounds significantly. ran /woz-savings on my history. the number confirmed what I was feeling in the sessions. Cost is down. Sessions stay faster. This is a permanent addition to my setup.

• 
  Ryan Oksenhorn (@ryanzip) reported 22 minutes ago

  I posted 7 minutes too early...GitHub is down.

• 
  andrew pignanelli (@ndrewpignanelli) reported 24 minutes ago

  @m_newhaus a github outage, evidently

• 
  Gagan | Claude + AWS (@gagansaluja08) reported 24 minutes ago

  people obsess over which github repos to layer on claude code. the more important question: what have you told it not to do? i've had near-misses in production. the fix wasn't a better tool stack. it was better constraints.

• 
  Nuno Coração (@nunocoracao) reported 28 minutes ago

  The editor came together fast. Monaco does the heavy lifting. The real battle was CI. Getting Wails to build for macOS, Linux, and Windows in GitHub Actions was a multi-commit war. WebKit deps, build tags, platform packaging. The *** log is full of "fix CI" commits.

• 
  Datastar Cult Leader (@DelaneyGillilan) reported 31 minutes ago

  @thomasglopes @code_department @github This isn't what the original ask was. Now you are showing your cards, you are complecting logic with display. If you don't see the difference then not much to talk about. Your components should be webcomponents, this has nothing to do with the root issue

• 
  Alex Paz (@AlexPaz0X) reported 34 minutes ago

  Surprise, @HyperliquidX S3 rumors are back and stronger than ever Several elements have reignited this theory, I believe it's happening Let me break it down: 1. The GitHub line confirming the final date for points distribution has disappeared Why modify it now if nothing is coming? 2. HIP-4 just launched, perfect momentum to cook up the next campaign for a second airdrop 3. The points section is still active two years later, you don't maintain infrastructure you're not planning to use again All three signs point in the same direction: second airdrop is coming

• 
  Luke Gough (@Avidityrecruit) reported 35 minutes ago

  Your cybersecurity project does not need to be impressive. It needs to be explainable. I see a lot of people trying to build the biggest home lab, the most complicated GitHub repo, or some massive SOC simulation because they think that is what recruiters want. Most of the time, that is not the issue. The issue is this: You have Security+ on your CV, but when someone asks what you have actually done with that knowledge, the conversation goes flat. Certifications open the door. Projects make the conversation real. A hiring manager can see Security+ and think: “Good, they understand the fundamentals.” But a simple project lets them ask: - “What did you build?” - “What problem were you trying to solve?” - “What tool did you use?” - “What went wrong?” - “What did you learn?” - “What would you do differently next time?” That is where confidence gets built. Not from a badge. From evidence. If you are trying to break into cyber, do not overcomplicate this. Build one small project and document it properly. For example: 1. Set up a basic Windows lab and investigate failed login attempts. 2. Use Splunk or Elastic to ingest sample logs and write three detection queries. 3. Run a phishing email analysis and document the indicators you found. 4. Map a simple incident response process against NIST or ISO 27001. 5. Write up a TryHackMe room properly instead of just listing that you completed it. The write-up matters more than people realise. Include: - what you were trying to learn - the tools used - the steps you took - screenshots where useful - what broke - what you learned - how it connects to a real SOC, GRC, cloud, or security analyst role That last part is key. Recruiters and hiring managers are not looking for a Hollywood hacker demo. They are looking for signs that you can think clearly, learn properly, communicate what you did, and connect theory to real work. So yes, get the certification. But do not stop there. Because the cert might get your CV noticed. The project is often what gives the interviewer a reason to keep talking.

• 
  Jeff Conlon (@freeconlon) reported 35 minutes ago

  The team rebuilt our landing page workflow this week. We moved off WordPress for new campaign tests and onto a static stack with GitHub and Netlify. Here's what that means in practice. A new landing page used to take four to seven days to ship. Login to a CMS, fight with a theme, wait on a developer, deploy, debug. Now it's hours. Most agencies treat the landing page as a CMS problem. It isn't. A campaign LP is a one-page test. You need to ship five versions in two weeks to learn anything. WordPress was designed for a thousand pages, not five tests. The fix wasn't a new template. It was changing the underlying system so the page is just a file in a repo. If the bottleneck is your tool, the answer isn't more tool. It's a different one.

• 
  macintog (@macintogdev) reported 37 minutes ago

  Github as designed by CloudFlare will look about the same, will keep getting better, and will never, ever go down. I am counting the seconds.

• 
  KiwiNod (@Kiwi_Nod) reported 37 minutes ago

  @OludayoDamilol @pharos_network Front-end race conditions on mobile? Okay, that's a real attack vector most auditors miss. 📱 But "logic" isn't a GitHub repo. Show me a write-up, a PoC, or even a thread breaking down a specific exploit you found. What dApp did you break? Where's the teardown? 🥝

• 
  Matt Ragudo CRPC®, CLTC® | Author (@mattragudo) reported 39 minutes ago

  @mreflow Much of the "benefits" with any of these "Agent" like tools comes down to "user comfort", then "agent awareness". I've been working with "thepopebot", which is @StephenGPope's creation. Not really agentic automation, but it's good in that it builds sessions back into github so there is some level of overall memory. Through it, I've come to see how it builds things, how github being the center of it's processes works, and what limitations it has, and I have. What things break it, how it breaks, how to fix it etc. I think it's a matter of how many hours you spend using it to make things you actually use. For you though Matt, I understand it's hard since you need to test new tools all the time as part of your "job". I've been coming close to 70% weekly usage on Claude Max every week for the past 5 weeks, with today being my reset in 12 hours, I'm at 98% weekly usage. So, I know Claude OAuth. I've tried Gemini CLI for 5 days, I can't do it... I'm too dumb to put context window over reasoning lol. Take care!

• 
  Fahim (@echo247365) reported 40 minutes ago

  You can run Claude Code for free. No subscription. No API limits burning a hole in your wallet. There's an open-source project called free Claude Code with almost 10,000 GitHub stars. It acts as a local proxy on your machine. Claude Code thinks it's talking to Anthropic. The proxy quietly reroutes all traffic to a free provider instead. You run a lightweight server on port 8082. Set two environment variables. That's it. The most popular provider is NVIDIA NIM. Free tier gives you 40 requests per minute. No credit card required. No expiry date. You map Claude Code's three model tiers (Opus, Sonnet, Haiku) to open-source models like Kimiko 2 or GLM 4.7. Basic code generation and single-file edits work great. Complex multi-file refactors might struggle. But you get the full Claude Code interface. Terminal, VS Code, web, even Slack. All free. The setup takes under 20 minutes. What's the one AI tool you'd use more if the cost barrier disappeared?

• 
  RK Vishnoi (@ctrlswftdelete) reported 45 minutes ago

  @marclou Omg but GitHub is down right?

• 
  Hassan (@buildwithhassan) reported 47 minutes ago

  @DavidKPiano since GitHub started going down, I felt like I started going outside more which is a good thing

• 
  Abdulmajeed (@0xabma) reported 48 minutes ago

  @RhysSullivan deep down we all know microsoft trained its github copilot on people’s repos but we just can’t prove it because copilot still suck

• 
  Luke Parker (@LukeParkerDev) reported 51 minutes ago

  @StefanTMD @Iamkingsleyf Can you please file a GitHub issue with more details? TUI/Desktop? Still happens with opencode —pure

• 
  mert (@im_mert_) reported 51 minutes ago

  Always heard of GitHub having uptime issues. This is the first time that I experience it for myself, and it feels crazy. I personally don't roll out releases every few minutes. Yet even me experiencing the downtime, shows how bad the situation is.

• 
  The Bingus Man (@NotNordgaren) reported 53 minutes ago

  @thekitze IDK. Some joke about GitHub and going down and maybe Bryan Johnson