Comcast + SWTOR = Lag

[LJ_Gibbs]

For the past week, I have had major issues with latency spikes. From my normal 23ms, up to 300, down to 64, up to 2000. I have only been able to play the game in the evenings, so that is when it is happening to me. And it's not constant. Very intermittent. But still very annoying.

 

I have noticed a few people on reddit have also been experiencing the same issues. Some people have mentioned it was since the last patch, and I tend to agree.

 

I just wanted to start a thread trying to verify how many people are actually having this issue.

[Dracofish]

For the past week, I have had major issues with latency spikes. From my normal 23ms, up to 300, down to 64, up to 2000. I have only been able to play the game in the evenings, so that is when it is happening to me. And it's not constant. Very intermittent. But still very annoying.

 

I have noticed a few people on reddit have also been experiencing the same issues. Some people have mentioned it was since the last patch, and I tend to agree.

 

I just wanted to start a thread trying to verify how many people are actually having this issue.

 

I have Comcast and all is fine with me. Could be an interruption in your area.

[Zidovain]

Here -- http://www.swtor.com/community/showthread.php?t=946047

 

Having this issue along with many others since 5.8.

[LJ_Gibbs]

I have Comcast and all is fine with me. Could be an interruption in your area.

 

Guildmate from 1000 miles away having same issues. It's been going on for a few weeks.

[kukumburr]

Okay I also have this problem and am on Comcast and I've been investigating it. I actually vaguely remembered having this problem YEARS ago but I think I stopped playing for awhile right around then. Anyways I did some forum searching and found the topic from back then here: http://www.swtor.com/community/showthread.php?t=642130. Same problem in the year 2013. I don't remember seeing ANY sort of official acknowledgement or help with this problem, but like I said I think I stopped playing around then and when I came back I wasn't having the problem anymore so I might have missed something.

 

So on top of that I've been running some Wireshark traces both during the spikes and during times my connection seems to be normal with low ms. When the spikes are bad there are a bunch of dropped/delayed packets between me and the EA server. This is something that ONLY occurs when the spikes are happening. I don't want to straight up post the traces because there is a lot of information in them and I'm not sure it's all safe but I sanitized one of them so all the IP addresses etc. have been changed to random ones. You can look at here on cloudshark: https://www.cloudshark.org/captures/9853396bfd53?filter=ip.addr%20eq%20121.255.239.187

 

The fake IP address that maps to the EA IP is the one listed in the display filter at the top. You can scroll through and see all the black highlighted rows where it's having trouble with the packets.

 

I also did a bunch of traceroutes to EA IPs. These are the IPs that I've seen in my Wireshark captures. You can see them all under the spoiler:

 

 

CC:\WINDOWS\system32>tracert 159.153.65.232

 

Tracing route to 159.153.65.232 over a maximum of 30 hops

 

1 <1 ms <1 ms <1 ms 192.168.1.1

2 10 ms 13 ms 9 ms 96.120.41.89

3 9 ms 7 ms 9 ms xe-11-3-1-sur01.macomb.mi.michigan.comcast.net [69.139.242.113]

4 8 ms 10 ms 10 ms xe-5-1-0-0-sur01.holt.mi.michigan.comcast.net [68.86.123.150]

5 12 ms 11 ms 11 ms be-39-ar02.pontiac.mi.michigan.comcast.net [68.87.188.229]

6 22 ms 15 ms 13 ms ae2.bar1.Detroit1.Level3.net [4.68.71.33]

7 * * * Request timed out.

8 98 ms 105 ms 107 ms 4.79.23.202

9 28 ms 32 ms 24 ms 159.153.92.10

10 27 ms 27 ms 25 ms 159.153.92.86

11 27 ms 28 ms 28 ms 159.153.65.232

 

Trace complete.

 

C:\WINDOWS\system32>tracert 159.153.65.232

 

Tracing route to 159.153.65.232 over a maximum of 30 hops

 

1 <1 ms <1 ms <1 ms 192.168.1.1

2 9 ms 11 ms 11 ms 96.120.41.89

3 9 ms 11 ms 10 ms xe-11-3-1-sur01.macomb.mi.michigan.comcast.net [69.139.242.113]

4 11 ms 11 ms 10 ms xe-5-1-0-0-sur01.holt.mi.michigan.comcast.net [68.86.123.150]

5 12 ms 11 ms 11 ms be-39-ar02.pontiac.mi.michigan.comcast.net [68.87.188.229]

