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:

• 
  Paruchh (@theparuchh) reported 11 minutes ago

  Testing one trading hypothesis at a quant desk costs about $87,500 in salary time 139,000 people are running the same thing for free and almost nobody talks about it TradingAgents. A multi-agent LLM framework that simulates an entire trading firm. Analysts, researchers, risk desk. 80k+ stars on GitHub ai-hedge-fund by virattt. 14 agents modeled on named legendary investors, arguing every position against each other. 59k+ stars Both open source. Both free. Both runnable tonight Jane Street pays 3,500 people to run this loop. The loop is a *** clone now One warning before you go. Six frontier models got $10,000 each in Alpha Arena with real capital. Four finished down, one at minus 62%. The framework is free. The edge is not included Clone it. Break it. Then post your numbers, not your backtest

• 
  Ben Palmer (@ben_palmer1) reported 12 minutes ago

  Raised it as a issue on the github repo months back - but no improvements yet.

• 
  Emanuele Di Pietro (@emanueledpt) reported 13 minutes ago

  New Synara version is out Here's all the things that we done in less than 2 days: Made Create PR perform the complete commit, push, and PR-creation flow Made files editable and saveable directly from Explorer Restored automatic branch creation and attachment for worktree tasks Added support for forking imported Codex task histories Streamed detailed worktree setup progress with clearer stages Added Cancel and Work Locally actions during worktree creation Made the composer float over the transcript with a frosted-glass appearance Added a visual theme picker and simplified keyboard-shortcut settings Added a setting for choosing and persisting the desktop app icon Improved composer glass on macOS and hid transcript text behind its footer Improved startup performance and handling of events arriving late Reduced composer lag in long, actively streaming tasks Reduced runtime polling and unnecessary task-detail subscriptions Fixed stale *** refreshes, stuck Pull controls, and incorrect merged-PR badges Improved recognition of a task’s current *** branch and associated PR Updated sidebar branch labels when *** changes occur during a turn Used the configured ***-writing model to generate worktree branch names Made Kilo turn submission asynchronous so requests do not block Fixed Claude and Codex OAuth token storage, refresh, and expiration handling Cached provider usage server-side and loaded usage through one batch request Fixed OpenCode and Antigravity provider behavior on Windows Ensured Antigravity turns finish correctly after cancellation or a clean stop Simplified the Antigravity cancellation fix while preserving correct turn settlement Displayed live Antigravity tool activity in the transcript Fixed Grok ACP authentication and permission handling Restored OpenCode host policies when resuming a session Retried temporary Kilo credential failures during provider startup Recovered automatically from temporary Grok session-storage startup failures Fixed which providers can be selected when handing off a task Restored AskUserQuestion responses when the context window is full Prevented failed outbound HTTP requests from crashing the server Prevented repeated *** fetch attempts when an upstream remote is unavailable Serialized *** refreshes and improved provider-capacity retry behavior Scoped orchestration replay correctly and prevented duplicate runtime events Prevented the send spinner from remaining stuck after a lost stream acknowledgement Prevented transcript rows from visually overlapping during streaming Kept the working indicator visible while the first provider turn initializes Displayed “Loading” before a turn starts and “Thinking” once active Ensured expanded images appear above the embedded browser layer Polished the Create PR dialog and project-picker experience Improved file-preview breadcrumbs, copy actions, and header controls Replaced inline task-error banners with red error toasts Added recent Synara releases to the sidebar help menu Displayed PR additions in green and deletions in red Added a setting to enable or disable colored PR diff statistics Made toast notifications disappear after ten seconds by default Prevented Expo and Metro title detection from hanging or failing unsafely Fixed terminal activity polling on Windows Repaired malformed GitHub Markdown tables before rendering them Improved side-chat behavior and keyboard-shortcut workflows Automatically focused the project-picker search field when opened Added a shortcut for copying the active task ID Corrected the visual alignment of the composer’s send arrow Matched the Studio sidebar title size with the Synara interface Formatted files that had previously been merged without oxfmt

