None of my players can connect to my Java Realm, including myself, it keeps timing out. Also tried to close the realms and restart, but just gets stuck at the "Closing the realm..." process screen. Same thing with trying to switch the world. Is anyone else having these issues?
Rollback Post to RevisionRollBack
There is a sixth dimension beyond that which is known to Steve. This is the dimension of imagination, an area which we call... The Blocky Place.
I also cannot join my friend's realm. It has the green traffic light and gives me this error
I have this same issue, and so does everyone else in the realm including the owner. It seems to have happened approximately 9 hours ago. It's also happened on multiple platforms including bedrock, (but it started for them a couple days ago) not sure how to resolve it, if anyone does?
Found a tweet by Mojang posted on the 8th saying that it would be down for maintenance on the 2nd. I guess it was a typo, and they meant the 9th? Would be pretty weird to announce they would be doing maintenance 6 days after it already happened.
The same on my end, made a new realms world to play and now I can't even access the Minecraft realms tab, just error 503 for myself and all the users of the realm. Does anyone have any idea how to fix it?
This sounds like an entirely separate but equally troubling issue. I'm experiencing the same thing on all of my realms (I don't own them). It's troubling that mojang does this because there are people out there that pay for realms.
My first realm, this is my first month paying for a realm and so far haven't been able to log into it for four days out of the last two weeks. THis really isn't good enough, especially for $7.99 a month
I'm having the same issue now. but this is touch and go said error 503 this morning then seemed to work an hour later, worked for like 5 hours, then I logged off for 30 mins and now I'm getting the same issue again.
None of my players can connect to my Java Realm, including myself, it keeps timing out. Also tried to close the realms and restart, but just gets stuck at the "Closing the realm..." process screen. Same thing with trying to switch the world. Is anyone else having these issues?
There is a sixth dimension beyond that which is known to Steve. This is the dimension of imagination, an area which we call... The Blocky Place.
I also cannot join my friend's realm. It has the green traffic light and gives me this error
I have this same issue, and so does everyone else in the realm including the owner. It seems to have happened approximately 9 hours ago. It's also happened on multiple platforms including bedrock, (but it started for them a couple days ago) not sure how to resolve it, if anyone does?
UPDATE: it works now, seemed to fix itself.
I've the same problem help la puta madre
I get an error occurred (503):
I think it was a ploy to get a bunch of people to say they 6, 9 with perfect vision: 6/9/2020
It works now, seems to have fixed itself, at least for us. everyone else?
Found a tweet by Mojang posted on the 8th saying that it would be down for maintenance on the 2nd. I guess it was a typo, and they meant the 9th? Would be pretty weird to announce they would be doing maintenance 6 days after it already happened.
The same on my end, made a new realms world to play and now I can't even access the Minecraft realms tab, just error 503 for myself and all the users of the realm. Does anyone have any idea how to fix it?
This sounds like an entirely separate but equally troubling issue. I'm experiencing the same thing on all of my realms (I don't own them). It's troubling that mojang does this because there are people out there that pay for realms.
My first realm, this is my first month paying for a realm and so far haven't been able to log into it for four days out of the last two weeks. THis really isn't good enough, especially for $7.99 a month
I'm having the same issue now. but this is touch and go said error 503 this morning then seemed to work an hour later, worked for like 5 hours, then I logged off for 30 mins and now I'm getting the same issue again.