Collapse Watch №3 — After 33 Days of Silence, Odysee Spoke. It Recommended Some Gaming Channels.

Our second reading closed with a platform whose own channel had gone a full calendar month without a post. That silence has now ended — and the way it ended is the finding. On September 2, Odysee's first post in 33 days appeared: a routine channel-recommendation roundup, with not one word about the departed CEO, the leadership vacuum, the lawsuits, or the performance collapse its own commenters were reporting underneath it. It was corrected the next day after commenters caught a misdescribed featured creator, it drew 138 comments in three days, and the company replied to none of them. Every claim below is sourced to data we fetched September 5–6, 2026, most of it now published in our own repository as a citable dataset.

I. The machine spoke

The timeline is worth laying out precisely, because all of it is verifiable on-chain. The July 31 “Channel Roundup” sat as the official channel's newest post for 33 days while users underneath it asked whether the platform was dying. On September 2 at 22:11 UTC, “Channel Roundup: August 2026” appeared — a text post recommending thirteen channels: Minecraft builds, a culture-war podcast, a Blender artist, a classic-metal stream, a hypnotherapist. It opens “Hello everyone,” closes “We look forward to seeing you in the comments,” and contains zero institutional words: no leadership, no ownership, no roadmap, no acknowledgment that anything has happened to the company since July 14. Ten minutes later, the July roundup — the post whose comment section had become the community's waiting room — was quietly updated; the blockchain records the edit, though not what changed.

Then the correction. Within hours, commenters noticed that the roundup's description of featured creator @Devcalner didn't match his channel. The creator himself replied: “I think Odysee mixed me up with someone else :P” and, later, “Yeah, that was totally wrong …” Another commenter asked: “Is it just me, or does it seem like they've given an AI generated description for each channel?” On September 3 at 13:36 UTC the chain records the roundup being edited — and a commenter confirms “the error in the post … was corrected later.” So the company's comeback post, its first communication in 33 days, misdescribed one of the thirteen creators it existed to celebrate, and had to be fixed after the community caught it. The company itself never commented. Its last comment anywhere that we can find remains a July 31 housekeeping reply. The account that wrote “we look forward to seeing you in the comments” has not appeared in them.

II. The comment section is the press room now

