Menu
Reply
  • 11
  • 0
  • 0
Deathbox
Joining in
616 Views
Message 1 of 17
Flag for a moderator

Low Speed and High Latency

Hello,

Over the past week I have been getting low speeds  and high latency in most evening starting around 6pm to around 2am. The problem is mainly the high latency.

Here are a few days worth of BQM's:

Today

Virgin 111 hubert

Saturday

Virgin 111 hubert

Friday

Virgin 111 hubert

Thursday

Virgin 111 hubert

Wednesday

Virgin 111 hubert

I would normally contact support about this issue but since the internet at this apartment is provided by the landlord I do not have the account number. I have contacted them but they have yet to respond. I was wondering if there is anyone who could suggest whats going on here?

 

Thanks for any help 

 

0 Kudos
Reply
  • 11
  • 0
  • 0
Deathbox
Joining in
578 Views
Message 2 of 17
Flag for a moderator

Re: Low Speed and High Latency

Hi, 

Here are 2 more graphs showing the issue.

Monday

Virgin 111 hubert

Tueday

Virgin 111 hubert

 

0 Kudos
Reply
  • 12.42K
  • 468
  • 1.11K
legacy1
Alessandro Volta
576 Views
Message 3 of 17
Flag for a moderator

Re: Low Speed and High Latency

Likely a routeing and QoS issue

When you get high Latency run cmd
ping -n 100 194.168.4.100
tracert 80.249.99.164

0 Kudos
Reply
  • 3.64K
  • 51
  • 820
CarlTSpeak
Wise owl
561 Views
Message 4 of 17
Flag for a moderator

Re: Low Speed and High Latency

Please disregard the above. 

Do you share that connection with anyone else given it's provided by the landlord? 

0 Kudos
Reply
  • 11
  • 0
  • 0
Deathbox
Joining in
528 Views
Message 5 of 17
Flag for a moderator

Re: Low Speed and High Latency

Hello,

Sorry for the late reply. I do not actually know as when I have asked I've got mixed messages.

