What are the fat red arrows under the latency plot? How bad is it and what is the cause of these? I am not an expert but the latency seams bad across the board and there is some jitter too. What could the 4th hop be? Somewhere at my ISP? Or even closer like the the optic fiber terminal in my building? Do these results indicate it is defective? From my understanding these problematic hops are near me and the first one is probably my modem right? SALT is the name of my ISP and the Modem is called Salt_Fiber_Box. It seams there is always 49 to 66%(!) packet loss on 1st and 4th hops. (most general address I could think of)ī (First gaming server I came up with)
Pingplotter fluctuation pro#
I ran PingPlotter pro 14 days trial for a few hours on the only PC that is wired to the modem. On mobile some apps get stuck or send "unable to reach server" messages for some minutes. Getting error messages on Youtube and unable to play videos for a few minutes.Īll of the above issues happened on multiple browsers and multiple devices, wired and Wifi. Random "Could not reach server" on startup from some apps. Youtube music videos stopping and restarting without intervention. Pages not loading for 4-5 seconds or sometimes longer. No reaction for long seconds when clicking links. On the network, at this time, there is 1 device that is wired with an Ethernet cable, 1 with WiFi 5Ghz and 4 WiFi 2.4Ghz.
Recently we started having way more problems than we used too, although we might have gotten increasingly sick of it too. I changed ISP around 2 years ago and it always felt like a pretty noticeable downgrade in quality even though I went from a 1 Gbit fiber to a 10 Gbit fiber plan. Here is all the information I think might be relevant: I followed u/ktfzh64338 and u/CFSworks (many thanks) indications and I need help to diagnose the problem(s) shown in PingPlotter.
Pingplotter fluctuation software#
This is a great article with some scenarios to look for.So, last week I asked this sub for recommendations on what software to use to gather data and assess the problems. Gaming and VoIP have many similarities in their latency requirements.
Switch to using the TCP packet type ( ), which is allowed through the WoW firewalls (since that's what 'language' the WoW servers talk). Once you have your server's IP, then you can try tracing to it - although Blizzard/WoW blocks ICMP at their border, so you'll need to use PingPlotter's TCP packet type to get all the way in. Look for your server by realm/location.Steps 1-4 here will walk you through discovering your IP address There are several ways of getting this information: Finding your server's IP addressįirst, you'll need your server's IP address.
Pingplotter fluctuation how to#
PingPlotter can trace to World of Warcraft servers! Here are some tips and links on how to make that work. How do I find my server, and how do I trace to it? Using PingPlotter to troubleshoot World of Warcraft
0 kommentar(er)