No press outlet in any language has yet covered this collapse — we re-verified that with a wide-net sweep on September 2 (news indexes, crypto press, German, French, Spanish and Russian tech press, Hacker News, newsletters, podcasts: nothing; ArchiveTeam, the internet's platform-death watch, has no Odysee project at all). Which means the only running coverage of Odysee's condition is being written by its own users, under its own posts. Under the July roundup they asked, on August 3, “is Odysee dying/being killed off?” — that thread then froze exactly as we archived it, 132 comments, not one added or removed since September 2. Under the August roundup, the questions matured. “How does Odysee survive with no views, no ads, no vlogs, no discoverability, no nothing? not complaining … just asking!” wrote one creator. On September 3, a user answered another's confusion the way a company spokesperson never has: “Chandra apparently left (or was removed from) Odysee a few months ago. He has not been with the company for a while. He made a post about it.” And on September 4, the thread arrived at the question this series has been asking since day one (the thread): “That's the thing, we don't know exactly who is running Odysee. Chandra didn't name anyone. We could say Forward Research but who exactly is the CEO of Odysee?”

Where facts are withheld, invention fills the space. One prolific commenter now asserts that Forward Research is a front for a German industrial dynasty — a claim with no basis in any corporate record we hold, repeated twice in the thread, and left standing because nobody official is present to answer anything. Another still addresses his complaints to “Julian,” apparently unaware the CEO left seven weeks ago: “Julian can't afford the servers anymore, big delay when trying to load and download fails frequently. Julian is dying slowly along with Odysee.com. …” Meanwhile the community has started governing itself: two users in the same thread push the “Hide Synced YouTube videos” setting — complete with a homemade how-to video — to filter out crossposted content, while a nastier faction wages a natives-versus-“YouTube refugees” fight over the platform's identity — “Crossposters are what's KILLING Odysees Identity,” writes one; a Portuguese-speaking newcomer adds that the platform is “making the same mistake as many other platforms that have already closed.” Thirteen recommended channels; 138 comments; zero answers.

III. “Unusable all week”

Threaded through the comments is something new and concrete: a cluster of availability complaints dated September 3–5. “I hardly use Odysee anymore as it is so slow and has been constantly buffering to the point of unwatchable for months now.” “Do you know why so many of my videos don't play? … load time of 2 t0 5 minutes or they don't play at all.” One user apologised for a triple-posted comment sent “right before the site went down.” And the same person who asked “is Odysee dying” back on August 3 returned on September 5: “Whole site has been unusable all week, this is the first time i've been able to make any comments under any video or post show up,” describing repeated “failed to synchronise” errors. Our own scanner's logs recorded 149 API read-timeouts against Odysee's backend during its September 4 scan run — we flag honestly that our scanner changed hosting mid-window and that the timeouts cluster in that one run, so we treat them as consistent with the user reports rather than independent proof. Nobody from the platform has acknowledged any of it; Odysee operates no status page — the obvious hostnames for one do not even resolve.

IV. What the scanner measured: the money moved — twice

The economics this window (August 30 19:36 UTC to September 5 07:21 UTC, 5.5 days) look at first like a thaw: 166,414 LBC of inflow, about 30,300 a day — double the collapsed floor of the previous two readings. Then you look at where it came from. 82% of the entire window's inflow is two channels placing fingerprint positions. @apologeet — the Dutch-language channel whose ladder of exact 50,000-LBC stakes we documented in the seventh self-stake reading — added exactly 100,000 LBC, as two stakes of exactly 50,000, the same signature as its July 29 move. @BarrettMopar's metronome ticked twice more: two new positions of exactly 18,540.01 LBC each, its thirteenth and fourteenth near-identical placements since August 3. And across the roughly 106,000 items that were already in the corpus on August 30, the total stake added by anyone, anywhere, was zero LBC — not small, zero. Everything else is flat: 27 newly flagged items (4.9 a day, level for a third window), the round-number count unchanged at 37 with no entries and no exits, the formal self-stake count 54 with its pool at 5,162,949 LBC as of the August 30 weekly reading.

The removals ledger held again, with one footnote worth recording precisely. Twenty-one items that our August 30 scans could still find in Odysee's search results have not been seen by any scan since; we resolved all twenty-one against the platform's API on September 5 and all twenty-one are live — buried, not removed. That is now 58 of 58 across three windows. Separately, for the first time in this series, one item left the corpus's live set entirely: an anonymous 0.5-LBC upload that stopped resolving. The blockchain explains it — the claim's bid was spent on September 3, an on-chain abandonment by whoever held it, and its filter flag is clear. Whoever deleted it, it was not the platform: Odysee's own removal record remains zero across every window of this watch.

V. What we are watching next

The calendar is unchanged from №2 and getting close. In the Texas litigation, the motion to strike the filings that include the Odysee-naming declaration awaits a ruling any day; the consolidated case's joint report is due October 1 and the parties meet Chief Judge Mazzant on October 15. And one infrastructure bill quietly got paid: the registry record shows odycdn.com — the CDN domain we flagged as expiring October 5 — was renewed on September 5, pushing its expiry to 2027. Somebody, somewhere, is still paying for infrastructure. The bigger test remains odysee.com itself, which the registry still shows expiring October 11, unrenewed as of this writing. The parked stake pools did not move again: 5.16M LBC of self-stake, @TheBornGenesis's 3.01M. And the roundup cadence itself is now an instrument on our dashboard's data feed: we track the official channel's posting gap and its comment sections continuously, from infrastructure that doesn't depend on anyone at Odysee answering questions.

Methodology & verification notes

Sources fetched and verified September 5–6, 2026. The August roundup's publication (September 2, 22:11 UTC), its September 3 edit, and the July roundup's September 2 edit are dated from the LBRY chain index (claim creation and update transaction timestamps, used consistently — not database index times, and not creator-settable metadata); the roundup's full text was retrieved from Odysee's own CDN; what the September 3 edit changed is commenter-attested, the fact of the edit is on-chain. All 138 comments on the August roundup and 132 on the July roundup were harvested via Odysee's comments API and are published in our repository as the citable record (comments are deletable; the July thread is bit-identical to our September 2 snapshot — zero comments added or deleted). Quotes are verbatim from that dataset; we do not reproduce the thread's slur-laden exchanges. Scanner figures computed by our now-published window-report tool from the August 30 and September 5 data commits. Two corrections in the interest of the series' reproducibility: №2's methodology note mislabelled which counting method produced №1's “126” — it is the claim-ID set difference, inflated by backfill of legacy rows, and №2's note has been corrected in place; and an early computation for this reading showed 864 items “fallen out of search,” a figure we refuted ourselves — the staleness rule was inconsistent with №2's and our scanner changed hosts mid-window with visible API timeouts, so the comparable rule (21 items, all live) is what we publish. Labeled unverified: the cause of the September 3–5 outage reports, the content of the July-post edit, and — as always — who places the fingerprint stakes. Counted honestly against the decline narrative: the channel did post, someone did fix the roundup's error within a day, the odycdn.com renewal shows an infrastructure bill being paid, and inflow did double, whatever its concentration.

Related coverage on OdyseeWatchdog

• Collapse Watch №2 — Day 48: The Flatline Holds, and the Only Money Still Moving Is a Metronome
• Collapse Watch №1 — Six Weeks After “It's Over Now,” Odysee Is Running on Autopilot
• “Goodbye Odysee” — The CEO Walked Out, the Money Ran Out, and Nobody Reported It
• Self-Stake Seventh Reading — The Counter Didn't Move. A Million LBC Did.
• Pay-to-Rank: Odysee's Search Is For Sale
• Zero — The Number of DSA Transparency Reports Odysee Has Ever Filed