JavaScript is required to use

Getting Configured: A guide to configuring your NAT settings.

Q: What does NAT mean?
NAT is your Network Address Translation. If you're interested in knowing more, there are numerous sites that provide additional information. What matters for your Destiny experience is that your NAT Type is set correctly. If it isn't set correctly we have guides to solve your problem.

Q: What are the differences between NAT types?
  • Open or Type 1 NAT – Nothing is getting between you and your connection to Destiny. You get the best experience using voice chat, joining games, and matchmaking with players.
  • Note: Open or Type 1 NAT may not be possible in many configurations. 
  • Moderate or Type 2 NAT – This is the most common configuration. You may experience longer matchmaking times, issues with voice chat, or other problems.
  • Strict or Type 3 NAT – Strict or Type 3 NATs often indicate your console network settings are restrictive. With Strict/Type 3 NAT types, we have a harder time giving you the best possible experience, including voice chat with all players in your Fireteam. A Strict NAT or Type 3 NAT is not recommended and may cause noticeable problems.

  • Q: How can I change my NAT type?
    In addition to changing your console’s network settings, in order to get an Open or Type 1 NAT connection you will have to change your home network settings. Check out the guides on for information on changing your network’s NAT type.

    In order to get an Open/Type 1 or Moderate/Type 2 NAT type, you may also have to set up a Static IP Address on your console. Here are more links on how to do that for different consoles:

    PlayStation 4:
    PlayStation 3:
    Xbox One:
    Xbox 360:

    If you are playing on a PlayStation 4 or PlayStation 3 console, Sony has a support article on configuring your network to play on PlayStation Network:

    If you are playing on an Xbox One or Xbox 360 console, Microsoft has a support article on configuring your network to play on Xbox Live: 

    Port Forwarding: What it does and when to use it.

    Destiny can transmit and receive traffic on the following ports.  If your router and/or firewall blocks traffic on these ports, symptoms may include being unable to log into your platform service (Xbox Live or PlayStation Network), being unable to log in to Destiny, and/or frequent BEAVER/FLATWORM/LEOPARD (Kicked To Orbit events) errors while playing Destiny.

    Ports that should be unblocked to play the game:

    TCP outbound
    TCP inbound
    UDP outbound
    UDP inbound
    Xbox 360                                     
    53, 80, 3074
    53, 88, 3074, 1001
    53, 88, 3074, 1001
    Xbox One
    53, 80, 3074
    53, 88, 500, 3074, 3544, 4500, 1200, 1001
    53, 88, 500, 3074, 3544, 4500, 1200, 1001
    80, 443, 3478, 3479, 3480, 5223, 8080 
    3478, 3479, 3658, 3074, 1001
    3478, 3479, 3658, 3074, 1001
    80, 443, 1935, 3478-3480
    L3478, 3479, 3074, 20013478, 3479, 3074, 2001

    Configuring NAT, UPnP and port forwarding for Destiny
    Certain networking issues are related to having “strict” or “moderate” rather than “open” NAT.  Please note that an open NAT isn’t a magic bullet that solves all networking issues.
    Changing the UPnP or port forwarding settings on your home network can potentially solve the following issues:

    • Unable to hear voice chat from other players in your own Fireteam 
    • Frequent empty towers
    • Matchmade activities failing to find a game, resulting in ‘unable to find a match in time’/MONGOOSE errors

    If you aren't experiencing these specific problems, we strongly recommend that you don’t mess with port forwarding as it is a delicate procedure that may worsen your situation if done incorrectly. 

    If you are afraid that you may have forwarded ports incorrectly, don’t worry: it can be undone. Please try removing any existing port forwarding rules that you implemented for gaming and enabling UPnP in your router settings if your networking hardware is updated to a recent firmware. UPnP is also typically the best solution if you have more than one gaming console on your network as each required port can only be forwarded to one console at a time. If you have UPnP on and no other forwarding rules and the problem still occurs, or if your networking hardware/setup doesn’t support UPnP, ONLY THEN attempt to forward ports manually. 

    Ports to forward to your console to provide open NAT:

    Xbox 360 53, 80, 3074
    53, 88, 3074
    Xbox One   53, 80, 3074
    53, 88, 500, 3074, 3544, 4500
    PS380, 443, 3478, 3479, 3480, 5223, 8080 
    3478, 3479, 3658
    PS480, 443, 1935, 3478-3480
    3478, 3479

    NOTE: In general, Destiny should work well with most off-the-shelf consumer routers without any custom configuration.  Before opening or forwarding ports manually, we would recommend making sure that UPnP is enabled on your router, as well as trying to connect your console more directly to your internet uplink.  
    Also, port forwarding can be an incomplete solution at best if you have more than one gaming console behind your router – you may fix the problem for one console, while causing more severe issues for the other.

    Please note: Not all NAT Type problems can be solved. If you are on a university or corporate network, or if your ISP limits what type of traffic you can send/receive you may have a NAT problem that is out of your control.

    Return to Network Troubleshooting Guide
    preload icon
    preload icon
    preload icon
    You are not allowed to view this content.