Feedback on Recent Infrastructure Migration – Communication & Post-Migration Guidance

Hello,

I’m writing to share some feedback following the recent infrastructure migration.

First of all, I want to make it clear that I am generally very satisfied with your services, and I regularly take the time to recommend Ultra.cc to others, including publicly. Precisely because of that, I feel it’s important to provide honest and constructive feedback when something could be improved.

In this case, the migration was announced quite late and, more importantly, without real post-migration guidance for users. Since the service came back online, I’ve spent more than 24 hours dealing with a series of small issues caused by the migration: BitTorrent ports changed without clear notice, applications that did not restart automatically or remained partially non-functional, and misleading states giving the impression that everything was working when it actually wasn’t.

Taken individually, none of these issues are critical. Taken together, however, they resulted in a significant and avoidable loss of time and stress—especially for sensitive services like BitTorrent.

Concretely, this situation forced me to send several private messages (X PMs) to trackers I am a member of in order to “prove good faith,” after receiving a cascade of Hit & Run pre-warnings. These warnings were not caused by user behavior, but by the fact that qBittorrent was effectively blocked after the migration (ports not aligned, announces not going through), without this being immediately obvious from the interface.

I fully understand that in the case of a true hardware emergency (for example, a failing disk or a critical incident), not everything can be anticipated. However, if this was a planned operation, I would have appreciated clearer, more structured communication, such as:

• “After the migration, please check your application ports”

• “Some applications may require a manual restart”

• “Here is a post-migration checklist to avoid common issues”

Even a short set of guidelines like this would have made a real difference and prevented the situation I described above.

I also noticed the upload capacity increase announced on your Discord, which is of course a positive change. That said, in my specific case—despite very large sharing volumes—I was rarely reaching the previous limits. What I am still waiting for, however, are more tangible evolutions in terms of storage capacity, which remains a much more structuring concern for me in the medium term.

This message is not meant as a complaint, but as constructive feedback. Your offering is solid, and it is precisely for that reason that this type of migration would benefit from more careful customer-side guidance in the future.

Thank you for your time, and best regards to your teams.

Kind regards,