GitHub 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:

• 
  François Leblanc (@leblanc_fg) reported 4 minutes ago

  I now have a local "main loop" worker, not tied to a specific provider. I end up having a hundred tiny little "personal life assistant" triggers a day that this thing can process! Write + triage github issues, first draft reply for email, sweep tasks for the day, etc.

• 
  DFIR Radar (@DFIR_Radar) reported 5 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

• 
  Lloyd Ebnchenge (@Lloyd56ebone) reported 6 minutes ago

  @cursor_ai Wow, is GitHub really in trouble? I can see this being useful considering when I start using cursor and GitHub for the first time I had a stroke trying to understand what GitHub was for, keep it up.

• 
  YanXbt (@IBuzovskyi) reported 12 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.

• 
  kosi (@kosiasuzu) reported 12 minutes ago

  @juliarturc Use GitHub issues

• 
  Evis Drenova (@evisdrenova) reported 13 minutes ago

  @sbilstein @SlackHQ yeah to your earlier point i think it depends at what layer you want to attack it i.e. rust builds are slow, caching can help but github actions is trash for it, but blacksmith isn't bad, is there a generic solution you can use that *just works* on any CI? alternatively, go after the actual docker execution layer but not clear to me how much of a bottleneck that actually is vs. language specific idiosyncrasies buildkit is pretty optimized from what i've heard but i generally agree with make it fast and stupidly easy to use!

• 
  Smakosh (@smakosh) reported 13 minutes ago

  This is why GitHub keeps going down

• 
  idan (@eddiearc6) reported 17 minutes ago

  @lai_jia_wei @linear github issue呢？

• 
  johnathan (@SimonCapath) reported 18 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

• 
  AminTechs (@AminTechs) reported 20 minutes ago

  @oscarlehuu Origin is Pro/Teams/Enterprise only — not on the free plan. It shipped 17 Aug as early beta. Cursor's own changelog still treats GitHub as source of truth for anything you started there; Origin is the mirror. Keep a GitHub remote until you can clone without a Cursor login.

• 
  Spocky Balboa (@spockybalboa) reported 22 minutes ago

  @thdxr Looks fun but Opencode has long standing bugs that just aren’t being addressed such as the API and the JavaScript SDK return 400 when a request is made specifying JSON as the return type. It’s been submitted on GitHub since May with no fix in sight.

• 
  Aurora Skye (@AuroraSkye21259) reported 23 minutes ago

  @koltregaskes @JamesZmSun @ChatGPT When you sign into, say, github inside work’s cloud browser, github can issue new session cookies to that cloud browser, those are not copied from your local browser.

• 
  Max Vmr (@vmrmax) reported 26 minutes ago

  A GITHUB REPO WITH 57,000 STARS IS SITTING ON 1.51 BILLION FREE AI TOKENS A MONTH. AT $3 PER MILLION, THAT IS $4,500 YOU ARE CURRENTLY PAYING SOMEBODY It is called OmniRoute. MIT licensed. One command. Right now your tool is wired to exactly one provider. One key, one price on every single call, and the moment they rate-limit you or go down, you stop working. Before: Cursor → OpenAI → their price, every call, every time After: Cursor → OmniRoute → 350 providers → whichever one is free and up Three things you get. You stop stopping. 19 routing strategies with automatic failover. Provider goes down, the request moves to another one. You get an answer instead of an error. You pay less. It ships a catalog of 90+ providers with free tiers and uses those first. On top of that it compresses what you send, which the project puts at 15% to 95% fewer tokens billed. You rewrite nothing. No code changes, no new prompts. You change one address. npm i -g omniroute Server boots on localhost:20128. Point your tool at [ and set the model to "auto". Claude Code, Cursor, Cline and Copilot all work as they are. Keys stay on your machine, encrypted. Two honest notes. It does not make models smarter. Answer quality is whatever the model that picked up the call gives you. And it is useless if your AI work is a chat window in a browser. This is for people whose tools call an API with a key. If that is not you, skip it. The free-token and compression numbers come from the project's own docs, not an independent benchmark. Run it for a week on your real usage before you quote them. Your AI bill is usually not a model problem. It is a routing problem.

• 
  capad / aadarsh (@aadarsh_io) reported 29 minutes ago

  @shownotover Btw one intresting thing I did to improve the SuperGrok limit I created a Skill for Grok called "/cheap-scout" In-short: - I had a catalog of "free" agents available through OpenCode Zen, Nous, OpenRouter, Free GMI/MinMax (until Sept 6) - Default model: Grok 4.6 (low) - What skill asked: The start of skill stated the agent to take of quick look at the local available catalogue of "free" agntes. And a very short and cheap look at the internet on performance of each model, benchmarks (based on work) and security (which models *may train on your data) - This was done once* the "/cheap-scout" skill was invoked. - Assign them work + effort level (spoiler: Grok defaulted to Medium for most free model, and very very surprisingly they did good). - Before assigning work to them Grok also did a security audit based on given task. For e.g. muse-spark-1.2-contributor was rejected from tasks that requires touching sensetive files (cuz meta being meta but a free model on zen) - PR quality was defined by Grok and cheap agents delivered Result? - High quality output with 80% Minor follow ups from CodeRabbit (ok most of those CodeRabbit was being code rabbit in those I generally considered/added only 20-30% of follow-ups and the follow up fixes ~ mostly docs/tests *not a code quality issues were done by those sub-agents it self) - I got to know about agents I'd have never tried in my life. Laguna, Hy3, Stepfun 😭 (wtf is stepfun) and more! - Grok also took-over the changes on it own when the review for agents seemed to more token heavy than implementation itself. - 18% Weekend Usage (based SuperGrok) for umm.. 4-6 hrs of non-stop programming ~ I'm not making those numbers up and I'm not tryna promote/sell my skill or anything. - Went upto 24% in those hours too cuz I was also make PR Reviews and small bug fixes through Grok App on my phone by giving it the GitHub FGT. And? Minor follow-ups. And product discussion itself. Also the "/cheap-scout" audit was put in another /model-preference.md. Grok constantly eavulated feedbacks, model failures and auto sub-agents re-routes. The original "/cheap-scout" skill was never edited. I found out if you stir these cheap models properly with proper instructions w short breakdown of tasks, they will perform and deliver. If you want I can refine and share this skill. I've been testing it for 3 days now. And I'm happy ngl.

• 
  Ricci Research (@ricci_nov) reported 31 minutes ago

  @github @openclaw @steipete Stars are free to give and reviews are expensive to do — that asymmetry is the whole maintainer problem. Fastest-growing repo in history means the issue queue scaled with adoption while the review capacity stayed at one person's evenings.