PTCL problems, need help from other service consumers here

Hi,

Using qtracker to play Battlefield 2, normally servers had around 180-200ms pings which was bearable, but for the past 2 days they have gone up, going above 370ms on PTCL broadband. Can anyone on other services confirm this issue? In general all pings to european IPs have gone up massively on PTCL.

Can anyone please post their ping results here for these servers:

188.40.93.133

and this one

212.26.144.9

Thanks!

Pinging 188.40.93.133 with 32 bytes of data:

Reply from 188.40.93.133: bytes=32 time=176ms TTL=49

Reply from 188.40.93.133: bytes=32 time=169ms TTL=49

Reply from 188.40.93.133: bytes=32 time=172ms TTL=49

Reply from 188.40.93.133: bytes=32 time=171ms TTL=49

Reply from 188.40.93.133: bytes=32 time=179ms TTL=49

Reply from 188.40.93.133: bytes=32 time=173ms TTL=49

Reply from 188.40.93.133: bytes=32 time=161ms TTL=49

Reply from 188.40.93.133: bytes=32 time=175ms TTL=49

Reply from 188.40.93.133: bytes=32 time=173ms TTL=49

Reply from 188.40.93.133: bytes=32 time=170ms TTL=49

Reply from 188.40.93.133: bytes=32 time=170ms TTL=49

Reply from 188.40.93.133: bytes=32 time=174ms TTL=49

Reply from 188.40.93.133: bytes=32 time=172ms TTL=49

Reply from 188.40.93.133: bytes=32 time=171ms TTL=49

Reply from 188.40.93.133: bytes=32 time=180ms TTL=49

Reply from 188.40.93.133: bytes=32 time=173ms TTL=49

Reply from 188.40.93.133: bytes=32 time=172ms TTL=49

Reply from 188.40.93.133: bytes=32 time=165ms TTL=49

Reply from 188.40.93.133: bytes=32 time=174ms TTL=49

Reply from 188.40.93.133: bytes=32 time=172ms TTL=49

Reply from 188.40.93.133: bytes=32 time=171ms TTL=49

Reply from 188.40.93.133: bytes=32 time=174ms TTL=49

Reply from 188.40.93.133: bytes=32 time=173ms TTL=49

Reply from 188.40.93.133: bytes=32 time=171ms TTL=49

Reply from 188.40.93.133: bytes=32 time=175ms TTL=49

Reply from 188.40.93.133: bytes=32 time=168ms TTL=49

Reply from 188.40.93.133: bytes=32 time=172ms TTL=49

Reply from 188.40.93.133: bytes=32 time=170ms TTL=49

Reply from 188.40.93.133: bytes=32 time=194ms TTL=49

Reply from 188.40.93.133: bytes=32 time=198ms TTL=49

Reply from 188.40.93.133: bytes=32 time=171ms TTL=49

On QUBEE (3:43PM)

What about this one: 212.26.144.9

Pinging 212.26.144.9 with 32 bytes of data:

Reply from 212.26.144.9: bytes=32 time=275ms TTL=112

Reply from 212.26.144.9: bytes=32 time=213ms TTL=112

Reply from 212.26.144.9: bytes=32 time=232ms TTL=112

Reply from 212.26.144.9: bytes=32 time=225ms TTL=112

Reply from 212.26.144.9: bytes=32 time=209ms TTL=112

Reply from 212.26.144.9: bytes=32 time=238ms TTL=112

Reply from 212.26.144.9: bytes=32 time=216ms TTL=112

Reply from 212.26.144.9: bytes=32 time=240ms TTL=112

Reply from 212.26.144.9: bytes=32 time=218ms TTL=112

Reply from 212.26.144.9: bytes=32 time=221ms TTL=112

Reply from 212.26.144.9: bytes=32 time=225ms TTL=112

Reply from 212.26.144.9: bytes=32 time=223ms TTL=112

Reply from 212.26.144.9: bytes=32 time=227ms TTL=112

Reply from 212.26.144.9: bytes=32 time=216ms TTL=112

Reply from 212.26.144.9: bytes=32 time=219ms TTL=112

Reply from 212.26.144.9: bytes=32 time=263ms TTL=112

Reply from 212.26.144.9: bytes=32 time=216ms TTL=112

Reply from 212.26.144.9: bytes=32 time=215ms TTL=112

Reply from 212.26.144.9: bytes=32 time=218ms TTL=112

Reply from 212.26.144.9: bytes=32 time=222ms TTL=112

Hmm pretty bad!

Actually, 230ms ping is ok for BF2 - look at what I am getting now on PTCL (WT @@@@@@ is happening) ???

Pinging 212.26.144.9 with 32 bytes of data:

Reply from 212.26.144.9: bytes=32 time=372ms TTL=111

Reply from 212.26.144.9: bytes=32 time=372ms TTL=111

Reply from 212.26.144.9: bytes=32 time=366ms TTL=111

Reply from 212.26.144.9: bytes=32 time=373ms TTL=111

Reply from 212.26.144.9: bytes=32 time=375ms TTL=111

Reply from 212.26.144.9: bytes=32 time=369ms TTL=111

Reply from 212.26.144.9: bytes=32 time=376ms TTL=111

Reply from 212.26.144.9: bytes=32 time=373ms TTL=111

Reply from 212.26.144.9: bytes=32 time=371ms TTL=111

Pinging 212.26.144.9 with 32 bytes of data:

Reply from 212.26.144.9: bytes=32 time=288ms TTL=111

Reply from 212.26.144.9: bytes=32 time=295ms TTL=111

Reply from 212.26.144.9: bytes=32 time=287ms TTL=111

Reply from 212.26.144.9: bytes=32 time=335ms TTL=111

Reply from 212.26.144.9: bytes=32 time=287ms TTL=111

Reply from 212.26.144.9: bytes=32 time=303ms TTL=111

Reply from 212.26.144.9: bytes=32 time=296ms TTL=111

Reply from 212.26.144.9: bytes=32 time=285ms TTL=111

Reply from 212.26.144.9: bytes=32 time=288ms TTL=111

Reply from 212.26.144.9: bytes=32 time=287ms TTL=111

This servers seems to have some problem.. pings fluctuate alot.

Pinged after ages. I remember I used to ping my local cablenet server all the time... hahah.

wow guy with Wireless connecting getting better pings than Dsl landline user .. just wow

The server is NOT having a problem - on the same server (212.26.144.9), I used to get 180ms before ***** started happening with PTCL a week ago.