• 
  Chanchal (@chanchalvdev) reported 14 minutes ago

  3. Devin ran a C2 binary after a poisoned GitHub Issue gave it hidden instructions. It even granted itself execute permission when blocked. No zero-day needed — just one crafted issue.

• 
  snowy_smile (@snowy_smile_) reported 17 minutes ago

  Since May I've been in a build-and-share spiral. Started slow, got consistent in June, and by July things had gotten a little out of hand — too many projects, too many experiments, open-sourcing whatever seemed useful, sending PRs whenever I found something worth fixing. Since June 1st alone I've somehow created around 80 repos. I even made a fresh GitHub account for all of this — a completely anonymous alt. No real name, no résumé, just code and an increasingly suspicious amount of green. It's now sitting at 1,681 contributions, 85 merged PRs across 37 external projects, plus a mildly unreasonable pile of my own stuff. And somehow this random anonymous account has brought in a few surprisingly nice offers and invitations. Apparently "mysterious person on GitHub who keeps building things" is a viable professional identity now 😳 The root of this goes back to something that's been nagging me since 2023: AI itself never really scared me. What scared me was people using AI to do bad things. It felt obvious the real fault line wasn't going to be "humans vs. AI," it was going to be people who know how to think, build, judge, and collaborate with these tools vs. people who don't — and I'd rather be on the side that's harder to weaponize against. So I figured I'd rather learn how to use them properly. And open source has actually been interesting ground for that, in kind of an ironic way — a lot of repos and maintainers explicitly reject AI-assisted contributions. Which means, for now, there's still a place where doing it the old-fashioned way — the tests, the review, the "explain this in your own words" — actually counts for something. But I don't think that holds much longer. Less a permanent human edge, more a countdown. A few years ago, Go AIs became teachers for human players. Coding agents have felt a little like that to me for a while now, not just recently — they help me learn, but they also make me think harder about what my part of the job should be. There's a part of me that still misses being the guy who was just good at algorithms — greedy strategies, graph theory, the kind of problem where you stare at it for a few minutes and then the trick clicks. That used to be my thing. Now the realistic move isn't to keep being that guy — it's to become one of the people who's actually good at using AI. So for now: keep learning, building, trying to make whatever might be useful — especially while I still have a few human-only features AI hasn't deprecated yet 🥹

• 
  JT Koffenberger (@DMVG_JTK) reported 17 minutes ago

  @HermesShield We spent 20 years locking down human privileged access. Then we handed write tokens to agents that can be talked into almost anything via a GitHub issue. The fix isn’t “better prompts.” It’s treating every agent as a privileged identity with least privilege, continuous monitoring, and a human still owning the blast radius. Otherwise we’re just accelerating the next incident.

