Packetloss

**|uK|chiseller** · 09-19-2013

What's wrong with the server? Seems like half of the people have packetloss including myself.

@SAM

22:10:07 @chis � anyone else having packet loss on public?
22:10:32 @Convict � pretty sure its been like that few days
22:10:34 @Convict � total shit
22:10:42 @chis � was fine for me till today
22:10:51 @chis � I know clock had it yesterday
22:13:11 +Soldado � i have pl too...

**][X][~FLuKE~][X][** · 09-19-2013

same here, sometimes with huge ping spikes.

**UNrealshots** · 09-19-2013

get better host provider instead of the cheapest u can get then no problem friends.

**'Zac** · 09-19-2013

i usually go from a regular 40 ping to a 120 ping sometimes when im running and someone else is running and hitting me at the same time, like 2 collisions running into each other.

**SAM** · 09-19-2013

Need some traceroutes before ascertaining whether there is a problem on serverside network..

**|uK|fleecey** · 09-19-2013

I know danger had 50 pl today... idk, but i dont have any here... but seems lots of people today had it...

**|uK|chiseller** · 09-19-2013

Originally Posted by SAM

Need some traceroutes before ascertaining whether there is a problem on serverside network..

Like I said, it's a general problem and not just on my end but to make you happy.

Code:

Tracing route to ash.xfactorservers.com [75.102.40.198]
over a maximum of 30 hops:

  1    <1 ms     1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    12 ms    24 ms    12 ms  217-168-56-233.static.cablecom.ch [217.168.56.23
3]
  4   102 ms   102 ms   100 ms  84.116.204.233
  5   101 ms   102 ms   103 ms  84-116-130-181.aorta.net [84.116.130.181]
  6    99 ms   112 ms   104 ms  ro-tm01a-rd1-te-2-1.aorta.net [84.116.130.246]
  7   106 ms   117 ms   101 ms  84.116.133.169
  8   102 ms     *      104 ms  eqix.xe-3-3-0.cr2.iad1.us.nlayer.net [206.126.23
6.61]
  9     *      100 ms     *     as23352.xe-3-0-0-101.cr2.iad1.us.nlayer.net [69.
31.30.19]
 10   101 ms   102 ms   101 ms  as36352.ge-1-1-5.cr2.iad1.us.scnet.net [75.102.4
3.122]
 11   101 ms   102 ms   102 ms  ash.xfactorservers.com [75.102.40.198]

Trace complete.


ping 75.102.40.198

Pinging 75.102.40.198 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 75.102.40.198: bytes=32 time=130ms TTL=118
Request timed out.

Ping statistics for 75.102.40.198:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
    Minimum = 130ms, Maximum = 130ms, Average = 130ms

**SAM** · 09-19-2013

Originally Posted by |uK|chiseller

Like I said, it's a general problem and not just on my end but to make you happy.

It's not to make me happy. If you look at the trace, you will see hop 8 hits NLayer (server side network).

The network engineers are busy enough as it is. They have 100's, thousands if not millions of servers processing internet information. Layers and layers of internet communication layers. If they don't know where to look, where do you expect them to look to find the problem?

The traceroute helps to find problems. Looks like hop 9 is the issue here are there are two time outs. One timeout usually means the server was too busy to respond however if the following ping is ok then all is normal, so hop 8 is ok.

More traceroutes = quicker results. So anyone else who wants to be productive please provide traceroutes.

**SAM** · 09-19-2013

I raised a ticket and they requested an MTR

http://www.unrealkillers.com/f19/hig...e-related-793/

Would appreciate if people experiencing issues can post a sample

User Tag List

Thread: Packetloss

Thread Tools

Packetloss

Thread Information

Users Browsing this Thread

Similar Threads

I have packetloss ONLY on pug server and high ping too.

Combo + lag + packetloss

i have packetloss evrywhere.....

Packetloss

Packetloss

Members who have read this thread : 40

Tags for this Thread

Posting Permissions