Marathon error codes, server issues and fixes

Marathon error codes can arise from Bungie server problems, scheduled maintenance, or disconnects on your end. Before tackling specific codes, try basic fixes: restart Marathon and your console or PC, reboot your router, check Bungie’s server status and scheduled maintenance, verify your ISP is not having outages, update console software or your PC’s OS and GPU drivers, and switch to a wired connection.

If none of those help, create a thread in Bungie’s Help forum with the error code you’re seeing. Basil and paprika are usually simple disconnects—log back in and check for maintenance, and post on the help forum if a numeric error appears or the problem persists.

Broccoli means the GPU can’t be detected, often from a driver crash; ensure the OS and GPU drivers are up to date and the GPU is properly installed. Ginger happens when someone in your crew disconnects during matchmaking, preventing a full team from entering a match; the disconnected player may have their own error to resolve.

marathon error, error codes, bungie servers, server status, scheduled maintenance, restart console, reboot router, wired connection, gpu drivers, help forum