PST Time 00:00:00GMT-8
Local Server Time 00:00:00GMT+8
ID
Password
FlashGuide
FlashGuide
HA Infomation

General Discussion
Forum Quick Menu

  Index

  • To all the recent laggers

    02. 20. 2012 06:21


normpearii
Since I have not lagged at all during the last 3 weeks, maybe if we compare my tracert to someone's who is lagging, we can find which hop is causing the lag issues for 75+% of the community.

Post your tracerts to: 211.43.149.199 (Nebraska) and 211.43.149.201 (Kaiser)

What SDE's ISP needs to fix the problem is information from Tracerts, not country and location, since every ISP routes differently.

 

  • Re : To all the recent laggers

    02. 20. 2012 06:25


normpearii
Nebraska

Originally Posted by normpearii


Tracing route to 211.43.149.199 over a maximum of 30 hops

1 (Home Network, Filtered for Security Reasons)
2 (Home Network, Filtered for Security Reasons)
3 17 ms 18 ms 21 ms cpe-98-27-176-1.neo.res.rr.com {98.27.176.1}
4 16 ms 11 ms 14 ms gig3-10.bathoh1-swt401.neo.rr.com {24.164.118.25}
5 18 ms 11 ms 11 ms tge1-3.stvloh1-swt401.neo.rr.com {24.164.117.83}
6 11 ms 11 ms 11 ms tge3-0-0.clevoh1-rtr01.neo.rr.com {24.164.117.134}
7 13 ms 13 ms 14 ms tge11-0-0.ncntoh1-rtr2.neo.rr.com {24.164.118.98}
8 18 ms 33 ms 16 ms tge2-0-1.ar01.clmkohpe.mwrtn.rr.com {65.25.137.65}
9 35 ms 16 ms 16 ms ae1.tr00.clmkohpe.mwrtn.rr.com {65.189.140.128}
10 27 ms 28 ms 28 ms ae-9-0.cr0.chi30.tbone.rr.com {107.14.19.16}
11 70 ms 29 ms 27 ms ae-1-0.pr0.chi10.tbone.rr.com {66.109.6.155}
12 59 ms 40 ms 40 ms xe-10-1-0.edge2.Chicago2.Level3.net {4.59.28.105}
13 44 ms 42 ms 47 ms vl-3502-ve-116.ebr1.Chicago2.Level3.net{4.69.158.6}
14 67 ms 60 ms 64 ms ae-3-3.ebr2.Denver1.Level3.net {4.69.132.61}
15 60 ms 57 ms 57 ms ae-1-100.ebr1.Denver1.Level3.net {4.69.151.181}
16 78 ms 76 ms 76 ms ae-3-3.ebr2.SanJose1.Level3.net {4.69.132.57}
17 90 ms 77 ms 79 ms ae-92-92.csw4.SanJose1.Level3.net {4.69.153.30}
18 76 ms 78 ms 76 ms ae-4-90.edge1.SanJose3.Level3.net {4.69.152.208}
19 85 ms 128 ms 84 ms PANTHER-EXP.edge1.SanJose3.Level3.net {4.53.208.10}****** (This is where I believe the issue to be)
20 87 ms 85 ms 86 ms 174.35.18.82
21 87 ms 87 ms 86 ms 174.35.13.242
22 77 ms 78 ms 78 ms 208.80.251.170
23 80 ms 80 ms 79 ms 211.43.149.199

Trace complete.



Kaiser

Originally Posted by normpearii


Tracing route to 211.43.149.201 over a maximum of 30 hops

