AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Pingplotter trace from me4/9/2023 ![]() ![]() You’ve got some data and a good idea of what to do next. Now you’re set to begin making your case. The next step is gathering the screenshots, sample sets, and other PingPlotter data you’ve collected to present your issue. If you need help finding the contact info for a service, we’ve gathered resources for many of the most popular providers out there. Got ‘em! If you can’t find the details on the hop’s owner, it’s best to default to your ISP as a point of contact. Time to spin this puppy up Enter the target DNS name or IP address into the Target Entry field and hit the green Start button. By taking the IP address or DNS name from the offending hop and doing a WhoIs lookup (from a site like who.is), you can usually find the organization and/or contact info for the responsible party. Step 2: Trace it PingPlotter Getting Started Guide Step 2: Trace it You’ve got PingPlotter installed and ready, and you’ve got a good target to trace. Luckily, you already have the best weapon for this fight: evidence!įirst, let’s find out who to talk to. ISPs and other service providers get the “it’s your fault” all the time, so they’re going to need some serious nudging before they listen. Got it out of your system? Good, because here comes the bad news: You probably have an uphill battle ahead. Good news? It’s not your fault! Woo! Get dunked on, tech support! U-S-A! U-S-A! ![]() If the network trouble seems to be originating somewhere outside your direct control, there’s - you guessed it - good news and bad news. Once you find a cause that matches, you’ll be all set to put this problem to bed! It’s somewhere other than me! We’ve collected a list of the usual suspects here, complete with graphs to help compare your data. To figure out the cause of the network issue, you need to start looking closely at the symptoms of the problem and the patterns you see in PingPlotter’s data. The good news? The ball’s in your court! Since the problem’s happening within your sphere of influence, you will hopefully be able to take care of it right away. You’re going to need to dig a bit deeper and figure out what’s causing the problem. ![]() If the network trouble seems to be originating from your end, there’s good news and bad news.īad news first: The ball’s in your court. Take a look at your collected data and see on which hop the latency and/or packet loss seems to originate: Oh crap! It’s hop one! I broke it! ![]() You can test these scripts by double-clicking them once you get them extracted. The PingPlotter install directory will work fine. The next steps are directly tied to where the problem starts. Download the start and stop scripts from here: Extract these to a directory of your choice. If the start of a route is squeaky clean, you can begin to rule out internal factors. Why? That’s simple: it’s you! Nasty red stuff at hop one usually means something on your end is causing the frowny face. If the final hop is the most important, the first hop is a close second. Now enter it into the WinMTR window:Īnd hit Start! Be patient with the traceroute, it can take a few minutes to complete.Remember this graph? We identified the captured data was a good snapshot of a possible issue, so let’s dive a little deeper. To do this, take the name and number of the voice server you're connected to (in the case above, mine would be "us-south495") and add ".discord.gg" to the end of it. Now that we have all the information we need, it's important to type the correct IP into the WinMTR window. Second, click the "Voice Connected" icon to pull up the voice server specifics. Next, connect to the voice channel you're having ping issues on. Go to User Settings through the cog wheel at the bottom left corner > Advanced > enable Developer Mode. To do that, you first need to make sure Developer Mode is enabled. We'll need the server name and number in the "Host" box to get the specific traceroute for that voice server. When you start the program, you'll get a small box with a couple of windows and some drop down menus. You'll get a document folder containing the WinMTR file. Open the zip file, and extract the program file. To gather the necessary details, follow these steps:įirst, go to WinMTR's download page. You'll have a choice to select either the 32 or 64 bit version of WinMTR. Downloading the file from either link will give you a zip file with both versions, so if the 64 bit doesn't work, you can use 32 bit anyways. With the combination of traceroute, ping, and whois, PingPlotter enables you to collect data over time and graphically present it, thereby providing you. If you've gone through all the troubleshoot steps to improve ping spikes in your connection to voice channels, running a WinMTR can give us extremely useful information about your connection. At Discord, we're always taking steps to improve connection stability and ping spike issues for users experiencing issues. ![]()
0 Comments
Read More
Leave a Reply. |