Gathering information from multiple user experiences from other forums along with my own experience, it seems that many users have been encountering issues with playing Realms for longer than 20-30 minutes without getting disconnected.
The flow of the bug happens as such: the player plays on a realm which everything seems to be normal (with some instances of the bug reporting extreme lag before disconnection), and then unexpectedly, the game would crash and give the player the error code “Goat”. It is important to note that error code “Goat” is usually for worlds in which the host has left or disconnected, which means this error code usually appears for worlds that require a host to be online—unusual for Realms.
Then, there is the issue of what happens after the disconnection. User experiences from this vary quite a bit, but the general consensus is one of two things happen after the crash. 1) Data for all players is rolled back—including build progress on the Realm, player inventories, etc., which seemed to be more common with players playing with multiple people in the realm. Or, 2) data for players is rolled back, but would be able to re-update and fix itself to the original data if “Save and quit” was pressed after reconnecting to the rolled-back server. The fixed data would include world progress and player inventory. This would typically happen if only one person is playing on the Realm at this time (such as my own experience), or rarely would happen to one lucky person out of multiple if the error happened with multiple players.
Most of the user reports on services such as DownDetector still indicate that there is a possible issue, with reports peaking at 9PM-12AM CST. Based on a lack of relieved users on other forums, and a persisted increased number of reports from baseline on DownDetector it is believed that this issue is still occuring.
EDITS:
(7/24, 3:00 PM CST) It should also be noted that: a) This is not a device specific error. b) The error code “Goat” is not the only code that may appear. One code from my experience is error code “Terracotta”, which is a general error code.
(6:00 PM CST) This bug appears to have other consequences related to Realm world slots, addons, gameplay settings (such as game difficulty), and backup save weirdness. Some users from outside discussion threads also note that all players online on a Realm will disconnect when there are more players joining from other regions. For those looking to attempt to replicate the issue, that may be a more viable way to do so.
(10:00 PM CST) Another noted issue that may stem from this bug is an issue with loading the Timeline feature (in which the game has to be exited and reopened). Furthermore, it seems that following Minecraft’s troubleshooting guide to fixing either error code “Goat” or “Terracotta” seems to have no effect.
Linked issues
is duplicated by 11
Comments 26
One more note: Only one player has seen the GOAT error code, and that is the owner of the realm (on PC Windows 11). But this player has had several different error messages as well. I am the user on PC Windows 10 and I commonly see a message saying the realm is no longer active, but I have not seen the GOAT code.
My friends and I have been experiencing the same issue in Western Canada since yesterday (23/July/2026). Sometimes the crash happens after a few minutes. Sometimes it happens after an hour or so. Sometimes progress is saved, and other times progress is completely lost. We ended up losing a few hours of progress total yesterday until we finally gave up. Exiting and saving the game manually does not seem to make a difference to whether the progress is backed up or not. We are all playing on Windows PC at the moment.
My friends and I also experienced this all of yesterday (July 23rd, 2026) where my mining progress was completely reset about 10 times before I got too exhausted to continue. Everyone was kicked at once with the error and all got the GOAT error.
While doing ‘Save and quit’ works, logging out and back in every 10-15 minutes to avoid the issue is very annoying.
I been experiencing this too on a single-player realm (myself) and am getting annoyed by it. Its exactly like this post says, they got to fix it now or we all might think Realms is not working as intended like some years ago.
We had multiple people online and occasionally one person would be in a different region. Their instance would be in Washington and ours in North Carolina
We couldn’t see them, they couldn’t see us
They could play as normal but when we all would get disconnected and connected back with the rest of us, nothing they had done was saved
I have been playing solo for the last couple days on PC and have had this issue multiple times. I started doing Save & Quit regularly so the rollbacks would be less annoying. It was Goat error when I still had the patience to check.
I am in Western Canada and always seem to connect to the Washington server… we also have poor air quality right now because of wildfires in Washington and BC… is the Washington server on fire?
This issue has been reviewed by our team.
Please add new, relevant information if it helps us understand or reproduce the issue. To show that you’re affected, use the vote feature rather than commenting.
If a fix is implemented, it will be listed in our official changelogs.
For major outages or urgent assistance, visit the Minecraft Help Center.
This has started happening in my realm since the 26.44 update. it’s extremely annoying and seems to be caused by the automatic updates not happening correctly - it doesn’t always boot us. sometimes it stabilises after a few minutes and no goat error. but it’s been consistent since it started inside the first 24hrs after the update. every half an hour the realm freaks out and then may or may not kick us all off - it happens if only one player is on or more than 1. when we are disconnected it rolls back to the last save it managed to do.
This was happening yesterday afternoon and it was maddening. Very sad to see it’s still an issue this morning.
I’d like to add that this is occurring for us with multiple devices/platforms being impacted, yesterday we had four players on using PC Windows 10, PC Windows 11, Android phone, and iPhone. All were impacted so this is not device/platform specific.
We have not yet tried the method of using “save and quit” after reconnecting to see if it fixes, we will experimentally try this.