NAT Table Full on Router – Fix NAT Translation Table Exhausted

Quick answer for advanced users

Reboot the router to clear the table immediately. Then reduce the NAT timeout values (TCP timeout to 600 seconds, UDP timeout to 120 seconds) and limit simultaneous connections per client (512 max).

What's happening here?

Your router keeps a list of every connection going through it — that's the NAT translation table. Every time you open a web page, send an email, or stream a video, the router writes down where the data came from and where it's going. This table has a limit, usually between 1,000 and 10,000 entries on home routers.

When that table fills up, the router can't make new connections. Old connections might drop too. You'll see websites stop loading, apps say "no internet," and ping times go wild. This happens a lot on networks with BitTorrent, IP cameras, game consoles, or people who leave tabs open for days.

The real trigger is often a program that opens lots of short-lived connections without closing them properly. Think of a torrent client with thousands of peers, or a Zoom call that keeps pinging every 2 seconds.

Step-by-step fix

1. Reboot the router. Unplug the power cord, wait 30 seconds, plug it back in. After the lights come back (about 2 minutes), check if internet works. This clears the table completely but only temporarily — the problem comes back if you don't change settings.
2. Log into your router's admin panel. Open a browser, type your router's IP (usually 192.168.1.1 or 192.168.0.1). Enter the username and password. If you don't know them, check the sticker on the router or look in the manual. Common defaults: admin/admin or admin/password.
3. Find the NAT timeout settings. Look for sections called "Advanced," "NAT," "Firewall," or "Connection Limits." Exact names differ by brand — Asus calls it "NAT Passthrough," TP-Link calls it "Advanced Routing." If you can't find it, search for "NAT timeout" in the router's help.
4. Reduce TCP timeout to 600 seconds (10 minutes). The default is often 3600 seconds (1 hour) or even higher. That's way too long. Set it to 600. This tells the router to forget old TCP connections after 10 minutes instead of waiting an hour.
5. Reduce UDP timeout to 120 seconds (2 minutes). UDP is used for DNS, streaming, and gaming. Defaults are around 300 seconds. 120 seconds works fine for most things. DNS queries finish in milliseconds, so 2 minutes is generous.
6. Set a per-client connection limit. Find the option for "Max Connections per IP" or "Per-Client Limit." Set it to 512. Most home users never need more than 200 connections per device. This stops one machine from eating the whole table.
7. Save and apply the settings. Click "Save" or "Apply." The router might reboot. After it comes back, test internet on a few devices. You should see pages load faster and fewer random drops.

If the main fix doesn't work

Sometimes the router just can't handle the load. Here's what else you can try:

• Update the router firmware. Old firmware versions have bugs that leak NAT entries. Go to the manufacturer's support page, download the latest firmware file, then upload it through the admin panel. DD-WRT and OpenWrt users often need to clear the table manually with iptables -F -t nat from SSH.
• Disable UPnP. Universal Plug and Play lets apps open ports automatically, but they often don't close them. Turn it off in the router settings under "UPnP" or "Advanced." This might break some game consoles and smart home devices, but it stops a lot of garbage from filling the table.
• Switch to a router with a bigger NAT table. If you hit the limit often, your current router is too small. Look for routers with 4,000+ entries. Business-grade routers like the Ubiquiti EdgeRouter or MikroTik hEX handle 100,000+ entries. Consumer routers from Asus (RT-AX series) and TP-Link (Archer series) usually cap at 8,000–16,000.
• Use a dedicated firewall. For truly large networks (50+ devices), put pfSense or OPNsense between your modem and the rest of the network. These let you set the NAT table size to 1,000,000 entries and fine-tune every timeout. It's overkill for most homes but works perfectly.

How to stop it from happening again

Prevention is simpler than fixing. Do these three things once, and you're done:

1. Set the NAT timeouts as described above — TCP 600 seconds, UDP 120 seconds. Write them down so you can reapply after firmware updates.
2. Limit P2P and torrent clients. Most torrent software has a setting for "Global Maximum Connections." Set it to 200. Also limit per-torrent connections to 50. This alone cuts your NAT table usage by 90%.
3. Check your internet usage once a month. Look at the router's status page for "NAT Table Entries Used" or "Active Connections." If it's over 80% of the limit, you need to reduce timeouts or upgrade hardware. Most routers show this under "System Log" or "Statistics."

Real talk: I've seen NAT table exhaustion crash home networks more times than I can count. The fix is always the same — shorten the timeouts and cap the connections. Do that, and you'll never see the error again. If you still do, your router is too small. Spend $50 on a used business router and move on.