NEED SOME HELP?

We’re here 24/7. 365 days a year.
Ask questions. Find your answers. Connect.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

UFO - Pings have Increased

Kie24k
Popular Poster
Message 6 of 6

Hi,

 

I've been with TalkTalk UFO for over a year now and apart from one issue, the service has been spot on. But lately I have noticed the latency has increased and I'm unsure if there's an issue or it's something I just have to put up with?

 

Here are things I have checked to see if there's a difference before I attached speed tests and pings etc:

 

- Connected directly to UFO with ethernet cable

> Sure this would rule out any router issue despite trial of different routers

 

- Usual power cycle of router and UFO port (complete removal of power including battery backup)

- Tried different network cables (cat 5e and 6, 7)

- Change of router

- Restart and power cycle of PC

- Switched off all WIFI devices that may interfere (despite all tests being hardwired)

- Tried all tests at different times of day and night

- Basically troubleshooted everything that can cause latency to randomly increase

 

Here are speed tests and pings / traces all done at different times with same results:

 

Original stats up until recently:

Old testOld testOld test 2Old test 2

old pingold ping

 

New Stats with increased ping (same server Leeds), including traces:

ne2ne2

 

 

Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=13ms TTL=58
Reply from 151.101.0.81: bytes=32 time=13ms TTL=58
Reply from 151.101.0.81: bytes=32 time=14ms TTL=58
Reply from 151.101.0.81: bytes=32 time=13ms TTL=58

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

C:\Users\kiere>ping google.co.uk

Pinging google.co.uk [216.58.212.195] with 32 bytes of data:
Reply from 216.58.212.195: bytes=32 time=13ms TTL=116
Reply from 216.58.212.195: bytes=32 time=13ms TTL=116
Reply from 216.58.212.195: bytes=32 time=14ms TTL=116
Reply from 216.58.212.195: bytes=32 time=14ms TTL=116

Ping statistics for 216.58.212.195:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 14ms, Average = 13ms
Tracing route to bbc.co.uk [151.101.0.81]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     6 ms     6 ms     6 ms  ae52-ner001.nec.as13285.net [78.144.1.9]
  3    18 ms    13 ms    13 ms  ae52-scr101.thw.as13285.net [78.144.1.8]
  4     *        *        *     Request timed out.
  5    14 ms    14 ms    14 ms  151.101.0.81

Trace complete.

C:\Users\kiere>tracert google.co.uk

Tracing route to google.co.uk [216.58.212.195]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.0.1
  2    28 ms     7 ms     7 ms  ae52-ner001.nec.as13285.net [78.144.1.9]
  3    14 ms    14 ms    14 ms  ae52-scr101.thw.as13285.net [78.144.1.8]
  4    15 ms    15 ms    15 ms  72.14.209.10
  5    14 ms    14 ms    14 ms  209.85.248.229
  6    15 ms    15 ms    15 ms  209.85.248.241
  7    14 ms    14 ms    14 ms  ams16s21-in-f3.1e100.net [216.58.212.195]

Trace complete.

 

 

 

Hope this can shed some light onto it or is it a matter of just accepting these strange increases? Please note I have done these tests at different times of day with same rules, different routers and to confirm I am wired directly to the router doing these tests. Please see troubleshooting steps above

 

Many Thanks!

0 Likes
5 REPLIES 5

Calpin
Chatterbox
Message 1 of 6

if i was going to have a educated guess, the your old tests your traffic was being routed to manchster and then back to leeds hence manchster server being 5ms and leeds 7ms. 

 

and now your traffic to the leeds server is going to london and then back up to leeds. 20ms to leeds is about right for a round trip from York-London-Leeds. most ISP traffic has to go through servers in london 1st. maybe try to a server in York you should find it to be around 22ms not 1-2ms like you would think. 

 

 

0 Likes

Message 2 of 6

Morning,

 

I'd recommend contacting the Future Fibre Team via Live Chat as they should be able to look into this further for you. They are available from 9am today.

 

Thanks

 

0 Likes

ferguson
Community Star
Message 3 of 6

Ok, no problem. Most people would find those numbers more than satisfactory. if you are actually having any problems with the performance of your service then get in touch with the Future Fibre support team, details here:

https://community.talktalk.co.uk/t5/FutureFibre/bd-p/FutureFibre

0 Likes

Kie24k
Popular Poster
Message 4 of 6

I wouldn't have posted if I didn't feel there was an issue. I appreciate your status as a community star but I don't find your reply very helpful.

ferguson
Community Star
Message 5 of 6

Honestly? Any real impact on any of your activities? 

0 Likes