1 (Home Network, Filtered for Security Reasons)
2 (Home Network, Filtered for Security Reasons)
3 26 ms 29 ms 29 ms cpe-98-27-176-1.neo.res.rr.com {98.27.176.1}
4 10 ms 13 ms 11 ms gig3-10.bathoh1-swt401.neo.rr.com {24.164.118.25}
5 12 ms 47 ms 11 ms tge1-7.stvloh1-swt401.neo.rr.com {24.164.117.155}
6 11 ms 11 ms 11 ms tge3-0-0.clevoh1-rtr01.neo.rr.com {24.164.117.134}
7 12 ms 11 ms 11 ms tge11-0-0.ncntoh1-rtr1.neo.rr.com {24.164.118.96}
8 17 ms 16 ms 16 ms tge3-0-1.ar01.clmkohpe.mwrtn.rr.com {65.25.137.73}
9 18 ms 16 ms 18 ms ae0.tr00.clmkohpe.mwrtn.rr.com {65.189.140.142}
10 28 ms 30 ms 28 ms ae-9-0.cr0.chi30.tbone.rr.com {107.14.19.16}
11 31 ms 29 ms 32 ms ae-1-0.pr0.chi10.tbone.rr.com {66.109.6.155}
12 50 ms 40 ms 40 ms xe-10-2-0.edge2.Chicago2.Level3.net {4.59.28.109}
13 71 ms 54 ms 43 ms vl-3504-ve-118.ebr1.Chicago2.Level3.net{4.69.158.14}
14 60 ms 58 ms 57 ms ae-3-3.ebr2.Denver1.Level3.net {4.69.132.61}
15 58 ms 56 ms 57 ms ae-1-100.ebr1.Denver1.Level3.net {4.69.151.181}
16 80 ms 76 ms 94 ms ae-3-3.ebr2.SanJose1.Level3.net {4.69.132.57}
17 81 ms 76 ms 76 ms ae-62-62.csw1.SanJose1.Level3.net {4.69.153.18}
18 78 ms 76 ms 76 ms ae-1-60.edge1.SanJose3.Level3.net {4.69.152.16}
19 85 ms 83 ms 83 ms PANTHER-EXP.edge1.SanJose3.Level3.net {4.53.208.10}
20 84 ms 85 ms 89 ms 174.35.18.82
21 88 ms 88 ms 88 ms 174.35.13.242
22 77 ms 78 ms 76 ms 208.80.251.170
23 82 ms 78 ms 78 ms 211.43.149.201

Trace complete.



PANTHER-EXP.edge1.SanJose3.Level3.net [4.53.208.10] Seams to be the trouble spot, where out of 4 tracerts to each server, it showed a high ping 50% of the time.

PANTHER-EXP.edge1.SanJose3.Level3.net [4.53.208.10] Ping results:
[QUOTE=normpearii]

Pinging 4.53.208.10 with 32 bytes of data:
Reply from 4.53.208.10: bytes=32 time=94ms TTL=45
Reply from 4.53.208.10: bytes=32 time=85ms TTL=45
Reply from 4.53.208.10: bytes=32 time=85ms TTL=45
Reply from 4.53.208.10: bytes=32 time=88ms TTL=45

Ping statistics for 4.53.208.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 94ms, Average = 88ms

Pinging 4.53.208.10 with 32 bytes of data:
Reply from 4.53.208.10: bytes=32 time=112ms TTL=45
Reply from 4.53.208.10: bytes=32 time=87ms TTL=45
Reply from 4.53.208.10: bytes=32 time=86ms TTL=45
Reply from 4.53.208.10: bytes=32 time=87ms TTL=45

Ping statistics for 4.53.208.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 86ms, Maximum = 112ms, Average = 93ms

Pinging 4.53.208.10 with 32 bytes of data:
Reply from 4.53.208.10: bytes=32 time=107ms TTL=45
Reply from 4.53.208.10: bytes=32 time=87ms TTL=45
Reply from 4.53.208.10: bytes=32 time=113ms TTL=45
Reply from 4.53.208.10: bytes=32 time=84ms TTL=45

Ping statistics for 4.53.208.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 113ms, Average = 97ms

Pinging 4.53.208.10 with 32 bytes of data:
Reply from 4.53.208.10: bytes=32 time=91ms TTL=45
Reply from 4.53.208.10: bytes=32 time=85ms TTL=45
Reply from 4.53.208.10: bytes=32 time=87ms TTL=45
Reply from 4.53.208.10: bytes=32 time=85ms TTL=45

Ping statistics for 4.53.208.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 91ms, Average = 87ms

