Stolen the copper cable and you haven't finished y...

Question

So as title suggests, we had a perfectly connecting broadband (still under 1 mb) but still it worked. Then "someone" stole all the copper cable leading to our village, leaving us without phone and internet for 2 weeks! untill you "repaired the problem".
as a result of your repairs our perfectly working router suddenly stopped working and we had to go back to using the BT supplied HomeHub (1.0) which was an abortion by the way, we have now upgraded our whole system at our expense ofc and are now connected to the internet. But we still have ping of between 300 -600!! most of the programs on your computer dont know how to deal with that sort of dodgy connection and just say "no connection" etc.
So how have you completed your repairs if the connection is worse than the pretty lowsy connection before?
Why did you not while repairing the cabling, put in some of the new fibre optic "infinity" that we were supposed to have got a month ago?
and no i would rather not call one of your foreign call centres where they just tell you to turn it off and turn it on again, we have been loyal customers for around 6 years, but your forcing us towards going else where.
I look forward to any feedback,
Bobby

Answer 1

thanks with the quick response:
UPSTAIRS
Pinging www.bbc.net.uk [212.58.246.90] with 32 bytes of data:
Reply from 212.58.246.90: bytes=32 time=360ms TTL=51
Reply from 212.58.246.90: bytes=32 time=413ms TTL=51
Reply from 212.58.246.90: bytes=32 time=440ms TTL=51
Reply from 212.58.246.90: bytes=32 time=350ms TTL=51
Ping statistics for 212.58.246.90:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 350ms, Maximum = 440ms, Average = 390ms
Pinging 192.168.2.1 with 32 bytes of data:
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=3ms TTL=64
Reply from 192.168.2.1: bytes=32 time=3ms TTL=64
Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms
DOWNSTAIRS
Pinging www.bbc.net.uk [212.58.244.69] with 32 bytes of data:
Reply from 212.58.244.69: bytes=32 time=351ms TTL=51
Reply from 212.58.244.69: bytes=32 time=404ms TTL=51
Reply from 212.58.244.69: bytes=32 time=459ms TTL=51
Reply from 212.58.244.69: bytes=32 time=484ms TTL=51
Ping statistics for 212.58.244.69:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 351ms, Maximum = 484ms, Average = 424ms
Pinging 192.168.2.1 with 32 bytes of data:
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms