Office seems pretty unplayable.

Pinging 173.231.35.18 with 32 bytes of data:
Reply from 173.231.35.18: bytes=32 time=118ms TTL=50
Reply from 173.231.35.18: bytes=32 time=116ms TTL=50
Reply from 173.231.35.18: bytes=32 time=114ms TTL=50
Reply from 173.231.35.18: bytes=32 time=116ms TTL=50

Ping statistics for 173.231.35.18:
    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-18.hosted.static.webnx.com [173.231.35.18]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    *        *        *    Request timed out.
  3    31 ms    28 ms    8 ms  10.48.40.21
  4    10 ms    40 ms    12 ms  201-218-92-197.cpe-statics.cableonda.net [201.21
8.92.197]
  5  105 ms  105 ms  136 ms  64.210.12.185
  6  100 ms  103 ms  102 ms  xe3-3-0-10G.scr1.PTY2.gblx.net [67.16.132.153]
  7  105 ms  113 ms  108 ms  ae0-70G.scr3.LAX1.gblx.net [67.16.141.18]
  8  119 ms  100 ms  115 ms  e5-1-40G.ar6.LAX1.gblx.net [67.17.111.65]
  9  100 ms  107 ms  111 ms  PACKETEXCHANGE-LTD.Ethernet6-4.ar6.LAX1.gblx.net
[67.17.134.110]
10  119 ms  114 ms  118 ms  67.199.135.234
11  119 ms  120 ms  119 ms  100-42-223-154.static.webnx.com [100.42.223.154]

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

13  138 ms  136 ms  115 ms  173-231-35-18.hosted.static.webnx.com [173.231.3
5.18]

Trace complete.

[Assassin]

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

  1    1 ms    1 ms    1 ms  mygateway1.ar7 [192.168.1.1]
  2    *        *        *    Request timed out.
  3  101 ms    23 ms    24 ms  89.148.62.26
  4    24 ms    23 ms    23 ms  89.148.62.25
  5    24 ms    28 ms    25 ms  172.17.2.66
  6    23 ms    25 ms    25 ms  172.17.2.113
  7  244 ms  252 ms  259 ms  if-1-0-2.mcore4.NYY-NewYork.as6453.net [209.58.6
0.17]
  8  171 ms  171 ms  170 ms  ge-0-2-0.0.pjr02.ldn001.flagtel.com [85.95.25.58
]
  9  256 ms  246 ms  257 ms  Vlan25.icore1.NTO-NewYork.as6453.net [216.6.90.6
2]
10  172 ms  171 ms  173 ms  so-1-0-0.0.cjr02.ldn004.flagtel.com [85.95.25.10
]
11  257 ms  251 ms  250 ms  te0-6-0-1.ccr22.jfk05.atlas.cogentco.com [154.54
.12.93]
12  301 ms  299 ms  295 ms  10gigabitethernet7-4.core1.nyc4.he.net [72.52.92
.241]
13  258 ms  256 ms  257 ms  te0-2-0-7.ccr22.dca01.atlas.cogentco.com [154.54
.41.9]
14  305 ms  298 ms  299 ms  10gigabitethernet3-2.core1.den1.he.net [184.105.
213.86]
15  282 ms  292 ms  282 ms  te0-3-0-7.mpd22.atl01.atlas.cogentco.com [154.54
.27.98]
16  323 ms  322 ms  320 ms  216.218.213.250
17  325 ms  323 ms  321 ms  te0-2-0-5.mpd22.lax01.atlas.cogentco.com [154.54
.0.249]
18  328 ms  319 ms  324 ms  100-42-223-194.static.webnx.com [100.42.223.194]

19  320 ms  324 ms  318 ms  38.122.146.26
20  326 ms  338 ms  321 ms  173-231-20-21.hosted.static.webnx.com [173.231.2
0.21]

Trace complete.



Pinging 173.231.20.21 with 32 bytes of data:
Reply from 173.231.20.21: bytes=32 time=315ms TTL=45
Reply from 173.231.20.21: bytes=32 time=320ms TTL=45
Reply from 173.231.20.21: bytes=32 time=315ms TTL=45
Reply from 173.231.20.21: bytes=32 time=320ms TTL=45

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


idk why but ping was 340

[Matt]

Tomix I got this reply from our host

Looking at historical graphs his location is unstable lately across almost every provider. While tinet has the lowest ping, cogent has the best average. So the FCP has the preference of cogent over tinet. HE, Nlayer, Gtt, and Tinet are all showing what appears to be the results of attacks targeting his location.

I actually have to agree as your first couple of hops are very jittery.