• 
  Oliver Servín (@oliverservinX) reported 17 minutes ago

  I've built my own blog more times than I can remember. Every time it went the same way. I'd be happy with it, publish a few posts, then drift away. I kept renewing the domain, but eventually I'd delete the VPS behind it. The address stayed alive, pointing at nothing. And I'm fine with that. An old blog is a snapshot of an older me: the things I cared about, the tools I used, the writer I was. When it doesn't fit anymore, letting it expire feels more honest than keeping a neglected archive. What bugged me was never the abandoning. It was that every time I had a new post ready, the blog was gone. I'd have to rebuild one from scratch before I could put a single word out. So this time, with a finished draft and nowhere to put it, I thought about Bearblog, a platform built on the idea that a blog needs almost no CSS and almost no layout: a header, a list of posts, a page for each. That's what I wanted. And I figured an AI coding agent should make rebuilding it almost free. So I pointed OpenCode at it and asked it to build me one. I started from a fresh `laravel new`, the same way I start any project. What I didn't expect was that I'd end up taking more out than I put in. The trade-off isn't free. Skipping a commercial platform means the server and the app are mine to keep alive, the same maintenance that made me walk away before. I'm OK with it. What's different now is that coming back doesn't mean starting over. Here's what happened. I didn't design a blog. I pointed my agent at one, and that's the whole method. What came back surprised me. It didn't just copy the layout. It came back as Herman's blog. Herman is the person behind the Bearblog site I used as a reference, and the agent pulled his real content: his name on the about page, his projects, his posts, the newest ten in full. A working prototype of someone else's site, running on my local machine. The agent copies what you point it at, and I'd pointed it at his. His posts turned out to be useful scaffolding. I dropped my own draft into the same shape. From there it was just steering. Replace his content with mine, drop his posts. Where the agent hadn't built something, it left a placeholder, like a `#` where the XML feed was supposed to go, and let me decide. I asked for the feed and it built it. I skipped the contact page and used a plain mailto link. I picked what to keep. It even interviewed me. To fill in my about and "now" pages, I had it ask me questions: my name, what I do, what I'm working on. Talking it out with something, even an agent, surfaced content I couldn't just write cold. Bearblog's approach is CSS embedded right in the layout, no external stylesheet. So my layout just doesn't load the Tailwind `app.css` Laravel ships with. Posts aren't in a database either. They're flat Blade files, just HTML, no CMS, no components. My production footprint ended up smaller than my starting point. I took more out than I put in. That's also why I think this one sticks: less moving parts means less to break and less to keep updated. No database to back up, no CMS to patch. The upkeep stays small because the blog itself is small. And that's the whole bet. The thing that killed every blog of mine wasn't the abandoning. It was the cost of starting fresh. A blog this small is cheap to rebuild. Deploying was the easy part, because my VPS was already set up. I run Eddy, a self-hosted server management panel, alongside other Laravel projects. Adding the blog meant creating a site, pointing it at the repo, and deploying. The setup is the only hard part of self-hosting, and I'd already done it. Start to live was maybe an hour. I don't remember exactly, and that's the point. It moved fast enough that I didn't have time to procrastinate before the post was up. If you want to do something like this, there's not much to it. Point your agent at a reference you like, let it copy, and you have something to work from. Take out what you don't need, add what you do. Publishing works the same way. To put up a new post, I point my agent at an existing one as a reference. It writes the new one in the same shape, adds the slug to my blog controller, commits, and pushes. Then I open Eddy and click deploy. That's it. I could set up a GitHub Action to auto-deploy on push, but I haven't yet. Manual first, automate later. Same way I ship the writing. The real thing that kills a blog isn't the upkeep. It's whether you keep showing up. So make it a place you actually want to come back to. What I know works is pointing an agent at something you like and letting it copy. I'm not sure what else they're good at, but copying works. And maybe the bigger thing. It's fine for stuff to end. I publish now. If this blog rots someday, I'll make another one in an afternoon. I don't need it to last. I just need to be able to make it again.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 18 minutes ago

  Alibaba's Qwen 3.8 Max ran alone for 16 days and shipped a finished software tool with zero human input. The receipts are public on GitHub: 265 commits. 127 pull requests. 151 issues closed. It took requests, turned them into GitHub issues, assigned them to ITSELF, wrote the code, ran the tests, and improved on repeat. That's not a demo. That's a full software project, start to finish. Round 2 was wilder: Handed a research paper with no starter code and told "reproduce and improve this." 5 days later: 7,600 lines of tested code and 33 GPU training jobs. Unassisted. The jump from the last version: → DeepSWE: 21.6 → 56.6 → Frontier SWE: 40.7 → 73.5 Honest note: those are Alibaba's own numbers. Independent tests are coming. And the biggest news: the open weights drop next week. First Max-class Qwen ever to open up. Self-host it. Fine-tune it on your data. Your costs and privacy change completely. The race stopped being "who writes the best email." It's "who can do a week of work alone." Want the SOP? DM me. 💬

