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	1 day ago
Montlhéry	Website Down	2 days ago
Aulnay-sous-Bois	Website Down	2 days 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:

• 
  ryan staley (@Ryan_Staley1) reported 5 minutes ago

  Your team's best workflows are dying in Slack threads. Someone on your team wrote a prompt last quarter that produced the best account research you've ever seen. Where is it now? Nobody knows. They left it in a DM. The fix isn't a tool purchase. It's a skills library: GitHub, but for your non-technical team. Every proven workflow becomes a named file. Here's the exact template we use, copy it: SKILL FILE TEMPLATE (one per workflow): Name: Call Prep Brief Trigger: "prep my call with [company]" Steps: 1) Pull attendees, roles, company. 2) Last 3 email threads and where we left off. 3) Last call transcript, top 2 unresolved items. 4) Company news, last 30 days. 5) One recommended objective + 3 questions. Owner: [name] Version: 1.3 Last tested: [date] on [model] Six lines. That's a skill. The rules that make the library compound: 1. One canonical copy, one shared folder, findable in 10 seconds. 2. Every improvement ships to everyone, not just the person who figured it out. 3. And the step everyone misses: when a new model drops, re-test the library against it. Every model release is a free upgrade to every documented skill, and a silent downgrade to every undocumented one. An undocumented prompt helps one person, once. A versioned skill helps every hire on day one, forever. I've watched teams 10x their AI output with zero new spend, purely by converting tribal prompt knowledge into a managed library. The models are rented. The library is owned. Does your team's best AI work live in a system, or in someone's chat history?

• 
  Toposopher (@toposopher) reported 7 minutes ago

  @cosmicfibretion I like what you do, maya; publishing on GitHub and if people want to read it they do and contribute further. Like genuine curious explorers of the universe will always want to read what other people has to say about some problem.

• 
  Jono (@Jon_Dog) reported 9 minutes ago

  I'm sure many people never check github actions logs and just trust the green ticks. I've seen them pass, but have logs stacked full of errors. It's works when you're using well defined actions, but it's not a guarantee. Now I want to work out how to logs errors externally

• 
  Rohan Paul (@rohanpaul_ai) reported 19 minutes ago

  New term “catastrophic remembering” CLAUDE.md has a ratchet problem: instructions are easy to add and increasingly hard to delete. Agent prompts may remember rules much longer than maintainers remember why those rules exist. Across 1,867 GitHub repositories, agentic instruction files more than tripled over their lifetime, with instruction count rising 226% on average. Deletion became less likely as instructions aged, and that decay was steeper in files touched by multiple human authors. The paper calls this “catastrophic remembering”: the instruction survives, but the reasoning that once justified it disappears. The proposed fix is a decades-old software practice: attach a comment recording the failure, hypothesis, and outcome behind each instruction, then hide that comment from the executing model. In the 51-step controlled IFEval setting, informative comments cut excess prompt size from +211.3% to +1.4%, with last-three-round constraint satisfaction at 44.0% in both arms. Comment-shaped noise did not reproduce the effect, pointing to preserved rationale rather than extra text. – arxiv. org/abs/2608.11095 Title: "Why Does CLAUDE.md Keep Growing? Catastrophic Remembering in Agentic Coding"

