Huge packet loss on specific destinations

[#1]

I got someone to traceroute in the other direction and it seems to report an entirely different route via as8218.eu

2  a9k2-1041.dc3.poneytelecom.eu (88.191.1.185)  0.960 ms  1.268 ms  1.350 ms
3  213.152.30.6 (213.152.30.6)  0.258 ms  0.349 ms  0.350 ms
4  xe2-2-0.tcr1.gs.par.as8218.eu (83.167.56.176)  0.726 ms  0.761 ms  0.759 ms
5  xe1-0-0.tcr1.thn.lon.as8218.eu (83.167.63.230)  9.012 ms  8.875 ms  9.001 ms
6  lonap-gw2.plus.net (5.57.80.155)  40.852 ms  40.933 ms  40.836 ms

Still a bad hike in response times.

[#2]

This has been going on for a couple of weeks or more now. What can be done about this? I should NOT have to connect only from 11pm-2pm to be able to use my connection for this? How do I go about getting this resolved?

[#3]

PlusNET can only inform the provider. Maybe you could contact them?

[#4]

PlusNet can change routing tables to avoid bad routes.

[#5]

Is as8218.eu the backbone provider?

[#6]

We've mailed proxad but they've not responded.

[#7]

Quote from: oruvin

PlusNet can change routing tables to avoid bad routes.

I don't think it's as simple as pressing a button, or they would have done it already.
A quick google search of proxad shows them to have a history of problems...

[#8]

Of course it isn't as simple as we think, but if there is no simple solution to fix a problem, more complicated solutions should be used.

[#9]

Things are looking up: quite a good service this evening. Shame I was watching telly instead of gaming so didn't benefit.

Target Name: 195-154-168-239.rev.poneytelecom.eu
         IP: 195.154.168.239
  Date/Time: 1/22/2014 8:57:46 PM to 1/22/2014 9:57:32 PM
Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1   240   0   0.0   0 217   4  my.router [192.168.3.254]
 2   240   2   0.8  16 570  58  lo0-central10.ptn-ag04.plus.net [195.166.128.193]
 3   240 240 100.0   0   0   0   [-]
 4   240   2   0.8  15 490  50  xe-8-2-0.ptw-cr02.plus.net [212.159.0.118]
 5   240   4   1.7  16 583  46  ae2.ptw-cr01.plus.net [195.166.129.4]
 6   240  20   8.3  16 496  50  linx-6k-1.routers.proxad.net [195.66.224.191]
 7   240   2   0.8  24 481  57  bzn-crs16-1-be1102.intf.routers.proxad.net [212.27.51.185]
 8   240 240 100.0   0   0   0   [-]
 9   240 240 100.0   0   0   0   [-]
10   240   3   1.3  25 493  57  45x-s44-1-1039.dc3.poneytelecom.eu [88.191.1.178]
11   240   3   1.3  24 476  53  195-154-168-239.rev.poneytelecom.eu [195.154.168.239]

[#10]

I hope that is sarcasm...

[#11]

Looks like the traffic has been rerouted via as8218 now. From what I've seen elsewhere that's probably a more stable route, and similar to the route seen when traced from the game server to me.

Target Name: 195-154-168-239.rev.poneytelecom.eu
         IP: 195.154.168.239
  Date/Time: 1/25/2014 12:45:09 PM to 1/25/2014 12:59:55 PM
Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1    60   0   0.0   0   3   1  my.router [192.168.3.254]
 2    60   0   0.0  15 351  41  lo0-central10.ptn-ag01.plus.net [195.166.128.190]
 3    60  60 100.0   0   0   0   [-]
 4    60   0   0.0  15  45  18  xe-5-2-0.ptw-cr02.plus.net [212.159.0.106]
 5    60   0   0.0  15 107  20  lonap1.thn.lon.neotelecoms.com [5.57.80.210]
 6    60   0   0.0  23  31  24  xe1-3-0.tcr1.th2.par.as8218.eu [83.167.63.231]
 7    60   0   0.0  23  58  27  xe0-0-0.tcr1.th2.par.as8218.eu [83.167.56.177]
 8    60  60 100.0   0   0   0   [-]
 9    60   0   0.0  24  81  29  45x-s44-1-1041.dc3.poneytelecom.eu [88.191.1.186]
10    60   0   0.0  24  31  25  195-154-168-239.rev.poneytelecom.eu [195.154.168.239]

[#12]

Is it performing better on the application you were using?

[#13]

Yes it is noticeably better now.

[#14]

My ticket says they have rerouted. But it's still showing Proxad with packet loss here.

[#15]

It's back to being horrendous packet loss tonight.