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

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	10 days ago
Quito	Sign in	11 days ago
Junín	Errors	11 days ago
Guadalajara	Errors	11 days ago
Paris	Website Down	11 days ago
Quito	Errors	11 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:

• 
  Valiant Vibe Coder (@GeorgeGood60669) reported 4 minutes ago

  @edzitron @StevenBartlett The GitHub point is another really sneaky one. You're arguing that AI is making the code at big tech companies worse, then you bring up GitHub going down as if that's evidence of it. But GitHub's recent problems have been driven by the sheer volume of traffic and AI-assisted development, not because GitHub itself has suddenly been written with vibe-coded slop. You even acknowledge this later when it gets pointed out that GitHub is being hammered by people pushing huge amounts of code. So why use GitHub downtime as evidence that the quality of the code these companies are writing is getting worse? You do this repeatedly. You make a point, throw in an example that sounds like it proves it, and most people listening won't know enough about the subject to realise the example doesn't actually support what you're saying.

• 
  Elaye (@Elayeek) reported 5 minutes ago

  @trq212 Ngl, I didn't know it couldn't before. I have reported some things in the past and I just did it by telling claude to do it. It investigated, drafted, opened a github issue, everything.

• 
  amal (@amal_ytics) reported 5 minutes ago

  @itsnotryan @github Maybe the query powering this dashboard is taking down the servers

• 
  DFIR Radar (@DFIR_Radar) reported 7 minutes ago

  Cisco Talos breaks down JavaScript obfuscation tradecraft used in phishing kits and malware loaders, with a practitioner workflow for turning hidden behavior into observable behavior. Key details: - Obfuscation techniques stack: string splitting, hex/Unicode/Base64 encoding, lookup tables with _0x-prefixed identifiers, dynamic property access (window["doc"+"ument"]), control-flow flattening into state machines, JSFuck punctuation soup, and dead-code noise. These hide URLs, exfil endpoints, and API calls from static search. Beautifying helps readability but restores none of this. - Runtime code generation is the critical choke point. eval(), Function(), and setTimeout("") all act as execution sinks. The practical move: replace the sink with console.log(), capture the intermediate payload, and analyze that layer separately in isolation. - npm package scripts extend the threat beyond the browser. preinstall/postinstall hooks running obfuscated Node.js can reach process.env, SSH keys, npm tokens, GitHub tokens, CI secrets, and the filesystem. "What does it read?" no longer means cookies; it means build-runner secrets. - Anti-analysis tricks include debugger loops, DevTools-open detection, timing-based breakpoint detection, navigator.webdriver checks, domain locks, and console.log replacement. The goal is not permanence; it is outlasting the first five minutes of analysis. #DFIR_Radar

• 
  Mark (@MarkGPlays) reported 8 minutes ago

  @Jxke72 @MarvelcoCode @ImpulsumFUT I was the first person to report a bug on github to him when he launched the 14 local server. Set it up, properly with a real EA Copy. Click on start. Fifa config shows up, but clicking on launch game does nothing. Dude tells me to wait. someone else found the fix which was 1/2

• 
  Gabriel Rubens (@gabrielrubenss) reported 10 minutes ago

  VPS deploy via GitHub (5/8): for now a blocked deploy simply runs again on a fresh runner, and that rescued five of the next six. It is a workaround though, not a fix. The strange part: it started out of nowhere and I changed nothing in my infra, so I still want the real cause.