6 16 ms 12 ms 15 ms ae2.bar1.Detroit1.Level3.net [4.68.71.33]

7 * * * Request timed out.

8 101 ms 98 ms 110 ms 4.79.23.202

9 30 ms 26 ms 25 ms 159.153.92.10

10 27 ms 29 ms 26 ms 159.153.92.86

11 27 ms 25 ms 25 ms 159.153.65.232

 

Trace complete.

 

C:\WINDOWS\system32>tracert 159.153.65.228

 

Tracing route to 159.153.65.228 over a maximum of 30 hops

 

1 2 ms <1 ms <1 ms 192.168.1.1

2 10 ms 7 ms 11 ms 96.120.41.89

3 10 ms 9 ms 9 ms xe-0-3-3-sur02.macomb.mi.michigan.comcast.net [69.139.242.17]

4 15 ms 12 ms 12 ms be-39-ar02.pontiac.mi.michigan.comcast.net [68.87.188.229]

5 24 ms 13 ms 15 ms ae2.bar1.Detroit1.Level3.net [4.68.71.33]

6 * * * Request timed out.

7 98 ms 109 ms 108 ms 4.79.23.202

8 31 ms 28 ms 26 ms 159.153.92.10

9 26 ms 35 ms 24 ms 159.153.92.86

10 23 ms 26 ms 26 ms 159.153.65.228

 

Trace complete.

 

C:\WINDOWS\system32>tracert 159.153.92.86

 

Tracing route to 159.153.92.86 over a maximum of 30 hops

 

1 2 ms <1 ms <1 ms 192.168.1.1

2 10 ms 11 ms 12 ms 96.120.41.89

3 19 ms 9 ms 9 ms xe-11-3-1-sur01.macomb.mi.michigan.comcast.net [69.139.242.113]

4 11 ms 11 ms 10 ms xe-5-1-0-0-sur01.holt.mi.michigan.comcast.net [68.86.123.150]

5 12 ms 12 ms 11 ms be-39-ar02.pontiac.mi.michigan.comcast.net [68.87.188.229]

6 46 ms 16 ms 13 ms ae2.bar1.Detroit1.Level3.net [4.68.71.33]

7 * * * Request timed out.

8 86 ms 86 ms 89 ms 4.79.23.202

9 28 ms 24 ms 23 ms 159.153.92.10

10 24 ms 26 ms 28 ms 159.153.92.86

 

Trace complete.

 

C:\WINDOWS\system32>tracert 159.153.92.86

 

Tracing route to 159.153.92.86 over a maximum of 30 hops

 

1 2 ms <1 ms <1 ms 192.168.1.1

2 9 ms 9 ms 13 ms 96.120.41.89

3 9 ms 10 ms 10 ms xe-11-3-1-sur01.macomb.mi.michigan.comcast.net [69.139.242.113]

4 10 ms 11 ms 9 ms xe-5-1-0-0-sur01.holt.mi.michigan.comcast.net [68.86.123.150]

5 12 ms 13 ms 12 ms be-39-ar02.pontiac.mi.michigan.comcast.net [68.87.188.229]

6 14 ms 12 ms 18 ms ae2.bar1.Detroit1.Level3.net [4.68.71.33]

7 * * * Request timed out.

8 89 ms 96 ms 97 ms 4.79.23.202

9 121 ms 122 ms 124 ms 159.153.92.10

10 128 ms 126 ms 120 ms 159.153.92.86

 

Trace complete.

 

C:\WINDOWS\system32>tracert 159.153.92.86

 

Tracing route to 159.153.92.86 over a maximum of 30 hops

 

1 1 ms <1 ms <1 ms 192.168.1.1

2 11 ms 11 ms 9 ms 96.120.41.89

3 15 ms 9 ms 9 ms xe-11-3-1-sur01.macomb.mi.michigan.comcast.net [69.139.242.113]

4 10 ms 10 ms 11 ms xe-5-1-0-0-sur01.holt.mi.michigan.comcast.net [68.86.123.150]

5 11 ms 12 ms 12 ms be-39-ar02.pontiac.mi.michigan.comcast.net [68.87.188.229]

6 12 ms 13 ms 13 ms ae2.bar1.Detroit1.Level3.net [4.68.71.33]

7 * * * Request timed out.

8 81 ms 80 ms 82 ms 4.79.23.202

9 125 ms 135 ms 125 ms 159.153.92.10

10 124 ms 128 ms 125 ms 159.153.92.86

 

