That's why I cancelled but I'd be curious about the technical reasons that something like this could happen, given that I'd expect cancellation to not be that much of a load on the servers compared to all the other actions users take on a streaming platform. Perhaps subscription changes go to a specific microservice that got overloaded? Or to an unsharded database that got overloaded?