Routing problems to maps.yandex.com

[#1]

Hello,
I've been trying to access maps.yandex.com, but the performance is really bad. The website loads fine on other internet connections, so I did a traceroute and found that there were a couple of points that timed out or seemed to have problems:

Tracing route to maps.yandex.com [77.88.21.189]
over a maximum of 30 hops:
  1     1 ms     1 ms     1 ms  dsldevice.lan [192.168.1.254]
  2    10 ms    10 ms    10 ms  lo0.10.central10.pcl-bng02.plus.net [195.166.130.151]
  3    16 ms     9 ms    10 ms  irb.10.PCL-CR01.plus.net [84.93.249.81]
  4    10 ms    12 ms    12 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  5    84 ms    88 ms    83 ms  linx-224.retn.net [195.66.224.193]
  6     *       97 ms     *     ae2-9.RT.TC2.AMS.NL.retn.net [87.245.233.97]
  7     *        *        *     Request timed out.
  8     *        *       91 ms  tulip-ae1.yndx.net [87.250.239.46]
  9     *       95 ms    88 ms  betamaps-slb.maps.yandex.net [77.88.21.189]
Trace complete.

I was wondering if there's something that can be done about that?
Thanks,
Amr

[#2]

It's just as bad from here:

Quote

1    2 ms    1 ms    1 ms  ZyXEL.Home [192.168.1.1]   2    35 ms    21 ms    42 ms  lo0.11.central11.ptn-bng01.plus.net [195.166.128 .229]   3    69 ms    85 ms    30 ms  irb.11.PTW-CR02.plus.net [84.93.249.18]   4    50 ms    *      71 ms  ae2.ptw-cr01.plus.net [195.166.129.4]   5    92 ms    *      101 ms  linx-224.retn.net [195.66.224.193]   6  124 ms  148 ms    *    ae2-9.RT.TC2.AMS.NL.retn.net [87.245.233.97]   7  123 ms  203 ms  105 ms  GW-Yandex.retn.net [87.245.246.14]   8  145 ms    *      101 ms  tulip-ae1.yndx.net [87.250.239.46]   9  111 ms    *      138 ms  betamaps-slb.maps.yandex.net [77.88.21.189]

I've also tried a few proxy server, most are very slow or don't even get there, but the following two proxy servers can access the site in a reasonable fashion if that's any help:
http://proxywebsite.co.uk/
http://www.englandproxy.co.uk
Judging by the results from the proxy servers I'm guessing there's a routing issue affecting more than just plusnet. Can you manage using a proxy ?

[#3]

Latency is 19ms for me same route externally to plusnet, But it still takes an age to load , well it did about 45mins ago, now loads  normally

[#4]

Now loading better here too.

[#5]

I was gonna say... all good here atm.
[tt]
                                      Packets              Pings
Host                                Loss%  Snt  Last  Avg  Best  Wrst StDev
1. 192.168.0.254                    0.0%  102    1.0  1.1  1.0  1.3  0.0
2. 195.166.128.191                  0.0%  102    8.3  10.1  7.8  46.7  5.4
3. 212.159.2.132                    0.0%  101    7.9  8.8  7.4  43.6  3.8
4. 212.159.0.112                    0.0%  101    7.6  9.6  7.2  48.2  6.4
5. 195.66.224.193                    0.0%  101    8.6  8.5  7.7  23.5  1.7
6. 87.245.233.97                    0.0%  101  13.6  14.4  13.1  29.0  1.9
7. 87.245.246.14                    0.0%  101  13.2  14.3  13.1  41.7  3.4
8. 87.250.239.46                    0.0%  101  13.5  14.4  13.1  32.5  3.0
9. 77.88.21.189                      0.0%  101  13.7  13.9  13.2  28.8  1.5
[/tt]

[#6]

mc.yandex.ru (gif) drops in after 15 odd seconds...

[#7]

It seems to be working fine now. Either a member of staff saw the message and it got fixed, or it's resolved itself somehow.

[#8]

I don't think any of us picked this up, so it was probably just a standard routing update that's fixed it.

[#9]

Was about to log a separate issue for performance via linx-224.retn.net which seems to be identical to this one,  skype is virtually unusable via this route and has been for a couple of days,  anyone else seeing issues?
Tracing route to maps.yandex.com [77.88.21.189]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    1 ms  192.168.1.254
  2    16 ms    16 ms    16 ms  lo0.12.central12.pcl-bng01.plus.net [195.166.130
.140]
  3    16 ms    16 ms    16 ms  irb.12.pcl-cr02.plus.net [84.93.249.114]
  4    17 ms    16 ms    16 ms  ae2.pcl-cr01.plus.net [195.166.129.6]
  5    18 ms    17 ms    17 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  6    *      90 ms    94 ms  linx-224.retn.net [195.66.224.193]
  7    *        *        *    Request timed out.
  8    97 ms    *        *    GW-Yandex.retn.net [87.245.246.14]
  9    97 ms    98 ms  102 ms  tulip-ae1.yndx.net [87.250.239.46]
10    98 ms    *      94 ms  betamaps-slb.maps.yandex.net [77.88.21.189]
Trace complete.
Tracing route to betamaps-slb.maps.yandex.net [77.88.21.189]
over a maximum of 30 hops:
  0  Lenova-PC [192.168.1.106]
  1  192.168.1.254
  2  lo0.12.central12.pcl-bng01.plus.net [195.166.130.140]
  3  irb.12.pcl-cr02.plus.net [84.93.249.114]
  4  ae2.pcl-cr01.plus.net [195.166.129.6]
  5  ae1.ptw-cr01.plus.net [195.166.129.0]
  6  linx-224.retn.net [195.66.224.193]
  7  ae2-9.RT.TC2.AMS.NL.retn.net [87.245.233.97]
  8  GW-Yandex.retn.net [87.245.246.14]
  9  tulip-ae1.yndx.net [87.250.239.46]
10  betamaps-slb.maps.yandex.net [77.88.21.189]
Computing statistics for 250 seconds...
            Source to Here  This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                          Lenova-PC [192.168.1.106]
                                0/ 100 =  0%  |
  1    0ms    0/ 100 =  0%    0/ 100 =  0%  192.168.1.254
                                0/ 100 =  0%  |
  2  17ms    0/ 100 =  0%    0/ 100 =  0%  lo0.12.central12.pcl-bng01.plus.ne
t [195.166.130.140]
                                0/ 100 =  0%  |
  3  ---    100/ 100 =100%  100/ 100 =100%  irb.12.pcl-cr02.plus.net [84.93.24
9.114]
                                0/ 100 =  0%  |
  4  19ms    0/ 100 =  0%    0/ 100 =  0%  ae2.pcl-cr01.plus.net [195.166.129
.6]
                                0/ 100 =  0%  |
  5  19ms    0/ 100 =  0%    0/ 100 =  0%  ae1.ptw-cr01.plus.net [195.166.129
.0]
                              46/ 100 = 46%  |
  6  ---    100/ 100 =100%    54/ 100 = 54%  linx-224.retn.net [195.66.224.193]
                                0/ 100 =  0%  |
  7  95ms    46/ 100 = 46%    0/ 100 =  0%  ae2-9.RT.TC2.AMS.NL.retn.net [87.2
45.233.97]
                                0/ 100 =  0%  |
  8  96ms    46/ 100 = 46%    0/ 100 =  0%  GW-Yandex.retn.net [87.245.246.14]
                                0/ 100 =  0%  |
  9  96ms    46/ 100 = 46%    0/ 100 =  0%  tulip-ae1.yndx.net [87.250.239.46]
                                0/ 100 =  0%  |
10  95ms    46/ 100 = 46%    0/ 100 =  0%  betamaps-slb.maps.yandex.net [77.8
8.21.189]
Trace complete.

[#10]

Gone back to being problematic again:

Tracing route to maps.yandex.com [77.88.21.189]
over a maximum of 30 hops:
  1     1 ms    <1 ms     1 ms  dsldevice.lan [192.168.1.254]
  2    10 ms    10 ms    10 ms  lo0.10.central10.pcl-bng02.plus.net [195.166.130.151]
  3    10 ms    10 ms     9 ms  irb.10.PCL-CR01.plus.net [84.93.249.81]
  4    10 ms    16 ms    10 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  5     *        *       83 ms  linx-224.retn.net [195.66.224.193]
  6    88 ms     *        *     ae2-9.RT.TC2.AMS.NL.retn.net [87.245.233.97]
  7    92 ms    85 ms     *     GW-Yandex.retn.net [87.245.246.14]
  8    85 ms    90 ms     *     tulip-ae1.yndx.net [87.250.239.46]
  9     *        *       89 ms  betamaps-slb.maps.yandex.net [77.88.21.189]
Trace complete.

Seems like it sometimes it works and other times it doesn't.