• 
  YanXbt (@IBuzovskyi) reported 14 minutes ago

  HERMES AGENT CAN NOW BROWSE AS YOU. YOUR LOGINS. YOUR COOKIES. YOUR SESSIONS. ONE CONFIG LINE. THE AGENT ACTS WITH YOUR REAL BROWSER PROFILE. every browser session in Hermes starts clean by default. logged into nothing. need the agent to check your dashboard? log in first. every time. real profile browsing fixes this. browser: use_real_profile: true one line in config.yaml. or Desktop app: Settings → Browser → Use My Real Browser Profile. the agent now browses with your existing Chrome, Edge, or Brave logins. your cookies. your saved passwords. your preferences. already signed in. HOW IT WORKS: Hermes copies your browser's active profile into a managed snapshot at ~/.hermes/browser-profile/[browser]/ your live browser profile is NEVER opened directly. the snapshot is a separate directory. no profile lock conflicts. no fighting with your running browser. auth files (cookies, logins, preferences) re-sync from your real profile whenever a fresh Hermes session starts. log into a new service in your normal browser. the agent sees it next session. WHAT THIS ENABLES: "check my Vercel dashboard for failed deploys" agent opens Vercel. already logged in. reads the data. "summarize my GitHub notifications" agent opens GitHub. your session. your repos. no OAuth setup. "check my analytics in Google Search Console" agent browses GSC with your Google account. "approve the pending PR on our private repo" agent reads the PR diff. already has access. any site you're logged into in your browser = the agent is logged into it too. SECURITY: this is a consent-gated convenience. OFF by default. you opt in explicitly. a page the agent visits runs with your real logins. only enable it when you want the agent acting as you. when you turn the toggle OFF, Hermes deletes the snapshot store (~/.hermes/browser-profile/). copied credentials don't linger after you revoke consent. WINDOWS NOTE: Chrome/Edge/Brave on Windows holds an exclusive lock on cookie and login databases while the browser is open. Hermes can't copy them while it's running. fix: fully quit the browser (including background/tray instances) before starting a Hermes browser session. or set: browser: real_profile_autoclose: true Hermes will offer to close the browser for you. it asks first. never closes automatically. only on your explicit approval. macOS and Linux can copy the profile while the browser is running. no issue. SUPPORTED BROWSERS: Chrome, Edge, Brave, Chromium. whichever is your OS default. a non-Chromium default (Firefox) = clear error message. no guessing. WORKS WITH ANY BACKEND: local browsing: automatic once the toggle is on. cloud backend (Browserbase, Browser Use): the agent can still open a real-profile local session on demand via browser_exec with the local argument. the cloud backend keeps serving everything else. THE DIFFERENCE: without real profile: "check my dashboard" → agent opens the site → login page → stuck. you paste credentials or set up OAuth. with real profile: "check my dashboard" → agent opens the site → already signed in → done.

• 
  Mr.Goober (@RealMrGoober) reported 15 minutes ago

  From a new thing perspective there really isn't a plugin that lets you edit huge images like this they all have limits, it takes a bit of time to apply on a huge image, but its good enough to use, at least for my use case. I'll fix it up a bit and then release it on github

• 
  💯James Bohan-Pitt💯🇬🇧🇺🇸 (@JamesBohanPitt) reported 16 minutes ago

  @jasonfreedman You have nailed it. As a small business owner. I don’t want to transform how marketing gets done, I want someone else to take it off my plate entirely. It’s the same with many tasks on the list. Trouble is, no one is interested in doing the actual work. That doesn’t scale and get the exit dollars. They just want to transform how the work is completed by others in hope of being purchased by a big player or scaling up to dominate a sector. I feel the same about agents. Every day a new Agent or Bot tweet comes out. Do these steps, make your work life betterer! I don’t have the time for this. Setting up Claude is like trying to work with GitHub as a non-developer. If you think your Bot/Agent is so good, why not put your money where your mouth is as prove it. Until companies are really willing to take things of the plates of business owners, I’m not seeing much really change for the majority of tired business owners.

• 
  Alejandro Milián (@alejmilian) reported 17 minutes ago

  Your GitHub activity is a terrible way to judge how good a developer is. A lot of great developers spend all day writing private code, solving boring production problems, reviewing PRs and helping teams ship. A green contribution graph doesn’t tell you much.

• 
  Ouattara Romuald (@ouattararomuald) reported 17 minutes ago

  @github Stacked PRs is so slow. It has been merging for more than 4 minutes before telling me I can't merge. Why merging takes 4 minutes?

• 
  johnathan (@SimonCapath) reported 19 minutes ago

  @Jxke72 @MarvelcoCode @ImpulsumFUT Hes playing the victim card here, yeah the community needs to be more patient, however what do you expect when you dont even help people with the bugs and delete issues on github

• 
  orangesurf (@OrangeSurfBTC) reported 20 minutes ago

  In general I wouldn't update to unreproducible binaries as an emergency fix - a project maintainer's github/signing accounts could be compromised and you end up installing malware. How many tokens does it take to identify the vulnerability by decompiling the binaries?

• 
  Emma De Silva (@EmmaDSCodes) reported 20 minutes ago

  The irony that making a PR to fix a race condition in my app caused an issue in GitHub due to a race condition

• 
  Bianca ₿ (@arapserkan2) reported 21 minutes ago

  @panda_ash19 Even if Tangem shut down, the mobile app wouldn’t be the thing holding your funds. The keys stay on your Tangem card, and transactions don’t depend on Tangem’s servers. The app is open-source and can still be downloaded from GitHub

• 
  Daniel (@itsdanielpurgal) reported 22 minutes ago

  Nvidia in talks to acquire Hugging Face at $12.9B at ~80x annualized revenue of $150M. Hugging Face is essentially GitHub for AI. Is this an attempt to lock down the open-source developer ecosystem?

• 
  Manny (🧱,🚀) (@codingwithmanny) reported 23 minutes ago

  So when you pay for GitHub and it goes down multiple times, does that mean we should get a rebate?

