Rare names this code but does not publish the wording it prints on screen, so we quote only the code itself: Marblebeard. Any site showing you an exact message for it has written one.
This error is produced locally. It does not appear because the service is down, so the fixes below are worth working through in order.
Rare reports Sea of Thieves services healthy
Rare's wording names the area precisely: “Your game is currently unable to communicate with the server it is trying to join. Please check your home network including firewall / anti-virus configuration and other networking options such as NAT type.”
Note what that does not say. It is not a claim that the server is down — the server is there and your machine cannot reach it.
If your crewmates are sailing and you are the only one getting this, it is your side, and Rare's wording agrees. If the whole crew drops at once, look at Greybeard and Fishbeard instead, which are Rare's own server-side codes.
Operator documentation: support.seaofthieves.com. Rare documents every beard code in one catalogue, last updated 22 May 2025, and that catalogue states its own completeness. It describes causes and fixes but never quotes the message the game prints, which is why this page does not either.
Rare's wording names the area precisely: “Your game is currently unable to communicate with the server it is trying to join. Please check your home network including firewall / anti-virus configuration and other networking options such as NAT type.”
This error is produced locally. It does not appear because the service is down, so the fixes below are worth working through in order.
Start with: Check your NAT type. Open is what you want. Strict NAT is the most common underlying cause of this class of error in any game that makes peer connections.