dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
728
vincom
join:2009-03-06
Bolton, ON

1 edit

vincom

Member

high latency to 77.87.181.63

any1 else have high latency for 77.87.181.63 aka pokerstars.
its been happening for quite some time now, everything else is ok except for this

Tracing route to 77.87.181.63 over a maximum of 30 hops

1 1 ms 1 ms 1 ms router [192.168.1.1]
2 12 ms 54 ms 7 ms 7.207.12.1
3 20 ms 103 ms 114 ms 66.185.90.37
4 49 ms 23 ms 83 ms 209.148.224.205
5 74 ms 55 ms 41 ms ae1_2120-bdr04-tor.teksavvy.com [69.196.136.68]

6 89 ms 36 ms 74 ms xe-3-0-1.cr1.tor1.ca.as4436.gtt.net [69.31.143.141]
7 47 ms 141 ms 38 ms ae2-69.tor10.ip4.gtt.net [46.33.80.241]
8 138 ms 126 ms 257 ms xe-1-2-0.par70.ip4.gtt.net [89.149.185.53]
9 171 ms * * ae0-69.cr1-cdg1.ip4.gtt.net [46.33.95.238]
10 234 ms 190 ms 118 ms as6762.xe-0-0-2.cr1.cdg1.fr.as4436.gtt.net [69.22.139.50]
11 149 ms * 177 ms xe-8-3-0.londra32.lon.seabone.net [89.221.43.119]
12 200 ms 172 ms * rational-service.londra32.lon.seabone.net [195.22.209.126]
13 * * * Request timed out.
14 258 ms 161 ms 277 ms 77.87.177.169
15 * * * Request timed out.
16 144 ms 170 ms * 77.87.180.14
17 222 ms 189 ms * 77.87.181.63
18 154 ms 222 ms * 77.87.181.63
19 164 ms * * 77.87.181.63
20 186 ms 206 ms 195 ms 77.87.181.63

Trace complete.

jmck
formerly 'shaded'
join:2010-10-02
Ottawa, ON

jmck

Member

that host is in Isle of Man which is in Europe so higher latency is expected (more than just London). also you're already getting really high latency to TSI's network in your first few hops (80ms).

RizzleQ
Cunningham's Law Enthusiast
Premium Member
join:2006-01-12
Windsor, ON
Ubiquiti UDM-Pro
Ubiquiti U6-LR

RizzleQ to vincom

Premium Member

to vincom
Everything goes way downhill shortly after leaving Canada:

Tracing route to 77.87.181.63 over a maximum of 30 hops
 
  1    <1 ms    <1 ms    <1 ms  router [192.168.1.1]
  2     6 ms     7 ms     7 ms  10.195.236.1
  3    15 ms    15 ms    16 ms  192-171-63-10.cpe.pppoe.ca [192.171.63.10]
  4    14 ms    14 ms    14 ms  ae2_6220-bdr01-tor.teksavvy.com [192.171.63.11]
  5    14 ms    15 ms    15 ms  ae1_2150-bdr04-tor.teksavvy.com [69.196.136.164]
  6    14 ms    13 ms    13 ms  xe-2-2-1.cr1.tor1.ca.as4436.gtt.net [69.31.143.125]
  7    13 ms    22 ms    14 ms  ae2-69.tor10.ip4.gtt.net [46.33.80.241]
  8   123 ms   120 ms   122 ms  xe-1-2-0.par70.ip4.gtt.net [89.149.185.53]
  9   122 ms   113 ms   111 ms  ae0-69.cr1-cdg1.ip4.gtt.net [46.33.95.238]
 10   119 ms   123 ms   122 ms  as6762.xe-0-0-2.cr1.cdg1.fr.as4436.gtt.net [69.22.139.50]
 11     *        *      124 ms  149.3.183.11
 12   131 ms   123 ms   123 ms  rational-service.londra32.lon.seabone.net [195.22.209.126]
 13   139 ms   151 ms   148 ms  192.168.1.1
 14   134 ms   137 ms   133 ms  77.87.177.169
 15   153 ms     *      145 ms  192.168.1.5
 16   132 ms   132 ms   129 ms  77.87.180.14
 17   126 ms   123 ms     *     77.87.181.63
 18     *      125 ms   125 ms  77.87.181.63
 
