Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
#11
I'll be raising a support ticket for this Tomix. I just noticed that WebNX is meant to have transit with TiNet so technically they should be able to at least try do something about it. Also Assassin your tracert is pretty whacked, can you do some more for me please?
#12
you mean do more tracing for other servers?
#13
I used to have 25-30, now it's 45-60. On office server it's 70-90.
[Image: jqmd52.png][Image: Craack.gif]
#14
Pinging 173.231.35.19 with 32 bytes of data:
Reply from 173.231.35.19: bytes=32 time=118ms TTL=50
Reply from 173.231.35.19: bytes=32 time=114ms TTL=50
Reply from 173.231.35.19: bytes=32 time=114ms TTL=50
Reply from 173.231.35.19: bytes=32 time=118ms TTL=50

Ping statistics for 173.231.35.19:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 114ms, Maximum = 118ms, Average = 116ms


Tracing route to 173.231.35.19 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    *        *        *    Request timed out.
  3    41 ms    11 ms    12 ms  10.48.40.21
  4    11 ms    8 ms    8 ms  201-218-92-205.cpe-statics.cableonda.net [201.21
8.92.205]
  5  101 ms  105 ms  103 ms  64.215.185.73
  6  102 ms  144 ms  102 ms  67.16.132.157
  7  128 ms  103 ms  101 ms  ae0-70G.scr4.LAX1.gblx.net [67.16.141.22]
  8  111 ms  100 ms  112 ms  e5-1-40G.ar6.LAX1.gblx.net [67.17.111.65]
  9  106 ms  107 ms  108 ms  PACKETEXCHANGE-LTD.Ethernet6-4.ar6.LAX1.gblx.net
[67.17.134.110]
10  117 ms  116 ms  118 ms  67.199.135.234
11  117 ms  124 ms  118 ms  100-42-223-154.static.webnx.com [100.42.223.154]

12  116 ms  118 ms  115 ms  100-42-223-170.static.webnx.com [100.42.223.170]

13  116 ms  133 ms  114 ms  173-231-35-19.hosted.static.webnx.com [173.231.3
5.19]

Trace complete.
[Image: 1qs5g7.png]
#15
Assassin Wrote:you mean do more tracing for other servers?

Any. I just want to see more.

Dr. Ruplayer Wrote:I used to have 25-30, now it's 45-60. On office server it's 70-90.

Tracert.
#16
Tracing route to 173-231-20-20.hosted.static.webnx.com [173.231.20.20]
over a maximum of 30 hops:

  1    2 ms    1 ms    1 ms  mygateway1.ar7 [192.168.1.1]
  2    *        *        *    Request timed out.
  3    32 ms    27 ms    25 ms  89.148.62.22
  4    23 ms    23 ms    24 ms  89.148.62.17
  5    24 ms    23 ms    24 ms  172.17.2.105
  6    24 ms    23 ms    22 ms  172.17.2.113
  7  170 ms  170 ms  170 ms  80.77.1.217
  8  169 ms  169 ms  170 ms  ge-0-2-0.0.pjr02.ldn001.flagtel.com [85.95.25.58]
  9  169 ms  169 ms  170 ms  ge-1-2-0.0.pjr02.ldn001.flagtel.com [85.95.25.141]
10  175 ms  181 ms  168 ms  so-1-0-0.0.cjr02.ldn004.flagtel.com [85.95.25.10]
11  170 ms  192 ms  199 ms  10gigabitethernet1-1.core1.lon1.he.net [195.66.224.21]
12  225 ms  225 ms  225 ms  10gigabitethernet7-4.core1.nyc4.he.net [72.52.92.241]
13  243 ms  243 ms  243 ms  10gigabitethernet8-3.core1.chi1.he.net [72.52.92.178]
14  289 ms  290 ms  296 ms  10gigabitethernet3-2.core1.den1.he.net [184.105.213.86]
15  296 ms  298 ms  298 ms  10gigabitethernet1-4.core1.lax2.he.net [72.52.92.38]
16  300 ms  299 ms  316 ms  216.218.213.250
17  300 ms  299 ms  300 ms  100-42-223-150.static.webnx.com [100.42.223.150]
18  300 ms  299 ms  299 ms  100-42-223-194.static.webnx.com [100.42.223.194]
19  300 ms  300 ms  299 ms  173-231-20-20.hosted.static.webnx.com [173.231.20.20]

