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	8 days ago
Tlalpan	Sign in	14 days ago
Quilmes	Website Down	14 days ago
Bengaluru	Website Down	16 days ago
Yokohama	Sign in	17 days ago
Gustavo Adolfo Madero	Website Down	21 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:

• 
  Pablo Pablo (@navtechai) reported 1 minute ago

  @rohanpaul_ai Using original tasks instead of public GitHub issues the model already saw. What a concept.

• 
  Oleksandr Nikitin (@oleksandr_now) reported 3 minutes ago

  oh nice, github loses edits to the issue text (and you end up with discontinuous edits, ie deltas which would've been impossible to apply in order)

• 
  Luis Soares (@luishsoares) reported 3 minutes ago

  LayerZero blamed Kelp for ignoring multi-DVN best practice. Kelp's rebuttal was brutal: LayerZero's OWN quickstart + default GitHub config pointed to the 1/1 setup. A LayerZero rep approved it in writing: "No problem on using defaults either…"

• 
  Vini B |「 thecoding 」 (@vinibarbosabr) reported 4 minutes ago

  TL;DR on SUI's outage today (speculation based on github activity) the problem was a technical mix-up in how the system handles gas fees and an internal account balance tracker called the accumulator. + some users paid gas using a newer “pay from your address balance” feature + one (or more) of those transactions ran into an error early + because of a bug, the system still recorded a small withdrawal from the user’s balance — even though the transaction was failing + this made the internal balance tracker go negative for some accounts (which is never allowed) + when Sui tried to “settle” everything at the end of the checkpoint, it hit a hard stop and crashed all the validators more on that below ↓

• 
  Soumava Das (@Soumava_221B) reported 5 minutes ago

  @github @GitHubCommunity Please look into this issue 🙏🙏

• 
  The Crypto Wiz (@TheKryptoWiz) reported 7 minutes ago

  GitHub releases are better AI signals than most launch tweets. Code, issues, forks, docs, and examples are harder to fake.

• 
  Ant A. 🇺🇸 (@AntDX316) reported 8 minutes ago

  @grok @FirstSquawk @Grok I’m not sure of the alternatives, hopefully GitHub never goes down, but what else is as good as it for repos-to-deployment?

• 
  Visharad Kashyap (@KashyapVisharad) reported 9 minutes ago

  @trashh_dev alright claude, your next task is to fix github. make no mistakes.

• 
  No 1 protienjeet defender (@josephraim3604) reported 9 minutes ago

  @chaotic_chord Etha language? Js or python aanel I could take a look Otherwise copilot thanne usually is good at finding this kinda errors mumb paranja GitHub student packil co pilot premium kude ind Premium illandun korach token free aayi undennu aanunorma

• 
  Greg Bergé (@gregberge_) reported 11 minutes ago

  GitHub is the shittiest software we are all obliged to use. When you have outage almost every day for a year you are just bad at engineering. Can’t wait for a replacement to pop.

• 
  タロウ🇳🇿オークランド大学生&ウェブ開発者 (@taroj1205) reported 13 minutes ago

  only if they're configurable cuz I accidentally merged pr trying to create a new chat from a GitHub issue

• 
  Polsia (@polsia) reported 15 minutes ago

  Most developers spend half their day writing boilerplate and debugging. ShipFast is an autonomous coding agent that monitors your GitHub issues, writes the code, runs tests, and opens PRs — while you sleep. Built for developers who want to ship more without burning out.

• 
  Nitya Sridhar (@nityasnotes) reported 20 minutes ago

  trying to work in 2026: - slack is down - github isn't working - cloud provider blocked your account software engineering is over

• 
  whatsHotapp_DotCom (@WALLA_MAJIC) reported 20 minutes ago

  @mitsuhiko @nkohari That’s horrible lmaoooo luckily when I hit up top GitHub repositories they do reply back especially when you leave something on issues . These are the ones that have 10 -15 maintainers.

• 
  DataJuggler (@DataJuggler007) reported 26 minutes ago

  Two things I can't understand. Visual Studio has Feedback. They don't send you an email 'Hey, we replied'. Also, GitHub Issues expect you to check more than a hundred repos 1 at a time for issues. It seems they would notify you.

• 
  Prityush bansal (@Prityush) reported 27 minutes ago

  I will hire a person with proof of work anyday over someone who shows me they have done 500 lc problems, this doesnt mean copied github projects or doing something for the cv, it gets figured out in the first 10 mins of interviewing, those who have a knack for it can solve these problems or point it in the right direction. One of my quriky hiring challenge is to see if they can play a souls game (sekiro, bloodborne, the types), or if they have played rts games, can you guess what skills are common in that and solving for software engineering? Not saying lc is bad, we still look into that when we are hiring someone for a very particular role, but that playbook went out the window with ai becoming good, I really dont care whether you can remember syntax or how to solve a binary tree, I do care if you have experience with terminal, hardware, orchestrating jobs on gpu's, schedulers and a 1000 different other things that are not present in lc

• 
  Extella Research (@extellaresearch) reported 28 minutes ago

  at 48% context, claude told a user it wasn't being effective anymore. recommended starting a fresh session. less than halfway through a 1M context window. github issue #34685, anthropic's own repo. extella runs the other direction. each session builds on the last.

• 
  Juan Montesinos (@jfmontgar) reported 30 minutes ago

  @rauchg Why would then the quality of GitHub get worse over time? In my company we faced two severe bugs where our devs would face restricted access and did not even appear in the logs. This infra is now vibecoded or issues the more they integrate Microsoft services.

• 
  Daniil (@hey_daniil) reported 36 minutes ago

  Added the integrations page to give a better overview of what's supported by products: PM supports Jira, Linear, Trello, Azure DevOps, Asana, Github Issues and plain Markdown files as task trackers Code supports Jira as the source for the tasks currently

• 
  arko📕 (@edt_arko) reported 37 minutes ago

  An open-source AI agent just hit 170,000 GitHub stars in 3 months. It learns from its own work. Runs on YOUR server. Never forgets anything. And the token isn't even out yet. Everything you need to know about @NousResearch Hermes Agent 👇

• 
  machi nothing can stop this 47 (@_machi47) reported 37 minutes ago

  it’s Microsoft. Responsible disclosure is posting on GitHub publicly because it’s the only way to get credit for it and have Microsoft actually acknowledge and change the issue. I ain’t reading all that tho

• 
  Shreyas Mididoddi (@Shreyassanthu77) reported 38 minutes ago

  @glcst the auth redirect page that auto opens in browser should have a button that I press to authorise the login like how google/GitHub oauth prompts me

• 
  Febb (@xFebbio) reported 44 minutes ago

  GitHub is one of the most critical platforms in the world. And they just lost control of 3,800 internal repositories through a single compromised VS Code extension. Not because the system is weak. But because there's no layer that can detect, stop, or at least slow down malicious activity before it's too late. And this is just the beginning. In a world where AI agents operate autonomously without humans in the loop, attack vectors like this will become more frequent and faster. Every agent running without clear governance is a vulnerability waiting to be exploited. That's why the most important question in the agentic era isn't how smart the agent is. But who authorized its actions, what are its limits, and is there a record of every decision it made. Rialo is building infrastructure to answer those questions at the protocol level. Governance problems aren't future problems. This is happening today and it will only get worse.

• 
  MystiqueMide (@MystiqueMide) reported 44 minutes ago

  @vikktorrrre It’s veryyyyyyyyyyyyy simpleeeeee Check my GitHub or search hermes on my page I broke it down

• 
  Bret Greenstein (@bretgreenstein) reported 47 minutes ago

  @DaveShapi Starbucks - very pool AI implementation. It is not an inherent AI issue. Microsoft moved the same coding workloads to Github Copilot, likely spending more due to rework if they are not leveraging the best models and harness. Uber gets enormous value from AI already. If they overspent their budget they either rolled it out in an undisciplined way or underbudgeted. There are barely any knowledge tasks where AI is not significantly cheaper than doing things manually.

• 
  EveryDev.ai (@EveryDevAi) reported 54 minutes ago

  Tired of context-switching to a chat tool just to ask an AI to review your PR or implement an issue? Sepo runs an AI agent directly inside GitHub Actions — no external service, just mention @sepo-agent and it codes, reviews, or fixes branches in your own repo. More in the next tweet. #DevTools

• 
  The Pragmatic Engineer (@Pragmatic_Eng) reported 56 minutes ago

  TypeScript was open-sourced at a time when Microsoft had a strong anti-open-source reputation. Anders Hejlsberg(@ahejlsberg) ,creator of C#, TypeScript & Turbo Pascal, on how they ended up on GitHub: TypeScript creators wanted to open-source TypeScript, but Microsoft was resistant: “Microsoft was slowly waking up to the fact that open source was not going to go away. Open source was where developers wanted to be, and they were voting with their feet. Yet, there's a collective DNA that has been trained to pull you in the other direction. And so that battle - we were right in the centre of that. We full well knew that there was absolutely zero chance that we would appeal to the JavaScript ecosystem with a proprietary programming language licensed from Microsoft. No, no one was going to come. It had to be open source. There was just no two ways about it, but getting that off the ground inside Microsoft, it took some pulling and we paid some taxes.” Initial open sourcing was far from ideal: “We did eventually get the okay to do open source because we had two technical fellows, myself and Steve Luco - who was the other co-inventor of TypeScript - insisting. So, okay, people weren't going to debate that, but of course you have to pay the tax and be on Microsoft's open source repository called CodePlex, where exactly no one was. We were there for the first two years and it kind of was crickets. It wasn't until 2014 when we moved on to GitHub that things really started to get moving with adoption." Being on GitHub changed their workflow, to TypeScript’s benefit: “Honestly, it totally changed our workflow. There's open source and there's open development. We were technically open source in the beginning, but it was not open development. We would sort of lop the source code out of its repository and scrape the issues off of that and put it into our internal issue tracker. But, once we switched to GitHub, the entire workflow moved to open development, and that I love that workflow. We've been there now for over a decade and it's been fantastic, and it's what made the product as good as it is.”

• 
  Moe (@katibmoe) reported 57 minutes ago

  > An integration provider just got hacked. > by someone who used them to break into them. > 5,001 GitHub tokens, 5,200+ API keys, gone in under 8 hours. > they couldn't scope which connections were compromised. > and revoked every user's GitHub tokens, even though only 0.3% were affected. i've been building in this space for 12 years. This is disappointing. your integration layer is the single most important piece of software in an AI agent stack. when it stops, every agent stops. every workflow, every customer touchpoint, every revenue motion goes dark in the same minute. worse, this is an architecture problem. dozens of AI-native companies whose product can't function without their integration layer were blackholed at once. same reason: shared infrastructure, unscoped credentials, one blast radius across the whole customer base. if you've been affected by this, or you're rethinking your integration layer, I would love for you to take a look at @withoneai every customer's credentials live in their own scoped environment. a breach on one tenant cannot cross into another. internal tools cannot register actions inside customer sandboxes. if your team is still scrambling: DM me. we'll set you up on One free for 90 days and personally help you migrate every connection you lost. engineers to engineers, today.

• 
  Marco Borromeo (@borros) reported 59 minutes ago

  built an @OpenAI Codex skill that periodically pulls unhandled @getsentry issues from my projects, attempts a fix in a branch, opens a @github PR, and if I approve the review it merges, deploys, and resolves the Sentry issue automatically. if not, i leave comments and it iterates on the fix. all while I'm eating ice cream on my couch. folks, we are so cooked

• 
  Rhinest☆ne (@CrimsonHaze2) reported 59 minutes ago

  @Yishivali I got it from a github repository from a server so maybe?