Cyanbeard error... AGAIN!

Restart your router/check console.
It's not the games fault.

'Cyanbeard means your connection to Xbox Live and/or the Sea of Thieves services has been disrupted or lost. Please check your console's network status via the Settings > Network menu.'

@magnaxbox360v said in Cyanbeard error... AGAIN!:

@d0mino28 ha detto in Cyanbeard error... AGAIN!:

Restart your router/check console.
It's not the games fault.

'Cyanbeard means your connection to Xbox Live and/or the Sea of Thieves services has been disrupted or lost. Please check your console's network status via the Settings > Network menu.'

I'm playing from the computer, not on the Xbox.
Anyway now I try restart the router.

Err yes, a network error.

@magnaxbox360v The other games you mentioned are not cross platform. I do not know what the answer to your problem is, but the reason you don't have the same problem with the other games you have mentioned probably relates to the fact that those other games are not "cross platform" games.

@magnaxbox360v said in Cyanbeard error... AGAIN!:

Cyanbeard error again guys.
I restarted both the computer and the router.

How did you restart the router? ONLY remove power cable for 10 seconds, no button.
Disconnected from wifi and reconnected?

@magnaxbox360v I am also having the same problem no matter what I try and I dont understand why it won’t work if my innernet is connected and I’m signed into Xbox live no problem why it will not work

@katttruewalker okay thank you I will try this when I get home I hope it helps I really want to play this game

@MagnaXBOX360v & @MissAshley686 I got the same problem.

I played first in the second scale test, tried again in the third, and - obviously - now in the beta. I experienced these CyanBeard-Errors every time, usually after five to fifteen minutes, 30 at most.
I attributed it to the nature of the scale test, but since its all the same today i opened a support ticket.

According to the xbox app the live-service is running, multiplayer NAT-type open and server connected with 16ms latency and 0% packet loss. I even bought a LAN-cable today, just to make sure the powerline adapter i use normally aren't part of the problem.
The windows resource monitor (sorry if that's not how its named, i'm translating from german) doesn't report any packet loss either. My router has not a single error (not even a correctable one!) on the dsl line.
Since sea of thieves is the only game (or application, for that matter) that supposedly has some network issue, i don't think the problem is on my end (but of course i could be wrong).

If anyone had this problem and managed to solve it for him-/herself , please share your solution!

Anyone experiencing CyanBeards after a few minutes of game play: please leave a note here so Rare gets an idea how many player are affected.

Yes please other people having the same problem please comment to keep this near the top so rare can see and try to help us

Me and my friends have the same problem.
I wrote a support ticket last beta and they told me:
"This is an active bug that the test team are aware of. Your report has been sent over for further investigation. "
I hope they will fix it until release.

@katttruewalker thank you for trying to help but I did everything it told me to and it’s still doing the same

@la-sleepyraptor I have no one to play with I was trying to play solo with no luck I do not understand why it still keeps disconnected when everything is up and running

I have raised a support request concerning my repeated CyanBeard-disconnects one week ago (Friday, march 9th, to be precise), which was answered with a generic "thank you, we got your request"-message.
I made a second post detailing something i had tried but failed to fix the problem :

I connected my PC via LAN-cable, just to rule out my in-home connection as the source of the problem. Still CyanBeard's :(
I've attached the Xbox Apps Network Settings page below (everything seems fine tho :/)

My request was marked as 'solved' on Monday, without any further comment. Assuming my wording "everything seems fine" could have been misunderstood, I reopened the request with a detailed list of what i had tried to solve the issue over the open-beta-weekend, but stating clearly that the issue remained.

Today my request got closed as 'solved' without any comment again.

Considering this experience and the fact, that this issue hasn't even been official acknowledged (never made it on the - no longer accessible - knowen-issues-list during the beta and test-weekends, but every little cosmetic complaint did), I do not expect it to be fixed. At least not until Tuesday.
To me it looks like too few people have this issue to catch rare's attention, so instead they have devoted their time to the infinite pirate generator instead...

To sum it up: I'm underwhelmed with rare's support.

Is everyone who is getting this error using a VPN?

No, I'm not.

And before you ask: my xbox live connection is reported to be stable (service running, connected, nat-type open, ~20ms latency and no packet loss). So i would think it's not a teredo related problem in my case.

@magnaxbox360v Alebasterbeard for 2 days running since launch... facepalm! PC user and 0 tolerance left for this game.

I didn't pay money to sit and see DC errors all day long, i could just go and play an EA game for that c**p

Please read here for the possible solution:

https://www.seaofthieves.com/forum/topic/27653/connect-to-xbox-live-error-cyan-beard/34

Same problem here;

In Beta and scale test, no problems.
In game realease no problem (more 10h playing in stream with out problem)
NO problems with other games.
Xbox network status, is conected, nice ping and no lose packages
Teredo network is ok.

But since 2 days ago, every 10min almost 45, cyanbeard stole my time, my chest and hype to play... one and other and other time

I've got the same problem - I'm always disconnecting by the cyanbeard error after 15 - 30 minutes.

I have this error too. I play since the game released and to this day I can't normally play. 10-20 minutes and I kick from the server. I hope Rare will pay attention to this problem.