Loading…
code:snake is different from the connection errors above. Respawn has never documented it, but it's widely associated with account-level restrictions — players report hitting it on accounts that were flagged, restricted, or matchmade into limited pools. Treat a persistent code:snake as a signal to check your account standing, not your router.
If code:snake persists across days and networks, check whether the account has been actioned. Look the account up on a ban tracker, check email linked to your EA account for enforcement notices, and review EA's ban history page for the account.
Account restrictions can only be reviewed by EA. Open a case through EA Help with your account details; third-party tools and reinstalls will not clear an account-level flag.
A single code:snake during a server incident is noise. Restart, try again later, and only escalate if it's persistent and specific to your account.
This code is commonly associated with account restrictions. We track ban events across the ranked ladder — look the account up here.
Not necessarily, but it's the error code most commonly associated with account restrictions. If it persists on your account while other accounts on the same connection play fine, check your account standing with EA and on a ban tracker.
No. If the code is tied to an account flag, it follows the account, not the installation. Local fixes only help in the rare case where it was a mislabeled server error.
Respawn doesn't publish an official meaning for most of these codes. These guides are written from community troubleshooting and the patterns we see across tracked accounts. Your progress through the steps is saved on this device.