cancel
Showing results for 
Search instead for 
Did you mean: 

xe-10-2-0.pcl-cr01.plus.net [212.159.0.200] - RTT nearer eme than 40ms

Gythral8PNC
Rising Star
Posts: 57
Thanks: 3
Fixes: 1
Registered: 06-02-2014

xe-10-2-0.pcl-cr01.plus.net [212.159.0.200] - RTT nearer eme than 40ms


Target Name: N/A
        IP: 159.100.232.171
  Date/Time: 01/11/2014 21:50:40 to 01/11/2014 22:03:25
Hop Sent Err  PL% Min Max Avg  Host Name / [IP]
1    52  0  0.0  0  1  0  dsldevice.lan [192.168.1.254]
2    52  0  0.0  46  80  49  lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3    52  0  0.0  46  48  46  link-a-central10.pcl-gw01.plus.net [212.159.2.168]
4    52  0  0.0  45 175  54  xe-10-2-0.pcl-cr01.plus.net [212.159.0.200]
5    52  0  0.0  46  89  48  xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
6    52  52 100.0  0  0  0  [-]
7    52  52 100.0  0  0  0  [-]
8    52  0  0.0  55  99  57  [212.162.9.150]
9    52  0  0.0  56  69  56  [195.122.154.3]
10    52  0  0.0  55  57  56  [159.100.232.171]

The last week trying to play ESO (EU) and getting EME type RTT from  xe-10-2-0.pcl-cr01.plus.net [212.159.0.200] on a regular basis
3 REPLIES
Community Veteran
Posts: 6,818
Registered: 27-10-2012

Re: xe-10-2-0.pcl-cr01.plus.net [212.159.0.200] - RTT nearer eme than 40ms

EME type RTT?
Gythral8PNC
Rising Star
Posts: 57
Thanks: 3
Fixes: 1
Registered: 06-02-2014

Re: xe-10-2-0.pcl-cr01.plus.net [212.159.0.200] - RTT nearer eme than 40ms

Earth - moon - Earth
Community Veteran
Posts: 6,818
Registered: 27-10-2012

Re: xe-10-2-0.pcl-cr01.plus.net [212.159.0.200] - RTT nearer eme than 40ms

Your pings to the destination are fine though.
The pings along your route are irrelevant as long as the the end destination ping time is fine.
Edit: To explain further - see this https://www.nanog.org/meetings/nanog45/presentations/Sunday/RAS_traceroute_N45.pdf
Quote
Latency spikes in the middle of a traceroute mean absolutely nothing if they do not continue forward absolutely nothing if they do not continue forward.

  • At worst it could be the result of an asymmetric path.

  • But it is probably an artificial rate-limit or prioritization issue.

  • By definition, if regularly forwarded packets are being affected you should see the issue persist on all future hops.