Traffic Management? - Update

[#1]

I would be grateful if one of the PN Staff could check that my madasafish connection has the correct profile with regard to traffic management.
I'm also curious as to why the latency/ping times have increased since the change over to WBC and IPSC for my maaf connection, would it be correct to assume that the routing has changed for the worse, hence the increase in ping times and can PN do anything to improve things?

[#2]

Hi Apprentice,
your traffic management profile is as it should be. I doubt that the change to IPSC would affect the routing negatively.
Jojo

[#3]

your routing is up the swanny......
i'm on fibre.... i like to play COD - MW2 on PC  (runs p2p protocol)
along with Left for Dead 2 on PC.....
MW2 connects me with europeon and further hosts......
Left for Dead tends to put me with French players.......
Although i moaned about o2 being rubbish (which they are), there routing made me connect with mainly UK players.    fear not, i know theres nothing u can do, so i just have to settle for it...

[#4]

Quote

MW2 connects me with europeon and further hosts...

This is a known issue with MW2 and that's why they've said they are going to fix this style of matchmaking for MW3.
L4D - I used to play this and L4D2 and never had a problem being connected with non-uk players. (I'm on a Fibre connection too). You haven't got your Steam setting for location to somewhere in Europe have you.

[#5]

Quote from: Joanne

Hi Apprentice, your traffic management profile is as it should be. I doubt that the change to IPSC would affect the routing negatively. Jojo

OK Jojo and thanks for checking that out.
Any idea what could be causing the increased latency/ping times as all the gateways or whatever they are called now I've connected to over the last few weeks give similar ping times, which at least shows they are well balanced.
I'll investigate further regarding latency, WBC and IPSC but it looks like its not going to improve, maybe best to blame it on the advent of FTTC.

[#6]

Not sure what it could be, unless your interleaving status has changed.

[#7]

After checking, the downstream and upstream interleaving depths appear to be the same as they were eleven months ago ....... according to data obtained from the DMT tool.

[#8]

Not sure what it could be, in that case.

[#9]

In that case that makes two of us then

[#10]

Ping time / latency for my 20CN connection has decreased and is back to more or less what it used to be  ,
this coincided with the recent increase in bandwidth / lit segments for the 21CN PN customers, strange or not?

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=47ms TTL=249
Reply from 212.58.241.131: bytes=32 time=46ms TTL=249
Reply from 212.58.241.131: bytes=32 time=47ms TTL=249
Reply from 212.58.241.131: bytes=32 time=46ms TTL=249
Ping statistics for 212.58.241.131:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 46ms, Maximum = 47ms, Average = 46ms
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    48 ms    48 ms    48 ms  lo0-central6.pcl-ag01.plus.net [195.166.130.87]
  3    49 ms    47 ms    48 ms  gi7-1-162.pcl-gw02.plus.net [84.93.255.83]
  4    48 ms    47 ms    47 ms  po5.thn-gw02.plus.net [212.159.1.133]
  5    47 ms    47 ms    47 ms  rt0.thdo.bbc.co.uk [212.58.239.25]
  6    48 ms    47 ms    48 ms  212.58.238.149
  7    47 ms    46 ms    47 ms  virtual-vip-231.thdo.bbc.co.uk [212.58.241.131]
Trace complete.

[#11]

Quote

this coincided with the recent increase in bandwidth / lit segments for the 21CN PN customers, strange or not?

I would say more or less coincidental, than anything else... Still, good to see the issue resolving itself
Regards