Unusual high ping

[W0lfy]

What's going on with the server? Ping went from 100 to 150 all week long

[W0lfy]

I would like to add it's not a normal 150 ping. Feels more like 500. Everyone I've seen from California that plays on the server has the same problem. I did a traceroute and the results weren't pretty.

[Jun1oR]

I would like to add it's not a normal 150 ping. Feels more like 500. Everyone I've seen from California that plays on the server has the same problem. I did a traceroute and the results weren't pretty.

Can you post the results from a tracert to the server please. Also try enabling the lagometer and make sure the only colors in it are blue and green.

[W0lfy]

current traceroute


traceroute from last night


even though the traceroute improved the lagged feeling remains. lagometer is fine, no red or yellow. like i said this has been going on for about a week. the server was fine for me before that.

Last edited by W0lfy on Mon Jul 15, 2013 9:19 pm, edited 1 time in total.

[Jun1oR]

I think hops located at 154.54.12.45 and 38.122.62.218 are the problem and not to be server related. I experience high pings and packet loss to those hops. I even experience a lot of jitter from 152.63.5.245

Here is my results on a good day, which is why you don't see me on the server that much anymore.

Code:

Tracing route to unknown18.113.65.69.defenderhosting.com [69.65.113.18]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  FILESERVER [192.168.1.1]
  2     7 ms     1 ms     1 ms  L100.VFTTP-17.PHLAPA.verizon-gni.net [71.185.45.1]
  3     2 ms     3 ms     3 ms  G0-13-1-6.PHLAPA-LCR-22.verizon-gni.net [130.81.191.222]
  4     1 ms    <1 ms     5 ms  130.81.199.20
  5    11 ms    10 ms    11 ms  0.xe-2-1-0.BR2.IAD8.ALTER.NET [152.63.5.245]
  6    49 ms    48 ms    48 ms  te0-6-0-0.ccr21.iad02.atlas.cogentco.com [154.54.12.45]
  7    48 ms    47 ms    48 ms  38.122.62.218
  8    21 ms    23 ms    22 ms  cs7170112b.iad.keepitsecure.net [69.65.112.54]
  9    21 ms    20 ms    20 ms  unknown18.113.65.69.defenderhosting.com [69.65.113.18]

Trace complete.

C:\Windows\System32>ping -t 154.54.12.45

Pinging 154.54.12.45 with 32 bytes of data:
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=52ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Request timed out.
Reply from 154.54.12.45: bytes=32 time=52ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Request timed out.
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=50ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250
Reply from 154.54.12.45: bytes=32 time=49ms TTL=250

Ping statistics for 154.54.12.45:
    Packets: Sent = 48, Received = 46, Lost = 2 (4% loss),
Approximate round trip times in milli-seconds:
    Minimum = 49ms, Maximum = 52ms, Average = 49ms

C:\Windows\System32>ping 38.122.62.218 -t

Pinging 38.122.62.218 with 32 bytes of data:
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Request timed out.
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=50ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=50ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=50ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=50ms TTL=250
Reply from 38.122.62.218: bytes=32 time=50ms TTL=250
Reply from 38.122.62.218: bytes=32 time=50ms TTL=250
Reply from 38.122.62.218: bytes=32 time=50ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=191ms TTL=250
Reply from 38.122.62.218: bytes=32 time=224ms TTL=250
Request timed out.
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=50ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=50ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=50ms TTL=250
Reply from 38.122.62.218: bytes=32 time=50ms TTL=250
Reply from 38.122.62.218: bytes=32 time=52ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250
Reply from 38.122.62.218: bytes=32 time=49ms TTL=250

Ping statistics for 38.122.62.218:
    Packets: Sent = 58, Received = 56, Lost = 2 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 49ms, Maximum = 224ms, Average = 54ms

[Hayling]

I'm not encountering any routing problems on my end.

I can sometime ping 98-150ms. My current normal ping to the server's actual address is 80ms.

Code:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\USER-PC>tracert 69.65.113.18

Tracing route to unknown18.113.65.69.defenderhosting.com [69.65.113.18]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  ControlPanel.Home [192.168.1.1]
  2    22 ms    22 ms    25 ms  65.48.189.1
  3    22 ms    20 ms    20 ms  65.48.207.21
  4    58 ms    56 ms    56 ms  bgi1-mia1.caribsurf.com [65.48.247.18]
  5    55 ms    54 ms    54 ms  te0-0-0-19.ccr21.mia03.atlas.cogentco.com [38.10
4.95.121]
  6    57 ms    55 ms    54 ms  te0-1-0-6.ccr21.mia01.atlas.cogentco.com [154.54
.80.41]
  7    72 ms    69 ms    70 ms  te0-0-0-5.ccr21.atl01.atlas.cogentco.com [154.54
.30.33]
  8    80 ms    81 ms    80 ms  te0-1-0-6.ccr21.dca01.atlas.cogentco.com [154.54
.24.153]
  9    82 ms    82 ms    81 ms  be2042.ccr21.iad02.atlas.cogentco.com [154.54.26
.126]
 10    81 ms    80 ms    80 ms  38.122.62.218
 11    82 ms    82 ms    81 ms  cs7170112b.iad.keepitsecure.net [69.65.112.54]
 12    81 ms    81 ms    82 ms  unknown18.113.65.69.defenderhosting.com [69.65.1
13.18]

Trace complete.

C:\Users\USER-PC>ping 69.65.113.18

Pinging 69.65.113.18 with 32 bytes of data:
Reply from 69.65.113.18: bytes=32 time=82ms TTL=53
Reply from 69.65.113.18: bytes=32 time=82ms TTL=53
Reply from 69.65.113.18: bytes=32 time=80ms TTL=53
Reply from 69.65.113.18: bytes=32 time=81ms TTL=53

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

Also Junior, is the file attachments for this forum turned off?

[Jun1oR]

Also Junior, is the file attachments for this forum turned off?

No file attachments are enabled, are you unable to upload an attachment?

[Hayling]

I'm not seeing the upload attachments button on the reply editor. I was looking everywhere for it.

[Jun1oR]

I'm not seeing the upload attachments button on the reply editor. I was looking everywhere for it.

Ok sorry about that, the registered users permissions was set to limited. You should now see an "Upload attachment" tab next to the "Options" tab below the "Save draft", "Preview", and "Submit" buttons. Attachments are limited to 2MB and not all file types are allowed.

[Hayling]

Okay I see it now. Thanks Jun1or. :)

[W0lfy]

Appreciate the responses but I have talked to multiple players on the server from both northern and southern California different ISPs and they have the same issue. The server is broken for west coast players.

[MAN-AT-ARMS]

Its the service provider in the datacenter

[Tragic]

Not sure if it's just north and south, I'm eastern and I find that my ping has gone from 50, to about 90-100 in the last few weeks.

[CarpetClay]

Same here...ping is now 70-100 was 30s

[xdeadeye1]

Same here...ping is now 70-100 was 30s

whine