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 (29%)
• Sign in (13%)

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	9 hours ago
Quito	Sign in	1 day ago
Junín	Errors	1 day ago
Guadalajara	Errors	1 day ago
Paris	Website Down	1 day ago
Quito	Errors	1 day 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:

• 
  Abbas Asadzade (@AbbasAsadzade) reported 3 minutes ago

  @thdxr a lot of teams are adding a fallback path instead of fully switching. github actions stays primary until the next multi-hour outage forces the decision

• 
  Dmonty (@Dmonty28516998) reported 6 minutes ago

  @joshmanders @AdamRackis the lack of CEO is just representative of how poorly MSFT has supported GitHub. To be clear, when I say ****** mgmt, i mean from microsoft, not github internally. GitHub has openly said, if everything had been moved to Azure, this wouldn't be happening. So it's kind of wild to say that this isn't a MSFT issue, when MSFT owns both github and azure.

• 
  Michael Roe (@mroe1492) reported 11 minutes ago

  @Teknium For me, it’s mainly the issue tracker that is down (and, I have been needing to read the issue tracker lots). Pushing commits to GitHub has, mostly, been ok.

• 
  Patrik Tang (@_patriktang) reported 17 minutes ago

  GitHub was down yesterday, claude just went down. The world is probably ending soon

• 
  Erik Kovari (@erikkovari) reported 18 minutes ago

  @oorestisime @thdxr @CodeAkram When GitHub is down, blacksmith is down - they are just providing the runners, gh still orchestrates the actions

• 
  0xMuninn (@0xMuninn) reported 26 minutes ago

  @BinanceWallet github skill for the agentic wallet under a pnl contest. they shipped the login as a repo.

• 
  Tyler (@ccatsss) reported 30 minutes ago

  @pyaaraacetamol I use Gitea which has their own Actions/Runner that seem to be similar to GitHub actions. I don’t use them, but instead Woodpecker CI which I think I have linked to both GitHub and Gitea - even with a cheap server you can do pretty decent things.

• 
  Shane O'Neill (@zeevoexe) reported 32 minutes ago

  @jdegoes You don't really know this. It could be surviving *because* of LLM coding, not despite of it. GitHub had a slow frontend before vibe coding. It now has a faster frontend in the last year or so.

• 
  ✧ 𝘌𝘯𝘪𝘨𝘮𝘺𝘺 ✧ (@enigmyy) reported 33 minutes ago

  @VixenVRC For the YouTube issue, what also fixed it on my end was replacing the yt-dlp.exe file in the VRC AppData/Tools folder with the latest release straight from GitHub, and then setting it to "Read only" so VRChat doesn't overwrite it.

• 
  Phil | Rentier Digital Automation (@rentierdigital) reported 34 minutes ago

  13,000 WordPress sites get hacked every day. 91% through plugins, not core. the median time between vulnerability disclosure and mass exploitation: 5 hours. not days. by the time you read the changelog email, automated scanners have already been through your login page twice. so i stopped patching. ripped out WordPress entirely on my personal sites. rebuilt them as plain HTML and CSS using Claude Code. no plugins. no admin panel. no CMS. the results: sites load roughly 2x faster bc there's no PHP running, no database queries, no plugin stack initializing on every request. hosting is free on GitHub Pages. the patch treadmill just stops turning. you can't get hacked through a plugin you didn't install. the catch: this only works under 10 pages. below that threshold, vanilla HTML wins. above it, you need a templating layer like Astro to avoid copy-pasting HTML blocks into maintenance hell. and if you're publishing 3x a week or running an online store or need multiple editors, WordPress is still the right tool. but for a 5-page personal site? the translation layer between human intent and markup isn't the bottleneck anymore. Claude Code handles that. what's left to justify a full CMS? i build and ship daily. Claude Code, Codex, whatever ships fastest. SaaS, tools, automations. ⭐ if AI can build it, i've probably broken it first. what works → link in bio

• 
  Surbhi Jain (@Surbhi_Insights) reported 35 minutes ago

  @Rushu_Tushu just after entering, made GitHub down ;)

