50M : Can you see something wrong here? *Video*

[Chrysalis]

Originally Posted by pillz

Can you explain what that means to someone who isn't greatly networking minded? =D

to further ignition's point even if you reach their threshold, they can and do sometimes cancel relief tickets if you fall below the threshold again, it seems the area has to be in a very bad state before they do relief work.

I have had 2 tickets closed in the past month without relief work done. Tech support just made a 3rd.

[pillz]

Originally Posted by Chrysalis

to further ignition's point even if you reach their threshold, they can and do sometimes cancel relief tickets if you fall below the threshold again, it seems the area has to be in a very bad state before they do relief work.

I have had 2 tickets closed in the past month without relief work done. Tech support just made a 3rd.

I just contacted them to confirm the fix , and that had confirmed it had been done. Now ive noticed a reduction in ping but the actual issue is still there its still all over the place , a few ping tests later i explained to the tech support guy and he said just wait for the fault to be closed down , and it could be a matter of the fault waiting to settle down.

[loopfish]

can u create a quality monitor at http://www.thinkbroadband.com/ping/monitors/create.html ?
would be interesting to see this unfold...

[pillz]

[Chrysalis]

Originally Posted by tweetiepooh

Still amazes me that anything uses ping (ICMP) for anything other than what it was designed for. It is a low priority traffic and when things get busy will get delayed or even dropped to allow for higher priority (TCP/UDP) traffic.

When things get really busy, ping will get lousy as that's how it should work. Now that's not to say that having bad ping and especially packet loss is acceptable especially where it degrades a service. Infinity may be better now while not many are on it, what's going to happen when that service gets really busy?

games dont use icmp.

---------- Post added at 11:57 ---------- Previous post was at 11:53 ----------

I just read your later posts so it seems you managed to get some upgrade work done?

your graph doesnt look very good but we dont know what it was like before the upgrade work so cant really comment if they fobbed you off or actually did do some work.

[pillz]

So ive given it a good few days to run various test , mainly personal tests in games to see whether or not any things changed , and i can honestly say not a single thing has :/ Its probably worse now than it was before. The utilization seems to have settled a bit.

Before:


After:



Every things just worse in game , everything gittering , constant spikes now which werent happening before , physical spikes where the game pauses for a few seconds and eventually balances out.

Looks like when the post office install there phoneline next week imma start hunting for a new isp.


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Pillz>ping -t www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.244.68] with 32 bytes of data:
Reply from 212.58.244.68: bytes=32 time=33ms TTL=54
Reply from 212.58.244.68: bytes=32 time=13ms TTL=54
Reply from 212.58.244.68: bytes=32 time=29ms TTL=54
Reply from 212.58.244.68: bytes=32 time=13ms TTL=54
Reply from 212.58.244.68: bytes=32 time=12ms TTL=54
Reply from 212.58.244.68: bytes=32 time=17ms TTL=54
Reply from 212.58.244.68: bytes=32 time=41ms TTL=54
Reply from 212.58.244.68: bytes=32 time=22ms TTL=54
Reply from 212.58.244.68: bytes=32 time=35ms TTL=54
Reply from 212.58.244.68: bytes=32 time=14ms TTL=54
Reply from 212.58.244.68: bytes=32 time=13ms TTL=54
Reply from 212.58.244.68: bytes=32 time=55ms TTL=54
Reply from 212.58.244.68: bytes=32 time=17ms TTL=54
Reply from 212.58.244.68: bytes=32 time=25ms TTL=54
Reply from 212.58.244.68: bytes=32 time=51ms TTL=54
Reply from 212.58.244.68: bytes=32 time=12ms TTL=54
Reply from 212.58.244.68: bytes=32 time=19ms TTL=54
Reply from 212.58.244.68: bytes=32 time=15ms TTL=54
Reply from 212.58.244.68: bytes=32 time=13ms TTL=54
Reply from 212.58.244.68: bytes=32 time=42ms TTL=54
Reply from 212.58.244.68: bytes=32 time=42ms TTL=54
Reply from 212.58.244.68: bytes=32 time=29ms TTL=54
Reply from 212.58.244.68: bytes=32 time=14ms TTL=54
Reply from 212.58.244.68: bytes=32 time=39ms TTL=54
Reply from 212.58.244.68: bytes=32 time=38ms TTL=54
Reply from 212.58.244.68: bytes=32 time=58ms TTL=54
Reply from 212.58.244.68: bytes=32 time=16ms TTL=54

Spikes in latency are still there and are fluxing way to much.

Oh well :/

[qasdfdsaq]

Y'know if you used the "Share" button in TBB it'd generate a graph without your IP address on it so you wouldn't have to try (and fail) at blanking it out?

[pillz]

Originally Posted by qasdfdsaq

Y'know if you used the "Share" button in TBB it'd generate a graph without your IP address on it so you wouldn't have to try (and fail) at blanking it out?

Yeah im not bothered about it anymore lol

[pillz]

LOL , i should of just kept my mouth shut , what ever they have done has made it all worse.