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:

• 
  ∆LΞX∆NDΞR D∆VIS (@_AlexanderDavis) reported 3 minutes ago

  @egavrilenko11 @bot I had to update my fine grain token for GitHub and now when it tries to authenticate the plugin, I'm getting the error: GitHub didn't provide a sign-in link My bot said: Known host bug, not you. The GitHub Authenticate button tries OAuth GitHub does not support. Checking whether a PAT on the plugin page is the working path. That's a Grok Bot host bug, still open: cursor/plugins#251. GitHub's connector is PAT-only. The Authenticate button tries OAuth GitHub does not support, so you get "didn't provide a sign-in link." Don't keep hitting it. But it worked before I updated my fine grain token...

• 
  Lummox (@Lummox_eth) reported 4 minutes ago

  My own built Grok Bot turned $1,000 into $5,300 for last 17 hours. Now the project behind it is sitting around $25K market cap. We already pushed past $60K once and gonna hit $200k soon The bot is still running. The utility is almost ready. GitHub is live. Dev tokens are burned. I’m still buying. Nothing about the actual project changed because the chart went down. At $20K MC, this is the entry I personally like far more than chasing the first move. The target hasn’t changed either. $100K+ is where I want to take this next. $LUM is just getting started.

• 
  🍔Kangdalf👑 (@WhopperWizard) reported 5 minutes ago

  @cachesaur > claude, get your changes into github what's the problem?

• 
  Wlad (@dawnhell_) reported 8 minutes ago

  @brekfuz q: that's a github issue or you patched it locally??

• 
  Speen Bhai (@Speenbhai) reported 8 minutes ago

  @johnternus Hi John. Congrats Let us see what new you bring with you. Affordability and intelligence. You have source code or an AI and can get it from GitHub. Why not turn 234 million iPhones to a massive distributed server infrastructure with zero power consumption

• 
  Suryansh Tiwari (@Suryanshti777) reported 10 minutes ago

  6. The Dependency Incident Check Grok has native real-time search across X. Breakage gets posted there hours before the GitHub issue is triaged. No other coding model has that feed. "You are a build engineer whose first move on a broken pipeline is to work out whether it broke for everyone or only for me. Search X and the web, last 14 days. Check: - Is anyone else reporting this failure with this package and version, and when did the reports start - The exact release that changed behaviour, and the changelog line that admits it - Whether maintainers have acknowledged it and what they recommended - The pin or patch people settled on, with the tradeoff of each - Whether this is my problem instead, and what evidence points that way Give me the verdict in the first line: their bug or mine. Then the evidence, newest first, with links. My failure: [PASTE THE ERROR, THE PACKAGE AND VERSION, AND WHAT CHANGED ON YOUR SIDE RECENTLY]"

• 
  Shawn Yeager (@shawnyeager) reported 11 minutes ago

  My @bot keeps reaching for the browser and `gh` instead of using the GitHub plugin. Known problem?

• 
  Chris (@c_hri_s) reported 11 minutes ago

  @Anime0t4ku Sorry - was an idiot and wasn't signed in. Instead of something useful github just says 'opening issues is restricted on this repository'

• 
  gatorade (@kadetXx) reported 11 minutes ago

  because it’s not worth it for the most part. most software failure or bug incidents don’t have any physical victims. at most company loses some money or the issues are almost instantly fixed, no lawsuits, no so much to answer to the state for if your software has a bug or fails to work as expected for a brief period (think, multiple downtimes from the big five so far, even github too, who died? exactly) and in the industries where bad code fan have physical consequences, they actually do test software like hardware engineers & physicists (i hope)

• 
  Jayesh Betala (@jbetala7) reported 13 minutes ago

  @github Exactly how issue issue comments should handle local media files

• 
  Yeemio (@yeemio) reported 14 minutes ago

  owlrunkit is on github now. public corresponding source for the npm package. issues go here.

• 
  阮添福-ThiênPhúc (@vietroadie) reported 17 minutes ago

  Feature request for @TradingView @TrendSpider @Schwab (ThinkOrSwim) engineering teams: Please add GitHub-native CI/CD for custom indicators. Connect a repo → validate on push → deploy approved scripts to my workspace → full version history + rollback. 1/ The Problem I maintain the same level set across ThinkScript, Pine, and JS. One level change = 3 manual copy/pastes into 3 browser editors.Result: drift between platforms, stale timestamps, and levels that silently disagree mid-session. No audit trail of what changed or when. 2/ Core ask — repo connection • OAuth GitHub App install, scoped to selected repos • Map a file path → a specific study slot (e.g. ES Levels/ES_LEVELS.pine → "ES Levels") • Branch selection (deploy from main, preview from a branch) • Config in-repo, e.g. .tradingview.yml / .trendspider.yml 3/ Core ask — validation • On push/PR: compile + lint the script server-side • Return errors as GitHub check runs with file + line numbers • Block merge on compile failure • Optional: run a backtest or smoke-render and post results as a PR comment 4/ Core ask — deploy • Auto-deploy on merge, or manual "promote" button • Atomic: study updates or fails cleanly, never half-applied • Deploy to draft/private first, publish separately • Preserve user-set inputs across deploys where param names are unchanged 5/ Core ask — versioning & safety • Every deploy tagged with commit SHA, author, timestamp • Version list in the UI with diff view • One-click rollback to any prior commit • Dry-run mode • Deploy log / webhook on success + failure 6/ Minimum viable alternative If full CI/CD is too big, just ship a documented REST API: GET/PUT /studies/{id}/sourcewith token auth + rate limits. We'll build the GitHub Action ourselves. That single endpoint unblocks the entire workflow. 7/ Why it matters Scripts are code. Code belongs in version control with review, CI, and rollback. This is table stakes in every other dev ecosystem — and it directly reduces the risk of a bad indicator edit going live during market hours. Who else needs this? 🙋

• 
  Coder Junkie (@CoderJunkie) reported 18 minutes ago

  BelNet Android v1.4.1 now has a public shipping checkpoint. GitHub evidence: released Sep 1 verified commit d23f155 four downloadable assets Android API level 36 revamped design latency and performance fixes that is more meaningful than a repository “updated” label. a tag identifies the version. artifacts give users something to install. but “fixed latency issues” still needs a measurement surface: median connection time p95 latency packet loss failure rate region and device breakdown release notes tell us what changed. benchmarks tell us how much it changed. BelNet shipped. now let the numbers login. @BeldexCoin #Beldex #BelNet

• 
  small_j (@a_small_j) reported 23 minutes ago

  @smalldocs_org recently crossed 200 stars on GitHub and 20 forks. SmallDocs is the first open source project I've managed. Handling other people's pull requests is not easy (and I need to improve). They implement features you're not considering and fix bugs you didn't know you had. Extremely useful, but if you're squeezed for time and trying to develop core functionality, it's hard to manage both things well.

• 
  Jeremiah K (@neolaj) reported 24 minutes ago

  @TiborAntal Gradually figuring out how to scale coding agents. Started with 1, manually handling all the ***/GitHub work. Moved to 3 because I had more ideas than one agent could keep up with. That’s when the real problems started: squashing, merging, branch drift, conflicts. I ended up rebuilding the workflow around deterministic *** logic, worktrees, ephemeral branches, and syncing with the integration branch before changes begin. Now I’m running 6: • 1 orchestrator (Fable or Opus) • 4 coding agents • 1 integration agent reviewing and merging PRs Building the process around them was the hard part. Right now im just doing a couple of PRs (using ORCA on windows on my home computer)