Pinging 4.53.208.10 with 32 bytes of data:
Reply from 4.53.208.10: bytes=32 time=91ms TTL=45
Reply from 4.53.208.10: bytes=32 time=97ms TTL=45
Reply from 4.53.208.10: bytes=32 time=87ms TTL=45
Reply from 4.53.208.10: bytes=32 time=85ms TTL=45
Reply from 4.53.208.10: bytes=32 time=87ms TTL=45
Reply from 4.53.208.10: bytes=32 time=87ms TTL=45
Reply from 4.53.208.10: bytes=32 time=94ms TTL=45
Reply from 4.53.208.10: bytes=32 time=87ms TTL=45
Reply from 4.53.208.10: bytes=32 time=85ms TTL=45
Reply from 4.53.208.10: bytes=32 time=91ms TTL=45
Reply from 4.53.208.10: bytes=32 time=88ms TTL=45
Reply from 4.53.208.10: bytes=32 time=87ms TTL=45
Reply from 4.53.208.10: bytes=32 time=86ms TTL=45
Reply from 4.53.208.10: bytes=32 time=86ms TTL=45
Reply from 4.53.208.10: bytes=32 time=87ms TTL=45
Reply from 4.53.208.10: bytes=32 time=85ms TTL=45
Reply from 4.53.208.10: bytes=32 time=102ms TTL=45
Reply from 4.53.208.10: bytes=32 time=85ms TTL=45
Reply from 4.53.208.10: bytes=32 time=112ms TTL=45
Reply from 4.53.208.10: bytes=32 time=86ms TTL=45
Reply from 4.53.208.10: bytes=32 time=86ms TTL=45
Reply from 4.53.208.10: bytes=32 time=86ms TTL=45
Reply from 4.53.208.10: bytes=32 time=101ms TTL=45
Reply from 4.53.208.10: bytes=32 time=131ms TTL=45
Reply from 4.53.208.10: bytes=32 time=88ms TTL=45
Reply from 4.53.208.10: bytes=32 time=86ms TTL=45
Reply from 4.53.208.10: bytes=32 time=86ms TTL=45
Reply from 4.53.208.10: bytes=32 time=87ms TTL=45
Reply from 4.53.208.10: bytes=32 time=85ms TTL=45
Reply from 4.53.208.10: bytes=32 time=86ms TTL=45
Reply from 4.53.208.10: bytes=32 time=118ms TTL=45
Reply from 4.53.208.10: bytes=32 time=85ms TTL=45
Reply from 4.53.208.10: bytes=32 time=117ms TTL=45
Reply from 4.53.208.10: bytes=32 time=93ms TTL=45
Reply from 4.53.208.10: bytes=32 time=124ms TTL=45
Repl

  • Re : To all the recent laggers

    02. 20. 2012 12:17


Doomraver
8 26 ms 26 ms 26 ms tinet-XE5-0-1-0-grtfraix4.red.telefonica-wholesa
le.net [213.140.52.98]
9 185 ms 182 ms 183 ms xe-1-0-0.sjc12.ip4.tinet.net [89.149.184.121]
10 182 ms 185 ms 183 ms panther-express-gw.ip4.tinet.net [77.67.68.138]

11 189 ms 189 ms 188 ms 174.35.18.62
12 188 ms 187 ms 190 ms 174.35.13.226
13 179 ms 179 ms 181 ms 208.80.251.170
14 179 ms 180 ms 182 ms 211.43.149.199


This is where it gets bad over here. From 26 ms to 183ms. Never had it that bad before.

  • Re : To all the recent laggers

    02. 20. 2012 12:47


AndrusN
Tracing route to 211.43.149.199 over a maximum of 30 hops

1 9 ms 13 ms 7 ms 10.107.14.1
2 9 ms 9 ms 17 ms 192.168.35.73
3 60 ms 59 ms 56 ms 192.168.102.6
4 58 ms 48 ms 51 ms xe-10-1-0.edge4.Chicago2.Level3.net [4.28.68.25]

