What is Reddit's opinion of
PingPlotter?
From 3.5 billion Reddit comments
100 reviews of this app found across Reddit:
It's possible lag could be coming from your router as well. The way I found out one of my routers was going bad was to run a traceroute (command is "tracert [IP]" on Windows) to Riot's servers, and the 1st few connections were giving the most ping, meaning the router itself was having problems connecting. An easier way to visualize it is to use a free program called PingPlotter to see the fluctuations. For example, here's a ping plot of before and after resetting my old, dying router.
Sounds like it may be time to track your internet performance and hit them with hard data. I had Cox in Phoenix for about 8 years, and had multiple hour outages 4-7 times a week. Turned out to be 10-40% packet loss due to my neighborhood node being overloaded with people/their hardware not being able to handle all the bandwidth. Completely fucked up both my wife and I's ability to work from home.
Check out Ping Plotter https://www.pingplotter.com/ - it's easy to use, has a free trial (or at least did when I used it), and will give you hard data you can take to Cox and the FCC showing how frequent your outages last and what is causing the outages. Always run this from a wired connection, WiFi can have similar issues that are not related to your ISP.
I like PingPlotter - https://www.pingplotter.com/ Shows where the slowdowns are too EDIT: should note I'm not affiliated with them in any way - used it once to show Google Fiber a problem and they fixed it
That would be best. Also, ping-plotter is a much better MTR tool because you can view the history. So you can just leave it running all the time and zero-in on problem times:
Live near Westport and get the speeds promised (on fastest TWC plan).
Some problems I've ran into / troubleshooting:
- Make sure the modem they provided is the right one. Verify that it can support the fast speeds.
- Use the modems built in router. I was using mine as a bridge to a Linksys router and it caused major issues. I was only getting 20-30 MBps. When I skipped the Linksys router and used the modem as the router, my speeds went up to 300ish.
- As others have said, test it on a wired connection. ALSO make sure your cable is Cat 5e or Cat 6.
- Check for packet loss. Use something like https://www.pingplotter.com. I was getting MAJOR packet loss from the first jump outside my house (you can tell by the IPs of each jump). I posted this information on http://dslreports.com and a rep from TWC on the forum sent it to the right people. Ended up being some squirrels or something damaged main line to the neighborhood.
If you want more information use pathping instead of tracert. That also gives you an idea in regards to packet loss (use WinMTR if you want a GUI).
Should you be interested in monitoring over a longer time period you can use PingPlotter. Gives a nice graph of how your ping/packet loss develops over time.
Try using PingPlotter to see where the issue lies (if it’s your router, Shaw servers, etc.). Try running it for the duration of the time you experience disconnections. That might be able to at least tell you where the problem is happening if it isn’t your router/modem.
Hope that helps at least a little bit, have a good night!
I got a bunch of packet loss yesterday. I used pingplotter and found something was broken between my end and WoT :P
use this address: wotna3.login.wargaming.net
If you use ping plotter you can find where the issue is.
If you "have good ping everywhere else" that just means the network path to those destinations isn't experiencing issues.
Pingplotter will figure out where the issue lays. The issue doesn't have to be the server or you, it can be anyplace between the two.
https://www.pingplotter.com/download
https://www.pingplotter.com/fix-your-network/interpret-results.html
Server Address: >wotna3.login.wargaming.net
https://www.pingplotter.com/fix-your-network is a great guide to finding out where on the network the problem is, if that is where the issue is.
I'd definitely recommend it to the OP as a place to start, given those symptoms. If it is a GGG server issue, email their support team directly about it, rather than just reddit post.
If you haven't tried it, I would recommend Ping Plotter. I liked it so much that I bought it but it offers a lot of functionality in the trial for free. Try out the free version here: https://www.pingplotter.com/products/free.html
Here's my trusty copy pasta. Queue a bunch of games on your region of choice, and you'll end up with a bunch of server IPs in your game log. You'll have to exhaustively collect each one though if you wanted to see all the current servers, but you don't need all of them for this. One will do if it shows a problem in your ISP's systems. So as long as you log one game where you're experiencing the problems you describe, that should do it.
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Since you've checked your server region, the below might help you locate the problem:
(But please people stop thinking bandwidth and latency have anything to do with each other.)
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Hey there!
I am no expert but try to help wherever possible, you have provided a lot of info here but it’s slightly hard to follow. If it’s easy enough a mud map (layout of your 3 levels with important pieces of equipment marked on it) might help diagnose your issue.
One key piece of info you seemed to have left out is the distances between all devices concerned, you should be able to rely on the mesh test for what the internal “puck to puck” connections are but it’s good to know the physical distance is potentially an issue.
For your suggested solutions I wouldn’t be going to your provider just yet, if you’re getting 200-220mbps that is way more than enough to stream 4K but there are so many factors in actually doing that all the way from where the content is being sent from to how your device grades the content which is to say some streaming services won’t automatically adjust quality and will just wait for ever to buffer 4K on a shitty internet service while others will adjust to suit your internet speeds.
I would firstly test your internet speed several times in different locations but with the same device each time. If you for example test on a laptop right next to the main mesh puck then as far from it but in the same level and then repeat for each level of the house to see if the distance is causing an issue. I would also suggest using Ping Plotter for this testing, download and upload speeds are important but I think people in general don’t understand that they really don’t mean everything. Using PingPlotter you can see how quick your internet is plus see any drop outs or packet loss for specific sites so you can get much better analysis plus can run in the background rather than an instantaneous result that may not identify intermittent issues.
OK, so your handover point is the cable modem. This probably has gone to NBN and they've got graphs which show your signal to noise ratio and signal strength from your cable modem over the past 24 hours / week etc. This is one of the things the engineer at NBN looks at to determine whether your cable modem is talking back correctly. They also see stats from your cable modem about uptime, how long it's been online etc.
NBN will refuse a tech visit unless something is out of spec on the RF (coax cable) side of things, or you've got more than say a drop a week. I don't know the exact numbers, but if you're connection is bad, you're going to get dropped .. like... 40 times a day. If it's twice per day, it's probably other interference, which isn't just affecting you (Power issues?)
For all they know, if you're insisting on using wifi, the times it's dropping out are actually when you're using your microwave (which also operates on 2.4Ghz) and you're saying that's NBN's fault, or it could also be interference from your neighbours house or something.
It's not NBN's problem to determine the cause of that fault, they're not there to fix your home network. Their handover point is the cable modem.
You'll need to get logs which show what's happening on your side with the drop outs etc and see if NBN can match that to something that's happening on their side.
Get something like ping plotter:
https://www.pingplotter.com/products/standard.html
ping something like google at 8.8.8.8 or Cloudflare at 1.1.1.1
See when it's failing; and if it's failing after a similar amount of time each time, or if it's at regular times etc etc then that gives ABB the information they need to go after NBN, or otherwise help you find the offending piece of equipment that's breaking things on your side.
traceroute means you would be pinging the server as well as all the routers that your data has to travel through to get to that server. There are complications that can muddy the result. But most of the time, if a router (or its preceding hardware) is being slow, then you should see latency in pings to all subsequent routers and the destination server. Not only that, you should see the latency repeated when you run successive traceroute tests. That's how traceroute functions as a good tool to diagnose latency issues.
To see these all visually, it's best you use a software with GUI (graphic user interface). pingplotter comes to mind.
Try pingplotter https://www.pingplotter.com/ to see if you can see where the latency is. You'll need to figure out the IP address of the game server.
I doubt it's the eeros causing this -- I get a pretty constant 35ms to the World of Warships servers.
I also work for an ISP, we mainly service rural areas and we use a wireless connection from tower to the residence, so speed issues are a constant thing for us. I'd strongly recommend Ping Plotter and PRTG I use both to monitor my customers and have had a good experience with each, I even run PRTG on my home network.
Best thing you can do is record, record, record. I would watch your network for at least 24 hours, though personally I would recommend at least one week, therefore you can get a baseline as to what your network looks like over an extended period of time. If you see the problem is outside of your network, call your ISP and report your findings, see if you can present them with your evidence as well. However if you see the problem is internal, we'll need to take another look at your network and see if you have a bottleneck somewhere (best way to test is to plug a computer directly into your modem and run a speed test) Good luck to you!
We need to get an MTR. Get the free version of ping plotter:
https://www.pingplotter.com/products/free.html
Install it. Open and and point it to: tagpro-chord.koalabeast.com
Run a test for about an hour, leave it running in the background while you are playing and make sure it's running when you get one of the DCs.
Then send the results to me.
I was having huge amounts of ping on everything the past weeks, which made playing any games enjoyable impossible, then found out it was my ISPs issue due to routing through an over-saturated/needs maintenance done to it node. My net restarted today and I am now connecting through a different node and experiencing zero lag and packet loss. Contacted them and they said they are doing work on the node I used to connect to and the issue should be fixed when they are done.
I'd suggest downloading Pingplotter and seeing where you are getting the connection issues at. It's like a constant running tracert that also has nice timeline graphs so you can easily see your ping and packet loss at each node. This is from yesterday when I was connecting through the bad node http://puu.sh/o9DDH/bc951d94d8.jpg to a random deathmatch server. As you can see the 2nd hop is causing massive issues with a jitter of 101 and an average ping of of 92. You can also see from the top timeline graph the high ping and packet loss, the large red bars are lost packets and the horizontal red bars at near the top of the graphs mean ping that is higher than the number on the left, in this case 476. I am now connecting through a different node and having zero issues what so ever. If you are getting high ping at one of your ISPs nodes, in my case TWC/RR (laugh it up, they're all I got where I live), contact your ISP and tell them about it and provide the evidence from pingplotter. Idk if this maintenance on this node has been coming but I literally talked to the support yesterday about getting maintenance done on it but the level 2 tech can't schedule that and I had to call them back during regular hours. I never did and they are preforming maintenance on it today.
I've had problems on-and-off with severe latency issues for all most a year now. Using PingPlotter, the problem all ways arises at the network nodes with "wargaming" in their DNS names (like this). The only way I have found to get stable network quality is by a third-party paid VPN-service specialized for gaming.
I live in Oslo with gigabit fiber connection (but Wargaming support still thinks the problem is with my connection, go figure)
It's probably not mts. I've heard it from others too.
Best course of action is to make sure you hard wire your box to the router. Get one with QOS to stop others from hogging all your bandwidth, mainly upload, as that's the easiest to fill.
secondly, if you want to track it down, run ping plotter on a second machine while you're playing on the original machine, to the server you're connecting to. it will show you where the lag is occurring..... maybe. if it comes back clear then it's something within the game.
Have the MTR ready, but don't start it until you start lagging out. That way we get a contained sample and not a bunch of the time that it's running fine.
Or just use pingplotter, which is what I do:
> Wie messe ich denn den Paketverlust?
Damit zum Beispiel:
https://www.pingplotter.com/download
Ich vermute mal, dass bei dir regelmäßig Packetloss vorhanden ist. Einfach mal über längere Zeit laufen lassen (48h+), während man das Internet normal benutzt.
Da sieht man sehr schnell, wenn Paketverlust auftritt.
Dann hast du höchstwahrscheinlich einen Rückwegstörer.
Da hilft dann echt nur, immer wieder anzurufen.
Rückwegstörer können garstig sein. Gerade wenn man in einem Wohngebiet mit lauter Einfamilienhäusern wohnt und Vodafone dann bei 100+ Häusern rein muss, um den Störer zu finden. Das kann Monate dauern, wenn man Pech hat.
Falls es dich aufmuntert (tut es nicht), bei mir war 5 Wochen das Internet wegen so einem Problem unbenutzbar, 17 Tickets bei Vodafone (die werden anscheinend von einem Automatismus sofort als gelöst geschlossen, wenn das Internet mal wieder für mehr als 30 Minuten funktioniert), über 20 Anrufe, 5 Technikerbesuche und 1 Email an die Bundesnetzagentur.
Dafür läuft es jetzt stabil. Bis irgendwo jemand neu einzieht und wieder einen Störer anstöpselt....
This can give more information than a simple ping that doesn't travel much of the same route as your Rocket League traffic:
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Welcome to the PC Master Race. Now you can actually troubleshoot your connection issues.
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Apartment buildings are notorious for Wi-Fi interference because there are sooo many networks trying to co-exist on the same frequency bands. That said:
Try temporarily running an ethernet cable from your game console or computer and hook it directly into the Frontier ONT (the modem-like device in your closet.. this is not the same thing as the router). Do you still get packet loss then?
You mentioned coaxial. There should be zero coaxial involved in a Fiber setup. If you're using Frontier's router, they might be somehow using the coaxial port as part of a MoCA setup?
Download a free tool called PingPlotter and do a traceroute to your game server. The tool will tell you where the packet loss is occurring between you and the game server.
Over on dslreports.com, there is a thread specific to Tampa area issues and ping. Can you tell us the model number of your ONT? Is it a GPON model # FOG421? If so, that's the slower type of hardware that may be contributing to your issue. Recommend calling Frontier again and asking for an XGS-PON ONT model # FOX222 (not sure if they offer it in the Tampa area, though).
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
I had 4 technicians visit in the past 2 weeks for the exact same issue.
To add to your troubleshooting, highly recommend downloading and running Pingplotter (Free) and check into your modem statistics (192.168.100.1).
In my case, I did get them on record stating the issue is on their end and they identified outside interference somewhere between my panel and OSP.
Problem is, they don't seem to have any good way to identify where that is. I'm tweeting @optimumhelp every time the internet goes out. I've also opened a legal claim against them through Fairshake, who is handling the filing process.
Optimum support is now simply stating "this is being handled by Optimum Corporate, please wait for them to respond".
Here's a thread where I show some of my packet loss. https://www.reddit.com/r/OPTIMUM/comments/nex6pl/pl_right_now_in_11776_anyone_else_had_two/
If you're in an area that has Starlink availability, I'd say go for it. I'm losing my patience with Optimum. Very close to taking a cut in speeds and switching to Tmobile 5G Home, which is available at my location.
Ran multiple speedtests from different points in my house from my Pixel 4a 5G to test. This is what I found (Port Jefferson Station, NY).
I know it says LTE, I just don't think Ookla updated their app. I definitely had the 5G antenna turned on.
Regardless, ~80-100Mbps DL (20ms ping) is usable. I would likely have no issues with video calls and streaming. Only place I might see some performance hits is with online gaming.
I really just don't want to give Optimum any more money.
Ping Plotter is a pretty user friendly option. You can leave it running like this while you're in game and use it as a reference for lag spikes. It can help you see if it's your routing or something related to your hardware.
If you have a pc of some sort, you can do this:
Copy pasta:
You can look up the server IP/hostname in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "StartJoin" backwards from the end of the log. You'll see something like this:
JoinGame: StartJoin Reservation=(BeaconURL="ip31-204-146-81.datahound.com:7843",[...]
In this case you'd use
ip31-204-146-81.datahound.com
Or rewrite it as an IP address:
31.204.146.81
Either one will work for this purpose. Grab one of those and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
I suffered the same terrible support from jio but this is what got it fixed for me: 1. Reach out to valorant support and get the ip of the server you are trying to reach (Mumbai or Singapore 1 or 2) and tell them that you need the ip for fixing ping issue. When I had reached out 2 weeks back this was the ip for Mumbai server 173.245.48.0 & AP (Asia Pacific) - 43.229.65.1 2. Run a trace route and if you are not sure how, go to the following app (https://www.pingplotter.com/download/windows)
In the Target field, enter in the following addresses Be sure you've set your test parameters for Trace Interval to 1 second and Focus Time to 5 minutes and try to run them in a custom match. Press the Play button on the left side to start the traceroute.
After the trace has completed, take a screenshot of the results in their entirety. Run a test for both IP addresses and send these screenshots to jio support Tell them the ip and the screenshots and tell them to fix the routing issue accordingly.
Warning: JIO SUPPORT IS TERRIBLE AS THIS IS A BACKEND ISSUE AND CALLING SUPPORT TEAM IS UTTERLY USELESS AS THEY WILL SAY WE HAVE ESCALATED THIS TO OUR BACK END TEAM WITH PRIORITY AND WILL ARRANGE A CALL BACK BUT NO ONE WILL CALL YOU BACK. SEND THIS EMAIL TO AND THEY LL SEND SUCH NOOBASS REPLIES. I HAD TO WAIT 10 DAYS FOR THEM TO FIX THIS SIMPLE ROUTING ISSUE. (9 DAYS TO JUST GET THEIR ATTENTION ON THIS) ISSUE CAN BE RESOLVED WITHIN MINUTES BUT JIO SUPP WON'T GIVE A FUCK 🙂
Copy pasta:
You can look up the server IP/hostname in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "StartJoin" backwards from the end of the log. You'll see something like this:
JoinGame: StartJoin Reservation=(BeaconURL="ip31-204-146-81.datahound.com:7843",[...]
In this case you'd use
ip31-204-146-81.datahound.com
Or rewrite it as an IP address:
31.204.146.81
Either one will work for this purpose. Grab one of those and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Copy pasta:
You can look up the server IP/hostname in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "StartJoin" backwards from the end of the log. You'll see something like this:
JoinGame: StartJoin Reservation=(BeaconURL="ip31-204-146-81.datahound.com:7843",[...]
In this case you'd use
ip31-204-146-81.datahound.com
Or rewrite it as an IP address:
31.204.146.81
Either one will work for this purpose. Grab one of those and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
This is a great question.
Those "connection timed out" pings mean packet loss. Call your ISP and ask to get someone to ping your modem from the node where your internet connection comes from, you got to apply some pressure if they give you poor tech support.
They rarely take documentation, that of course depends but I've worked with them before and it's pretty much the same. But, to make sure you can use https://www.pingplotter.com/ to test your internet connection to a remote server such as 1.1.1.1 and analyze the results.
Pingplotter kind of does that but I don't think you can give it data to display. But understand it is a tool to show variance, not necessarily a tool to pinpoint weighted routing. It traces a path over time and shows the variance (or change) of hops.
You might be able to ask support there if they can import data.
EDIT: Missed that you asked for a free tool but you could probably find similar using the name of pingplotter as part of your search.
What you need to do first is to find out at what point in the network (yours ot your ISP) the packet gets dropped or experiences latency. You can identify that by running pingplotter when you are not seeing any latency and when you are experiencing it. If the latency or packet drop is because of a bad node on your ISP network, there's nothing you can do other than open a support ticket with your ISP.
There doesn't seem to be an easy way to test this independent from the game on PS4.
Packet loss is usually a problem with your router or ISP rather than the game. Particularly if it's consistently higher than 1%. 1% probably won't interfere with your game too much.
I would suggest trying a laptop on the same connection / wire as your PS4. Ideally run something like Pingplotter to look for issues (https://www.pingplotter.com/products/free.html) . Pingplotter will show issues independent of the PS4 and the game.
You will need to run it a few times to get a clear picture. Download PingPotter, which will give you a nice graphical interface which should show where the drops are happening: https://www.pingplotter.com/
use /ip in game for an address to trace
just leave it going until you are experiencing the issue. if you are already experiencing the issue leave it running for a few minutes especially if it continues to persist
Then go to PingPlotter's File->Save Image, post image, also useful thing to provide if you are contacting support.
Without something like that it is just useless guessing.
Other games and browsers are not particularly relevant because routes can be drastically different from one thing to another. What you have eliminated is 1) your modem(most of the time) 2) the first node on your ISP's network. Which leaves a dozen other places or more where things can go wrong.
The first thing I would do is set up a pingplotter (https://www.pingplotter.com/products/free.html)
Set up a ping to your ISP's DNS, CloudFlare's Dns (1.1.1.1), Your Router's Internal IP, and your modem's gateway. See which goes down first and it helps you narrow down where the issue is.
> Before anyone asks about my ISP, my ISP is fine. I play other MMO’s and consistently run 30-50ms without lag spikes.
But since those MMO's are prolly not using lockstep, you wouldn't notice ping spikes. The next time you have those lag spikes, try pinging your instance IP which is located in the client.txt and use something like [Pingplotter](https://www.pingplotter.com/). I have the same issue and I know it's my ISP. For example, my latency usually is around 10 ms. But sometimes it is around 30ms avg, a closer look shows that my avg ping is actually still 10ms but I have 200-400ms jumps every few seconds which go unnoticed. Playing with lockstep, this results in annoying screen freezes while I don't notice it in predictive.
Please use : https://www.pingplotter.com/ and https://www.nperf.com/en/ to test your bandwidth before complaining on reddit. If you have trouble with your gaming setup ask help in /r/pcmasterrace/
Try using tracert, which should identify where the latency is coming from.
Alternatively, you could download a graphical tracert tool - such as PingPlotter.
Check out Ping plotter, you should also run iperf simultaneously if you want to test thoroughly. Just keep in mind that once you fill the pipe everything is going to backup if you don't use traffic shaping or limit your bandwidth.
There are a bunch of useful tools out there, I'd recommend https://www.pingplotter.com/, if you use the 20 day free pro licence you can collect the data over a couple days and export it out. For the graph I sent I'm using https://www.paessler.com/prtg which is way more than just a ping tool, it collects information from a bunch of probes on devices you specify. I'm using it mainly to keep an eye on devices in my home since they have a free up to 100 probes licence.
probably just gonna have to trace it out. I've used pingplotter in the past. Long time ago actually, but back then at least it was pretty simple to use and gave good info.
If you want to post or message me what IPs you are pinging I am willing to try them from where I am just as a sanity check.
Beyond that I think i'm out of ideas for now. I'll check back in if I think of something else to try.
I'm uncertain without having tried it there, and there are a bunch of variables.
But what I'd do in your position if you're unsure is use ping plotter to target the server addresses for each server:
SEA = login.worldoftanks.asia
NA West = 162.213.61.57 NA East = 162.216.229.21
And just let it run for a bit. What you obviously need to bear in mind is the trade-offs of each in terms of when the peak players will be (due to timezone differences), starting your account over if you transfer, and the language barriers on the SEA server that aren't as present on the NA server. That all being said, I'd be quite surprised if you don't get decent enough ping to the NA West Server in California given how well linked up Hawaii is, and that I get around 100 ms ping playing from London on NA East (while I holiday)
https://greatscottgadgets.com/throwingstar/
pass the signal wires (passive) into an arduino and if anything recieved in the last 10 seconds keep a light green... nothing in 30 yellow, 60 red... etc.
But i'd just run something like pingplotter instead. https://www.pingplotter.com
While this could be an issue with the server or the kill cam just doing kill cam things, I just want to point out that for awhile I had similar desync issues and it turned out that I was the problem.
I apparently had an old CRT television hooked up in the garage that was failing and feeding back noise onto my line. This was causing jitter on my end and made my ping fluctuate wildly in a way that the ingame ping counter didn't detect. (You need better tools, like PingPlotter) - You'll see massive spikes in your ping, I was getting jumps of 200ms+ from my normal ping.
The fix for me was to get rid of the TV. The improvement was immediate. No more dying behind cover and or inconsistencies between things like me going prone on my end, but my friends watching my cam not seeing me go prone (Right as I die).
Check your modem, your router, your coaxial lines and your ethernet. Be sure someone else isn't hogging your bandwidth and never, ever, play on WiFi. Then, if you are pretty certain you have a problem still, call your cable company if you think you might have an issue with your line. (They might charge you if you don't have a protection plan. I added one and then cancelled it after the visit where they tracked down my problem.)
have you checked your packet loss on your connection https://www.pingplotter.com/
A good Ping does not mean your not dropping packets.
One of the biggest sources of this type of problem is something called “packet loss.” You can still have a very good ping but be having issues with packet loss because although the data is being sent and ultimately received fairly quickly by the destination server, not all of the data is getting there correctly.
http://combofix.org/understanding-packet-loss-and-ping.php
The ping plotter will tell you if your dropping packets you can start with Google or even Battle.net
Try PingPlotter Free. It sounds like you're looking for something like this. You'll have to identify the address of the things you're trying to track first though. I've used an older version of the software to diagnose where my connections to game servers goes wrong.
You are not the only person reporting it. I can say that personally, no such trouble, which suggests it could be something network related.
You can try using -clientport 80 or -clientport 443 which can sometimes bypass ISP throttling. You can also follow the guide here to figure out if there is a network issue, and who to talk to about fixing it: https://www.pingplotter.com/fix-your-network
Finally, it's probably not a crash, since you were explicit about a disconnect, but it's always worth removing DPS meters, graphics tools like reshade, GPU "optimization" software, etc, and trying a reboot of the computer, to help rule out some of the occasional causes of these sort of problems.
>The wierd thing is he has quite the fast internet speed (100)...He had constant lag.
The internet is all the same "speed". A 100mbit connection is no "faster" than a 1mbit connection, the speed of light in fiber: ~ 1.9 x 10^8 m/s. Bandwidth doesn't describe how fast a connection is; rather, how wide.
The only thing that matters is routing. Either of these tools will help solve this problem: https://www.pingplotter.com/
Fixing it however is another matter. If his isp has terrible peering... well... that's unfortunate, but they're not going to be breaking any contracts because a home user has bad ping to a video game. If it's somewhere along the path, then you have to wait it out. If it's the lowrez servers... good luck with that. Sorry to be blunt.
A common source of problems is the level3 / telia gateway, between some people's ISP and the NCSoft data center. (By "between" I mean "several hops from either end".)
The best bet is to grab https://www.pingplotter.com/ or some equivalent, and see where the problem is in connection to the server. (use the /ip chat command to find the world server :)
That will help you -- or screenshots when you have this problem will help us -- advise you on where exactly the problem lies.
Once you know that we can maybe help figure out how to resolve it.
If its acting shitty even in single player i doubt this will help but try connecting your modem directly to you Xbox if your on a router. You can also download ping plotter, if you see a bunch of red its probably your router.
Download and install the free version of PingPlotter. Set the target to 8.8.8.8 and the interval to 1 second. Let it run for an hour or 2 and post a screenshot of the results. This will help isolate where the problem.
An excellent tool with good guidance notes. If you really want to dig into interpreting the output they have a few walkthroughs in their manual - fine is a relative concept unfortunately :-)
Something I don't know if people have ever tried or tested, to see if its somewhere along the hops to the servers, your provider, trion, ect.
Just get the ip of the server you're on by going start>run>resmon and ticking archeage, plop the ip in and then check the latency.
The program is a free trial, may be something better, but it is a decent program.
In EB when you get the lag spikes, write /ip
Write down the numbers and get ping plotter from here
https://www.pingplotter.com/
Download that and run it with the ip provided for 10min or so. That will let you pin point exactly where the throttling is happening.
Include pingplotter info or we can not assist you. At least a tracert to the GW2 servers.
saying "Other games are fine" does NOT mean it is GW2s fault - that's like saying "I can drive to Chicago in 2 hours, but it takes me 5 hours to get to X random city - so CLEARLY it's X's fault!"
Unless you literally live inside the A.Net building (and even then probably...) you do not have a direct connection to what ever server you are using. It's easy to blame A.Net, and it is possible that it's their fault, but it is much more likely that something else has changed along the route, or the route itself has changed.
Other info that is helpful if you don't want to provide pingplotter or something equivilant, ISP, general region you are from, EU vs NA, etc.
If you're running Windows, get the trial version of PingPlotter:
...switch to the Standard trial and let it draw the graph over 24 hours.
You can get the IP for the currently assigned server in the lower left corner of the starting screen of Elite.
Please note, that nodes on the way that are NEVER reachable just don't answer ICMP requests. However, in the graphs, you should be able to recognize a trend which hop causes problems if there are any.
Grab Pingplotter and just use the free version, when given the option after installation. Then, get the IP of the server you're connected to: generally, this can be done by opening the console (~) and typing status. EG: 103.10.125.68
Trace a route to the IP when you're seeing high pings ingame. If the ping is bad on the first hop, then you might have a program or device that's uploading data on your own network (EG: iCloud Backups). If the ping shoots up on any resolved names say "on.ii.net", there's an issue with iiNet's end. If it's anywhere else, there's very little you can do.
Feel free to PM me a screenshot, if you wish.
What sort of time frame of records are you looking to keep? PingPlotter will do what you want but he new free version 4 is hamstrung in a LOT of ways compared to the older version. Download the old version here. It's worth the money for the Pro version if you can afford it.
Edit: Sorry for the Windows centric answer.
For troubleshooting these kind of issues in the past I've found that using PingPlotter can help a lot, it does a traceroute and shows the results on graph which can give you a pretty accurate idea of where the problem is occurring
They do offer a free version which is more than enough for basic diagnostics https://www.pingplotter.com/freeware.html
For instance if you're getting packet loss within your ISP network then WTFast or similar tools wont change a thing
Edit: you can get the ip adress for your FFXIV server on http://arrstatus.com/ also you can try using the adress of your ISP main webpage it's usually located within their own network so if you get packet loss on that it's very likely that your ISP is the issue
Its an issue with comcast. I had a server collocated in miami, and still had jitter issues when connected to it. The data center had peering with comcast, and it was like 5 hops from my house to the server.
Also a much better tool to use is pingplotter, https://www.pingplotter.com/freeware.html
You might try a ping tracing tool to see if there is some congestion at a hop from your ISP, or through a peering point between ISP's. I've found this tool seems to be useful.
Edit: Forgot to post link: https://www.pingplotter.com/
From my own experience in gaming, I found that my issues connecting were actually my local wireless network. It seemed to happen more during busy times, and I expect it was due to more traffic on the airwaves from the neighbors. Switching to wired fixed my issues completely. Just a thought, in case you are connecting wirelessly.
This actually appears to be the desync issue that some players are currently suffering from. On the Asia server, this is affected a lot of players in Australia connecting to Asia via Internode. What we're speculating is that what's happening is the game's lag detection and compensation at work (which was implemented in patch 0.3.0 in CBT). However, it's neither the fault of your connection to the internet or the server itself, but an ISP node somewhere in between that's either malfunctioning or resulting in packet loss, causing your game client to fail to receive the information it needs to accurately update the game shown on your screen.
The most you can do now is try to run pingplotter or a traceroute to your respective World of Warships server (ask in your region's forum abt how to do it), and post the results to your region forum's bug reporting section. Contact your ISP as well, outlining the problem.
As far as I know, the devs are aware of the issue, but appear to have problems replicating it because it's more of an ISP problem than a game code problem. Sorry I can't be of more help.
That timeout at hop 17 doesn't mean anything. The router simply isn't responding to ping requests, which isn't necessarily bad.
Your problem is that (from looking at the DNS) your packets are going on a world tour.
The major delay is between hop 6 and 7, where your packets leave your ISP's net (pldt.net => "Philippine Long Distance Telephone Company") , which I am assuming is in the Phillipines and enter Cogent's. You can see a dramatic increase in ping times. I don't exactly know where hop 6 is physically located, but from the DNS name I'd guess you're going from the Philippines to Los Angeles (LAX in the DNS), which is roughly 12000km by air. That alone will add about 120ms in travel time through fiber.
You then go from LA to Houston, another 2000km and 20ms travel time alone (the 50ms between hops 8 and 9 seems high and something Cogent should be able to improve), and so on until you land in Boston. So you are going from the Philippines to the US West Coast and then on to the East Coast. Thus your ping is always going to be 200ms+.
As far as spikes are concerned there are a few outliers in that tracert, e.g. your ping to hop 2 varies a lot. That doesn't reflect in the rest of the route though and may just be due to ping requests being treated differently by the router than other traffic.
You could try monitoring your connection for a longer time to see, whether you can identify any consistent issues.
Try WinMTR or PingPlotter for that.
To answer you question, Pingplotter may be a good, simple program to monitor. There might be a better alternative for long term motioning but it's quick and easy.
Pay special attention to your LAN first though. Ping your router for a duration with just ping -t, new doesn't always mean perfect.
Poland here 40-50 ping on Frankfurt no lag spikes. Didint check London simple because i have no need for it.
Use it https://www.pingplotter.com/ , and check "where" you have lags/packet loss etc. Its very good program that show everything. Sometimes one "bad" server on they road can make your game lag etc
Before you blame anyone , check who is fucking up your gameplay.
Ever tried tracing your connection? (for example with pingplotter or CMD/Terminal)
High chance you experience this cause of packet-loss and/or bad routing. Endless posts regarding this in the official forums too. :)
https://www.pingplotter.com/manual/standard/interpretgraphsexampleone.html
Here is something you can read to help understand the results you are getting.
However, if its outside your ISP's network, chances are you cant do much, unless your ISP is directly peered with them, then you can contact your ISP to see if they can help.
You could try using pingplotter to find where the problem is located. Find the IP of a game server or other service you're experiencing this lag with then when it happens again run pingplotter to see which hop is causing it.
If it's not in the first few hops (between your pc and your ISP) there's nothing you can do except call your ISP and demand better service.
Auch im Norden, auch Vodafone Kabel. Hatte das Problem auch ab und an - beim nachschauen mit PingPlotter stellte sich raus, dass das Problem hauptsächlich Paketverlust irgendwo entlang der Route waren. Vielleicht ist's das bei dir auch.
I don't think the router is the problem. You can run a pingplotter to see where the bottleneck is along the route.
If it was the router using a VPN would still have problems.
Thanks for the compliment, but I'm not really that knowledgeable lol. They do have some great info right on their site though (unless it's hidden and only found with a Google search haha)
https://www.pingplotter.com/fix-your-network/interpret-results.html
Is that traceroute done while the problem is occurring? Ideally it should be already running before it starts. I would recommend running https://www.pingplotter.com/ while playing using an ip from the /ip command in game. The latency graph on it makes it fairly easy to spot where a problem is occurring once you figure out how the graph works.
Although traces can be incomplete such as the one you have there which would make tracing less useful.
In addition to being incomplete that first trace is also a little unexpected. The second to last address(15.230.23.203) is allocated to a US branch of Amazon which would imply that your connection is going from Australia to US, crossing over the entire US then over to the server. Maybe that is actually the fastest route but at least based on geography that doesn't seem right
I've been using PingPlotter to trace route the whole thing, from me towards the servers of ESO. Well it seems its an ISP issue, because there are 100% packet losses in 2 of the servers the routing it takes. This needs fixing from the ISP, and sadly that is quite hard, so you either change provider or you try to talk to them about it so they can do the change, or you stuck with it and play with VPN instead.
Install Pingplotter on a wired device or server in the network.
Set the trace intervals to 1 second, let it just run for 24 hours. Right click the column headers and click "Errors" so it shows you each dropped packet along each hop. See where the loss is to one of those destinations (or multiple). But maybe start with one destination to ensure your firewall isn't ICMP filtering like crazy. That should help pinpoint where the loss is occurring. You can save the data to TXT or CSV and also export the graph image for some evidence to provide Spectrum.
There's a decent little program called PingPlotter that gives a graphical representation of what what's going on with hops your packets take. I just use the free version but it's still super useful for troubleshooting. https://www.pingplotter.com/.
The Windows command line utility 'pathping' does similar stuff ('mtr' in Linux.)
It's interesting that people are now paying more attention to latency & response times - important now that we're video chatting etc. Arguably as important as the "speed" tiers packages that the ISPs like to sell us.
Probably lots of people out there with a similar problem, but yeah, in each case it's likely just you (or them). You can try the below to try to find out where the ping jumps:
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
>my current TC4400 is causing jittering
What makes you think it's your modem? There are potentially dozens of servers between your modem and your intended destination that can introduce a host of networking issues.
Test your modem here: http://www.dslreports.com/tools/puma6.
Check your connection quality using PingPlotter.
Neither of these tools is a catch-all solution, but they can help diagnose a problem.
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
It looks your local node is over utilized and it tanks the performance.
You can easily troubleshoot by downloading a free network ping tool like ping plotter: https://www.pingplotter.com
Ping to popular sites like google.com and your game server host name or IP address. Do it when it is working good and during the times you have issues.
Pretty much it will give you a ms average of all the hops your connection goes though.. and it will tell you if one of those hops is performing bad.
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Suddenly having 100+ higher than usual is pretty indicative of a routing problem. Try the below to find out where the ping jumps:
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
That you are aware of. The internet is always moving, shifting. A 10 ms difference is not going to be easy to diagnose however. But you can try. I'd recommend Pingplotter (WinMTR simply doesn't show enough detailed information):
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Those particular copy pastas are out of date. The log format has changed since. I'll just give you the latest version:
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Ich hab gerade pingplotter installiert und mir ein paar tutorials durchgelesen, in einem wurde das reverse traceroute zur eigenen IP vorgeschlagen gerade um rauszufinden, ob man auf dem asymmetrischen Rückweg Probleme hat.
Allerdings wurde auch im ersten Absatz erwähnt, dass viele Router ICMP traffic einfach ignorieren. Schätze da kann ich nichts weiter machen?
>my ping is fine when pinging sites using commands
The only thing that's interesting is how your ping is (over time) to the various Rocket League servers. If you ping some random site, sure, some of the route taken will be the same, and at best you will have proven that this part of the route is working just fine. But some of the route won't be the same, and the problem might be in that part. I say "at best" because it depends how comprehensively you tested it to rule out local causes.
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with PingPlotter or WinMTR. It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.