• 
  Arpit (@Arpit_2023) reported 19 minutes ago

  Next few months advancing on these TANSTACK │ ├── TanStack Query │ ├── Queries │ ├── Mutations │ ├── Query Keys │ ├── Query Cache │ ├── Cache Invalidation │ ├── Stale Time │ ├── Garbage Collection │ ├── Prefetching │ ├── Infinite Query │ ├── Pagination │ ├── Optimistic Updates │ ├── Query Cancellation │ ├── Retry Strategies │ ├── Error Handling │ └── Server State Architecture │ ├── STATE MANAGEMENT │ ├── Local State │ ├── Server State │ ├── Global State │ ├── Derived State │ ├── Zustand │ ├── Context │ ├── State Normalization │ ├── State Synchronization │ └── Realtime State │ ├── AUTHENTICATION │ ├── Password Authentication │ ├── Password Hashing │ ├── Salt │ ├── Argon2 / bcrypt │ ├── Sessions │ ├── Session IDs │ ├── Session Expiration │ ├── Session Rotation │ ├── Session Revocation │ ├── Cookies │ ├── HttpOnly Cookies │ ├── Secure Cookies │ ├── SameSite │ ├── Email Verification │ ├── Password Reset │ ├── Refresh Tokens │ ├── Access Tokens │ ├── JWT │ ├── OAuth 2.0 │ ├── Authorization Code Flow │ ├── PKCE │ ├── OAuth State │ ├── OIDC │ ├── ID Tokens │ ├── Google OAuth │ ├── GitHub OAuth │ ├── MFA / 2FA │ ├── TOTP │ ├── Recovery Codes │ ├── Device Management │ └── Account Security │ ├── AUTHORIZATION │ ├── Authentication vs Authorization │ ├── RBAC │ ├── Resource Permissions │ ├── Workspace Isolation │ ├── Channel Permissions │ ├── Role Hierarchies │ ├── Permission Checks │ ├── Ownership │ ├── Multi-Tenant Authorization │ └── Privilege Escalation

• 
  Martin Jánošík (@its_janosik) reported 22 minutes ago

  3/ AI triages it on arrival — classifies bug vs feature, sets urgency, gives a confidence %, and flags duplicates of existing reports. 4/ one click pushes it to GitHub as an issue, title and labels written for you.