5 49 ms 49 ms 60 ms 4.69.158.134
6 84 ms 80 ms 86 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
7 86 ms 167 ms 96 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

8 125 ms 98 ms 107 ms ae-3-3.ebr2.SanJose1.Level3.net [4.69.132.57]
9 102 ms 97 ms 126 ms ae-92-92.csw4.SanJose1.Level3.net [4.69.153.30]

10 99 ms 108 ms 105 ms ae-4-90.edge1.SanJose3.Level3.net [4.69.152.208]

11 99 ms 99 ms 98 ms PANTHER-EXP.edge1.SanJose3.Level3.net [4.53.208.
10]
12 101 ms 103 ms 99 ms 174.35.18.82
13 106 ms 103 ms 113 ms 174.35.13.246
14 99 ms * 98 ms 208.80.251.170
15 99 ms 131 ms 110 ms 211.43.149.199

Trace complete.

  • Re : To all the recent laggers

    02. 20. 2012 13:37


BradeLern
I did a tracert and a pathping just to be safe cause i don't know what i'm doing :P.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Brademan>tracert 211.43.149.201

Tracing route to 211.43.149.201 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms core31.stolaf.edu [130.71.31.1]
2 11 ms 4 ms 4 ms v1202.core1.msp1.he.net [216.66.73.193]
3 13 ms 21 ms 23 ms 10gigabitethernet7-4.core1.chi1.he.net [184.105.
213.133]
4 37 ms 47 ms 37 ms 10gigabitethernet3-2.core1.den1.he.net [184.105.
213.86]
5 64 ms 63 ms 72 ms 10gigabitethernet11-4.core1.sjc2.he.net [184.105
.213.105]
6 64 ms 64 ms 70 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
7 * * * Request timed out.
8 64 ms 64 ms 64 ms 174.35.18.82
9 66 ms 70 ms 66 ms 174.35.13.242
10 65 ms 65 ms 65 ms 208.80.251.170
11 65 ms 66 ms 66 ms 211.43.149.201

Trace complete.

C:\Users\Brademan>pathping 211.43.149.201

Tracing route to 211.43.149.201 over a maximum of 30 hops

0 Brademan-VAIO.stolaf.edu [130.71.31.65]
1 core31.stolaf.edu [130.71.31.1]
2 v1202.core1.msp1.he.net [216.66.73.193]
3 10gigabitethernet7-4.core1.chi1.he.net [184.105.213.133]
4 10gigabitethernet3-2.core1.den1.he.net [184.105.213.86]
5 10gigabitethernet11-4.core1.sjc2.he.net [184.105.213.105]
6 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
7 * * *
Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Brademan-VAIO.stolaf.edu [130.71.3
1.65]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% core31.stolaf.edu [130.71.31.1]
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% v1202.core1.msp1.he.net [216.66.73
.193]
0/ 100 = 0% |
3 16ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet7-4.core1.chi1.he
.net [184.105.213.133]
0/ 100 = 0% |
4 40ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet3-2.core1.den1.he
.net [184.105.213.86]
0/ 100 = 0% |
5 67ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet11-4.core1.sjc2.h
e.net [184.105.213.105]
0/ 100 = 0% |
6 67ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet3-2.core1.pao1.he
.net [72.52.92.69]

Trace complete.

I'm completely dying out over the 7th hookup. That's why my pathping fails at step 6. If i did it wrong, tell me how to do it right and I'll fix it.

  • Re : To all the recent laggers

    02. 20. 2012 13:44


BradeLern
[QUOTE=BradeLern]


6 64 ms 64 ms 70 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
7 * * * Request timed out.
8 64 ms 64 ms 64 ms 174.35.18.82
9 66 ms 70 ms 66 ms 174.35.13.242
10 65 ms 65 ms 65 ms 208.80.251.170
11 65 ms 66 ms 66 ms 211.43.149.201
[/QUOTE]

Originally Posted by normpearii

18 76 ms 78 ms 76 ms ae-4-90.edge1.SanJose3.Level3.net {4.69.152.208}
19 85 ms 128 ms 84 ms PANTHER-EXP.edge1.SanJose3.Level3.net {4.53.208.10}****** (This is where I believe the issue to be)
20 87 ms 85 ms 86 ms 174.35.18.82


