I wanted to take the time to share a few things I've learned during my time troubleshooting ping/disconnect issues for the past year or so in hopes that it will help ease some frustration many of you have who are suffering from similar issues. There are a few things to consider/troubleshoot when you're facing issues. The first few steps are going to be the "usual" stuff, so more than likely you'll need to skip to step 3.
For the purpose of this thread, I'm going to focus on the following symptoms:
- 999+ Ping (or higher than your usual)
- Disconnecting to login screen (not hard crashes to your desktop)
- Rubberbanding (example: everyone stops moving... and then after a few seconds, everyone/skills move at 2-3x speed for a second or two)
- Skills not casting, interacting with objects not working, or taking multiple attempts
Before I go any further, if you ever have the above issues, please take a second to fill out the survey from ZoS to help isolate where the issues are coming from:
👉
[Survey Link](https://feedback.bethesda.net/jfe/form/SV_5dLZWx81Em0b3oO?utm_source=Bethesda)
---
Step 1) Check Your Drivers, Windows Updates, and Repair ESO
I know, I know... but you'd be surprised how many issues will be fixed by doing this. Now, I'm going to assume you already did that, so let's move on.
---
Step 2) Use a Wired Connection If Possible
- If at all possible, ensure you're connected via a wired connection.
- If you must be on WiFi, consider getting a WiFi repeater and placing it closer to your device if the connection is poor.
If it's not a WiFi/wired or driver issue, let's move on to the meat of this guide.
---
Step 3) Disable All Add-ons and Test
- Do you still run into the issue?
- Large add-ons like RDK/Bandits can sometimes contribute to underlying issues.
- Running the next step without add-ons will help diagnose the problem.
---
Step 4) Use PingPlotter to Monitor Your Network
A network monitoring tool like PingPlotter helps track your ISP’s routing path, latency, and packet loss.
*I won't link it here to avoid breaking forum ToS, but a quick Google search will find the free version.*
---
Setting Up PingPlotter
- Pick an IP or domain to test (I always test 8.8.8.8 for Google DNS and the ESO server IP so I can compare the two).
- NA IP Addresses: 198.20.200.1
- EU IP Addresses: 159.100.230.1
- Open PingPlotter and enter the IP/domain in the address bar.
- Set the interval (e.g., 2.5 sec for real-time tracking, 15 sec for long-term tracking).

---
Start Monitoring
- Click the green play button to start testing.
- Watch as hops appear, showing the data's route through different network points.
- Let it run for at least 5-10 minutes for quick testing or 24+ hours for deeper analysis.
- You don’t have to be in-game while testing, but linking in-game issues to PingPlotter data helps significantly.

---
How to Read the PingPlotter ChartTop Section (Hop List)
- Hop: Each router/server between your device and the destination.
- PL% (Packet Loss): Percentage of lost packets at each hop.
- Latency (Avg, Min, Cur): Time (in milliseconds) for data to travel.
Right-Side Latency Graph
- Green Zone: Good latency (fast response).
- Yellow/Red Zones: Increasing latency (possible issues).
- Red X’s or Gaps: Packet loss (dropped data).
Bottom Section (Time Graph)
- Black Line: Latency over time.
- Red Vertical Lines: Moments of packet loss.
- Spikes Up: Higher latency (laggy periods).
---
Key Observations from My Screenshot1. Latency (Ping) Issues
- The latency (round trip time) increases significantly around Hop 12 and beyond, reaching 55.1 ms at the destination.
- Some latency spikes are visible in the bottom graph, but the average remains stable.
2. Packet Loss
- Hop 6 has 35.6% packet loss, which could indicate a network congestion issue or ICMP deprioritization.
- Hop 12 shows 6.8% packet loss, which might indicate some degradation in connectivity.
- The final hop (198.20.200.1) has 1.7% packet loss, which is minor but could still impact performance.
3. Latency Spike & Packet Loss Event
- The red vertical line in the lower graph marks a moment of significant packet loss or a network drop.
- A latency spike (black line increasing) occurs before the
--
Now What?
Once you have gathered your PingPlotter data, it's time to analyze and compare the results.
- Run the test using both the ESO IP address and a known reliable IP, such as Google DNS (8.8.8.8).
- Compare the results—do you see packet loss, higher latency, or instability on both, or just on the ESO server?
If packet loss or high latency is present on Google DNS (8.8.8.8):
- This indicates a potential issue with your ISP.
- Contact your ISP and open a support ticket.
- Provide them with the screenshots of your PingPlotter results.
- If you can run these tests for multiple days, it will help justify your case that an issue needs to be addressed.
If packet loss is not present on Google DNS but is affecting ESO’s IP:
- ESO doesn’t handle packet loss very well, so even minor issues can cause major gameplay problems.
- If you see red lines (packet loss) while testing ESO’s IP, check whether you experienced any performance issues in-game at that time.
- If you did, this is important information that should be shared with the ESO team.
If you didn’t experience issues during the test:
- Slowly start re-enabling your add-ons, one or two at a time.
- Play normally and see if the issues return.
- If the issues start again, you’ve likely found an add-on contributing to the problem.
Still Nothing?
- At this point, the issue might be outside the scope of this thread.
- Consider checking for CPU/GPU overheating, system load issues, or other hardware-related problems.
- Monitoring system performance while playing could help identify any resource bottlenecks affecting gameplay.
If you've gone through all these steps and still have issues, it might be time to dig deeper into hardware diagnostics or advanced network troubleshooting.
Edited by LadyGP on February 26, 2025 3:21PM LadyGP/xCatGuy