Observer

Latency Issues

[Spreading post out because of character limits]

So I'm going to put the nine yards of things wanted on here so this can get resolved asap. Some background info: I game using my PC and I experience latency spikes throughout said games. This didn't start happening until maybe a month ago, so I went about figuring out what the problem was, and since I've recently only been playing through one companies brand so I put in tons of support tickets to rule out things. I was ultimately told it was my ISP. I called tech support and I was told there was an issue with the modem, but apparently everything looked fine on his side. I tested out a few different ethernet cords to assure that wasn't the issue, and I did try directly connecting my computer to my modem (I have a separate router but still use a wired connection), neither worked. I was told to go in and exchange my modem (still not convinced it’s the modem), and I’m posting here to get a definitive resolution so I don’t have to waste a techs time, or my own by going downtown and the modem switch ending up not working. The strange thing about all of this is that the spikes occur more in certain game modes within the game (possibly because of server locations?).

 

Location: Cleveland, OH, 44105; multifamily

I only get internet through Spectrum

Modem: Arris TM1602A

Router: Netgear WNR2000

Modem Page:

Spoiler

 

Downstream

 

DCID

Freq

Power

SNR

Modulation

Octets

Correcteds

Uncorrectables

Downstream 1

24

765.00 MHz

2.60 dBmV

37.64 dB

256QAM

1995365837

3577

15346

Downstream 2

1

627.00 MHz

2.80 dBmV

38.61 dB

256QAM

582676599

7250

24775

Downstream 3

2

633.00 MHz

2.70 dBmV

38.61 dB

256QAM

558127212

7201

23438

Downstream 4

3

639.00 MHz

2.90 dBmV

38.61 dB

256QAM

580095572

8187

22008

Downstream 5

4

645.00 MHz

3.10 dBmV

38.98 dB

256QAM

575317500

6158

23460

Downstream 6

5

651.00 MHz

3.40 dBmV

38.61 dB

256QAM

595832720

6325

23136

Downstream 7

6

657.00 MHz

3.10 dBmV

38.61 dB

256QAM

664576360

5169

23095

Downstream 8

7

663.00 MHz

3.20 dBmV

38.61 dB

256QAM

646319857

4546

23866

Downstream 9

8

669.00 MHz

3.30 dBmV

38.61 dB

256QAM

652241653

4732

21652

Downstream 10

9

675.00 MHz

3.10 dBmV

37.94 dB

256QAM

869924833

4438

21836

Downstream 11

10

681.00 MHz

3.30 dBmV

38.98 dB

256QAM

581936433

4665

21890

Downstream 12

11

687.00 MHz

2.90 dBmV

38.61 dB

256QAM

644883015

4332

21637

Downstream 13

12

693.00 MHz

2.90 dBmV

38.98 dB

256QAM

646566519

4412

22065

Downstream 14

13

699.00 MHz

2.90 dBmV

38.61 dB

256QAM

811337758

4294

21452

Downstream 15

14

705.00 MHz

3.10 dBmV

38.61 dB

256QAM

590575114

4877

23051

Downstream 16

15

711.00 MHz

3.10 dBmV

38.61 dB

256QAM

650580360

4480

21335

Downstream 17

16

717.00 MHz

2.90 dBmV

38.61 dB

256QAM

608622562

3564

22063

Downstream 18

17

723.00 MHz

2.90 dBmV

38.61 dB

256QAM

636466036

3355

16476

Downstream 19

18

729.00 MHz

2.80 dBmV

38.98 dB

256QAM

676378254

5452

17029

Downstream 20

19

735.00 MHz

2.80 dBmV

38.61 dB

256QAM

647228691

5382

28407

Downstream 21

20

741.00 MHz

2.90 dBmV

38.61 dB

256QAM

651639649

4271

31472

Downstream 22

21

747.00 MHz

2.90 dBmV

38.61 dB

256QAM

689891303

6157

26437

Downstream 23

22

753.00 MHz

2.80 dBmV

38.98 dB

256QAM

618302114

3774

35584

Downstream 24

23

759.00 MHz

3.00 dBmV

38.61 dB

256QAM

640116514

3901

19338

 

Reset FEC Counters

Upstream

 

UCID

Freq

Power

Channel Type

Symbol Rate

Modulation

Upstream 1

66

24.20 MHz

43.00 dBmV

DOCSIS2.0 (ATDMA)

5120 kSym/s

64QAM

Upstream 2

68

37.00 MHz

43.75 dBmV

DOCSIS2.0 (ATDMA)

2560 kSym/s

64QAM

Upstream 3

67

30.60 MHz

45.25 dBmV

DOCSIS2.0 (ATDMA)

5120 kSym/s

64QAM

Upstream 4

65

19.40 MHz

43.00 dBmV

DOCSIS1.x (TDMA)

2560 kSym/s

16QAM

 

 

12 REPLIES 12
Observer

Re: Latency Issues

 Modem Page cont.

Spoiler

System Uptime:

1 d: 21 h: 31 m

Computers Detected:

staticCPE(1), dynamicCPE(1)

CM Status:

OPERATIONAL

Time and Date:

Wed 2019-01-02 20:25:17

 

Interface Parameters

 

Interface Name

Provisioned

State

Speed (Mbps)

MAC address

LAN

Enabled

Up

100(Full)

2C:95:69:16:4D:47

CABLE

Enabled

Up

-----

2C:95:69:16:4D:48

MTA

NotInitiated

Down

-----

2C:95:69:16:4D:49

 

--

System:

ARRIS DOCSIS 3.0 / PacketCable 2.0 Touchstone Telephony Modem

HW_REV: 1

VENDOR: ARRIS Group, Inc.

BOOTR: 2.2.0.45

SW_REV: 9.1.103J8TW1.SIP.PC20.TW

MODEL: TM1602AP2

Serial Number:

81Y2T8539105255

Options:

 

 

Firmware Name:

TS0901103J8TW1_010918_1602.TM_PC20_TW

Firmware Build Time:

Tue Jan 9 16:21:59 EST 2018

 

--

 

Date Time

Event ID

Event Level

Description

12/31/2018 23:05

84000500

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:05

84000700

5

RCS Partial Service;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:05

84000500

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:05

84000700

5

RCS Partial Service;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:05

84000500

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:05

84000700

5

RCS Partial Service;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:05

84020200

5

Lost MDD Timeout;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:05

84000700

5

RCS Partial Service;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:05

84020200

5

Lost MDD Timeout;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:05

84000700

5

RCS Partial Service;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:06

84020200

5

Lost MDD Timeout;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:06

84000700

5

RCS Partial Service;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:06

84000500

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:06

84000700

5

RCS Partial Service;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:06

84000500

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:06

84000700

5

RCS Partial Service;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:06

84000500

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:06

84000700

5

RCS Partial Service;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:06

84020200

5

Lost MDD Timeout;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

12/31/2018 23:06

84000700

5

RCS Partial Service;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

1/1/2019 12:43

82000200

3

No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:16:4d:48;CMTS-MAC=00:01:5c:89:20:72;CM-QOS=1.1;CM-VER=3.0;

 

Date Time

Event ID

Description

MTA Events List Empty

 

--

CM State:Docsis-Data Reg Complete

Docsis-Downstream Scanning

Completed

Docsis-Downstream Ranging

Completed

Docsis-Upstream Ranging

Completed

Docsis-DHCP

Completed

Docsis-TFTP

Completed

Docsis-Data Reg Complete

Completed

Telephony-DHCP

Not Started

Telephony-TFTP

Not Started

Telephony-Reg with Call Server

Not Started

Telephony-Reg Complete

Not Started

 

TOD State:

Time of Day

Retrieved

 

BPI State:

BPI Status

Enabled, Authorized

 

DHCP Attempts to obtain CM IP Address:

IPv4 Attempt(s)

1

IPv6 Attempt(s)

0

 

 

Observer

Re: Latency Issues

Modem is online and SN/MAC is correct

 

I believe I have the 60mbs plan; testing on Spectrum Columbus: Up is 12.1mbs, Down is 94.4mbs, ping and jitter aren't shown

 

As said before I've tested using a direct connection, connecting modem-router-computer wired, and wirelessly, nothing changes it.

 

I can't say how the cables are wired outside, but there is a splitter in my room, one goes to my modem and one is there from someone who had TV service here before. I'm currently using the cable that has always been connected to a modem. The splitter is an SV-2GT. The connector going into the modem is a PPC EX6 11. For the other it’s RG-59/U

 

The ethernet cord running from my modem to router, and router to computer are both CAT.5E. I have two other cables that are the same type.

 

Traceroute from their webtool

Spoiler

TRACEROUTE:

traceroute to 173.91.114.205 (173.91.114.205), 15 hops max, 60 byte packets

1 Blizzard Blizzard 1.133 ms 1.130 ms 1.130 ms Blizzard(24.105.18.2) 2.212 ms 2.247 ms 2.261 ms

3 137.221.105.14 (137.221.105.14) 2.266 ms 2.280 ms 2.302 ms

4 137.221.66.18 (137.221.66.18) 2.262 ms 2.275 ms 2.281 ms

5 137.221.83.66 (137.221.83.66) 6.692 ms 6.708 ms 6.712 ms

6 137.221.65.68 (137.221.65.68) 6.597 ms 6.302 ms 6.290 ms

7 137.221.68.32 (137.221.68.32) 6.235 ms 6.060 ms 6.048 ms

8 ae34.pr1.lax10.tbone.rr.com (66.109.9.160) 5.640 ms 6.081 ms 6.068 ms

9 bu-ether17.tustca4200w-bcr00.tbone.rr.com (107.14.19.55) 53.556 ms 53.572 ms 53.187 ms

10 be4.clmkohpe01r.midwest.rr.com (107.14.19.37) 57.330 ms 57.294 ms 56.916 ms

11 bu-ether16.chctilwc00w-bcr00.tbone.rr.com (66.109.6.226) 49.489 ms 56.758 ms 54.247 ms

12 be2.clmkohpe01r.midwest.rr.com (107.14.17.253) 61.475 ms 60.758 ms 60.743 ms

13 be1.pltsohae01r.midwest.rr.com (65.29.1.29) 76.061 ms 75.588 ms 75.573 ms

14 be2.bathoh0601r.midwest.rr.com (65.29.1.88) 68.600 ms 68.397 ms 68.211 ms

15 24.33.103.103 (24.33.103.103) 78.195 ms 78.204 ms 85.276 ms



01/01/2019 05:53:14 UTC

--------------------


TRACEROUTE:

traceroute to 173.91.114.205 (173.91.114.205), 15 hops max, 60 byte packets

1 Blizzard Blizzard 0.688 ms 0.696 ms 0.698 ms Blizzard(24.105.18.2) 1.395 ms 1.415 ms 1.424 ms

3 137.221.105.14 (137.221.105.14) 1.446 ms 1.431 ms 1.434 ms

4 137.221.66.18 (137.221.66.18) 1.376 ms 1.379 ms 1.381 ms

5 137.221.83.66 (137.221.83.66) 6.032 ms 6.053 ms 6.058 ms

6 137.221.65.68 (137.221.65.68) 24.902 ms 22.281 ms 22.253 ms

7 137.221.68.32 (137.221.68.32) 5.652 ms 5.685 ms 5.800 ms

8 ae34.pr1.lax10.tbone.rr.com (66.109.9.160) 5.454 ms 5.467 ms 5.469 ms

9 bu-ether17.tustca4200w-bcr00.tbone.rr.com (107.14.19.55) 50.133 ms 49.571 ms 49.536 ms

10 be4.clmkohpe01r.midwest.rr.com (107.14.19.37) 54.595 ms 52.566 ms 52.547 ms