• 
  Alex Kemper (@ajkemps) reported 36 minutes ago

  @thedeif Do you mean multiple GitHub organizations, or multiple GitHub login accounts?

• 
  Elestio (@elest_io) reported 38 minutes ago

  GitHub was down often enough that HN asked for exits. 575 points. Your self-hosted forge will have worse uptime. What changes is who can end the outage. #selfhosted #gitea

• 
  George Mayer (@GeorgeMayer) reported 38 minutes ago

  So, lots of people said I was holding it wrong. So I'll share a bit about my agent coding workflow and what I'm doing now to make things better and some experiments I plan to try. 1) to baseline: I don't write any code by hand. I'm usually driving 5-10 agents on my computer at any given time (if you're curious about this setup I can do that in another one). 2) I don't use cloud agents that much, except for brainstorming with the codebase on the go, mostly because I feel they need too much iteration (per the quoted tweet) and I find iterating via PRs clunky. If I end up having to pull the code down anyway, might as well just start locally. 3) Agents have written 15k tests. Some of which are good and test core pieces, most of which are probably trash. That said, I do /ask/ them to write tests to validate the behavior. 4) It's the typecheck that really consumes my memory and CPU though. I've set up an internal thing like @steipete 's crabbox to offload work into AWS microVMs. So agents will do their work, and then sync the worktree into a sandbox and run the expensive checks. 5) I run almost no checks on github, because they are slow and costly. Instead, my agents use the github signoff API to run their own checks and sign off on the PR. 6) I have multiple quality loops (almost all driven via codex). a) codex code review focused on cleanliness and style. There is a list of things that are block-worthy and otherwise codex files tasks for later. b) codex task claim loop where it takes these refactors and implements them. These are conditioned on no behavior change. They get merged without human review. c) codex performance loop where it queries sentry for latest slow traces and tunes them. These are also conditioned on no behavior changes and must have a test that validates that. d) Codex test expert loop that runs daily to just prunes tests. It also methodically goes through the whole test suite and consolidates 3) codex architecture loop where it reviews changes and loops for abstractions to present to me. Tbh, this one is probably going away. In terms of how I code with the agents: 7) within the repo, I have pretty strict guidance for simplicity. I'll often do a simplicity pass at the end either adversarially with a different agent, just ask it to use a subagent or use the skill. 8) I spend a lot of time on the plan so I understand it well. I look especially for flags that indicate the agent actually has no idea what it's talking about. They're kind of everywhere. 9) We've built lots of tools for agents to have access to local and production logs, to certain sensitive read-only **** data to debug. When debugging, I focus mostly and ensuring the agent is grounded and verifying the evidence it presents. 10) I review the code myself and test the feature myself AFTER having the agent do all of it's own validations. I'll usually also just ask... "Did you test in XYZ way like the plan said?" They're honest, "You're right to ask that..." Things I plan to try: 1) Driving with luna and managing tasks on my own. I have to be more present, but I think I'm pretty present as it is 2) more experiments around ephemeral tests. Not sure what this looks like yet, but I want both API boundary tests in the PR, but also only canonical tests making it into main 3) some sort of auto-deletion policy. At meta we had code-reapers that would just delete unused code. I want this telemetry to both auto-delete old experiments and show the agents whether they're editing critical files or things that haven't even made it into alpha. I hope this last idea can steer strongly on overengineering on the latter side and chesterton's fence on the former. Finally, the product I'm building is AI-managed regression suites. This is the thing that let's me sleep at night. And it's going to keep getting better (link in bio). I expect the future to be mostly agent driven coding, but I don't trust them enough let go of the rope (and neither should you). Open to suggestions to improve these things or things you've found particularly useful.

• 
  ΔS (@cemgineer) reported 39 minutes ago

  All the X-bots assembled to promote Origin and blaming GitHub for struggling under 180 million "devs" is absurd. Origin is an empty toll road mocking the public highway for having a traffic jam. It would crumble and go permanently down if it even handled half the load.

• 
  Stéphane Paquet (@stpaquet) reported 40 minutes ago

  @excid3 @github Actions have been a mess for too long. They need to fix them, starting by efficiency. My understanding is that there are a lot of useless code on their end that are penalizing developers and teams.