Trace complete.

Pinging 173.231.20.20 with 32 bytes of data:
Reply from 173.231.20.20: bytes=32 time=300ms TTL=44
Reply from 173.231.20.20: bytes=32 time=299ms TTL=44
Reply from 173.231.20.20: bytes=32 time=298ms TTL=44
Reply from 173.231.20.20: bytes=32 time=299ms TTL=44

Ping statistics for 173.231.20.20:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 298ms, Maximum = 300ms, Average = 299ms




Tracing route to 173-231-35-18.hosted.static.webnx.com [173.231.35.18]
over a maximum of 30 hops:

  1    2 ms    1 ms    1 ms  mygateway1.ar7 [192.168.1.1]
  2    *        *        *    Request timed out.
  3    23 ms    23 ms    23 ms  89.148.62.22
  4    23 ms    22 ms    23 ms  89.148.62.25
  5    25 ms    22 ms    23 ms  172.17.2.58
  6    23 ms    22 ms    26 ms  172.17.2.113
  7  171 ms  170 ms  170 ms  so-2-2-0.cjr03.ldn001.flagtel.com [62.216.146.73]
  8  170 ms  171 ms  170 ms  ge [85.95.25.58]
  9  170 ms  171 ms  173 ms  ge [85.95.25.141]
10  172 ms  169 ms  171 ms  so [85.95.25.10]
11  173 ms  173 ms  174 ms  10gigabitethernet1 [195.66.224.21]
12  236 ms  227 ms  227 ms  10gigabitethernet7 [72.52.92.241]
13  243 ms  247 ms  249 ms  10gigabitethernet8 [72.52.92.178]
14  290 ms  291 ms  299 ms  10gigabitethernet3 [184.105.213.86]
15  298 ms  299 ms  297 ms  10gigabitethernet1 [72.52.92.38]
16  301 ms  300 ms  301 ms  216.218.213.250
17  301 ms  301 ms  303 ms  100-42-223-154.static.webnx.com [100.42.223.154]
18  300 ms  301 ms  301 ms  100-42-223-170.static.webnx.com [100.42.223.170]
19  300 ms  299 ms  300 ms  173-231-35-18.hosted.static.webnx.com [173.231.35.18]

Trace complete.

Pinging 173.231.35.18 with 32 bytes of data:
Reply from 173.231.35.18: bytes=32 time=299ms TTL=44
Reply from 173.231.35.18: bytes=32 time=299ms TTL=44
Reply from 173.231.35.18: bytes=32 time=299ms TTL=44
Reply from 173.231.35.18: bytes=32 time=300ms TTL=44

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




Tracing route to 173-231-35-19.hosted.static.webnx.com [173.231.35.19]
over a maximum of 30 hops:

  1    1 ms    1 ms    1 ms  mygateway1.ar7 [192.168.1.1]
  2    *        *        *    Request timed out.
  3    25 ms    23 ms    24 ms  89.148.62.18
  4    24 ms    23 ms    22 ms  89.148.62.49
  5    23 ms    23 ms    22 ms  172.17.2.86
  6    23 ms    23 ms    23 ms  172.17.2.113
  7  170 ms  170 ms  169 ms  80.77.1.217
  8  169 ms  194 ms  169 ms  ge [85.95.25.58]
  9  175 ms  171 ms  170 ms  ge [85.95.25.141]