11 bu-ether16.chctilwc00w-bcr00.tbone.rr.com (66.109.6.226) 52.198 ms 50.343 ms 50.059 ms

12 be2.clmkohpe01r.midwest.rr.com (107.14.17.253) 69.299 ms 69.324 ms 69.240 ms

13 be1.pltsohae01r.midwest.rr.com (65.29.1.29) 81.920 ms 75.550 ms 75.534 ms

14 be2.bathoh0601r.midwest.rr.com (65.29.1.88) 74.573 ms 68.767 ms 68.763 ms

15 24.33.103.103 (24.33.103.103) 82.227 ms 82.692 ms 82.714 ms


PING:

PING 173.91.114.205 (173.91.114.205) 56(84) bytes of data.


--- 173.91.114.205 ping statistics ---

4 packets transmitted, 0 received, 100% packet loss, time 2997ms

Traceroute ran from CMD

Spoiler

(Traceroute ran from cmd)


C:\WINDOWS\system32>pathping -n 24.105.40.32


Tracing route to 24.105.40.32 over a maximum of 30 hops


0 192.168.1.6

1 192.168.1.1

2 142.254.157.93

3 24.164.114.165

4 24.33.103.102

5 65.29.1.89

6 65.29.1.28

7 107.14.17.252

8 66.109.5.136

9 66.109.5.225

10 66.109.9.149

11 137.221.69.35

12 * * *

Computing statistics for 275 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 192.168.1.6

0/ 100 = 0% |

1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1

0/ 100 = 0% |

2 18ms 0/ 100 = 0% 0/ 100 = 0% 142.254.157.93

0/ 100 = 0% |

3 24ms 0/ 100 = 0% 0/ 100 = 0% 24.164.114.165

0/ 100 = 0% |

4 22ms 0/ 100 = 0% 0/ 100 = 0% 24.33.103.102

0/ 100 = 0% |

5 26ms 0/ 100 = 0% 0/ 100 = 0% 65.29.1.89

0/ 100 = 0% |

6 28ms 0/ 100 = 0% 0/ 100 = 0% 65.29.1.28

0/ 100 = 0% |

7 40ms 0/ 100 = 0% 0/ 100 = 0% 107.14.17.252

0/ 100 = 0% |

8 44ms 0/ 100 = 0% 0/ 100 = 0% 66.109.5.136

0/ 100 = 0% |

9 40ms 0/ 100 = 0% 0/ 100 = 0% 66.109.5.225

0/ 100 = 0% |

10 --- 100/ 100 =100% 100/ 100 =100% 66.109.9.149

0/ 100 = 0% |

11 87ms 0/ 100 = 0% 0/ 100 = 0% 137.221.69.35


Trace complete.

I also collected WinMTR stats when I was in a game with the latency issues.

Spoiler

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


|                                      WinMTR statistics             |


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


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


|                             192.168.1.1 - 0 | 203 | 203 |    0 | 0 | 52 | 0 |


|                          142.254.157.93 - 0 | 202 |  202 | 9 | 19 | 189 | 13 |


|         ae59.clevohaw02h.midwest.rr.com -    0 | 203 | 203 | 17 | 38 | 191 |   25 |


|         be22.bathoh0601r.midwest.rr.com -    0 | 203 | 203 | 14 | 25 | 226 |   18 |


|         be12.pltsohae01r.midwest.rr.com -    0 | 202 | 202 | 15 | 27 | 190 |   17 |


|         be25.clmkohpe01r.midwest.rr.com -    0 | 203 | 203 | 20 | 32 | 208 |   22 |


|                           107.14.17.252 - 0 | 202 |  202 | 28 | 40 | 191 | 35 |


|bu-ether11.chcgildt87w-bcr00.tbone.rr.com -    0 | 202 | 202 | 29 | 43 | 194 | 34 |


|                            66.109.5.225 - 0 | 202 | 202 |   28 | 44 | 183 | 31 |


|                            66.109.9.149 - 0 | 203 | 203 |   28 | 39 | 191 | 31 |


|              ae1-br01-eqch2.as57976.net -    0 | 202 | 202 | 29 | 53 | 255 |   38 |




Proven Sharer

Re: Latency Issues

