Turtle WoW's Website, Forums and Social Channels Go Dark — the Final Line of the Shutdown Timeline
The last date in the Turtle WoW shutdown timeline arrives today. When the team said goodbye in April, the farewell letter set three dates: servers offline at midnight on May 15, and the website, forums and social media channels closing on October 16. The servers went dark on schedule five months ago. As of October 16, 00:30 Beijing time, we can confirm turtle-wow.org no longer completes a TLS handshake — the site is gone or is being taken down right on schedule, while the rest of the internet (we checked github.com and cnb.cool as controls) responds normally.

Original editorial illustration by RealmList, generated for this article. This is artwork, not game footage or official promotional material.
How the timeline played out
| Date | Event |
|---|---|
| August 2025 | Blizzard sues Turtle WoW's operator (reported as AFKCraft Ltd.) for copyright and trademark infringement |
| April 11, 2026 | Resolution reported in Blizzard's favor; a confidential settlement follows, with reporting describing a permanent injunction covering the server, derivative clients (including the UE5-based "Turtle 2.0"), and assisting others to run similar projects |
| April 17–18, 2026 | Torta's farewell letter: final day May 14, servers offline midnight May 15, realms pushed to their final progression patch, donations closed, web presence to shut October 16 |
| May 15, 2026 | All game servers go offline after nearly eight years of operation |
| October 16, 2026 | Website, forums and social channels go dark — today |
One detail worth flagging for accuracy's sake: English-language coverage of the ruling says the judge sided with Blizzard on "nearly every count," while Chinese coverage describes all seven copyright claims being upheld. The precise count tally sits inside a confidential settlement, so we can't independently reconcile the two; what every source agrees on is the outcome — a permanent injunction and an orderly, negotiated shutdown rather than an abrupt seizure.
The same April announcement covered Stormforge, which closed a day earlier (May 14) under its own agreement with Blizzard; its closure message implied the team would move to original projects outside Blizzard's IP.
What the takedown actually erases
The game servers died in May, so today's shutdown takes out everything that described the project: patch notes for Turtle's custom content, the forums where its community organized, and the social accounts that announced new zones and races back when "Classic+" was a fan-community word and not a Blizzard product category. For anyone arriving late, the practical consequences are:
- No official downloads, no official realmlist, no forums. Anything still circulating comes from mirrors or community archives, and should be treated with the usual caution we outline in our client-download checklist.
- The community didn't evaporate. Successor projects, migration paths and the takedown-hardening behavior of these teams are things we've followed in the Turtle successor coverage and the English-setup migration guide.
- Our own directory entry for Turtle WoW remains as an Offline archive — realmlist and history preserved as a record, not as a recommendation, consistent with how we handle every shutdown on the site.
The longer arc
GameRant's retrospective draws the obvious parallel: Nostalrius was taken down on April 10, 2016, and World of Warcraft Classic was announced a year and a half later. The 2026 version of that rhyme is more pointed — Blizzard spent the year dismantling the largest Classic+ projects (Turtle, Stormforge, Ascension) and then announced WoW: Forever at BlizzCon, an official Classic+ with new zones, new races and new raids on the vanilla map.
Whether Forever satisfies what those servers built is the question the next months will answer. What is already settled: the unofficial side of that history lost its most durable landmark this week, and as of today there is no turtle-wow.org to even read about it.
Sources and further reading
External references used to verify or expand this article.