Mario Kart Tour Is Gone: A Shutdown Checklist for Small Studios Running Live Games

Mario Kart Tour went offline at the end of September 2026, nearly seven years after it launched on mobile in 2019. Nintendo's own closure is a useful case study for any small studio running a live game, because it shows what a well-resourced publisher does when a live service reaches its end, and what it does not do.

What happened, based on trade reports. Nintendo announced the shutdown in July. Ruby sales, the game's premium currency, were stopped ahead of the closure, automatic Gold Pass renewals were cancelled, and from August 4 every player received Gold Pass benefits for free. Servers went dark on September 29 at 11 p.m. Pacific, according to one report; another cites September 30, so treat the exact hour as approximate. Reports say there is no offline mode planned, which means player progress is gone. The game had also stopped getting new tours, tracks and drivers back in 2023, shifting to rotating existing content. It follows Nintendo's earlier mobile closures of Dr. Mario World and Dragalia Lost.

The sequence is the lesson. Stop taking money first. Then give players something in return for the notice period. Then switch off. From announcement to shutdown was less than three months, and the spending stopped before the servers did. That ordering is what separates an orderly sunset from one that feels like a rug pull.

Why a small Indian studio should care. Most of us run lean live games on hosted backends, with a few hundred to a few lakh daily players, and many titles are one or two people's side projects that quietly stop earning. Nobody plans the ending. But a game with accounts, cloud saves, a leaderboard or purchases has a duty to its players the day it stops, and it is far cheaper to plan that duty at the start than at the end.

A practical sunset plan for a small studio. First, decide your kill criteria in advance, for example a revenue floor below your server and support cost for three straight months. Second, turn off purchases before you turn off the game, and honour anything still unspent where you reasonably can. Third, give clear notice in-game and in the store listing, with a date. Fourth, if the game can run without a server, ship a final offline build; it is the single kindest thing you can do for a puzzle, idle or casual title. Fifth, keep players' data handling in line with your privacy policy when you delete accounts, and check the current store policies and consumer-law requirements that apply to your markets before you announce.

The deeper takeaway is about design, not closure. Games that are built to work offline first, with the server as an optional extra, age better. If your next title is a casual or puzzle game, that choice costs little at the start and saves a painful goodbye later. We are building with it in mind.