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:

• 
  Juan C. Andreu 🦇🔊 (@andreujuanc) reported 4 minutes ago

  @github App is trash fix it

• 
  Dan Liu (@danliu) reported 4 minutes ago

  @Scobleizer yea large corporation issues... but google / apple at least seem to be making some reasonable progress? and how did github get so bad? i feel like it's really perfectly positioned given the strongest usecase for ai today is coding. but it basically got *worse*...

• 
  John Morlan (@JohnSmarterRisk) reported 5 minutes ago

  @github Your platfrom is amazing. Your sign up process is terrible, specifically the re-captcha BS is the most overboard security thing I have ever seen. Do better.

• 
  DFIR Lab (@DFIR_Lab) reported 7 minutes ago

  🦅 Tool Tuesday: Hayabusa — Fast Windows Event Log Analysis for Threat Hunters When you're knee-deep in a Windows compromise and staring at gigabytes of EVTX files, speed matters. Hayabusa is a Rust-based event log analyzer that rips through Windows event logs at scale, applying Sigma-compatible detection rules to surface threats fast. Built by Yamato Security, it ships with 4000+ built-in detection rules covering everything from credential dumping to lateral movement. It scans EVTX files offline, generates a consolidated timeline of security-relevant events, and outputs to CSV, JSON, or HTML — whatever fits your workflow. Real-world use case: You've pulled EVTX logs from 50 endpoints during an active IR engagement. Instead of manually parsing Security.evtx looking for 4624/4625 patterns, you point Hayabusa at the entire dataset. Within minutes, you have a sorted timeline flagging Mimikatz execution, suspicious PowerShell, and abnormal logon patterns — all color-coded by severity. Why it matters: Traditional EVTX analysis is slow. Hayabusa's Rust core makes it blazing fast, and Sigma rule compatibility means your existing detection content works out of the box. It's offline-capable, so you can analyze logs on an isolated IR laptop without network dependencies. Alternatives: DeepBlueCLI (PowerShell-based, lighter but slower), EvtxECmd (Eric Zimmerman's tool, great for parsing but less detection-focused), and Chainsaw (another Rust option with Sigma support). Get it: hXXps://github[.]com/Yamato-Security/hayabusa #DFIRTools #IncidentResponse

• 
  Ming (@tslaming) reported 7 minutes ago

  @Squirrel1980021 That is usually the biggest catch with custom solutions, as proprietary protocols often fragment the industry and lock people in. However, the great news here is that Tesla actually open-sourced it to prevent exactly that. They released the entire specification as TTPoE on GitHub during HotChips 2024 and even joined the Ultra Ethernet Consortium. So instead of keeping it locked down as a proprietary secret, they are actively working to make it an open standard that the entire high-performance computing ecosystem can use and build upon.

• 
  Karan Lokchandani (@karaninthewire) reported 8 minutes ago

  it was not directly relevant to any of the roles I applied for but I was a member of the official swiftlang github org and got to weigh in on issues, write RFCs and review process there + a couple dozen merged PRs across WASM, k8s and swift projects. I suppose their openclaw looked me up well on github.

• 
  Ryan Delaney (@_rrdelaney) reported 21 minutes ago

  @jhasanofficial @karrisaarinen @linear Coding sessions run in a secure sandbox with no access to secrets or credentials, and limited GitHub access. Additionally, for externally created issues we lock down the sandbox's network access.

• 
  WallStreetAIs (@WallStreetAIs) reported 22 minutes ago

  Hermes Agent automation blueprints are not just cron jobs with a nicer name. TRUSTTT. They are fully built workflows you can copy, customize, and run right away. Nightly GitHub issue triage that sends a digest to Telegram Automatic PR code reviews posted directly on the pull request CI failure analysis that explains what broke and how to fix it Stripe payment monitoring that flags disputes as urgent Everything ships ready to use. You are not building automations anymore. You are just turning them on.

• 
  泽林 🌫 (@zelin1107) reported 24 minutes ago

  1/ GitHub Actions not pinned to SHA Using @v6 instead of commit hash = supply chain attack risk. Fix: uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 #GitHub #Security

• 
  Mike Greiling (@mikegreiling) reported 25 minutes ago

  @MattHartman @github @claudeai somebody recommended it in some discord channel I'm a part of, I honestly don't remember which one. I've had it installed and have been using it for several weeks now. It's great! I just decided today to click "check for updates" button in the menu and it gave me an obtuse error

• 
  Vapin Gamers 👑 - Dev, Streamer, Gamer (@VapinGamers) reported 27 minutes ago

  @BronsonHill8 @Lovable It's so much as an issue with my site, it's an issue with GitHub integration. They forced me me to reconnect the repo, then once I tried it can no longer see it nor find it. I can reconnect and have it create a new repo. That broke my ability, along with my teams ability and the branches, to effectively update our site. The fix is in the repo that lovable is no longer pointing to.

• 
  Moondalorian (@moondaloriansol) reported 30 minutes ago

  @ziwenxu_ can you upload to a web server so we can all play, most normies dont know how to navigate github - if we can all easily engage that would be unreal build it out to multiplayer in the long run type ****. would be insane

• 
  SkinAlyze (@SkinAlyze) reported 34 minutes ago

  @cyberbebebe Hey i tried reaching out to you in DM but it didnt work, Could you make an issue in the github repo of the extension and report it there or report it in the discord?

• 
  Techjunkie Aman (@Techjunkie_Aman) reported 34 minutes ago

  Over 400 Arch Linux AUR packages were just compromised. And this is a reminder that open source doesn't automatically mean secure. Attackers reportedly hijacked package maintenance and injected malware capable of: • Stealing GitHub credentials • Extracting SSH keys • Harvesting browser cookies • Accessing Slack, Discord & Teams data • Collecting VPN credentials • Deploying an eBPF rootkit The scary part? Many developers install AUR packages without reviewing every PKGBUILD. Affected systems may have exposed: • GitHub tokens • npm credentials • Docker & Podman secrets • HashiCorp Vault tokens • SSH artifacts • Browser session data If you're running Arch or an Arch-based distro and recently installed AUR packages: • Audit installed packages • Check for indicators of compromise • Rotate credentials immediately • Consider a clean reinstall if rootkit activity is suspected This isn't an Arch Linux problem. It's a software supply chain problem. One compromised package can put thousands of developer machines at risk. Do you review PKGBUILDs before installing AUR packages, or do you trust the community by default?

• 
  Waldek Mastykarz (@waldekm) reported 35 minutes ago

  You're building a tool that calls the GitHub API — repository data, user profiles, issues, pull requests. GitHub's API is everywhere. It also has rate limits, and during development you barely touch them since everything works. Then your tool gets popular, runs in CI, or 5 team members fire it simultaneously, and you get 403 Forbidden because you never tested this path. Dev Proxy has a preset that simulates GitHub's rate limiting locally. Grab it and start testing: devproxy The preset adds realistic rate limit headers to every response: - `X-RateLimit-Limit`: total allocation - `X-RateLimit-Remaining`: what's left - `X-RateLimit-Reset`: when it resets Exceed the limit and you get 403 with a proper error response, just like the real API. With the preset you can build proper handling: - Check remaining requests before making calls - Add backoff when limits are low - Show users when they're approaching limits - Queue requests when throttled One command, real rate limiting behavior, no waiting for production to surprise you. How do you handle GitHub API rate limits in your tools?