Trace complete.
 

jmck
formerly 'shaded'
join:2010-10-02
Ottawa, ON

jmck

Member

110s ms to Paris isn't super out of the norm here, it's maybe 10-20 ms higher than better transit but expected too...
mikee
join:2012-12-21
Gloucester, ON

mikee to vincom

Member

to vincom
i'm getting fairly decent results for where the server is located:

Reply from 77.87.181.63: bytes=32 time=105ms TTL=50
Reply from 77.87.181.63: bytes=32 time=105ms TTL=50
Reply from 77.87.181.63: bytes=32 time=105ms TTL=50
Reply from 77.87.181.63: bytes=32 time=106ms TTL=50
Reply from 77.87.181.63: bytes=32 time=105ms TTL=50
Reply from 77.87.181.63: bytes=32 time=105ms TTL=50
Reply from 77.87.181.63: bytes=32 time=105ms TTL=50
Reply from 77.87.181.63: bytes=32 time=105ms TTL=50
Reply from 77.87.181.63: bytes=32 time=105ms TTL=50

RizzleQ
Cunningham's Law Enthusiast
Premium Member
join:2006-01-12
Windsor, ON
Ubiquiti UDM-Pro
Ubiquiti U6-LR

RizzleQ to jmck

Premium Member

to jmck
Around 100ms latency over such a distance is normal, but I was more so referring to the packet loss.

Tracing route to 77.87.181.63 over a maximum of 30 hops
 
  1    <1 ms    <1 ms    <1 ms  router [192.168.1.1]
  2     6 ms     7 ms     7 ms  10.195.236.1
  3    17 ms    17 ms    17 ms  192-171-63-10.cpe.pppoe.ca [192.171.63.10]
  4    19 ms    15 ms    15 ms  ae2_6220-bdr01-tor.teksavvy.com [192.171.63.11]
  5    15 ms    15 ms    15 ms  ae1_2150-bdr04-tor.teksavvy.com [69.196.136.164]
  6    16 ms    15 ms    17 ms  xe-2-2-1.cr1.tor1.ca.as4436.gtt.net [69.31.143.125]
  7    15 ms    16 ms    15 ms  ae2-69.tor10.ip4.gtt.net [46.33.80.241]
  8   105 ms   108 ms   109 ms  xe-2-2-2.par70.ip4.gtt.net [141.136.108.97]
  9   109 ms   140 ms     *     ae0-69.cr1-cdg1.ip4.gtt.net [46.33.95.238]
 10   110 ms   108 ms   107 ms  as6762.xe-0-0-2.cr1.cdg1.fr.as4436.gtt.net [69.22.139.50]
 11   109 ms   108 ms   109 ms  149.3.183.11
 12   114 ms   111 ms   113 ms  rational-service.londra32.lon.seabone.net [195.22.209.126]
 13     *      147 ms   136 ms  192.168.1.1
 14   119 ms   119 ms   120 ms  77.87.177.169
 15   136 ms     *        *     192.168.1.5
 16     *      115 ms   120 ms  77.87.180.14
 17     *      112 ms     *     77.87.181.63
 18   111 ms     *      114 ms  77.87.181.63
 
Trace complete.
 

Ping statistics for 77.87.181.63:
    Packets: Sent = 145, Received = 120, Lost = 25 (17% loss),
Approximate round trip times in milli-seconds:
    Minimum = 110ms, Maximum = 140ms, Average = 112ms
 

TSI Gabe
Router of Packets
Premium Member
join:2007-01-03
Gatineau, QC

TSI Gabe

Premium Member

Run an MTR (winmtr or other flavour) to find out where the loss truly is.
TSI Gabe

TSI Gabe

Premium Member

never mind I ran it myself I'm seeing it too