Your modem reports that it is receiving a significant number of uncorrectible packet data errors on all of its incoming (DS) channels.  You say that you have a splitter with two cables but only one is connected, to your modem.  This is configured incorrectly.  You should remove the splitter, insert a coupler (aka 'barrel connector), and connect the modem cable directly to the incoming drop cable. 

 

That length of unused RG-59/U cable is acting like an antenna, inserting RF noise into your home cable wiring and degrading the data packets, which adds to the packet ping times.  RG-59/U cable is no longer approved for in-home wiring because its shielding is ineffective at cellphone frequencies.

 

@agentx5  Next, reviewing the tracert path info, here is the line for hop 9 where the delays jump from about 6 msec to 53 msec.

9 bu-ether17.tustca4200w-bcr00.tbone.rr.com (107.14.19.55) 53.556 ms 53.572 ms 53.187 ms

Hop #9 shows a device name referencing Tustin CA.  Either this device was physically moved in the network but not renamed, OR there's a  network path loop from OH out to CA and back.

You should make copies of the entire tracert lists and ask the home service tech to escalate your complaint to Tier 3 tech support.  They can check to make sure the internet backbone route to the IXP gateway is correctly programmed from end to end.

Observer

Re: Latency Issues

Just called tech support - apparently there aren't any tiers to support anymore. I explained what happened and I told him about the Tustin hop, to which he didn't pay much mind to. I asked him about the backbone route to the IXP gateway but it seemed like he had no clue what I was talking about. He told me the only solution would be port forwarding (which he didn't explain), and that since I have my own router I'd be on my own doing so. Not sure where to go from here. 

I'm going out this weekend to get the barrel connector to replace the splitter, I noticed after removing the other cable from my splitter that there are little to no correcteds/uncorrectables on the modem page, but I'm still experiencing the latency problem. 

 

Not applicable

Re: Latency Issues

Signals don't look too bad. The uncorrectables/correctables could use some work given you've been up for only a day. But I have seen a lot worse. Make sure you're using RG-6 cable and the connections are tight between the cable drop coming into your house, and all wiring in between that and your modem.

 

Do consider your modem to be the problem here. The Arris TM1602 has the Intel Puma6 in it. These have been known to cause the exact issues that you're seeing. Spectrum supplies new DOCSIS 3.1 modems now which are either Broadcom or Puma7 based. Puma7 has some issues but does not have the performance issues of the Puma6. These new modems go under the Spectrum branding but have the model numbers E31T2V1, E31H2V1, E31N2V1, and E31U2V1, made by Technicolor, Hitron (the middle two), and Ubee respectively.

 

Read more: https://www.dslreports.com/forum/r31122204-SB6190-Puma6-TCP-UDP-Network-Latency-Issue-Discussion

Observer

Re: Latency Issues

Looked at the article and ran the test I saw on there, it probably is an issue with the modem. Never would have thought it'd be for that reason though considering tech support told me the modem was fine. I plan on going this weekend to get my modem exchanged.

 

Pertaining to the barrel connector, I see a lot less correcteds and no correctables after replacing the splitter, though it didn't seem to help my issue, I'm assuming it will help in the longrun. 

 

Appreciate all of the help so far. 

Observer

Re: Latency Issues

Alrighty so I finally got the time to test after having the modem for about a week now. I can't really say I see less issues with the modem change. I continue to notice problems within the game with interpolation delay, will put in a spoiler elaborating what that means per their website considering the techs I had on the phone didn't know what that meant. 

 

9 bu-ether17.tustca4200w-bcr00.tbone.rr.com (107.14.19.55) 53.903 ms 52.803 ms 52.741 ms
10 bu-ether14.lsancarc0yw-bcr00.tbone.rr.com (66.109.6.4) 54.888 ms 52.995 ms 52.401 ms

Full New Traceroute:

Spoiler

TRACEROUTE:
traceroute to 24.93.186.232 (24.93.186.232), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.229 ms 0.224 ms 0.318 ms Blizzard(24.105.18.2) 1.387 ms 1.418 ms 1.442 ms
3 137.221.105.10 (137.221.105.10) 1.305 ms 1.322 ms 1.353 ms
4 137.221.66.16 (137.221.66.16) 1.283 ms 1.368 ms 1.376 ms
5 137.221.83.66 (137.221.83.66) 5.762 ms 5.788 ms 5.798 ms
6 137.221.65.68 (137.221.65.68) 5.604 ms 5.799 ms 5.801 ms
7 137.221.68.32 (137.221.68.32) 5.546 ms 5.581 ms 5.590 ms
8 ae34.pr1.lax10.tbone.rr.com (66.109.9.160) 5.740 ms 5.740 ms 5.738 ms
9 bu-ether17.tustca4200w-bcr00.tbone.rr.com (107.14.19.55) 53.903 ms 52.803 ms 52.741 ms
10 bu-ether14.lsancarc0yw-bcr00.tbone.rr.com (66.109.6.4) 57.126 ms 56.341 ms 55.718 ms
11 bu-ether16.chctilwc00w-bcr00.tbone.rr.com (66.109.6.226) 54.016 ms 53.266 ms 51.912 ms
12 be1.clmkohpe01r.midwest.rr.com (66.109.6.69) 60.377 ms 60.380 ms 60.101 ms
13 be1.pltsohae01r.midwest.rr.com (65.29.1.29) 67.697 ms 67.203 ms 67.170 ms
14 be1.mcdnohbg01r.midwest.rr.com (65.29.1.86) 64.779 ms 64.893 ms 64.889 ms
15 65.189.128.165 (65.189.128.165) 65.882 ms 66.216 ms 67.105 ms


21/01/2019 19:50:24 UTC
--------------------

TRACEROUTE:
traceroute to 24.93.186.232 (24.93.186.232), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.218 ms 1.186 ms 1.184 ms Blizzard(24.105.18.2) 1.425 ms 1.505 ms 1.695 ms
3 137.221.105.10 (137.221.105.10) 1.477 ms 1.555 ms 1.694 ms
4 137.221.66.16 (137.221.66.16) 1.558 ms 1.560 ms 1.564 ms
5 137.221.83.66 (137.221.83.66) 6.723 ms 6.736 ms 6.737 ms
6 137.221.65.68 (137.221.65.68) 6.574 ms 5.733 ms 5.718 ms
7 137.221.68.32 (137.221.68.32) 5.398 ms 5.524 ms 5.578 ms
8 ae34.pr1.lax10.tbone.rr.com (66.109.9.160) 5.339 ms 5.348 ms 5.347 ms
9 bu-ether17.tustca4200w-bcr00.tbone.rr.com (107.14.19.55) 56.398 ms 56.427 ms 55.849 ms
10 bu-ether14.lsancarc0yw-bcr00.tbone.rr.com (66.109.6.4) 54.888 ms 52.995 ms 52.401 ms
11 bu-ether16.chctilwc00w-bcr00.tbone.rr.com (66.109.6.226) 51.834 ms 51.187 ms 57.122 ms
12 be1.clmkohpe01r.midwest.rr.com (66.109.6.69) 65.604 ms 65.078 ms 65.057 ms
13 be1.pltsohae01r.midwest.rr.com (65.29.1.29) 65.245 ms 65.248 ms 65.277 ms
14 be1.mcdnohbg01r.midwest.rr.com (65.29.1.86) 64.849 ms 65.473 ms 65.551 ms
15 65.189.128.165 (65.189.128.165) 66.345 ms 66.361 ms 66.367 ms

 

This hop is still showing up in my traceroutes as well, when I tried explaining to the tech that this was happening he's saying if there was a problem it would be happening in Columbus, which clearly doesn't really help. I can't tell where hop 10 goes, and the route seems to have changed since I've gotten the new modem. 

 

interpolation delay:

Spoiler
IND: Interpolation Delay

To make sure other players' movements and actions appear smooth on your screen, there is a small buffer of time between when your client gets information from the server, and when it's shown to you in the game. This is normally around 50-60ms for normal games.

The IND value spikes up to 100+ during times of constant movement or movement/actions of a large group of players within an area. 

Sharer

Re: Latency Issues

Something fishy with that routing for sure. Looks like a jaunt through Chicago to L.A. and back for some strange reason. Tracing the same address from my router in South Carolina follows a much more logical path through NC/VA before the Chicago waypoint (we all have to hit that... which is a whole other problem), and then it drops down into OH. Aside from that Chicago area check-in, the latency grows accordingly according to distance... 18, 28, 36, 38, 40... and it only hit that 40-ish ms mark twice (around Chicago and Cleveland).

Something that T3 definitely needs to look into. They have that tier of support. They may call it something else... but it is there (it is a general term for a specific administrative level within the ISP's staffing).

Your case needs escalation to that higher tier of support to address this, as it is deeper into the upstream than the lower levels you typically get on the phone are set up to deal with. Some companies will not transfer you directly these days... it gets submitted "internally" and if they want/need to talk to you, you get a call back from them. They may be adopting this approach. In such formats, it is sometimes best to direct message their online representatives with the signal and tracert data so they can forward it appropriately.
Observer

Re: Latency Issues

I got a hold of someone though Spectrums online support who seemingly knew what she was talking about. See the confusing thing to me is definitely the routing from CA back to the midwest. The Spectrum agent told me that this is completely normal, and I believed it actually was considering Blizzard's headquarters are located in that area of CA. I decided to take to Blizzard's support and was told I would be connected to their Chicago server. The connection does actually from CA back to IL, the only thing that adds up here is it going to IL. The Blizzard agent said that I would be connected to the server that would give me the best connection possible, which of course is the one in Chicago. They also said that if there aren't enough players in my region within the certain gamemodes that I could be connected to a further server, which isn't consistent with my problem, where this only started happening a few months ago with certain gamemodes. 

 

I realize that the traceroutes from looking glass go from Blizzard to my location, I'm going to put in extra tests in spoilers below, which have sort of similar results. When running a ping through lookingglass I get 100% packet loss. When talking to the first Spectrum agent she told me I was getting 100% packet loss, she did something and ran tests again and said I still had that packet loss. This led her to suggest making an appointment for a tech to come out and look at the problem, which I think might be for the best honestly unless something groundbreaking occurs. 

 

On note of this issue I surprisingly found someone with a similar issue with the same exact game. It appears they live in the Florida area, but the connection goes to the same Tustin server and spikes up at that point. This was also fairly recent (just last month). 
http://www.tomshardware.com/answers/id-3844927/perfect-internet-speed-high-packet-loss-jitter-games....

Regardless of which way I trace it I don't see why it would jump up so high when going from LA(?) to Tustin. WinMTR traces to the servers directly, that being the IP I'm connected to, doesn't give off bad jumps. That's what gets me - if the WinMTR connected directly to the server shows no loss of packets and no huge spikes in ping, why is the delay so high?

 

 

Just talked to another agent and apparently they have it set up as their online chat being T2 support and the over-the-phone support being T3? Which doesn't really make sense considering nobody I talked to on the phone knew what I was on about. 

 

----------------------------------

Edit:
I just tested using my phones hotspot. Sadly I got smoother gameplay with that rather than my own interent. Of course there were spikes in the aforementioned stats but it's to be expected and didn't happen when multiple players were together or when I/other players were completing actions. It was more sporadic though, which again, to be expected. I was fortunate enough to finally get the trace and mtr results from looking glass. 

 

(carrier Sprint) 

Spoiler

TRACEROUTE:
traceroute to 184.217.67.242 (184.217.67.242), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.454 ms 0.465 ms 0.478 ms Blizzard(24.105.18.2) 1.478 ms 1.513 ms 1.530 ms
3 137.221.105.10 (137.221.105.10) 1.509 ms 1.536 ms 1.577 ms
4 137.221.66.20 (137.221.66.20) 1.470 ms 1.475 ms 1.491 ms
5 137.221.83.68 (137.221.83.68) 6.163 ms 6.180 ms 6.192 ms
6 137.221.65.68 (137.221.65.68) 5.997 ms 6.065 ms 6.035 ms
7 137.221.68.32 (137.221.68.32) 5.778 ms 5.789 ms 5.770 ms
8 213.248.78.166 (213.248.78.166) 6.353 ms 6.347 ms 6.347 ms
9 213.248.73.106 (213.248.73.106) 5.507 ms 5.658 ms 5.644 ms
10 144.232.15.34 (144.232.15.34) 12.147 ms 11.553 ms 10.787 ms
11 144.232.22.90 (144.232.22.90) 14.936 ms 14.340 ms 13.135 ms
12 144.232.22.95 (144.232.22.95) 17.188 ms 24.351 ms 24.354 ms
13 144.232.15.238 (144.232.15.238) 21.859 ms 21.864 ms 21.468 ms
14 144.232.15.91 (144.232.15.91) 32.542 ms 32.076 ms 32.287 ms
15 144.232.8.156 (144.232.8.156) 30.862 ms 30.385 ms 30.442 ms


22/01/2019 02:57:51 UTC
--------------------

TRACEROUTE:
traceroute to 184.217.67.242 (184.217.67.242), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.294 ms 0.293 ms 0.289 ms Blizzard(24.105.18.2) 0.615 ms 0.662 ms 0.755 ms
3 137.221.105.10 (137.221.105.10) 0.571 ms 0.635 ms 0.756 ms
4 137.221.66.20 (137.221.66.20) 0.713 ms 0.738 ms 0.751 ms
5 137.221.83.68 (137.221.83.68) 5.921 ms 5.947 ms 5.950 ms
6 137.221.65.68 (137.221.65.68) 5.681 ms 5.731 ms 5.717 ms
7 137.221.68.32 (137.221.68.32) 5.595 ms 5.610 ms 5.483 ms
8 213.248.78.166 (213.248.78.166) 7.232 ms 7.242 ms 7.243 ms
9 213.248.73.106 (213.248.73.106) 5.534 ms 5.530 ms 5.326 ms
10 144.232.15.34 (144.232.15.34) 12.694 ms 11.056 ms 10.341 ms
11 144.232.22.90 (144.232.22.90) 14.320 ms 13.843 ms 12.753 ms
12 144.232.22.95 (144.232.22.95) 17.113 ms 17.282 ms 16.756 ms
13 144.232.15.238 (144.232.15.238) 21.863 ms 21.715 ms 21.830 ms
14 144.232.15.91 (144.232.15.91) 32.670 ms 31.591 ms 31.601 ms
15 144.232.8.156 (144.232.8.156) 30.284 ms 31.385 ms 31.371 ms


22/01/2019 02:57:51 UTC
--------------------

MTR:
Start: Tue Jan 22 02:57:51 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.2 0.2 0.3 0.0 Blizzard 0.0% 10 0.6 0.6 0.5 1.3 0.0
3.|-- 137.221.105.10 0.0% 10 0.5 0.8 0.5 2.5 0.6
4.|-- 137.221.66.20 0.0% 10 0.6 0.9 0.5 3.9 0.9
5.|-- 137.221.83.68 0.0% 10 5.7 9.0 5.6 38.8 10.4
6.|-- 137.221.65.68 0.0% 10 5.6 5.7 5.6 5.9 0.0
7.|-- 137.221.68.32 0.0% 10 5.7 5.7 5.5 6.3 0.0
8.|-- 213.248.78.166 0.0% 10 5.8 5.9 5.7 7.2 0.3
9.|-- 213.248.73.106 0.0% 10 5.5 5.7 5.4 7.2 0.3
10.|-- 144.232.15.34 0.0% 10 9.3 9.3 6.5 12.5 2.4
11.|-- 144.232.22.90 0.0% 10 10.1 10.9 7.6 15.1 2.6
12.|-- 144.232.22.95 0.0% 10 19.0 20.6 16.9 24.5 2.5
13.|-- 144.232.15.238 0.0% 10 20.8 24.0 20.8 26.7 2.1
14.|-- 144.232.15.91 0.0% 10 33.6 32.3 30.4 33.9 1.1
15.|-- 144.232.8.156 0.0% 10 30.3 30.4 30.2 31.2 0.0
16.|-- 144.223.84.14 0.0% 10 30.8 31.0 30.7 32.0 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


22/01/2019 02:57:51 UTC
--------------------

MTR:
Start: Tue Jan 22 02:57:51 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.6 0.6 0.5 1.4 0.0
3.|-- 137.221.105.10 0.0% 10 0.8 0.7 0.5 0.9 0.0
4.|-- 137.221.66.20 0.0% 10 0.6 0.8 0.5 2.3 0.5
5.|-- 137.221.83.68 0.0% 10 5.9 7.4 5.6 21.6 4.9
6.|-- 137.221.65.68 0.0% 10 5.9 6.6 5.5 12.7 2.1
7.|-- 137.221.68.32 0.0% 10 5.4 5.6 5.4 5.8 0.0
8.|-- 213.248.78.166 0.0% 10 5.9 5.9 5.6 7.3 0.3
9.|-- 213.248.73.106 0.0% 10 5.5 5.4 5.3 5.5 0.0
10.|-- 144.232.15.34 0.0% 10 11.8 9.6 6.9 12.5 2.0
11.|-- 144.232.22.90 0.0% 10 12.5 10.3 7.6 13.2 2.0
12.|-- 144.232.22.95 0.0% 10 21.4 20.0 16.7 24.5 2.4
13.|-- 144.232.15.238 0.0% 10 23.3 23.4 20.4 26.6 2.4
14.|-- 144.232.15.91 0.0% 10 32.1 32.1 30.4 34.1 0.8
15.|-- 144.232.8.156 0.0% 10 30.6 30.4 30.2 30.8 0.0
16.|-- 144.223.84.14 0.0% 10 30.8 30.9 30.6 32.3 0.3
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


22/01/2019 02:57:51 UTC
--------------------

 

 

----------------------------------

latest trace from looking glass

Spoiler

TRACEROUTE:
traceroute to 24.93.186.232 (24.93.186.232), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.687 ms 1.670 ms 1.673 ms Blizzard(24.105.18.2) 2.398 ms 2.463 ms 2.477 ms
3 137.221.105.10 (137.221.105.10) 2.338 ms 2.363 ms 2.407 ms
4 137.221.66.16 (137.221.66.16) 2.375 ms 2.379 ms 2.382 ms
5 137.221.83.66 (137.221.83.66) 25.939 ms 25.945 ms 25.951 ms
6 137.221.65.68 (137.221.65.68) 7.075 ms 6.367 ms 6.349 ms
7 137.221.68.32 (137.221.68.32) 6.018 ms 6.032 ms 6.039 ms
8 ae34.pr1.lax10.tbone.rr.com (66.109.9.160) 5.436 ms 5.482 ms 5.489 ms
9 bu-ether17.tustca4200w-bcr00.tbone.rr.com (107.14.19.55) 51.255 ms 51.583 ms 50.982 ms
10 bu-ether14.lsancarc0yw-bcr00.tbone.rr.com (66.109.6.4) 55.647 ms 55.614 ms 52.038 ms
11 bu-ether16.chctilwc00w-bcr00.tbone.rr.com (66.109.6.226) 49.555 ms 49.525 ms 49.585 ms
12 be1.clmkohpe01r.midwest.rr.com (66.109.6.69) 64.280 ms 64.146 ms 64.095 ms
13 be1.pltsohae01r.midwest.rr.com (65.29.1.29) 71.178 ms 72.087 ms 72.065 ms
14 be1.mcdnohbg01r.midwest.rr.com (65.29.1.86) 65.571 ms 64.877 ms 65.209 ms
15 65.189.128.165 (65.189.128.165) 66.814 ms 66.607 ms 66.572 ms


22/01/2019 00:56:35 UTC
--------------------

TRACEROUTE:
traceroute to 24.93.186.232 (24.93.186.232), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.302 ms 1.270 ms 1.272 ms Blizzard(24.105.18.2) 2.104 ms 2.186 ms 2.191 ms
3 137.221.105.10 (137.221.105.10) 1.147 ms 1.172 ms 1.176 ms
4 137.221.66.16 (137.221.66.16) 1.094 ms 1.097 ms 1.102 ms
5 137.221.83.66 (137.221.83.66) 24.644 ms 24.649 ms 24.658 ms
6 137.221.65.68 (137.221.65.68) 5.780 ms 6.401 ms 6.398 ms
7 137.221.68.32 (137.221.68.32) 6.247 ms 6.298 ms 6.308 ms
8 ae34.pr1.lax10.tbone.rr.com (66.109.9.160) 6.039 ms 5.342 ms 5.327 ms
9 bu-ether17.tustca4200w-bcr00.tbone.rr.com (107.14.19.55) 51.938 ms 51.312 ms 51.539 ms
10 bu-ether14.lsancarc0yw-bcr00.tbone.rr.com (66.109.6.4) 55.918 ms 55.553 ms 54.263 ms
11 bu-ether16.chctilwc00w-bcr00.tbone.rr.com (66.109.6.226) 51.430 ms 51.458 ms 51.432 ms
12 be1.clmkohpe01r.midwest.rr.com (66.109.6.69) 66.325 ms 66.349 ms 64.863 ms
13 be1.pltsohae01r.midwest.rr.com (65.29.1.29) 72.096 ms 66.026 ms 66.048 ms
14 be1.mcdnohbg01r.midwest.rr.com (65.29.1.86) 64.768 ms 64.847 ms 65.174 ms
15 65.189.128.165 (65.189.128.165) 66.783 ms 66.521 ms 66.552 ms


22/01/2019 00:56:35 UTC
--------------------

PING:
PING 24.93.186.232 (24.93.186.232) 56(84) bytes of data.

--- 24.93.186.232 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3001ms

 

22/01/2019 00:56:35 UTC
--------------------

PING:
PING 24.93.186.232 (24.93.186.232) 56(84) bytes of data.

--- 24.93.186.232 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3000ms

 

22/01/2019 00:56:35 UTC
--------------------

MTR:
Start: Tue Jan 22 00:56:34 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0 Blizzard 0.0% 10 0.5 1.0 0.5 5.2 1.3
3.|-- 137.221.105.10 0.0% 10 0.5 0.6 0.5 0.7 0.0
4.|-- 137.221.66.16 0.0% 10 0.6 0.6 0.5 0.8 0.0
5.|-- 137.221.83.66 0.0% 10 5.7 5.8 5.7 5.9 0.0
6.|-- 137.221.65.68 0.0% 10 5.7 6.2 5.6 9.7 1.0
7.|-- 137.221.68.32 0.0% 10 5.5 5.6 5.5 5.8 0.0
8.|-- ae34.pr1.lax10.tbone.rr.com 0.0% 10 5.3 6.2 5.3 13.5 2.4
9.|-- bu-ether17.tustca4200w-bcr00.tbone.rr.com 0.0% 10 53.0 53.0 49.7 56.0 2.0
10.|-- bu-ether14.lsancarc0yw-bcr00.tbone.rr.com 0.0% 10 54.8 53.4 49.7 56.4 2.2
11.|-- bu-ether16.chctilwc00w-bcr00.tbone.rr.com 0.0% 10 57.2 53.6 49.4 57.2 2.6
12.|-- be1.clmkohpe01r.midwest.rr.com 0.0% 10 60.3 62.8 59.8 66.5 2.4
13.|-- be1.pltsohae01r.midwest.rr.com 0.0% 10 72.3 69.0 64.8 72.3 2.5
14.|-- be1.mcdnohbg01r.midwest.rr.com 0.0% 10 64.8 64.9 64.8 65.0 0.0
15.|-- 65.189.128.165 0.0% 10 66.2 66.5 66.1 67.2 0.0
16.|-- gig18-0.mntroh1-ar43.neo.rr.com 0.0% 10 70.1 70.1 70.0 70.1 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


22/01/2019 00:56:34 UTC
--------------------

MTR:
Start: Tue Jan 22 00:56:35 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.5 0.6 0.5 0.9 0.0
3.|-- 137.221.105.10 0.0% 10 0.7 0.6 0.5 0.9 0.0
4.|-- 137.221.66.16 0.0% 10 0.7 1.5 0.5 6.2 1.9
5.|-- 137.221.83.66 0.0% 10 8.4 8.4 5.6 28.8 7.2
6.|-- 137.221.65.68 0.0% 10 5.7 11.4 5.7 35.1 9.6
7.|-- 137.221.68.32 0.0% 10 5.7 9.0 5.6 27.6 7.3
8.|-- ae34.pr1.lax10.tbone.rr.com 0.0% 10 5.4 5.7 5.3 8.9 0.9
9.|-- bu-ether17.tustca4200w-bcr00.tbone.rr.com 0.0% 10 51.2 53.4 50.4 56.7 2.2
10.|-- bu-ether14.lsancarc0yw-bcr00.tbone.rr.com 0.0% 10 52.9 52.8 49.6 56.2 2.2
11.|-- bu-ether16.chctilwc00w-bcr00.tbone.rr.com 0.0% 10 55.1 53.4 49.9 56.7 2.2
12.|-- be1.clmkohpe01r.midwest.rr.com 0.0% 10 66.3 63.1 59.0 66.3 2.3
13.|-- be1.pltsohae01r.midwest.rr.com 0.0% 10 70.3 68.6 65.1 72.6 2.3
14.|-- be1.mcdnohbg01r.midwest.rr.com 0.0% 10 64.9 65.0 64.8 65.3 0.0
15.|-- 65.189.128.165 0.0% 10 66.5 66.8 66.2 67.4 0.0
16.|-- gig18-0.mntroh1-ar43.neo.rr.com 0.0% 10 70.0 70.1 70.0 70.2 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


22/01/2019 00:56:35 UTC
--------------------

 

trace to 24.105.18.2

Spoiler

Tracing route to 24.105.18.2 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 19 ms 10 ms 8 ms 142.254.145.137
3 11 ms 12 ms 11 ms 24.164.118.9
4 9 ms 8 ms 9 ms 24.164.236.2
5 10 ms 13 ms 14 ms be14.clevohek02r.midwest.rr.com [65.29.1.98]
6 14 ms 14 ms 15 ms be25.clevohek01r.midwest.rr.com [65.29.1.32]
7 22 ms 22 ms 22 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
8 24 ms 22 ms 23 ms bu-ether11.asbnva1611w-bcr00.tbone.rr.com [66.109.6.30]
9 17 ms 17 ms 16 ms 0.ae4.pr0.dca10.tbone.rr.com [107.14.19.133]
10 17 ms 24 ms 17 ms ae-14-0.ar0.dca10.tbone.rr.com [66.109.9.115]
11 78 ms 77 ms 79 ms ae1-br01-eqdc2.as57976.net [137.221.72.33]
12 78 ms 77 ms 78 ms et-0-0-2-br01-eqch2.as57976.net [137.221.65.13]
13 108 ms 96 ms 82 ms et-0-0-4-br01-eqda6.as57976.net [137.221.65.39]
14 77 ms 78 ms 78 ms et-0-0-2-br02-swlv10.as57976.net [137.221.65.67]
15 79 ms 77 ms 81 ms et-0-0-67-pe02-swlv10.as57976.net [137.221.83.73]
16 78 ms 78 ms 77 ms las-swlv10-ia-bons-04.as57976.net [137.221.66.23]
17 78 ms 78 ms 77 ms 24.105.18.2

Trace complete.

pathping to 24.105.18.2

Spoiler

Tracing route to 24.105.18.2 over a maximum of 30 hops

0 Andy [192.168.1.6]
1 192.168.1.1
2 142.254.145.137
3 24.164.118.9
4 24.164.236.2
5 be14.clevohek02r.midwest.rr.com [65.29.1.98]
6 be25.clevohek01r.midwest.rr.com [65.29.1.32]
7 bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
8 bu-ether11.asbnva1611w-bcr00.tbone.rr.com [66.109.6.30]
9 0.ae4.pr0.dca10.tbone.rr.com [107.14.19.133]
10 ae-14-0.ar0.dca10.tbone.rr.com [66.109.9.115]
11 ae1-br01-eqdc2.as57976.net [137.221.72.33]
12 et-0-0-2-br01-eqch2.as57976.net [137.221.65.13]
13 et-0-0-4-br01-eqda6.as57976.net [137.221.65.39]
14 et-0-0-2-br02-swlv10.as57976.net [137.221.65.67]
15 et-0-0-67-pe02-swlv10.as57976.net [137.221.83.73]
16 las-swlv10-ia-bons-04.as57976.net [137.221.66.23]
17 24.105.18.2

Computing statistics for 425 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Andy [192.168.1.6]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 142.254.145.137
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% 24.164.118.9
0/ 100 = 0% |
4 10ms 0/ 100 = 0% 0/ 100 = 0% 24.164.236.2
0/ 100 = 0% |
5 14ms 0/ 100 = 0% 0/ 100 = 0% be14.clevohek02r.midwest.rr.com [65.29.1.98]
0/ 100 = 0% |
6 14ms 0/ 100 = 0% 0/ 100 = 0% be25.clevohek01r.midwest.rr.com [65.29.1.32]
0/ 100 = 0% |
7 21ms 0/ 100 = 0% 0/ 100 = 0% bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
0/ 100 = 0% |
8 20ms 0/ 100 = 0% 0/ 100 = 0% bu-ether11.asbnva1611w-bcr00.tbone.rr.com [66.109.6.30]
0/ 100 = 0% |
9 20ms 0/ 100 = 0% 0/ 100 = 0% 0.ae4.pr0.dca10.tbone.rr.com [107.14.19.133]
0/ 100 = 0% |
10 18ms 0/ 100 = 0% 0/ 100 = 0% ae-14-0.ar0.dca10.tbone.rr.com [66.109.9.115]
0/ 100 = 0% |
11 23ms 0/ 100 = 0% 0/ 100 = 0% ae1-br01-eqdc2.as57976.net [137.221.72.33]
0/ 100 = 0% |
12 32ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-2-br01-eqch2.as57976.net [137.221.65.13]
0/ 100 = 0% |
13 56ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-4-br01-eqda6.as57976.net [137.221.65.39]
0/ 100 = 0% |
14 82ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-2-br02-swlv10.as57976.net [137.221.65.67]
0/ 100 = 0% |
15 --- 100/ 100 =100% 100/ 100 =100% et-0-0-67-pe02-swlv10.as57976.net [137.221.83.73]
0/ 100 = 0% |
16 --- 100/ 100 =100% 100/ 100 =100% las-swlv10-ia-bons-04.as57976.net [137.221.66.23]
0/ 100 = 0% |
17 80ms 0/ 100 = 0% 0/ 100 = 0% 24.105.18.2