Field note · Updated · Jay Fan
A NAT label tells you who can join. It does not grade your delay.
NAT type is the console’s name for how freely unsolicited game and party traffic can reach you through the router. Xbox prints Open, Moderate, or Strict. PlayStation prints Type 1, Type 2, or Type 3. Nintendo Switch prints A through F on its connection test. A stricter label can block an invite, a host, or a voice channel. It does not, on its own, raise the delay to a distant server, and an open label is not a latency score. We have not published an Xbox, PlayStation, or Switch NAT capture.
Symptom
What does party trouble look like when NAT is even plausible?
The session never quite becomes a session. The invite spins. You can join one friend and not another. Party chat is one-way, or you hear nobody while they hear you. The match moves off you the moment you try to host. Those are reachability symptoms. The console’s NAT line is a fair first label for them, because the vendors define the labels in terms of who can connect to whom, not in terms of a delay figure.
Xbox’s live documentation names three settings. Open can connect with any of them. Moderate can connect with Moderate or Open. Strict can connect only with Open. A fourth value, Unknown, means the service response was not recognized. Nintendo’s matchmaking article describes the Switch connection test from A through F: A is the peer-to-peer-friendly end, B works with most other types, C has trouble with more restrictive types, D generally connects with A, and F does not complete peer-to-peer play. Sony’s Remote Play note says a Type 3 result can block that feature. The same family of connection test is where a PlayStation prints Type 1, Type 2, or Type 3.
“Party lag” is a sloppy name. If the party already formed and the complaint is that everyone feels late, or that characters snap, you may already be past NAT. Write one sentence before you open the network screen: cannot join, one-way voice, cannot host, or the match feels late. Only the first three put the NAT letter in the lead. The fourth belongs on the delay-and-loss note.
What does a strict label leave unexplained?
A Strict, Type 3, D, or F result does not explain a large flat delay on a match you are already inside. The packets of that match found a way through. Whatever remains is delay, missing packets, or a client hitch, and those use different instruments. An Open, Type 2, or Type B result does not explain them either. On PlayStation, Type 2 is the ordinary “this console is behind a router” label. It is not a failed test, and it is not a speed grade. Type 1 has long meant the console is sitting directly on the internet, without a home router doing translation. Read the word your own test prints rather than a forum screenshot from another firmware year.
Nintendo’s connection-test page describes Type A as best for peer-to-peer communication, and Type F as unable to complete it. That use of “best” is about whether peers can reach each other. It is not a ranking of delay, and this site will not treat the letter as one. A download or upload figure printed beside the letter is a throughput grade. Nintendo uses a low download figure as a separate reason matchmaking might time out, once the NAT letter is already A or B. That grade is still not your delay shape. Do not fold it into the letter and call the combination a ping.
A strict label also does not explain a snap that hits every player at the same second, including people who do not live in your house. Their consoles are not behind your router. Keep the game name and the approximate time for the publisher’s status page. Your NAT letter is a weak story for a shared timestamp.
Troubleshooting steps
How do you read the test the console already runs?
Run the built-in test and copy the label. Do not start by forwarding ports copied from a forum. Menu names move between system updates. If the path below does not match your firmware, use the vendor page linked in the last column and write down the label the current screen actually shows. We did not run these tests on a console at this desk.
| Console | Where to look | Labels you may see | What the vendor pages support | What this page will not add |
|---|---|---|---|---|
| Xbox | The network settings screen. The NAT type line is on that status view. | Open, Moderate, Strict. Unknown if the service response is not recognized. | Who can connect to whom, from the Xbox Live NAT setting definitions. | A delay figure, a packet-loss percentage, or a claim that Open is a faster route. |
| PlayStation 5 or PlayStation 4 | Settings, then Network, then the connection test. Sony’s Remote Play steps for a PS5 test are Settings, Network, Connection Status, Test Internet Connection. | Type 1, Type 2, or Type 3. | Type 3 can block features such as Remote Play. A PS5 connection error page also says to remove a stack of NAT routers. Type 2 is the usual behind-a-router result. | A claim that Type 1 lowers delay. A copied port list. A second change mixed into the same retest. |
| Nintendo Switch | System Settings, Internet, Test Connection. The result list includes NAT Type, plus download and upload figures. | A, B, C, D, or F. | A and B are the peer-to-peer-friendly end. C is partial. D generally reaches A. F does not complete peer-to-peer. If A or B still fails to find a match, Nintendo points at delay and the speed lines. | A DMZ recipe or a forward of every port. Nintendo mentions those as admin steps. They are not repeated here. |
Sources, read November 5, 2026, for the label meanings rather than for a measurement of our own: Xbox Live NAT setting definitions for the Open, Moderate, and Strict model, PlayStation Remote Play connection troubleshooting for Type 3 and the connection-test path, PS5 error NW-102468-1 for the multiple-router warning, and Nintendo’s connection test plus matchmaking NAT notes. If a vendor page moves, trust the test on the console over a cached copy of this paragraph.
Which single change is allowed on the next try?
- Write the symptom sentence and the party host. If you are the host, your label is the one everyone else has to be able to reach. If someone else is the host, your strict label can block you from them even when their session looks fine on their own screen.
- Run one console’s test. Copy the NAT label. On Switch, also note whether the internet-connection line said success. Leave the speed grade unread until you know the symptom survived an open label.
- If the symptom is join, voice, or hosting, and the label is at the strict end, change one thing the vendor already describes. If a modem and a second router are both translating addresses, Sony’s connection-error page tells you to remove that stack. Otherwise follow that vendor’s current document for UPnP or for a port it actually lists. Then retest the same party host. Do not also move the console from wireless to a cable in that try. The cable is a different experiment, on the Wi-Fi note, and many Switch sessions have no cable at all.
- If the label is already at the open end, do not “improve” it. There is nothing for a port forward to explain about an invite that already succeeds. Go to the next section and switch instruments.
- If two consoles in the same house disagree, write both labels before you buy anything. A guest network, a second router, or a wireless extender can put one device behind an extra translation. That is a topology note. It is not a measurement we are publishing, and it is not a reason to forward every port on both boxes.
Void the try if a game update ran during it, if the party host changed, or if you restarted the router and switched from wireless to wired at the same time. A void row stays in the notebook. The next row starts clean.
| What you see in the party | NAT can be the lead | NAT is a weak story | Next single check |
|---|---|---|---|
| Invite fails, or only some friends can join | Your label and theirs sit at a strict pairing: Strict with anything but Open, Type 3 with another restricted type, D or F with anyone but A. | Both labels are already at the open end. Another forward will not invent a missing friend. | Copy both labels. Change one documented router setting, or remove a second translating router. Retest that same host. |
| Voice is one-way, match otherwise exists | Voice can fail to open a return path even after the game session did. A strict label is a fair suspect. | The game itself is snapping or showing a loss mark. That is a different shape. | Stay on NAT for the voice path only. If the picture is the problem, switch notes. |
| You cannot host, others can | Hosting needs unsolicited inbound traffic. Strict, Type 3, D, and F are the labels vendors tie to that limit. | You are not the host, and the person who is hosting has the open label. Your letter is not their route. | Confirm who the host is. Retest with that fact held still. |
| Everyone feels late, or everyone snaps together | Rarely, once the session has already formed. | A shared timestamp outside your house is not your router’s inbound filter. A flat high number is not a NAT grade. | Leave this page. Name the delay shape on the other note, or check the publisher’s status if the timestamp is shared. |
When to switch measurement method
When should you stop reading NAT and switch instruments?
Switch as soon as the symptom is no longer “who can reach me.”
Nintendo already draws this line in public. If the connection test says A or B and matchmaking still times out, their article says the network can be fine for peer-to-peer play and that delay may be what expired the search. That is a vendor telling you to leave the letter. Use the delay-and-loss note and name the shape: flat and high, jump and return, or a hole. The Switch download and upload lines are the wrong shape even then. They are bulk figures. A low one can explain a timeout during matchmaking. It does not tell you whether a match you are already in is flat, jumpy, or losing packets.
Switch when the match has connected and the complaint is rubber-banding, a loss mark, or a steady high number. The NAT test will still print a letter if you run it again. The letter is not the instrument for that match. A Strict result beside a connected match only tells you that hosting the next lobby may be hard. It does not locate the hitch inside this one.
Switch off network labels entirely when the picture hitches and the network line the game shows is calm. NAT cannot draw a frame, and neither can a port forward. Valorant, Tarkov, WoW, and Genshin are where a specific HUD word matters. This note does not borrow their session checklists.
Stay on NAT when the invite fails, voice is one-way, or only the strict pairs cannot see each other, and you have not yet done one vendor-documented change plus a retest with the same host. Stay on it when two consoles in one house print different letters. That disagreement is still a reachability fact.
Do not switch by changing DNS, enabling a DMZ, and moving to a cable in one evening. A resolver answers names. Once the console is already online and names resolve, the party problem is either inbound reachability or delay. Those are two files. This is only the first. The August 19 web-edge record is a Windows tunnel to public and publisher websites. It has no console and no NAT letter. It will not settle an argument about Type 3.
A private first sort, before you spend the evening in router admin, is still Diagnose lag. Pick the symptom that matches the sentence you wrote. The tool does not read your NAT line, and it does not store the answer.
Questions readers ask after mixing the labels up
Does an open NAT label mean the delay number is lower?
No. Open, Type 1, Type 2, and Type A or B describe how inbound party and match traffic is filtered. They are not a delay measurement. A console can print an open label and still sit on a distant server with a large, steady delay.
Why can I join some friends and not others?
The other person’s label matters as much as yours. Xbox’s definitions say Strict connects only with Open, and Moderate connects with Moderate or Open. Nintendo says Type D generally connects with Type A, and Type F is not set up for peer-to-peer play. That is a join question, not a delay grade.
Should I put the console in a DMZ or forward every port?
Not from this page. Nintendo’s matchmaking article mentions a DMZ and a very wide forward as steps for an ISP or network admin. This site does not repeat that range. Use the vendor’s current document, change one setting, and retest the same party host.
Party chat is one-way, but the match delay looks ordinary. Is that NAT?
It can be. Voice and game traffic are not always the same path, and a strict label is a fair lead for one-way chat or a failed invite. If the match is already up and the complaint is rubber-banding or a loss mark, switch to the delay-and-loss note. NAT is the wrong instrument for that shape.
Do you have a console NAT capture from this desk?
No. We have not published an Xbox, PlayStation, or Switch NAT test. The labels on this page are the names the vendors print, not a lab result, and they are not a ranking of routes.
Editorial log
November 5, 2026. First publication by Jay Fan. No console NAT capture is attached. Labels are quoted from vendor documents. Corrections: [email protected].