My best guess would be individual 50Mb connections controlled by one business modem.(I've seen hitron in the name of one of the addresses).

Though it could be possible is one shared connection.

Sorry I couldn't be of more help.

I will say the issue was still persisted by its never bad on friday or saturday, which is bizarre.

0 Kudos
Reply
  • 11
  • 0
  • 0
Deathbox
Joining in
522 Views
Message 6 of 17
Flag for a moderator

Re: Low Speed and High Latency

And here are the ping test and tracert requested.

Pinging 194.168.4.100 with 32 bytes of data:
Reply from 194.168.4.100: bytes=32 time=73ms TTL=60
Reply from 194.168.4.100: bytes=32 time=227ms TTL=60
Reply from 194.168.4.100: bytes=32 time=161ms TTL=60
Reply from 194.168.4.100: bytes=32 time=262ms TTL=60
Reply from 194.168.4.100: bytes=32 time=226ms TTL=60
Reply from 194.168.4.100: bytes=32 time=299ms TTL=60
Reply from 194.168.4.100: bytes=32 time=405ms TTL=60
Reply from 194.168.4.100: bytes=32 time=289ms TTL=60
Reply from 194.168.4.100: bytes=32 time=290ms TTL=60
Reply from 194.168.4.100: bytes=32 time=406ms TTL=60
Reply from 194.168.4.100: bytes=32 time=285ms TTL=60
Reply from 194.168.4.100: bytes=32 time=206ms TTL=60
Reply from 194.168.4.100: bytes=32 time=187ms TTL=60
Reply from 194.168.4.100: bytes=32 time=175ms TTL=60
Reply from 194.168.4.100: bytes=32 time=200ms TTL=60
Reply from 194.168.4.100: bytes=32 time=52ms TTL=60
Reply from 194.168.4.100: bytes=32 time=56ms TTL=60
Reply from 194.168.4.100: bytes=32 time=139ms TTL=60
Reply from 194.168.4.100: bytes=32 time=262ms TTL=60
Reply from 194.168.4.100: bytes=32 time=139ms TTL=60
Reply from 194.168.4.100: bytes=32 time=321ms TTL=60
Reply from 194.168.4.100: bytes=32 time=408ms TTL=60
Reply from 194.168.4.100: bytes=32 time=330ms TTL=60
Reply from 194.168.4.100: bytes=32 time=430ms TTL=60
Reply from 194.168.4.100: bytes=32 time=270ms TTL=60
Reply from 194.168.4.100: bytes=32 time=118ms TTL=60
Reply from 194.168.4.100: bytes=32 time=183ms TTL=60
Reply from 194.168.4.100: bytes=32 time=157ms TTL=60
Reply from 194.168.4.100: bytes=32 time=198ms TTL=60
Reply from 194.168.4.100: bytes=32 time=146ms TTL=60
Reply from 194.168.4.100: bytes=32 time=170ms TTL=60
Reply from 194.168.4.100: bytes=32 time=460ms TTL=60
Reply from 194.168.4.100: bytes=32 time=416ms TTL=60
Reply from 194.168.4.100: bytes=32 time=337ms TTL=60
Reply from 194.168.4.100: bytes=32 time=44ms TTL=60
Reply from 194.168.4.100: bytes=32 time=113ms TTL=60
Reply from 194.168.4.100: bytes=32 time=116ms TTL=60
Reply from 194.168.4.100: bytes=32 time=106ms TTL=60
Reply from 194.168.4.100: bytes=32 time=39ms TTL=60
Reply from 194.168.4.100: bytes=32 time=201ms TTL=60
Reply from 194.168.4.100: bytes=32 time=43ms TTL=60
Reply from 194.168.4.100: bytes=32 time=92ms TTL=60
Reply from 194.168.4.100: bytes=32 time=245ms TTL=60
Reply from 194.168.4.100: bytes=32 time=251ms TTL=60
Reply from 194.168.4.100: bytes=32 time=14ms TTL=60
Reply from 194.168.4.100: bytes=32 time=310ms TTL=60
Reply from 194.168.4.100: bytes=32 time=244ms TTL=60
Reply from 194.168.4.100: bytes=32 time=146ms TTL=60
Reply from 194.168.4.100: bytes=32 time=303ms TTL=60
Reply from 194.168.4.100: bytes=32 time=357ms TTL=60
Reply from 194.168.4.100: bytes=32 time=190ms TTL=60
Reply from 194.168.4.100: bytes=32 time=73ms TTL=60
Reply from 194.168.4.100: bytes=32 time=231ms TTL=60
Reply from 194.168.4.100: bytes=32 time=207ms TTL=60
Reply from 194.168.4.100: bytes=32 time=156ms TTL=60
Reply from 194.168.4.100: bytes=32 time=80ms TTL=60
Reply from 194.168.4.100: bytes=32 time=17ms TTL=60
Reply from 194.168.4.100: bytes=32 time=254ms TTL=60
Reply from 194.168.4.100: bytes=32 time=150ms TTL=60
Reply from 194.168.4.100: bytes=32 time=42ms TTL=60
Reply from 194.168.4.100: bytes=32 time=18ms TTL=60
Reply from 194.168.4.100: bytes=32 time=137ms TTL=60
Reply from 194.168.4.100: bytes=32 time=336ms TTL=60
Reply from 194.168.4.100: bytes=32 time=238ms TTL=60
Reply from 194.168.4.100: bytes=32 time=207ms TTL=60
Reply from 194.168.4.100: bytes=32 time=242ms TTL=60
Reply from 194.168.4.100: bytes=32 time=114ms TTL=60
Reply from 194.168.4.100: bytes=32 time=128ms TTL=60
Reply from 194.168.4.100: bytes=32 time=140ms TTL=60
Reply from 194.168.4.100: bytes=32 time=238ms TTL=60
Reply from 194.168.4.100: bytes=32 time=116ms TTL=60
Reply from 194.168.4.100: bytes=32 time=112ms TTL=60
Reply from 194.168.4.100: bytes=32 time=51ms TTL=60
Reply from 194.168.4.100: bytes=32 time=165ms TTL=60
Reply from 194.168.4.100: bytes=32 time=116ms TTL=60
Reply from 194.168.4.100: bytes=32 time=52ms TTL=60
Reply from 194.168.4.100: bytes=32 time=68ms TTL=60
Reply from 194.168.4.100: bytes=32 time=40ms TTL=60
Reply from 194.168.4.100: bytes=32 time=44ms TTL=60
Reply from 194.168.4.100: bytes=32 time=49ms TTL=60
Reply from 194.168.4.100: bytes=32 time=33ms TTL=60
Reply from 194.168.4.100: bytes=32 time=104ms TTL=60
Reply from 194.168.4.100: bytes=32 time=295ms TTL=60
Reply from 194.168.4.100: bytes=32 time=243ms TTL=60
Reply from 194.168.4.100: bytes=32 time=356ms TTL=60
Reply from 194.168.4.100: bytes=32 time=224ms TTL=60
Reply from 194.168.4.100: bytes=32 time=216ms TTL=60
Reply from 194.168.4.100: bytes=32 time=139ms TTL=60
Reply from 194.168.4.100: bytes=32 time=90ms TTL=60
Reply from 194.168.4.100: bytes=32 time=122ms TTL=60
Reply from 194.168.4.100: bytes=32 time=162ms TTL=60
Reply from 194.168.4.100: bytes=32 time=157ms TTL=60
Reply from 194.168.4.100: bytes=32 time=50ms TTL=60
Reply from 194.168.4.100: bytes=32 time=197ms TTL=60
Reply from 194.168.4.100: bytes=32 time=393ms TTL=60
Reply from 194.168.4.100: bytes=32 time=227ms TTL=60
Reply from 194.168.4.100: bytes=32 time=35ms TTL=60
Reply from 194.168.4.100: bytes=32 time=73ms TTL=60
Reply from 194.168.4.100: bytes=32 time=234ms TTL=60
Reply from 194.168.4.100: bytes=32 time=74ms TTL=60

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

Tracing route to pingbox1.thinkbroadband.com [80.249.99.164]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms <1 ms 192.168.0.1
3 35 ms 24 ms 17 ms 10.154.240.1
4 56 ms 21 ms 27 ms perr-core-2b-xe-102-0.network.virginmedia.net [80.0.176.181]
5 * * * Request timed out.
6 * * * Request timed out.
7 360 ms 306 ms 93 ms eislou2-ic-2-ae0-0.network.virginmedia.net [62.254.84.62]
8 514 ms 468 ms 317 ms linx-gw2.thdo.ncuk.net [195.66.236.240]
9 257 ms 319 ms 310 ms po4-31.core-rs2.thdo.ncuk.net [80.249.97.85]
10 211 ms 278 ms 113 ms pingbox1.thinkbroadband.com [80.249.99.164]

Trace complete.

0 Kudos
Reply
  • 12.42K
  • 468
  • 1.11K
legacy1
Alessandro Volta
501 Views
Message 7 of 17
Flag for a moderator

Re: Low Speed and High Latency

Might you have someone on the connection doing a large download or upload?

0 Kudos
Reply
  • 11
  • 0
  • 0
Deathbox
Joining in
495 Views
Message 8 of 17
Flag for a moderator

Re: Low Speed and High Latency

That could be the case but the ping spike is pretty consistent in that it usually begins around 6pm and goes onto to around 12am everyday, the only exception seems to be Friday and Saturday the days you'd expect the most traffic to be present.
0 Kudos
Reply
  • 11
  • 0
  • 0
Deathbox
Joining in
461 Views
Message 9 of 17
Flag for a moderator

Re: Low Speed and High Latency

My current theory is that the modem/box is being overloaded with the amount of connections going through it causing very high latency. Also my landlord contacted me to say that the speed that virgin media was supplying is being increased to see if it helps.

 

Here is another tracert from tonight to www.google.com

 

Tracing route to www.google.com [74.125.193.103]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms <1 ms Hitronhub.home [192.168.0.1]
3 497 ms 387 ms 298 ms 10.154.240.1
4 368 ms 321 ms 499 ms perr-core-2b-xe-212-0.network.virginmedia.net [80.0.176.169]
5 * * * Request timed out.
6 311 ms 524 ms 584 ms eislou2-ic-3-ae0-0.network.virginmedia.net [94.174.238.226]
7 274 ms 374 ms 424 ms m426-mp2.cvx3-a.ltn.dial.ntli.net [213.104.85.170]
8 484 ms 502 ms 350 ms 108.170.246.143
9 383 ms 502 ms 521 ms 216.239.58.179
10 532 ms 489 ms 516 ms 209.85.255.220
11 408 ms 512 ms 287 ms 66.249.95.3
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 556 ms 600 ms * ig-in-f103.1e100.net [74.125.193.103]
19 273 ms 423 ms 581 ms ig-in-f103.1e100.net [74.125.193.103]

Trace complete.

Whatever the 10.154.240.1 step is, is where the latency starts to show itself.

0 Kudos
Reply
  • 11
  • 0
  • 0
Deathbox
Joining in
452 Views
Message 10 of 17
Flag for a moderator

Re: Low Speed and High Latency

Here’s is the BQM for tonight too. Lot more packet loss than usual.04B0CE49-725C-49D2-8B69-260B7FB8E24B.png

 

0 Kudos
Reply