Huge packet loss on specific destinations

[#1]

Hello,
I have a huge packet loss (40%+) on specific destinations during afternoon times. Problem arises from 1-3pm every day and disappears at 8-9pm. Packet loss happens on routes through RETN LINX server, I've tested many other routes and no problems there, only with RETN route. I've opened CS ticket with the same question, but still got no answer. I'm attaching graphs from monitoring software so you can see where and when problem occurs. Would be nice to get some reply from tech stuff with suggestions how to fix/avoid this problem.

[#2]

Hi oruvin,
I've taken a look over your connection and can't see anything from our end and from our suppliers systems that would indicate a problem.
You mention that the issue only happens on RETN route, is that right? You don't have any other issues with different routes?

[#3]

Hi,
Yes, as I mentioned, problems only occur on RETN route (packet loss starts between ae2.ptw-cr01.plus.net and linx-224.retn.net routers as you can see on the graphs attached), for example, try to trace ya.ru server from your workplace. I believe it isn't problem with PlusNET itself or with "last mile" suppliers, the problem is with connection to the RETN LINX router. I'm not sure what could be done, maybe need to change routing tables to avoid RETN LINX server, or need to contact RETN itself and see what can they say.
jim:quote

[#4]

Are you seeing packet loss right now?

[#5]

This is what I'm currently seeing:

HopIP             Hostname                                 last [ms]min [ms]max [ms]ava. [ms]var. [ms]total Lossperc. 			RTTL	ASN     
1  10.3.5.253     10.3.5.253                               0        0       0       0                           0                          255 AS65534 
2  10.0.3.5       10.0.3.5                                 0        0       0       0        0        0         0                          64  AS1     
3  84.93.216.88   vlan380.pbs-cr01.plus.net                1        1       1       0        1        0         0                          254 AS6871  
4  84.93.216.95   gi6-8.ptp-cr01.plus.net                  1        1       5       1        1        0         0                          253 AS6871  
5  84.93.224.49   gi1-22.pcl-gw01.plus.net                 8        8       21      10       4        0         0                          252 AS6871  
6  195.166.129.40 ae3.pcl-cr01.plus.net                    8        8       44      10       8        0         0                          60  AS6871  
7  195.166.129.0  ae1.ptw-cr01.plus.net                    8        8       42      11       9        0         0                          60  AS6871  
8  195.66.224.193 linx-224.retn.net                        106      102     163     109      14       0         0                              AS10026 
9  87.245.233.237 ae6-10.RT.EQX.FKT.DE.retn.net            124      119     133     124      3        0         0                          58  AS9002  
10 87.245.246.150 GW-IntecTradeInc.retn.net                124      117     125     122      2        0         0                          57  AS9002  
11 176.122.240.130unused-176.122.240.130.intectradeinc.com 125      117     125     121      2        0         0                          56  AS59513 
12 176.122.240.253176.122.240.253                          122      119     123     121      1        0         0                          56          

[#6]

Yes. This /tracert done 10 secs ago:

C:\Users\Oruvin>tracert ya.ru
Tracing route to ya.ru [87.250.250.203]
over a maximum of 30 hops:
  1     1 ms    <1 ms    <1 ms  RT-N66U [192.168.10.1]
  2    15 ms    15 ms    15 ms  lo0-central10.ptw-ag01.plus.net [195.166.128.195]
  3    15 ms    15 ms    15 ms  link-b-central10.ptw-gw02.plus.net [212.159.2.146]
  4    15 ms    15 ms    17 ms  xe-4-2-0.ptw-cr02.plus.net [212.159.0.242]
  5    15 ms    16 ms    15 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
  6     *        *       87 ms  linx-224.retn.net [195.66.224.193]
  7     *       94 ms     *     ae2-9.RT.TC2.AMS.NL.retn.net [87.245.233.97]
  8    93 ms    93 ms     *     GW-Yandex.retn.net [87.245.246.14]
  9    96 ms     *       94 ms  tulip-ae1-0.yndx.net [87.250.239.46]
 10     *       96 ms     *     www.yandex.ru [87.250.250.203]
 11     *        *       91 ms  www.yandex.ru [87.250.250.203]
Trace complete.

[#7]

Kelly,
As I see you have no packet loss, BUT you have different PlusNET router (ae1.ptw-cr01.plus.net) connected to the RETN network, my route is going through ae2.ptw-cr01.plus.net router. Maybe there is problem with PlusNET router (ae2.ptw-cr01.plus.net)?

[#8]

Yeah, that's what I'm wondering.  Disconnect and reconnect and see if you end up with a different route through our network?
www.yandex.ru

HopIP             Hostname                     last [ms]min [ms]max [ms]ava. [ms]var. [ms]total Lossperc. LossLatitudeLongitudeRTTLASN     
1  10.3.5.253     10.3.5.253                   0        0       0       0                           0                          255 AS65534 
2  10.0.3.5       10.0.3.5                     0        0       1       0        0                  0                          64  AS59513 
3  84.93.216.88   vlan380.pbs-cr01.plus.net    0        0       6       1        1                  0                          254 AS6871  
4  84.93.216.95   gi6-8.ptp-cr01.plus.net      3        1       14      2        3                  0                          253 AS6871  
5  84.93.224.49   gi1-22.pcl-gw01.plus.net     8        8       8       8        0                  0                          252 AS6871  
6  195.166.129.40 ae3.pcl-cr01.plus.net        8        8       22      9        3                  0                          60  AS6871  
7  195.166.129.0  ae1.ptw-cr01.plus.net        8        8       9       8        0                  0                          60  AS6871  
8  195.66.224.193 linx-224.retn.net            105      101     136     107      7                  0                              AS10026 
9  87.245.233.97  ae2-9.RT.TC2.AMS.NL.retn.net 113      108     118     111      2        1         0                          58  AS9002  
10 87.245.246.14  GW-Yandex.retn.net           110      109     112     111      1                  0                          57  AS9002  
11 87.250.239.46  tulip-ae1-0.yndx.net         114      110     114     112      1                  0                          53  AS13238 
12 87.250.250.3   www.yandex.ru ;               113      109     115     112      1        1         0                          52  AS13238 
13 87.250.250.3   www.yandex.ru ;               111      111     111     111                         0                                      

[#9]

That was the first thing I've tried to do. Problem with this destination is going on for at least a week, tried to obtain different IP subnet to see if routing table changes, but looks that I'm really unlucky (have had more than 3 different IPs), routing didn't change.

[#10]

Sorry to reanimate this topic, but problem still occurs. Try to tracert packets to ya.ru right now and see it yourself. Is it possible to get alternative route somehow to avoid linx-224.retn.net router?

[#11]

50% packet loss, can't even open a webpage, lovely service..

[#12]

The URL you're tracing to has huge packet loss for me too. Is it still only RETN traffic you're seeing this on?
What do traces to other URLs look like?

[#13]

Also have you been rebooting the router a lot over the past hour or so? It seems there's been a few drops in connection:
<img src="http://community.plus.net/visualradius/generated/image13886815344503.png"/>

[#14]

Hi,
Yes, I've been trying to get a different IP to see if I get different route (routes were different, but all of them had same issues with linx-224.retn.net router), that's why you see many reconnects.
As I mentioned in early posts, problem ONLY occurs within RETN network (RETN LINX), with all other routes (that I'm using) there is absolutely no problem.

[#15]

So it could be a RETN problem then...  Have you approached them about the problem?