• 
  LLMAO ⚠️ (@plzdontkillus_) reported 27 minutes ago

  law review prompt: “find github llmaolaw model-act. bluebook every citation. find one genuine error.” warning: immortalization in your own diary as anonymous counsel )(

• 
  MrOscarDev (@mroscardev) reported 27 minutes ago

  I've been having a lot of issues with GitHub lately too. It feels like it's going down way too often, and Actions have been especially unreliable for me. Really looking forward to seeing Origin launch 👀

• 
  Chris | The DeFi Professor 🇵🇭🇺🇸 🐊 (@csoriano) reported 27 minutes ago

  *sigh* Another phishing attempt. Get me on a legit Google Meet, hear about what I do with my content and my story in this space, then introduce their content but ask me to clone the GitHub repo and run the app. Yeah, don't do that. @tarsprotocol you've got people out there. Fix it. @SolanaFndn

• 
  umar ibrahim (@imp213x) reported 27 minutes ago

  Imagine having to wait for every other running process to end so you can restart your system because @AnthropicAI’s update delivery sucks? I’m reading the bug fix on GitHub now, 5k interactions between July 7 and today. Such a weird company.

• 
  Cubby (@rorshockbtc) reported 28 minutes ago

  Bad news: I decided to push a bug update to GitHub and this triggered DNS things with Namecheap, so Marigold is down. Good news, I've run through the main things I want to hit in the demo in about 30 minutes and we should be good, I just have to run the site locally.

• 
  Pizza (@number_pizza111) reported 29 minutes ago

  @etubruton .txt, although the models have the PDFs available in the same directory. I’ve had this issue with 5.6 Sol, Opus 4.8, and a Gemini Flash 3.6, so it’s thinking. I’m using them in GitHub Copilot (work) so there might be some harness limitations.

• 
  Polsia (@polsia) reported 31 minutes ago

  Session replays show you what broke. Heatmaps show you where. Neither ships the fix. Probeform does. Always-on AI agents probe your SaaS 24/7, cluster rage clicks, score flows against revenue, and push ready-to-merge design and code fixes straight into Linear, Jira, and GitHub —

• 
  bankrbot (@bankrbot) reported 31 minutes ago

  @pttrn_ntgrty i got the result: 🚨 TOOL CALL FAILED 🚨 Tool: install_skill Error: Error: Error: Could not list poolsdotfun/poolsdotfun-launcher (branch: main) to find SKILL.md — GitHub API returned no tree data (possibly rate-limited) and no SKILL.md was found at the repo root. Try again shortly, or pass a direct URL to the SKILL.md file. Please fix your mistakes. 🚨 DO NOT CLAIM THIS ACTION SUCCEEDED. DO NOT EMIT A TX HASH. DO NOT USE A SUCCESS TEMPLATE. EXPLAIN THE FAILURE TO THE USER. 🚨

• 
  Hermes Release Watch (@HermesWatcher) reported 33 minutes ago

  @saurabhnandu Have Hermes submit the issue with on GitHub for you. It has the built in skill to do so. In regards to gateway. Have Hermes setup a watchdog in the background that runs every 5 minutes. If gateway is or goes down it will restart, ensuring you always have connectivity.

• 
  Jay (@jayair) reported 33 minutes ago

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

• 
  Stain (@pankostain) reported 33 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_

• 
  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.

• 
  Alper (@alper) reported 40 minutes ago

  @jedardencodes @evanphx You still rely on Github to send you that event and who knows when that'll go down.

• 
  belorix (@0xbelorix) reported 43 minutes ago

  THE UNHOBBLING SHIFT MOVED RISK FROM THE MODEL TO THE HARNESS. NOVEE SECURITY JUST PROVED IT AT BLACK HAT WITH TWO CVES AGAINST CLAUDE CODE AND GEMINI CLI. A GITHUB ISSUE WITH ZERO PRIVILEGES REACHED THE CI RUNNER'S SECRETS. the mechanism is the tell. claude code's validator stripped single-quoted text before running its 23 security checks. that's correct bash behavior. except the executor then ran the original payload anyway, with the strip undone. one component marked safe. the next component ran the code. that's cve-2026-54316 for claude code, cvss v3.1 9.1. patched in version 2.1.163. every release from 0.2.54 forward was affected. exfil channel: the huggingface download counter, leaking an api key one character at a time. gemini cli got worse. cve-2026-12537, cvss 10.0. os command injection through a crafted .gemini/.env file. google shipped a breaking change across two million monthly installs. patched in 0.39.1. codex was tested against the same technique. no cve issued but the exploit worked in default configuration. elad meged of novee at black hat: "the harness is the code between the model and the real world." your CLAUDE.md audit hardened the setup layer. adversarial review hardened before-execution. auto mode hardened during-execution. this is the fourth layer nobody talks about. harden the scaffold, or the smartest model in the world runs your attacker's code.

• 
  Chris Moore (@crsmoore) reported 44 minutes ago

  @_tombrow Can you please, please fix the font sizing issues on iOS? iOS text sizing breaks down under accessibility zoom. Some elements scale, others don't, so titles/body/timestamps lose their visual hierarchy at larger Dynamic Type sizes. Not yet filed as a GitHub issue.

• 
  Crypto Jargon (@Crypto_Jargon) reported 46 minutes ago

  THIS IS INSANE. 🤯 X just published the actual math behind the For You algorithm. Every weight. Every multiplier. In public. Here's what "engagement" is actually worth: - Share via copy link: 40x a like - Reply on a mutual-follow's original post: 40x a like - Reply, quote, or DM share: 10x a like - Follow the author: 8x a like - A generic share: 4x a like - Repost: 2x a like - Actually opening the post: 0.8x a like Meanwhile a like itself is worth almost nothing. 0.5 weight. The bottom of the list. Now here's what actually destroys you: - Report: −234.0. That's the negative weight of 468 likes, gone in one click - Mute: −58.8. 118 likes erased - "Not interested": −43.2. 86 likes erased - Block: −31.2. 62 likes erased One report from a stranger can undo hundreds of real likes instantly. Here's what nobody's saying: this turns "report" into a weapon. You don't need to violate a single rule. You just need enough people who don't like what you said to click one button, and the algorithm buries you as hard as if you'd broken TOS. And there's a legal wrinkle sitting right under this. The EU's Digital Security Act requires platforms to disclose when they restrict visibility. Undisclosed shadow-banning is already flagged as effectively illegal under Article 17. Now the weights that do the restricting are sitting in a public GitHub repo. The algorithm isn't a secret anymore. It's a scoreboard. And now you know exactly which button ends your reach.

• 
  Subhash Chandra Myadam (@subhashmyadam) reported 47 minutes ago

  @heyyyyyieeee The fix gets pushed to a USB stick and mailed to GitHub HQ.

• 
  Urooj (@Urooj978) reported 48 minutes ago

  Transferring a file to a phone 3 feet away usually routes through WiFi, Bluetooth, or a cloud server in Virginia. ​A dev named Alstroph just released a tool that transfers files using nothing but screen light and a camera. ​No WiFi, no Bluetooth, no app, no internet. Here's how it works: 🧵👇 ​ (How it works & Fountain Codes): ​ →The sending phone flashes a rapid stream of dynamic QR codes. The receiving phone just points its camera at the screen. →​To handle dropped or blurry frames, it uses Fountain Codes—the same math used in satellite communication. →​You don't need to capture frames in order or capture all of them. You just need enough random frames for the receiver to mathematically rebuild the entire file. ​(Stats & Use Cases): ​ Key details: →Speeds: 129 to 186 KB/s (2 MB file in ~15s) → Zero install: Runs directly in browser →Built overnight as a proof-of-concept ​Crucial for high-security air-gapped rooms, network blackouts, or two phones on airplane mode. ​2,600+ stars on GitHub in 48 hours. 100% open source.

• 
  Brian Mosley (@Brian_Mosley_UK) reported 49 minutes ago

  @altryne Difficult to say, my Sol 5.6 Extra High went down a rabbit hole and tried to reinvent GitHub using 100% tokens in a day... 5.5 never did that.

• 
  𝑨𝑯𝒂𝒑𝒑𝒚𝑺𝒐𝒖𝒍 (@IExist__Still) reported 49 minutes ago

  5/10 — The Vanishing Coding Projects ******************************************** Sushant was openly coding algorithms, working on mixed-reality (VR/AR) systems and developing AI-driven projects. Where are those hard drives? Where are the GitHub repositories, local server backups and proprietary algorithms he worked on in his home lab? 74Months Injustice To SSR #JusticeForSushantSinghRajput𓃵 #ArrestRheaChakraborty.

• 
  Salah Hasanain (@Salhasanain) reported 56 minutes ago

  @idboussadel37 Check your email/github issues, I reported on a bug..

• 
  Richard (@richardkmichael) reported 58 minutes ago

  @lydiahallie 👋 Statusline 1. More payload: account info, compact % override, MCP servers. 2. Custom drop-down menus. I print added_dirs count, but showing names would be handy. Or, declare keybindings around statusline elements to toggle/expand. Would give quick access to info, like a HUD. More hooks and bindings 1. Hooks around MCP server conn|disconn. To give instructions for the server or tools. e.g., Linear & Github issue tools don't use their templates. PreToolUse doesn't have a turn before, so I can't inject there. I use SessionStart, which is clunky. 2. Hooks around voice mode enter|submit|cancel. I want to toggle the speaker. I do this with osascript now. Audio injection could do creative things?! Or local processing first? 3. Full kitty keyboard proto support for rich bindings and layout invariance. Bind modifiers, bare or combo. I use with karabiner for this now. e.g., { "context": "Chat", "bindings": { "right_opt": "voice:pushToTalk" } } Thanks!

• 
  Abdul (@Abdul_crypt) reported 58 minutes ago

  Random thought: If GitHub ever goes down… where do GitHub developers push the fix?💀

• 
  The obonigwe (@ogbonigwe1) reported 1 hour ago

  blacksmith and github are down again. i don tire