Trace complete.

 

C:\WINDOWS\system32>tracert 159.153.92.86

 

Tracing route to 159.153.92.86 over a maximum of 30 hops

 

1 <1 ms <1 ms 1 ms 192.168.1.1

2 11 ms 11 ms 26 ms 96.120.41.89

3 10 ms 24 ms 10 ms xe-11-3-1-sur01.macomb.mi.michigan.comcast.net [69.139.242.113]

4 10 ms 8 ms 10 ms xe-5-1-0-0-sur01.holt.mi.michigan.comcast.net [68.86.123.150]

5 15 ms 12 ms 13 ms be-39-ar02.pontiac.mi.michigan.comcast.net [68.87.188.229]

6 12 ms 13 ms 13 ms ae2.bar1.Detroit1.Level3.net [4.68.71.33]

7 * * * Request timed out.

8 89 ms 89 ms 81 ms 4.79.23.202

9 125 ms 129 ms * 159.153.92.10

10 127 ms 128 ms 133 ms 159.153.92.86

 

Trace complete.

 

C:\WINDOWS\system32>tracert 159.153.92.86

 

Tracing route to 159.153.92.86 over a maximum of 30 hops

 

1 <1 ms <1 ms <1 ms 192.168.1.1

2 10 ms 10 ms 10 ms 96.120.41.89

3 11 ms 11 ms 11 ms xe-11-3-1-sur01.macomb.mi.michigan.comcast.net [69.139.242.113]

4 9 ms 11 ms 10 ms xe-5-1-0-0-sur01.holt.mi.michigan.comcast.net [68.86.123.150]

5 12 ms 14 ms 11 ms be-39-ar02.pontiac.mi.michigan.comcast.net [68.87.188.229]

6 14 ms 13 ms 13 ms ae2.bar1.Detroit1.Level3.net [4.68.71.33]

7 * * * Request timed out.

8 88 ms 92 ms 104 ms 4.79.23.202

9 126 ms 124 ms 129 ms 159.153.92.10

10 124 ms 125 ms * 159.153.92.86

11 125 ms * 128 ms 159.153.92.86

 

Trace complete.

 

C:\WINDOWS\system32>tracert 159.153.92.86

 

Tracing route to 159.153.92.86 over a maximum of 30 hops

 

1 <1 ms <1 ms <1 ms 192.168.1.1

2 15 ms 12 ms 8 ms 96.120.41.89

3 11 ms 14 ms 9 ms xe-11-3-1-sur01.macomb.mi.michigan.comcast.net [69.139.242.113]

4 11 ms 12 ms 9 ms xe-5-1-0-0-sur01.holt.mi.michigan.comcast.net [68.86.123.150]

5 24 ms 23 ms 22 ms be-39-ar02.pontiac.mi.michigan.comcast.net [68.87.188.229]

6 13 ms 15 ms 27 ms ae2.bar1.Detroit1.Level3.net [4.68.71.33]

7 * * * Request timed out.

8 108 ms 107 ms 99 ms 4.79.23.202

9 140 ms 126 ms 126 ms 159.153.92.10

10 126 ms * 125 ms 159.153.92.86

 

Trace complete.

 

C:\WINDOWS\system32>tracert 159.153.65.228

 

Tracing route to 159.153.65.228 over a maximum of 30 hops

 

1 <1 ms <1 ms <1 ms 192.168.1.1

2 10 ms 9 ms 11 ms 96.120.41.89

3 9 ms 13 ms 10 ms xe-0-3-3-sur02.macomb.mi.michigan.comcast.net [69.139.242.17]

4 11 ms 11 ms 11 ms be-39-ar02.pontiac.mi.michigan.comcast.net [68.87.188.229]

5 12 ms 13 ms 14 ms ae2.bar1.Detroit1.Level3.net [4.68.71.33]

6 * * * Request timed out.

7 93 ms 86 ms 83 ms 4.79.23.202

8 126 ms 150 ms 126 ms 159.153.92.10

9 137 ms * 125 ms 159.153.92.86

10 * 125 ms 125 ms 159.153.65.228

 

Trace complete.

 

C:\WINDOWS\system32>tracert 159.153.65.228

 

Tracing route to 159.153.65.228 over a maximum of 30 hops

 

1 <1 ms <1 ms <1 ms 192.168.1.1

2 12 ms 12 ms 10 ms 96.120.41.89

