Thx Geo

Think we hit high of day Geo. 1140 EST?

With the semis not really coming down, or at least not a great sell signal yet, is a qqq short going to gain much traction?

Net P&L to me: about -$11. That’s not the story. The story is:

1. A 10-day persistent defect with a customer-service workflow built around it isn’t a defect — it’s a feature someone is tolerating. Real execution bugs get war-roomed in hours. FINRA Rule 5310 (best execution) makes this a serious supervisory problem.
2. The notification landed exactly when the rally went parabolic. Gap-ups on April 14 and April 17, declining volume on the way up. If the defect predates the email — which we can’t rule out — the March 30 ? April 13 leg is in scope too.
3. The retail book was heavily short. Six weeks of grinding down left every short trader with protective buy-stops above the market. A “bug” that converts stops to market orders without requiring the trigger price is a mechanism to force that entire short-stop pool to execute on demand — a manufactured squeeze with plausible deniability.
4. The route is a separate legal entity from the broker (Lightspeed’s own docs confirm orders flow through third-party vendors before reaching market makers). The “bug” lives at a layer customers can’t see and the broker can disclaim — but the two are coupled tightly enough for same-day customer calls.
5. A BYND cluster in my blotter. I closed a BYND long at 1:47 PM ET for +16% at $0.99. At 2:36 PM ET — 49 minutes after I was flat — four BYND orders appear at the same timestamp (14:36:52), same price ($0.99), 500 shares each, alternating sides: SSD / BOT / SLD / BOT. I didn’t place them. That looks like the route cycling something through my account after I was out. I want to know what and against whom.

My theory: this isn’t a bug in the ordinary sense. It’s a mechanism — intentional or tolerated — to convert retail resting orders into forced market flow. In the current positioning (short-heavy retail book, buy-stops pooled above), that flow skews net-long. The beneficiaries are whoever needed the indices to ramp vertically into earnings season and macro data — wealth effect, pension marks, short-vol NAV recovery — without organic buying pressure to support it. My account came out flat by coincidence of position mix. Net-short traders would have been destroyed.

The timeline. The indices bottomed March 30 (SPY ~630, QQQ ~556) and began a short-squeeze rally. By April 13, SPY closed at 686 and QQQ at 618. On April 14, Lightspeed emailed me:

“Please be aware that all GTC orders were cancelled yesterday, 4/14/2026, due to an issue with the routing destination… GTCs are currently not functional but we expect they will be again within the next couple days.”

(Note the date contradiction in their own email — dated April 14, claims cancellation happened “yesterday, 4/14/2026.”)

Right after that notification, the rally went vertical: SPY gapped to 687 on April 14, gapped again to 705 on April 17, and drifted higher on declining volume — the textbook signature of distribution into forced buyers, not organic accumulation. As of today, April 23, the “couple of days” has stretched to ten days and GTCs are still broken. That’s when customers were notified — how long the defect actually existed before the email is an open question, and the March 30 ? April 13 leg up is a worth investigating.

What happened to me today. I placed GTC stop orders — sell-stops on longs (PGR, CRMT, HRL, SJM) and buy-to-cover stops on shorts (AFRM, SNDK). Stop prices were well away from current price. None were close to triggering.

At ~11:40 AM PST, every stop was executed as a market order. Not triggered at the stop price — just force-filled at prevailing NBBO regardless of the trigger I entered.
I didn’t discover it myself. Lightspeed proactively called me. They said “the route” (identified as LITE) notified them of a “discrepancy” and they had updated my account to reflect the stop market orders the route had filled. So the route knows in real time when this fires, the broker knows, and there’s enough of a process that Lightspeed is making same-day outbound calls. That’s not a bug being discovered through customer complaints — that’s a normalized operational workflow. The response is “call the customer after the route has already filled their stops as market orders,” not “halt the route.”

(continued in next comment)