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:

• 
  André (@andr3barroso) reported 6 seconds ago

  Everyone is saying ChatGPT Plus isn’t worth it because you burn through the Codex limits too fast. I think they’re looking at Plus the wrong way. Most of what I do happens in Chat mode, not Codex or Work. From my iPhone, in a normal Chat, I can: • Connect to GitHub, PostHog and other tools • Research anything on the web • Review code and PRs • Work through problems in my projects • Take a photo and instantly translate or understand it • Talk naturally using probably the best dictation I’ve used And this doesn’t consume my Codex/Work allowance. Then, when I actually need an agent to work on a repo, I switch to Codex or Work and use that allowance. I can even connect my iPhone directly to my Linux VPS and keep working without opening my MacBook. For me, ChatGPT Plus isn’t just a Codex subscription. It’s an AI assistant

• 
  amal (@amal_ytics) reported 1 minute ago

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

• 
  Navneet (@navneet_rabdiya) reported 4 minutes ago

  @JeremyCMorgan This is the pattern. Most cascading failures aren't the initial problem - they're clients retrying without jitter or backoff. Recovery becomes reattack. The fix is boring: exponential backoff + per-client retry budgets. GitHub probably has this now.

• 
  Daniel (@itsdanielpurgal) reported 7 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?

• 
  ꃅꀎ$꓄꒒ꍟ ꓄ꂦꀘꍟꈤ (@Hustle_Token_Bp) reported 8 minutes ago

  Try to fix the issue asap! @github

• 
  Gabriel Rubens (@gabrielrubenss) reported 11 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.

• 
  Daniel San (@dani_avila7) reported 11 minutes ago

  Can I submit a PR to GitHub to try to fix GitHub? I wish parts of it were open source. I have so many ideas to contribute

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

• 
  Павло (@VZaginay) reported 16 minutes ago

  @Rinnegatamante @Waynaldo_T hey! I have the same issue, like i created same folders like the github repo has mentioned, then pasted the bin file, but nothing other than VitaGL and #6440cf0

• 
  Devon Govett (@devongovett) reported 17 minutes ago

  @rafalfilipek can you open a GitHub issue for this? seems fine to add that.

• 
  AminTechs (@AminTechs) reported 19 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.

• 
  The DevOps Guy (@justdevopsguy) reported 21 minutes ago

  honest question: why are people paying @linear when they could just use @github issues and projects that already map nicely to their code and PRs?

• 
  Muhammad Ahmed (@ahmed_ah206) reported 22 minutes ago

  @BRuteLogic created an issue on github with title : "False positive: curl -X OPTIONS treated as bypass on 403 URLs " with details and screenshot

• 
  François Leblanc (@leblanc_fg) reported 31 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.

• 
  0xdoppo (@0xdoppo) reported 31 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.