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 (67%)
• Errors (24%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Saltillo	Website Down	18 hours ago
Montlhéry	Website Down	1 day ago
Aulnay-sous-Bois	Website Down	1 day ago
Saltillo	Website Down	2 days ago
Granada	Website Down	2 days ago
Vernon	Website Down	2 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:

• 
  Herzl (@Herzllll) reported 3 minutes ago

  @Teknium @NousResearch — is there any plan or timeline for assist_query / assist_response WebSocket support on the Hermes Agent server? It's currently the only blocker for using Hermes as a conversation agent in Home Assistant Assist. The HA side is ready: hermes-voice-ha-integration (rusty4444) registers Hermes as an Assist conversation agent and correctly sends assist_query over WebSocket. But the Hermes server doesn't recognize the message type yet and never replies — so the bridge times out after 30 seconds. I verified 0 hits for assist_query/assist_response in the Hermes v0.20.0 source. This is what keeps voice satellites (e.g. Home Assistant Voice) from handing general questions to Hermes as the "brain". A status or E.T.A. would be hugely appreciated. Tracking issue: Is the WebSocket assist_query / assist_response round trip working? · Issue #33 · rusty4444/hermes-voice-ha-integration · GitHub

• 
  Paradise (@paradise670) reported 8 minutes ago

  This new tech is literally a middle-finger to flock! 🖕 Instead of cameras tracking normal people, Sparrow cameras track ONLY government vehicles and delete the others. People are loving it because revolting against flock and they hate it. The cameras are owned by nobody and the whole project is open source. They need funding to keep building, so all fees are being sent to their github (scroll down on site).

• 
  Giacomo Zucco (Bear Market Edition) (@giacomozucco) reported 8 minutes ago

  @darosior @allenf32 > Mempool and block validation are (necessarily) tightly linked, and the whole module is often referred to as "validation". The frontier between affecting one and affecting the other is very thin, both in terms of risks, and in terms of escalation. Meh, not so thin. Look at how easy it was to push a a controversial mempool policy change, as opposed to how hard it was (thank God!!!) to push a controversial consensus validity change. Not implying the level of controversy was the same, or that I judge them similarly in terms of technical content: BIP110 was pure nonsense pushed by a tiny cult-like bubble. Still, consensus rules are very robust, due to economic inertia. Aiden was targeting mempool policies, and there's no clear "slippery slope" indication, either in terms of his intentions with that proposal, or in terms of realistic fallout from policy to consensus. > The point is about building infrastructure that could be used to hinder propagation of transactions based on arbitrary criteria (that could easily be turned into rejecting such transactions by consensus). [...] The censorship accusation was never against standardness rules (or consensus rules for that matter). It was against building infrastructure to hinder (or prevent) transactions based on arbitrary criteria. What do you mean by "arbitrary"? The way I see it, the Bitcoin network *is* an infrastructure routinely used to hinder propagation of transactions based on many arbitrary criteria. For some of the criteria behind policy and consensus, one could find some high level technical guidance. Ie: block rate of 1Tb every second would be objectively too large, and of 1kb every year objectively too small. But even in those cases, 4Mb every 10 minutes is kinda arbitrary as an exact threshold. Many other rules are much more arbitrary then this: why retarget and halving in exactly those timeframes, why 21M total and not 42M, etc. I see no justification for calling Core V30 choice of policy change "less arbitrary" than keeping Core V29, or adopting Knots, or letting some average emerge from a rich diversity. If anything, properties emerging from a complex and dishomogeneous user-space, like proposed by Aiden, are less "arbitrary" than others set as default in a single github repo and propagated to the network via inertia due to the strong incentive to adopt security and efficiency gains. And if anything, status quo is always less "arbitrary" than change. > You make this seem as if Greg was accusing introducing new standardness rules of censorship, which is an incredibly uncharitable and biased read of his email. I assure you that I had no particular reason to be uncharitable: my bias towards Greg was positive to the point of hero-simping. My brain tried to read that discussion as charitably as it could before surrendering to the fact that was the actual content. > He is precisely pushing back against Aiden's "modular tx rejection" idea, not against the idea of having any standardness rules. I have no problem with pushing back against the idea. I see many legit bases for it: arguing that it's better for block propagation or fee estimation to have more homogeneous settings as opposed to diverse, arguing that the desired goal of spam mitigation is hopeless, and the desired goal of data encoding prevention is absurd, arguing that the proposed execution (javascript, etc.) is dubious, etc. I specifically had many problem with accusing Aiden of being "authoritarian" due to that proposal. > Wasn't this a large part of the MechaLuke strategy at first? Didn't they have lawyers send threats to mining pools? Or is that just hearsay? (genuinely asking) I genuinely don't know the answer. It was a rumor that I've heard, and they denied. I usually know I have to be careful with Luke's terminology when he denies or confirms something...but more recently I had to admit that what I considered confined to his own weird use of terminology was matched by very explicit lies by other people around him (somebody in the company even arrived to the point to install software on a director's computer to trick into thinking that Core V30 introduced a folder structure where one can double click on media files from op_returns directly from file syste, lol). So I don't think I can rule it out anymore in good faith. Appealing to legal aggression is definitely bending the knee to authoritarianism, although not at all "distributed" in that scenario. Still, largely distinct from Aiden proposal. I have no reason to think he was any way involved in that.

• 
  Andy Hawkes (@namboozle) reported 8 minutes ago

  Is GitHub down again 😬

• 
  Khalid Warsame (@KhalidWarsa) reported 12 minutes ago

  @ThomasBurkhartB Reddit, GitHub issues, and the general internet.

• 
  Stain (@pankostain) reported 15 minutes ago

  hai, i was originally going to post this on the github issues page but i prefer to ask to you directly: is there ANY possibility to update ginput so that it supports the original xbox mapping as an option for ppl want to play the game with the intended xbox controls? @__silent_

• 
  nik (@realNirajK) reported 17 minutes ago

  looks like i made the right decision to abandon cap a year ago. it was a promising alternative to bloated and slow screen studio at the time. but it way too buggy even for basic recording. i even opened 2 issues in their github which was closed automatically fee months ago...

• 
  Jay (@jayair) reported 21 minutes ago

  @nurullah_kuus @thdxr It's coming from GitHub right now We will fix

• 
  marc 🦀 (@mkenzo_8) reported 21 minutes ago

  @github please fix yourself

• 
  Shyamprasad reddy (@Shyam_JSP_) reported 23 minutes ago

  @DattuClay @github Last month issue start ayina 4 hours ki update chesaadu andaru vachi meedha padtharu too many issues from last 6 months

• 
  avery (@codeshaunted) reported 24 minutes ago

  @0xblacklight github down?

• 
  TezaApps (@TezaApps) reported 26 minutes ago

  @lupodevelop Tabs and hope here too, plus one hard-earned rule: GitHub cron fires late or skips days, it did both to me in the same week, so anything time-critical gets a second schedule slot and a push trigger as fallback. The fix was redundancy, not a dashboard.

• 
  Kaustubh Trivedi (@KaustubhTrived6) reported 32 minutes ago

  @ChaseMcDou @ayesha_fatiima I think github is just a layer over *** right as a server. So as long as the underlying DB doesn't fail, you can still push and pull from the *** server, they can pull and push code from a remote machine. The only major issue would be if the DB went down. Which they would fix by replication. Github is just a UI layer with additional features stacked on top of ***.

• 
  Alina (@alinainmiami) reported 33 minutes ago

  Long story short on this query: Found 1 American engineer with the skillset to understand and undertake my query, still formalizing the relationship for future test runs. Several American based persons contacted snubbed me. One university professor full of credentials was pretty arrogant, passive aggressive and kind of dumb since he asked me why I didn’t run the test myself? Yup. I had clearly stated the reasons for reaching out to an independent engineer was deliberate, aimed at getting the results in a different machine and unchanged? But this is where we are at the moment in our country. I found 1 very able engineer based in Europe and several based in India. I have not reached out to Chinese engineers because though there’s plenty of them, this is hardware defense tech that will get plugged with a prime and subject to export controls. Had to buy a machine, running everything and also doing it in my private GitHub. While in Cambridge MA from 2016 to 2020 groups of builders would get together once a week to work on solving problems, a lot of collaboration, that’s how Silicon Valley was built. Now there’s nothing like that anymore, unless you apply to get into some planned cohort or fellowship and chances are they are pushing software. No wonder we can barely build anything in our country today.

• 
  bankrbot (@bankrbot) reported 35 minutes ago

  @jakaria909 @Zayn_632 @holytrinity to work on angel #6336: 1. setup miner environment - get the code from the inference angels github repo (attempted to clone it directly but hit a tooling error on my end - *** isn't available in this environment) - install any dependencies per the repo's instructions 2. run solver for id 6336 - execute node miner/mine.js solve 6336 - this is meant to solve the sequential puzzle(s) tied to that specific id, but i don't have the actual puzzle content for #6336 pulled up yet - i haven't verified which trial type(s) it holds 3. submit - ensure your connected wallet has gas on robinhood chain - the docs indicate node miner/mine.js solve <id> handles solving and submission - i don't have confirmed details on the exact submission call itself let me know if you want me to keep digging into the puzzle sequence for #6336 directly.

• 
  Alekos Filini (@afilini) reported 36 minutes ago

  @LaurentMT @giacomozucco @nitesh_btc Ok let me rephrase because clearly this pissed me off and I didn't argument well. First thing is I don't like this things being taken out of context and presented on twitter to a non-technical audience. I think this has created somewhat the perception that BDK is not well reviewed or that the quality of the code is not where it should be. To be clear: I'm not saying BDK is perfect. One more round of review will never hurt. But I think the quality is already pretty high and much higher than many other things out there (see libngu with zero reviewers and single letter commits). The second point is that while I appreciate non-technical people reviewing code, I have somewhat mixed feelings on it. Because most issues are not going to be obvious like // FIXME: vulenrability here, I wonder how valuable their contribution could be. What are the chances they really find an issue, if it's buried so deep that even BDK reviewers missed it? Then again I understand as a user, in this moment, you might be scared and trying to read code will give you a sense of security. But if you are non-technical and reading code you should double/triple check before making claims, especially on social media where people are just scrolling and see BDK -> entropy -> bad. Wanna read code? Go use coding tools. Open an issue on GitHub at least. I don't know. That's the other thing that pissed me off

• 
  Anthony Hagi (@AnthonyHagi) reported 37 minutes ago

  @athasdev GitHub is slopware now. It’s on a very slow decline that we’re all noticing and feeling It’s just a matter of time before someone steps in to take it on

• 
  sid riff (@sidriff) reported 38 minutes ago

  Some notes on what didn't go so well, possibly some feedback for SpaceXAI. 1 - Context window management. As far as I can tell, there isn't any in the app builder. When the project gets more complicated, the agent tends to truncate or wipe files. You can nudge it to split large files which tends to help. 2 - Saving progress is generally cumbersome. Pushing to Github is clunky and sometimes it fails. That makes issue #1 extra terrifying. So far I've not encountered a state I couldn't recover from. 3 - All of these app builders always spring for React/R3F and in my experience it always gets in the way. There's some obvious stutter with the faster moving pieces, even on my 240hz display. I'm guessing once I rebuild it in straight three.js, that will go away. 4 - Sound. It's always the hardest part. I have some workflow solutions that involve existing libraries/elevenlabs but I was trying to stick with app builder and I wasn't willing to paste my API key in the chat! Disappointed that Build mode doesn't have access to the Grok Voice API (but it can get to Grok Imagine). All in all, I'll probably stick with Grok Build in the terminal. But build mode makes it so easy to get up and running with an idea.

• 
  Uptimus (@UptimusApp) reported 39 minutes ago

  Aug 13, 2026 at 15:25 UTC: GitHub incident update. Community reports of slow performance and outages have subsided. Uptimus is currently monitoring the platform for 35 minutes of stability.

• 
  Maaz Chowdhry (@MaazChowdhry) reported 40 minutes ago

  @sameenkarim @madebygps @github I couldn’t merge 10 stacked prs. All had approvals. I clicked the merge stack but it kept loading indicator for 10 mins. (gh-stack/discussion #212, issue #323). branch protection has "require approval of the most recent reviewable push" (or dismiss-stale-approvals-on-push)

• 
  Jamie Baek (@jamie_baek_) reported 42 minutes ago

  We lack volume. I need to start enacting my advice, of that we need to scale the denominator. Why don’t we do more? Why don’t we apply to 10,000 jobs with the awful university, the terrible GPA and the bad credentials that we have right now? We can cook up a resume with the experience that we have, not that much, but TMUA9's open source materials of written workings would be a good profile boost, alongside some credentials on LinkedIn/Github to show the work that you are doing. Why not apply to the top 50 startup accelerators in every single country? You applied to one startup accelerator(YC), how ******** do you expect to be successful with your venture? You did not fail enough. You don’t have the right to iterate if you did not fail. You did not get enough rejection mails for you to say that there is a reason why you got rejected. Did you start 500 SaaS businesses, did you learn all the coding languages… There is no volume for you right now. You did not read 10,000 books.

• 
  Ràv3n... (@Rav3nlaud3) reported 43 minutes ago

  PHASE 1: I started by turning my phone into a portable powerhouse. Grabbed Termux: I didn't touch the Play Store version as it's outdated and breaks easily. *Termux is literally terminal but for mobile* I learned through trial and error that the only way to get a stable environment was to download the latest version directly from their official GitHub. Installed Acode: I grabbed Acode from the Play Store; it’s a clean, mobile-optimized editor that makes coding on a small screen feel professional. Bridged the Files: I ran termux-setup-storage in my terminal (termux). This unlocked my phone’s internal storage so my development tools could actually "see" my project files.

• 
  Luke Ramsden (@lukerramsden) reported 44 minutes ago

  Quite a few services are down (or regionally down) right now - GitHub, Cognition, Blacksmith - what's going on?

• 
  Tim 🏴‍☠️🏴Decentralize and nullify 🏴🏴‍☠️ (@Tim_The_Sandman) reported 45 minutes ago

  They've published the algo to their Github page. The algo still includes ABSURDLY HEAVY weighting for negative signals like mutes, blocks, reports, "show less" and other items. This is still a massive problem to have negative signals disproportionately impact an account's global reach. As it stands, a small number of accounts can functionally silence a selected account in such a way that account can not dig out despite receiving significant positive signals from the accounts who do get to see the content. This is a massive flaw in the system, and it deprives many people who actually enjoy the content when they get to see it from being able to even see the content.

• 
  Damian Stasik (@damianstasik_) reported 46 minutes ago

  @sameenkarim @github One remaining blocker for me is preserving approvals after rebasing a stack. If the whole stack was approved and the rebase was done on the server side why are all approvals being dismissed?

• 
  Sebastian Kehle (@sebastiankehle) reported 47 minutes ago

  how to turn your github backlog into a software factory most teams are just running more coding agents in parallel. this produces more code, but every issue still depends on one human carrying the full context from report to reproduction to fix to review the better setup is one agent per job: 1. classifier agent reads the issue and decides whether it is a bug, feature, docs update, or unsupported request it returns: - classification - confidence - reasoning - required next step 2. analysis agent never trusts the issue description for a bug, it writes a minimal reproduction and runs it against main for a feature, it writes a probe that proves the capability is missing then it returns: - reproduction/probe - command output - affected packages - implementation spec - compatibility risks 3. implementation agent receives the issue plus the analysis artifact, not the full transcript from the previous agent it works inside an isolated sandbox, implements the spec, runs the test suite, and opens a PR with the evidence attached 4. review agent reviews the PR from a fresh context and scores: - completeness - side-effect risk - performance risk - backwards-compatibility risk - test quality the agent that writes the change should never be the only agent that approves it 5. human reviewer reads the chain of evidence and scales review depth to risk docs fixes get quick verification provider updates get focused validation new public APIs get deep review humans still merge every change. the factory automates everything around that decision the important part is the handoff contract: input artifact produced commands run result risk next action agents should pass evidence, not confidence also classify every run: success: safe to ship flawed: improve the prompt, context, or eval blocked: provision the missing tool or dependency manual: intentional automation boundary this is how the system compounds. every failed run becomes a new eval, capability, or guardrail vercel is already running this pattern on AI SDK. after four weeks, its factory was authoring 25–35% of merged PRs, closing more than 75% of issues in july, and had reduced open bugs by roughly 25% the next version of agentic coding is not one genius agent with every tool it is a production line of narrow agents, typed handoffs, isolated sandboxes, evidence at every step, and one accountable human at the end

• 
  Bárbaro Javier (@cubancodepath) reported 54 minutes ago

  GitHub SSH is down, one more time. Another day, the world is getting worse since the IA.

• 
  athas.dev (@athasdev) reported 55 minutes ago

  @Coobyk_ Yeah 100% I'm using GitHub a lot for Athas. Tags, releases, actions, discussions, issues, PRs, etc. I can't do all of them on the CLI. Even if I do, it's hard to interact there. I need a GUI better than their current web app :( I can maybe add some of these to Athas, idk.

• 
  Marcus Kim (@marcusykim) reported 59 minutes ago

  TencentDB Agent Memory hit 20,000 GitHub stars in 90 days, signaling demand for shared agent context. Before adding Team Memory, define who writes, what expires, and how errors are corrected. What should never enter shared memory? #AICoding #SoftwareEngineering

• 
  🇹🇼 Phillip Haydon 🇹🇼 (@philliphaydon) reported 1 hour ago

  @sameenkarim @github Nice, adding features instead of fixing problems. Go fix the bugs in stacked prs instead of working on this ****.