Connection very slow at peak times!

[Rik]

 

[Wivelrod]

For reference, IDNET confirmed that my exchange was congested with BT on the 13th May and informed me that BT would fix it on the 5th of July!

Even so, the Exchange still shows as Green on exchange checker web pages.

I'm eagerly awaiting the 5th, but I'm pessimistic! I expect that day to pass and still find I have less than 1mbit at peak times 

[Rik]

Most exchange checker sites are relying on out of date information from BT, unfortunately.

[HoriZon]

Got this back frim IDNet today:

--------------------------------------------------------------------------
If the problem continues, BT are currently working to resolve the issue,
normal lead time to make further bandwidth available is usually around
10 working days however they do have engineers working on this ASAP.
--------------------------------------------------------------------------

I guess all i can do is wait for now.

[Rik]

I'm afraid so.

[HoriZon]

Is it a hardware fix or software?

Also i guess this issue is effecting most people on the exchange or just a select few ?


At work now but just done a remote test to my PC and all is fine at home atm, tongiht it all changes.

[Rik]

It's a hardware fix, BT need to make more fibre available at the exchange, hence the lead time. It will be affecting everyone connected to the affeced VP, which can result in your neighbour not being affected, but someone a couple of streets away suffering as you are.

[HoriZon]

Well over a week later and BT are yet to fix the exchange, will wait till Tuesday to see if the works been done before I contact IDNet again.

They have two more working days!!






ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=254ms TTL=59
Reply from 212.69.36.10: bytes=32 time=350ms TTL=59
Reply from 212.69.36.10: bytes=32 time=275ms TTL=59
Reply from 212.69.36.10: bytes=32 time=196ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 196ms, Maximum = 350ms, Average = 268ms


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=338ms TTL=59
Reply from 212.69.36.10: bytes=32 time=257ms TTL=59
Reply from 212.69.36.10: bytes=32 time=315ms TTL=59
Reply from 212.69.36.10: bytes=32 time=316ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 257ms, Maximum = 338ms, Average = 306ms


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=340ms TTL=59
Reply from 212.69.36.10: bytes=32 time=273ms TTL=59
Reply from 212.69.36.10: bytes=32 time=257ms TTL=59
Reply from 212.69.36.10: bytes=32 time=263ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 257ms, Maximum = 340ms, Average = 283ms

[HoriZon]

Really bad right now and its not like I can change hosts either not that I want to.

Can't surf much at all like this.

Not uploading anything.

Feels like I'm on a 56k modem right now

Not been able to play any games or stream any video on a night for over a week now, starting to get annoyed now.

Just hope this fix is just that next week, but I have my doubts anything will change though. I understand its not IDNet's fault and its an issue with the exchange but its effecting how we use the internet in a big way right now.

Maybe I should go down to the local exchange with a sledgehammer?   








ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=610ms TTL=59
Reply from 212.69.36.10: bytes=32 time=689ms TTL=59
Reply from 212.69.36.10: bytes=32 time=726ms TTL=59
Reply from 212.69.36.10: bytes=32 time=759ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 610ms, Maximum = 759ms, Average = 696ms


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=787ms TTL=59
Reply from 212.69.36.10: bytes=32 time=671ms TTL=59
Reply from 212.69.36.10: bytes=32 time=692ms TTL=59
Reply from 212.69.36.10: bytes=32 time=782ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 671ms, Maximum = 787ms, Average = 733ms


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=893ms TTL=59
Reply from 212.69.36.10: bytes=32 time=860ms TTL=59
Reply from 212.69.36.10: bytes=32 time=889ms TTL=59
Reply from 212.69.36.10: bytes=32 time=678ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 678ms, Maximum = 893ms, Average = 830ms

[Steve]

I agree it's awful come on BT get your finger out!

[HoriZon]

Well its been a few days since the 4th now and it looks like its been fixed as its much better on a night now (ping back to normal and about a 5mb connection which is a bit lower than what i get in the day but that's probably to be expected at these times) and that site is saying the VP is GREEN again, will keep an eye on it but hopefully that's it for now!

http://usertools.plus.net/exchanges/?exchange=Pocklington&exact=1552&plugin=vp

Well I can only hope

[Steve]

Thanks for the update and 

[HoriZon]

Well its been a few weeks and tbh its not as bad as it was but during these times its not great and no way can i play any games which is a shame and there is nothing i can do about it.

The exchange reports Amber once again also.

Anyone at IDNet able to say what is going on ?

[Rik]

You'd have to ask them, but my best guess would be BT failed to install enough new capacity.

[HoriZon]

Yeah i will but need to do a few BT Speedtest over the next few days to send to them.

Right now its fine, 

[Rik]

Classic signs of capacity problems, I'm afraid.