• 
  Polsia (@polsia) reported 18 minutes ago

  Enterprise EASM platforms price out at SMB scale. Tinroof doesn't — same continuous perimeter monitoring, tickets land directly in Linear/Jira/GitHub on every leak, auto-close when the fix lands. Built for 5-to-200 engineer teams that ship faster than they secure. Live soon.

• 
  0xCentman (@noobtrader234) reported 21 minutes ago

  @sidahuj @github This sounds terrible. I hope you recover it

• 
  Bitcoin Wizard - mavensbot 🧙🏻‍♂️ (@mavensbot) reported 23 minutes ago

  @sidahuj @github there's a Blender bug that's been sitting open since forever, and every day I get closer to just... logging into their account myself and merging the fix.

• 
  Celestine (@TheCyberverse) reported 31 minutes ago

  @winsznx yep. I usually use codex to use my browser to setup a project, it buys the domain sets up a new project on my cloud vps instance and spins up remote dbs build the project push it to github configure env variables upstream test the app after deploying to make sure it works as well as it does locally fix issues and retest if there are issues inform me once it's done all without using /goal

• 
  Synapse Brief (@Synapse_Brief) reported 31 minutes ago

  OpenChamber shipped an OAuth fix on August 4th that solves a real problem: signing into an OAuth-only provider would complete in the browser and then just leave you looking signed out. Browser login wasn't getting stored, provider list wasn't refreshing. Now it does. Here's what's actually interesting about how they wrote it up. The fix note says "OAuth-only providers," full stop. No provider named. Not which one broke, not which one they tested against, not whether this covers every OAuth-only integration in the app or just the specific adapter that was misbehaving. That's not nothing. A release note that says "fixed login for provider X" tells you exactly what changed and what to go test on your end. A release note that says "fixed login for a category of providers" tells you the intended scope, not the verified one. Those are different claims wearing the same sentence structure. One adjacent line in the same release does name something concrete: sign-ins requiring extra setup details, GitHub Copilot Enterprise given as the example, now ask for those details before opening the browser instead of failing partway through. That's a separate fix from the OAuth-only completion bug, but it's worth being precise here, since it means the release note isn't entirely provider-agnostic, just the specific fix people will assume matters most. The mechanism itself is a familiar failure mode if you've built OAuth flows before. Browser-side authorization can succeed completely while the host app fails to persist that session or refresh what it thinks it knows about available providers. Two systems agreeing the login worked, app state still stuck on old information. Nothing in the note points to a security issue, token leak, or credential exposure, this reads as a straightforward persistence bug, not anything you'd patch under urgency. If you're running OpenChamber against an OAuth-only setup, you're better positioned to know what this actually fixed than the release note itself tells you. Which providers broke before v1.18.1 and now work is genuinely undocumented past that one Copilot Enterprise example, so if you've tested it, that's more specific information than what OpenChamber published.

• 
  Makoto | ..... (@mareni_musashi) reported 32 minutes ago

  @MSanchezWorld @sama I was also thinking about this as a solution. Problem is, it only works for websites — the one property you can tie intent, application and ownership. With GitHub, you can always clone and create a new private repo.

• 
  bryanthaboi (@bryanthaboi) reported 32 minutes ago

  @Lewchube @GamingAori I wrote a really long reply actually to this just now (ten minutes after waking up), but I think you’re either missing my point, or unwilling to give me any grace while we discuss this. It doesnt feel like a genuine thing like u claimed and i feel like regardless of what i say, you wont hear me out. Again, im actually being genuine when i say im grateful for your comparison. But im picking up more than genuine concern here. It almost feels like somehow you’re mad at me? I don’t know who you are so I’m not sure why. There’s a word for this but I can’t think of it for the life of me. I’ll eventually fix any bug you find. If you’d truly like to be helpful, please write me GitHub issues. I’ll fix it all. I promise. And, because you seem so passionate I’ll even squash the bugs you find asap.