3 10 ms 9 ms 17 ms xe-0-3-3-sur02.macomb.mi.michigan.comcast.net [69.139.242.17]

4 12 ms 12 ms 13 ms be-39-ar02.pontiac.mi.michigan.comcast.net [68.87.188.229]

5 19 ms 12 ms 13 ms ae2.bar1.Detroit1.Level3.net [4.68.71.33]

6 * * * Request timed out.

7 93 ms 91 ms 93 ms 4.79.23.202

8 40 ms 35 ms 28 ms 159.153.92.10

9 26 ms 35 ms 33 ms 159.153.92.86

10 25 ms 27 ms 25 ms 159.153.65.228

 

Trace complete.

 

 

 

Everything is always fine early on, which from my understanding usually means it's not a problem with the ISP. The 6th hop doesn't appear because it doesn't seem to accept ping requests so can't tell what's going on there. The 7th hop has a bit higher ms but it's fairly consistent in every trace, and looking up the IP it seems to belong to Level 3 Communications. The 159.153 addresses are EA IPs and you'll notice some traces have them at high ms and some at a low ms (correlating to the spikes I assume).

 

I also ran WinMTR to see packet loss as well as latency. The results of that are here:

 

 

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.1.1 - 0 | 230 | 230 | 0 | 0 | 2 | 0 |

| 96.120.41.89 - 0 | 230 | 230 | 8 | 12 | 29 | 14 |

|xe-0-3-3-sur02.macomb.mi.michigan.comcast.net - 0 | 230 | 230 | 7 | 12 | 34 | 11 |

|be-39-ar02.pontiac.mi.michigan.comcast.net - 0 | 230 | 230 | 10 | 14 | 25 | 15 |

| ae2.bar1.Detroit1.Level3.net - 0 | 230 | 230 | 10 | 15 | 34 | 13 |

| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |

| 4.79.23.202 - 0 | 230 | 230 | 36 | 68 | 105 | 71 |

| 159.153.92.10 - 8 | 182 | 169 | 0 | 128 | 160 | 129 |

| 159.153.92.86 - 6 | 187 | 176 | 123 | 129 | 266 | 129 |

| 159.153.65.228 - 6 | 186 | 175 | 0 | 127 | 143 | 124 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

 

 

I sat and watched my latency in-game while this ran. I had no packet loss even when my latency was ~180 which is still a bit high for me. However I saw packet losses starting anytime it spiked higher, like 300-500+. I didn't see any huge spikes at the time I was running it. Anyways important thing to note here is packet loss (the % column) only ever occurred at the EA IPs. So the problem has something to do either with the 4.79.23.202 or with the EA ones as far as I can tell.

 

Now I'm really no expert at network stuff so I might be making mistakes or whatever but I'd seriously like some help with this. I have no idea if I should be complaining to Comcast or to EA, but I'm learning towards EA. It also seems weird to me that this just started around when the 5.8 patch came out. I have had absolutely no problems with anything else other than SWTOR as well.

[TrixxieTriss]

It’s not just Comcast.

[Shirvington]

Confirm. I am getting lag spikes up to 1600 or so for no reason. I am on Comcast as well if it matters.

 

I'm running Pingplotter on servers such as Google and Pingplotter's own site and my pings are fine.

[justindtis]

I'm getting the exact same thing. Ever since patch 5.8. It's really getting frustrating.

[Marphlets]

Having the same problem here. Comcast customer. I spike from between 90ms to 15000ms. As far as I've been able to gather from guildmates and teammates, this is happening to players from Seattle to Miami and everywhere between. I've seen screen shots of up to 200k ms. Honestly didn't think that could happen without a dc. Comcast customer service seems clueless("REALLY?!" you say sarcastically).

 

I just want to be able to do something as simple as type in chat without a 10 second delay on posts. Even basic questing and flashpoints provide me with more of a slideshow that an actual gaming experience - forget progression ops.

[DocDAM]

Another Comcast user. And yes, last 2 weeks or so, I've had terrible lag spikes. Don't recall if the timing exactly coincided with 5.8 release, but it was around then. And the server mtce yesterday didn't help.

 

Very sporadic, sometimes it is clean for a 1-2 hr session. Other times, it will be varying from my usual 20+ ms to 120-250, and with jumps to single red dot and occasional red-X. So, anywhere from fine to unplayable.

 

