Fresh reports from July 24 and 25 show subscriptions marked expired days before renewal, duplicate charges, and servers vanishing despite confirmed payments from multiple users on Reddit and feedback sites.
If you pay for Minecraft Realms expecting your server to stay online, this week has been rough. A fresh batch of complaints reveals a stubborn billing glitch that tells players their subscription has expired or been canceled even when the payment cleared and the renewal date sits days in the future.
The reports started picking up steam on r/realms and the official Minecraft Feedback site. Users on Bedrock across console, PC, and mobile describe making payments only to watch their Realm disappear or throw errors preventing friends from joining. Some ended up charged twice by their platform store while support stays quiet.
What Players Are Reporting
- Realm dashboard shows canceled or expired status days before the next scheduled charge
- Multiple identical purchases attempted because the first appeared to fail
- Server becomes inaccessible after renewal with no warning or rollback of world data
- Cross version mismatches from recent Bedrock updates kicking everyone when one player joins
One detailed post from July 24 explains buying the subscription twice after the first transaction seemed to vanish, only for the bank statement to show both charges while the Realm stayed dead. Others mention waiting on Mojang support tickets that go days without replies.
Mojang maintains a help page for Realms subscription payment errors that recommends restarting the purchase flow or checking Microsoft account status. While that covers some cases the current spike in identical reports suggests the problem sits on the backend where platform stores talk to Realms infrastructure.
This is not the first time Realms monetization has stumbled but the timing feels particularly bad with summer playing seasons in full swing and many groups relying on private worlds for events and long term builds. If you are currently affected the best immediate step is documenting every transaction ID and opening a ticket through the official help channels while the community pressure builds.