I agree with you norm that it's the San Jose location. The serial numbers match up there for us afterwards. I time out though, so I can't be positive.

  • Re : To all the recent laggers

    02. 20. 2012 13:55


jimbursch
I have never had a lag problem until this week.

Since I don't know how to copy/paste from the command prompt, I grabbed a screen capture here:
http://tinypic.com/view.php?pic=vrq5wy&s=5

[IMG]http://i39.tinypic.com/vrq5wy.jpg[/IMG]

  • Re : To all the recent laggers

    02. 20. 2012 17:20


adams67s
Tracing route to 211.43.149.199 over a maximum of 30 hops

1 3 ms <1 ms <1 ms EDIT
2 30 ms 30 ms 30 ms EDIT
3 41 ms 42 ms 41 ms 72.36.48.1.dyn.actaccess.net [72.36.48.1]
4 53 ms 54 ms 54 ms 72.36.7.109.static.actaccess.net [72.36.7.109]
5 78 ms 78 ms 76 ms 66.62.227.17
6 77 ms 77 ms 75 ms den1-core-01-ae1.360.net [66.62.2.193]
7 77 ms 76 ms 77 ms xe-8-3-0.edge3.Denver1.Level3.net [4.28.20.13]
8 87 ms 77 ms 76 ms vlan51.ebr1.Denver1.Level3.net [4.69.147.94]
9 103 ms 101 ms 102 ms ae-3-3.ebr2.SanJose1.Level3.net [4.69.132.57]
10 102 ms 113 ms 102 ms ae-72-72.csw2.SanJose1.Level3.net [4.69.153.22]

11 103 ms 137 ms 103 ms ae-2-70.edge1.SanJose3.Level3.net [4.69.152.80]

12 109 ms 109 ms 143 ms PANTHER-EXP.edge1.SanJose3.Level3.net [4.53.208.10]
13 110 ms 110 ms 111 ms 174.35.18.82
14 113 ms 111 ms 109 ms 174.35.13.242
15 102 ms 105 ms 103 ms 208.80.251.170
16 106 ms 103 ms 104 ms 211.43.149.199

  • Re : To all the recent laggers

    02. 20. 2012 17:59


snoweman
2 results for Nebraska
Tracing route to 211.43.149.199 over a maximum of 30 hops

1 11 ms 18 ms 19 ms 10.169.64.1
2 9 ms 10 ms 10 ms ip68-6-12-118.sd.sd.cox.net [68.6.12.118]
3 9 ms 11 ms 11 ms elcnsysc02-tec142.sd.sd.cox.net [68.6.8.56]
4 21 ms 22 ms 63 ms paltbprj01-ae2.0.rd.pt.cox.net [68.1.2.98]
5 25 ms 25 ms 27 ms 198.32.176.104
6 45 ms 32 ms 28 ms 174.35.18.82
7 26 ms 27 ms 26 ms 174.35.13.242
8 27 ms 25 ms 25 ms 208.80.251.170
9 27 ms 42 ms 27 ms 211.43.149.199

Trace complete.

Tracing route to 211.43.149.199 over a maximum of 30 hops

1 9 ms 21 ms 8 ms 10.169.64.1
2 9 ms 9 ms 11 ms ip68-6-12-118.sd.sd.cox.net [68.6.12.118]
3 9 ms 23 ms 11 ms elcnsysc02-tec142.sd.sd.cox.net [68.6.8.56]
4 22 ms 23 ms 21 ms paltbprj01-ae2.0.rd.pt.cox.net [68.1.2.98]
5 27 ms 25 ms 23 ms 198.32.176.104
6 30 ms 33 ms 32 ms 174.35.18.82
7 25 ms 27 ms 27 ms 174.35.13.242
8 26 ms 26 ms 23 ms 208.80.251.170
9 28 ms 26 ms 38 ms 211.43.149.199

Trace complete.