• 
  Gabriel Rubens (@gabrielrubenss) reported 26 minutes ago

  VPS deploy via GitHub (7/8): I copied that check to my other apps, and Farlist, my slow journal for long term goals, answered on the first run: every deploy had failed since May 25. Ten weeks of merged work never reached the server, and the site returned 200 the whole time.

• 
  Millsy.dev (@Millsydev) reported 27 minutes ago

  @TimSweeneyEpic @fortniteonlinux Well your Linux support has been terrible and very lacking If you had the API I can access to create my own for everyone to use and put it on GitHub I would. I would make it RUST /REACT Tauri2

• 
  pdp (@pdp) reported 30 minutes ago

  @markfenner What are the issues in GitHub or Linear if not prompts? You can type them in a centralised database or you can type them in the chat box. It is the same. Also the factory pattern does not apply for iterative tasks such as when developing apps from feedback and input.

• 
  Joshua Stanton (@ShiftingPathway) reported 33 minutes ago

  @kilocode @Zai_org Why is it impossible to paste into your Kilo Code CLI prompt field. This is absurdly annoying and intermittent. Its been an issue in your github issues repeatedly for months. I don't understand why you would focus on a new app rather than making basic functionality work

• 
  Ahmad Hajjar - ***-quick.dev (@ashajjar85) reported 45 minutes ago

  GitHub gave orgs a way to cap how many PRs outsiders can keep open. But maybe the problem isn’t only what enters the queue. Maybe it’s what nobody is touching ... Maybe Github should add a cap on idle PRs instead. Until they do you can use GitQuick ;)

• 
  Andrés Matte (@andresmatte) reported 47 minutes ago

  The Kapso Agent has “modes" Modes are like big agent skills + tools. (borrowed the idea from the PostHog Agent) The agent can decide when to switch to a specific mode based on the task. It works really well! And now you can create your own Kapso Agent modes. Example: If you want to create a “Support Assistant,” you can add: - Add a custom prompt - Connect an MCP server to provide tools - And even connect GitHub repos containing relevant knowledge or code. Then, in the Inbox, you can ask the Kapso Agent for help with any support task, and it will automatically switch to your Support Assistant mode.

• 
  Bilal (@BilalBudhani) reported 47 minutes ago

  Github down again?

• 
  0xdoppo (@0xdoppo) reported 51 minutes ago

  @solomonstre GitHub Actions schedules only get you down to about 5 minute intervals. Cron runs whenever you tell it to. Sometimes the local job isn't pretending to be CI, it just needs to run more often than GitHub allows.

• 
  Udoh Jeremiah (@udohjeremiah_) reported 55 minutes ago

  Your GitHub is full of beginnings. That's the problem.

• 
  OSS | Let's Connect (@ossbuildconnect) reported 56 minutes ago

  GitHub’s recent 7-hour outage is a useful engineering reminder: Critical workflows need fallback plans. Keep local copies, document release procedures, avoid depending on one service for every operation, and design systems assuming external platforms can fail. #DevOps #GitHub

• 
  佐藤ひつじ@業務系システムエンジニア (@_hitsuji_sato) reported 58 minutes ago

  Update: Recovery reports have been posted on GitHub Issue #5365. According to the reports: - First HTTP 400 errors were observed around 2026-08-26 18:08 UTC - One JP seller account started returning HTTP 200 around 2026-08-27 04:10 UTC - All three seller accounts managed by the reporter were returning HTTP 200 by 2026-08-27 05:43 UTC There has also been a recovery report from another seller account. In the same issue thread, it was suggested that recovery may have been rolled out on a per-seller-account basis rather than all at once. The reporters noted that no client-side changes were made before the issue recovered. At this time, no official explanation or details regarding the root cause have been provided by Amazon. I'll continue monitoring the situation and will share any further updates if new information becomes available.

• 
  Invest Alpha Pro (@InvestAlphaPro) reported 59 minutes ago

  🚨 Nvidia is buying Hugging Face. $12.9B for the GitHub of open source AI, months after they turned Nvidia down at $7B. The breakdown 👇 •Price: $12.9B, one of Nvidia’s largest deals ever. •Rejected offer: $500M at $7B in late 2025. •Multiple: 86x annual revenue. •The logic: locks in the open source developer funnel as OpenAI, Google, Amazon and Anthropic build their own chips. •Timing: landed hours after a $96B quarter. Long $NVDA. NFA

• 
  AminTechs (@AminTechs) reported 60 minutes ago

  @gopikl @bot A GitHub issue is not a Claude Routine trigger. Docs: GitHub triggers subscribe to pull_request and release only. issues.opened is not on the list. You also need the Claude GitHub App installed — `/web-setup` clones, it does not enable webhooks.