Pingplotter showed all the dropped packets on the SWTOR (159.153...) IP's. Other IP's (Google, Amazon) were fine. (Though Google has been 60's of late, instead of usual 15-16 ms.)

Edited April 11, 2018 by DocDAM

[Andryah]

Is it possible that Comcasts throttling software is the cause? As more and more people stream more and more content on line, and at 4k resolution levels.. this does congest the internet channels.. and if this is mainly being an evening time (local US) I can see this happing.

 

I ask because they are kind of notorious for being draconian with their throttling... and not just at the local user level, but even upstream. I think almost all the major ISPs in the US are guilty as well... but it seems Comcast is the most aggressive. I also wonder if Comcast gives better performance to customers accessing a site or server where the business owner of said site or server has "paid a fee" "for better service to customers". Comcast has been vocally against net neutrality (as are most big ISPs) and has been aggressive with their customers and businesses on the presumption that they can be.

 

As an AT&T user on the west coast.... I have not seen these issues. I do see occasional spikes in ping rate, which has pretty much always been the case given the number of hops to get to the game servers .... but overall... ping is smooth and sitting at ~90ms for me.

 

Now.. if AT&T is doing backend maintenance or changes to their infrastructure (which do from time to time) I have seen degradation in performance... but not just for playing an MMO... but for everthing.. and speedtest runs showed a localized problem about 4 miles from my home which was indeed AT&T.

 

By the way... this particular MMO seems to be more tolerant of latency than any other MMO I have played. Which is why you can see wild increases in ping numbers on the client (well up into the thousands) and the client will still stay connected (even though effectively frozen). It seems to take a lot for the client to give up and disconnect.. which is both good and bad. Good in that you get less actual drops over time. Bad in that it misleads the player into thinking they have high latency when in fact there are connections issues or packet loss taking place and the client is not actually talking with the server........which most MMO clients would simply disconnect and crash rather then try to recover.

Edited April 11, 2018 by Andryah

[JediQuaker]

Often times these problems are due to a flaky router/hub/connection somewhere between you and the EA servers and it's not the fault of either your ISP or EA. Usually these problems fix themselves when the flaky router/hub/connection gets repaired or replaced.

[FerkWork]

Same issues as well. Been ongoing for about 2 weeks now.

[zyglrox]

same thing here, theres like 5-6 threads about this spread throughout swtor/reddit forums.

 

went from 25-32 ping to 130-150 with spikes in the thousands during peak hours.

[ItzProficient]

I can assure you this is a problem on EA’s side. Everyones connection was fine UNTIL PATCH 5.8. Whatever they did in regards to connection in patch 5.8 messed up it up. Is there ANY news or official announcement made by Bioware on this issue? Are they even going to acknowledge it or or they just going to purposely turn a blind eye and foresake their subscribers? Im giving Bioware until the end of my Sub to fix this or im taking my money elsewhere. Simple as that.

[Suprderk]

I have had problems too. Three or four times in the past few days I have tried to log in and got to the loading screen and it wouldn't go further. A couple of times i just left it there to see if it would eventually log in, but twenty minutes later it was still there. I have had the dreaded red X on the server status in game some as well. I don't use comcast so I don't think it is related to the service provider.

[MerlockVonBaron]

you could be having line loss also meaning your cables may need replacing I would call Comcast mention it and have someone come out to check the poles

 

I had the same issue and it was fixed make sure ya reboot your system

[Holocron]

Remember net neutrality? Don't worry, pretty soon you'll be able to upgrade to comcast's new "premium connection bundle" with no throttling for an extra $150 a month.

[Joonbeams]

I'm a comcast user. I didn't have any issues prior to the last patch - I haven't logged in since Sunday so I can't verify if anything changed with the new patch, but I should be able to check tonight. I do have a dedicated "business" connection at the house, so I may not be the best person anyway.

 

Can affected people share some pingplots? That will help in the troubleshooting...

[kukumburr]

I doubt it's ISP throttling. I have zero issues with Overwatch, youtube, netflix, twitch livestreams, or literally anything else. I download things, including SWTOR patches, very quickly. I'm also not sure throttling would look like this where sometimes you get crazy spikes but other times it'll be normal for awhile. Wouldn't it be more consistent? Also like I said before this was a problem that happened on SWTOR as far back as 2013, maybe even further.

 

Other than the first thread I posted earlier from 2013 there were a bunch of threads about similar issues. And a lot of people claimed to have problems after a patch. Seriously just google "swtor lag spikes after patch" and filter for http://www.swtor.com. Back then it seems some people had trouble with an intermediate hop as6453 but as far as I can tell I'm not hitting one of those. There is one hop I can't ping so I don't know if that's something.

 

But yeah people should post tracerts and pingpaths maybe there's a common theme. But I don't see how BioWare can wash their hands of this when SWTOR is the only thing being affected and it seems like it happens to people all over the country (maybe other countries too?) after a patch.

[SaerethDL]

another comcast customer here, have been having this issue since around 5.8 please.. its very unenjoyable and I'm thinking of not playing the game as much.. pvp is almost impossible now, and watching people teleport around in flashport and ops sucks.. it happens night for me now.. my connection is fine.. i'll be testing my ping and bandwidth at the same time swtor is going bad.. it's not throttling I'm at full bandwidth speeds.. no problems on my end. Edited April 11, 2018 by SaerethDL

[KamiSongheart]

My husband and I play through Comcast and have not noticed any issues. I hope everyone is able to get it resolved quickly.

 

Now that I've said that, I'll probably log into nothing but lag.

[Mournblood]

If you're experiencing issues with your ISP, and your home network is setup properly, it's likely a router between you and BW servers that is the culprit. The only way you're going to be able to address the issue is to do some basic troubleshooting on your own, and then provide that information to both your ISP (Comcast) and/or Bioware tech support. For those who are not IT savvy, here's how:

 

You can generally use NSLOOKUP in your CMD prompt (be sure to run as administrator) to translate domain names such as http://www.swtor.com into an IP address. In this case for looking up a server IP, you'd want to use NETSTAT. The specific command arguments would be NETSTAT -n - p TCP -b | more. You need to already be IN the game when you run that command, otherwise you'll ping the login server instead. To save some of you some time, the IP for Satele Shan I see is 159.153.65.225 (class B network).

 

Once you know the server IP addy, you can run a trace route in your CMD prompt to determine which router along the path is potentially causing you problems. The syntax to use in your CMD prompt is TRACERT 159.153.65.225, which in this example is the IP that NETSTAT returned for me. You'll see the hops displayed in milliseconds. If any are inordinately long, like 200-300 ms or more, that is likely where the connection problem is occurring and you can report that to your ISP and Bioware. Keep in mind that if there is a problem with a specific router along your path, your ISP may not own that router and may not be able to resolve the issue for you. Also note that if you see any hops timing out, that's usually because that specific router is not broadcasting its IP address, meaning it's private.

 

If you don't see any issues in TRACERT, then you need to consider potential issues within your home network setup. Are you using a combination modem/router provided by Comcast (which is what they tend to give you because most customers are not network technicians and don't know how to properly setup their own routers)? If so, you won't be able to configure that router without their help, and even if you do, you'll lose any configurations whenever they swap out your equipment (which is often their solution for issues with your modem/router). My recommendation would be to only use their modem and to go out and buy our own (wireless) router. If you use your own router, you need to setup port forwarding for SWTOR. If you don't know which ports to open, here's the link: https://help.ea.com/en-us/help/star-wars/star-wars-the-old-republic/swtor-ports/. You'll need to refer to your specific router manufacturer's instructions on how to access your router's GUI to configure port forwarding. For example, for Linksys routers, you'd type http://192.168.1.1 in the web browser of your PC/laptop that's connected to the router.

 

Hope that helps.

Edited April 12, 2018 by Mournblood

[LJ_Gibbs]

I think I figured out how to get the info you need (I think I found the IP of my server).

 

OK... here is what I see between hops 6-11

 

6 14ms 13ms 13ms 4.68.71.133

7 * * * Request timed out

8 20ms 21ms 18ms 4.79.23.202

9 91ms 87ms 89ms 159.153.92.10

10 110ms 107ms 108ms 159.153.92.86

11 87ms 91ms 93ms 159.153.65.228

Edited April 12, 2018 by LJ_Gibbs

[Thepyrethatburns]

I would recommend MX Toolbox to do a lookup. You can lookup ARIN information, PTR records, everything to get you on the right track of where the jumps are failing or lagging out.

 

For example, using one of the IPs above, 4.79.23.202 is a Level 3 address.

 

OrgName: Level 3 Parent, LLC

OrgId: LPL-141

Address: 100 CenturyLink Drive

City: Monroe

StateProv: LA

PostalCode: 71203

 

So, if you hit a point where the traceroute suddenly goes astronomical between one jump or another, you'll be able to make an educated guess where the tracert is failing and between which areas.

 

https://mxtoolbox.com/SuperTool.aspx#