2 results for Kaiser
Tracing route to 211.43.149.201 over a maximum of 30 hops

1 10 ms 11 ms 11 ms 10.169.64.1
2 12 ms 9 ms 9 ms 68.6.11.233
3 10 ms 9 ms 9 ms elcnsysc02-tec142.sd.sd.cox.net [68.6.8.56]
4 21 ms 25 ms 21 ms paltbprj01-ae2.0.rd.pt.cox.net [68.1.2.98]
5 28 ms 33 ms 29 ms 198.32.176.104
6 26 ms 26 ms 28 ms 174.35.18.82
7 27 ms 25 ms 25 ms 174.35.13.242
8 27 ms 27 ms 25 ms 208.80.251.170
9 25 ms 25 ms 27 ms 211.43.149.201

Trace complete.

Tracing route to 211.43.149.201 over a maximum of 30 hops

1 12 ms 9 ms 9 ms 10.169.64.1
2 10 ms 9 ms 9 ms 68.6.11.233
3 10 ms 10 ms 9 ms elcnsysc02-tec142.sd.sd.cox.net [68.6.8.56]
4 24 ms 23 ms 21 ms paltbprj01-ae2.0.rd.pt.cox.net [68.1.2.98]
5 26 ms 25 ms 25 ms 198.32.176.104
6 30 ms 28 ms 27 ms 174.35.18.82
7 27 ms 25 ms 29 ms 174.35.13.242
8 25 ms 23 ms 25 ms 208.80.251.170
9 27 ms 25 ms 25 ms 211.43.149.201

Trace complete.


That doesn't look too bad but I am still lagging every game, even late at night when traffic is not as heavy. Not to mention the website is slower than usual. This just started in the last 2-3 weeks.

  • Re : To all the recent laggers

    02. 20. 2012 18:12


master72
ya the website takes longer to load

  • Re : To all the recent laggers

    02. 20. 2012 18:44


maykel
Tracing route to 211.43.149.201 over a maximum of 30 hops

0 ---
1 ---
2 180.191.30.1
3 120.28.64.13
4 120.28.1.65
5 120.28.0.22
6 120.28.0.122
7 203.208.131.201
8 203.208.166.57
9 203.208.171.186
10 203.208.171.154
11 198.32.176.104
12 174.35.18.82
13 174.35.13.242
14 208.80.251.170
15 211.43.149.201

Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 ---

1 ---

2 22ms 0/ 100 = 0% 0/ 100 = 0% 180.191.30.1
0/ 100 = 0% |
3 24ms 0/ 100 = 0% 0/ 100 = 0% 120.28.64.13
0/ 100 = 0% |
4 24ms 0/ 100 = 0% 0/ 100 = 0% 120.28.1.65
0/ 100 = 0% |
5 25ms 0/ 100 = 0% 0/ 100 = 0% 120.28.0.22
0/ 100 = 0% |
6 67ms 0/ 100 = 0% 0/ 100 = 0% 120.28.0.122
0/ 100 = 0% |
7 110ms 0/ 100 = 0% 0/ 100 = 0% 203.208.131.201
0/ 100 = 0% |
8 106ms 0/ 100 = 0% 0/ 100 = 0% 203.208.166.57
0/ 100 = 0% |
9 227ms 0/ 100 = 0% 0/ 100 = 0% 203.208.171.186
0/ 100 = 0% |
10 256ms 0/ 100 = 0% 0/ 100 = 0% 203.208.171.154
0/ 100 = 0% |
11 179ms 0/ 100 = 0% 0/ 100 = 0% 198.32.176.104
0/ 100 = 0% |
12 212ms 0/ 100 = 0% 0/ 100 = 0% 174.35.18.82
0/ 100 = 0% |
13 216ms 0/ 100 = 0% 0/ 100 = 0% 174.35.13.242
0/ 100 = 0% |
14 221ms 0/ 100 = 0% 0/ 100 = 0% 208.80.251.170
0/ 100 = 0% |
15 213ms 0/ 100 = 0% 0/ 100 = 0% 211.43.149.201

Trace complete.

1 2