• 
  Darek Gusto (@darekgusto) reported 42 minutes ago

  @TomasReimers @cursor_ai I've been a Cursor user for over a year by now so I'm myself covered. But yes, even just the existence of an external domain would say "yes, Origin a standalone service, come host your stuff within an environment built from scratch with agentic use in mind even if you're not a Cursor user". I get that it's easier to start small and under Cursor wings, an in case of any problems to keep it on a Cursor feature level. And I'm not as much against the idea as I was yesterday. But you have to admit based on reactions so far, countless people want it to be a general use Github alternative created from scratch with agents in mind. Thanks for all the hard work on it btw and reaching out twice too!

• 
  Groktopus (@groktopus) reported 43 minutes ago

  @jdegoes No, that's not true at all. GitHub has had scaling problems for more than 10 years now. It's only been exacerbated by the use of AI coding by its users, but this problem was always there. Bad architecture loses every time.

• 
  Peter Schacherl (@peterschacherl) reported 43 minutes ago

  What if we just store our repo in localStorage should solve the whole Github uptime issue

• 
  Tatenda Zhou (@realtatendazhou) reported 45 minutes ago

  @thdxr Im also thinking of switching cs in my case I have local runners on my Mac but if GitHub itself is down I lose anyways

• 
  gianmarco simone ✨ (@ggsimm) reported 45 minutes ago

  3 steps to fix github performance 1. slow down every request not by me and my friends by like 10% 2. start randomly failing requests just to get some breathing room 3. randomly logout people 4. increase prices by 10% this should work

• 
  Josh (@joshmanders) reported 46 minutes ago

  @orcdev @github I think the next outage will have the same people who left this time complaining again, as they quietly came back and now are upset again.

• 
  オジサンWatching (@USinJapan1) reported 47 minutes ago

  @ForwardEditor Codex CLI does not lose context or restart when you switch model or reasoning effort mid-session. This was added as a documented feature (mid-session switching without losing context) and an open GitHub issue on the topic explicitly instructs that the warning text should not claim model quality necessarily degrades. What actually happens: switching model or reasoning effort mid-session breaks prompt-cache continuity for that provider. This raises cost and latency for the next turn because cached tokens have to be reprocessed. It does not mean the context window is regenerated from scratch or that output quality drops as a rule.

• 
  Mikhail Rogov (@i_mika_el) reported 47 minutes ago

  @BennyLam launching your own code host during a github outage is either great timing or a stress test nobody asked for

• 
  SambXBT (@bmasXBT) reported 48 minutes ago

  @dbmikus GitHub outage is a norm

• 
  Rui Silva (@ruisilva450) reported 48 minutes ago

  @mattyp I know this is a joke but... You still launched this when github was down anyway

• 
  CodeGlitch (@codeglitch) reported 49 minutes ago

  @shekshiulong1 @thsottiaux will maybe one day see my codex bug reports If not, need to create a issue in github

• 
  Anaya Jain (@AnayaJa10) reported 52 minutes ago

  I didn't know whether GitHub was down because I'd been a couch potato all morning.

• 
  Cynthia Ozumba (@CynthiaOzumba) reported 53 minutes ago

  If you're using Claude without this, you're probably using maybe 1% of its brain. This one thing can unlock the other 99%, and it's called Claude Skills. Claude Skills are blowing up right now, but the mistake almost everybody is making is trying to hunt down the right one for themselves. There is a site with almost 10,000 Claude skills. Skills for coding, sales, research, writing, and all of it. But instead of guessing which one to install, use the number one skill on the whole website. It's called Find Skills. It has over 1.8 million installs right now, and it does the hard part for you. You tell Claude what you're trying to do, and it finds the exact skill for that job. But here is the important part: Don't just randomly install skills from GitHub. The site has a security audit page that checks them first. It shows what's safe, what has alerts, and what's high risk before you paste anything into Claude. So the play is simple: Find the skill. Check its safety. Install it. Now Claude starts acting like it already knows what you need.

• 
  Aryaman (@howaryaman) reported 53 minutes ago

  Genuinely thought I'd broken something yesterday. Pushed three times, got three different results, went digging through my own config. It was just a routine GitHub outage.