10  170 ms  169 ms  168 ms  so [85.95.25.10]
11  170 ms  171 ms  171 ms  10gigabitethernet1 [195.66.224.21]
12  230 ms  226 ms  225 ms  10gigabitethernet7 [72.52.92.241]
13  247 ms  249 ms  248 ms  10gigabitethernet8 [72.52.92.178]
14  289 ms  298 ms  295 ms  10gigabitethernet3 [184.105.213.86]
15  297 ms  299 ms  299 ms  10gigabitethernet1 [72.52.92.38]
16  299 ms  300 ms  300 ms  216.218.213.250
17  300 ms  299 ms  300 ms  100-42-223-154.static.webnx.com [100.42.223.154
18  300 ms  299 ms  299 ms  100-42-223-170.static.webnx.com [100.42.223.170
19  298 ms  299 ms  299 ms  173-231-35-19.hosted.static.webnx.com [173.231.5.19]

Trace complete.


Pinging 173.231.35.19 with 32 bytes of data:
Reply from 173.231.35.19: bytes=32 time=304ms TTL=44
Reply from 173.231.35.19: bytes=32 time=299ms TTL=44
Reply from 173.231.35.19: bytes=32 time=301ms TTL=44
Reply from 173.231.35.19: bytes=32 time=299ms TTL=44

Ping statistics for 173.231.35.19:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 299ms, Maximum = 304ms, Average = 300ms
#17
Pinging 173.231.20.20 with 32 bytes of data:
Reply from 173.231.20.20: bytes=32 time=134ms TTL=50
Reply from 173.231.20.20: bytes=32 time=115ms TTL=50
Reply from 173.231.20.20: bytes=32 time=116ms TTL=50
Reply from 173.231.20.20: bytes=32 time=117ms TTL=50

Ping statistics for 173.231.20.20:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 115ms, Maximum = 134ms, Average = 120ms


Tracing route to 173-231-20-20.hosted.static.webnx.com [173.231.20.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    *        *        *    Request timed out.
  3    10 ms    56 ms    12 ms  10.48.40.21
  4    10 ms    11 ms    31 ms  201-218-92-205.cpe-statics.cableonda.net [201.21
8.92.205]
  5  116 ms  103 ms  102 ms  64.215.185.73
  6  103 ms  114 ms  105 ms  xe3-3-0-10G.scr2.PTY2.gblx.net [67.16.132.157]
  7  103 ms  121 ms  110 ms  ae0-70G.scr3.LAX1.gblx.net [67.16.141.18]
  8  103 ms  103 ms  104 ms  po2.ar4.LAX1.gblx.net [67.16.132.214]
  9  104 ms  106 ms  161 ms  PACKETEXCHANGE-LTD.Ethernet6-4.ar6.LAX1.gblx.net
[67.17.134.110]
10  119 ms  120 ms  117 ms  67.199.135.234
11  116 ms  118 ms  117 ms  100-42-223-150.static.webnx.com [100.42.223.150]

12  117 ms  133 ms  115 ms  100-42-223-194.static.webnx.com [100.42.223.194]

13  131 ms  118 ms  117 ms  173-231-20-20.hosted.static.webnx.com [173.231.2
0.20]

Trace complete.
[Image: 1qs5g7.png]
#18
24/7 office unbearable with more than 20 ppl.  interp at .07
#19
Mr.Tea Wrote:24/7 office unbearable with more than 20 ppl.  interp at .07

Quote:Tracing route to 173-231-35-18.hosted.static.webnx.com [173.231.35.18]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    9 ms    9 ms    8 ms  182.55.88.3
  3    8 ms    8 ms    8 ms  182.55.0.34
  4    18 ms    8 ms    9 ms  182.55.0.53
  5    9 ms    8 ms    8 ms  203.117.36.29
  6    8 ms    8 ms    8 ms  203.117.36.38
  7  209 ms  200 ms  213 ms  paix.cr2.sjc1.us.packetexchange.net [198.32.176.38]
  8  205 ms  211 ms  214 ms  69.174.120.181
  9  204 ms  203 ms  203 ms  67.199.135.234
10  203 ms  203 ms  203 ms  100-42-223-154.static.webnx.com [100.42.223.154]
11  204 ms  203 ms  203 ms  100-42-223-170.static.webnx.com [100.42.223.170]
12  204 ms  203 ms  203 ms  173-231-35-18.hosted.static.webnx.com [173.231.35.18]

Trace complete.


was with Tea. my ping is always around the 200ms range. So it looks pretty normal in this case?

but there was a moment it went up to 280, along with the others. Maybe doing a tracert then would have been a better help.
be the best version of yourself, that's all you can do.
#20
Hey Matt, Can you talk to me when you get on steam? I want to tracert it, but I lost/deleted the program you gave last time. Also, D2 servers, and Office.. Lag a lot.
[Image: 1UH9a8H.png]



[Image: 5pfuEDP.gif]

Users browsing this thread: 2 Guest(s)