Menu
Reply
  • 2
  • 0
  • 2
phoenixflames82
Settling in
171 Views
Message 11 of 18
Flag for a moderator

Re: Ping issues in evenings (gaming)

Hi, message of solidarity here as I'm experiencing EXACTLY the same issues and likewise the problem is around the same times. I'm in the call queue for the 4th time in a couple of weeks and I'm close to switching to BT at this rate.

  • 12
  • 0
  • 0
fixmynetplease
Tuning in
166 Views
Message 12 of 18
Flag for a moderator

Re: Ping issues in evenings (gaming)

Let me know if you get anywhere with them - i'm out of contract as of last month so I'm tempted to make the switch back to BT myself. 

0 Kudos
Reply
  • 2
  • 0
  • 2
phoenixflames82
Settling in
157 Views
Message 13 of 18
Flag for a moderator

Re: Ping issues in evenings (gaming)

Well they gave me more information this time and apparently they've picked up connection issues between the exchange cabinet and the house (nothing wrong with my equipment in the house). so they've put me on some sort of 'monitoring status' which allows them to alter bandwidth and so far solves the problem albeit papering over the cracks. They've assured me the technician who's booked to visit Monday eve has instructions to test the cabinet and connection so will let you know how that goes. It could be interference caused by high load You may be able to push for something similar especially as you can prove the ping drop outs. PS I'm a massive gamer also and this issue simply isn't tolerable, we're not just browsing facebook or amazon in an evening Smiley Happy
  • 12
  • 0
  • 0
fixmynetplease
Tuning in
130 Views
Message 14 of 18
Flag for a moderator

Re: Ping issues in evenings (gaming)

Run a daytime test again for more examples:

----------------------------------------------------------------------------------------------------------------------

**** 3PM ****


Tracing route to 104.160.141.3 over a maximum of 30 hops

1 3 ms 4 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 17 ms 17 ms cosh-core-2b-xe-805-0.network.virginmedia.net [80.0.142.229]
4 * * * Request timed out.
5 17 ms 32 ms 19 ms brnt-ic-1-ae0-0.network.virginmedia.net [62.254.42.198]
6 24 ms 19 ms 19 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
7 * * * Request timed out.
8 * * * Request timed out.
9 29 ms 29 ms 32 ms nl-ams04a-ri2-ae7-0.aorta.net [84.116.134.89]
10 35 ms 50 ms 29 ms nl-ams04a-ri3-ae0-0.aorta.net [84.116.135.57]
11 33 ms 31 ms 31 ms 213.46.182.2
12 * * * Request timed out.
13 29 ms 30 ms 29 ms 104.160.141.3

Trace complete.

----------------------------------------------------------------------------------------------------------------------

 

as you can see again, the aorta.net servers are responding fine during normal hours. Will run another test tonight and update this thread again when they inevitably go bad. 

0 Kudos
Reply
  • 12
  • 0
  • 0
fixmynetplease
Tuning in
118 Views
Message 15 of 18
Flag for a moderator

Re: Ping issues in evenings (gaming)

Early evening update:

**** 5PM ****

----------------------------------------------------------------------------------------------------------------------

Tracing route to 104.160.141.3 over a maximum of 30 hops

1 2 ms 4 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 14 ms 18 ms 15 ms cosh-core-2b-xe-805-0.network.virginmedia.net [80.0.142.229]
4 * * * Request timed out.
5 26 ms 30 ms 19 ms brnt-ic-1-ae0-0.network.virginmedia.net [62.254.42.198]
6 24 ms 19 ms 19 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
7 * * * Request timed out.
8 * * * Request timed out.
9 43 ms 42 ms 46 ms nl-ams04a-ri2-ae7-0.aorta.net [84.116.134.89]
10 45 ms 41 ms 43 ms nl-ams04a-ri3-ae0-0.aorta.net [84.116.135.57]
11 37 ms 39 ms 44 ms 213.46.182.2
12 * * 53 ms ae-100.br02.ams02.riotdirect.net [104.160.141.37]
13 57 ms 59 ms 52 ms 104.160.141.3

Trace complete.

----------------------------------------------------------------------------------------------------------------------

As you can see, ping is creeping up to the mid 40s already (from 30~ at 3pm).

 

3PM result for reference:

Spoiler

Tracing route to 104.160.141.3 over a maximum of 30 hops

1 3 ms 4 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 17 ms 17 ms cosh-core-2b-xe-805-0.network.virginmedia.net [80.0.142.229]
4 * * * Request timed out.
5 17 ms 32 ms 19 ms brnt-ic-1-ae0-0.network.virginmedia.net [62.254.42.198]
6 24 ms 19 ms 19 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
7 * * * Request timed out.
8 * * * Request timed out.
9 29 ms 29 ms 32 ms nl-ams04a-ri2-ae7-0.aorta.net [84.116.134.89] 
10 35 ms 50 ms 29 ms nl-ams04a-ri3-ae0-0.aorta.net [84.116.135.57]
11 33 ms 31 ms 31 ms 213.46.182.2
12 * * * Request timed out.
13 29 ms 30 ms 29 ms 104.160.141.3

Trace complete.

Will post another update after 6pm. That's usually when it hits the 50+ ping mark.

0 Kudos
Reply
  • 1.27K
  • 65
  • 227
Adduxi
Knows their stuff
114 Views
Message 16 of 18
Flag for a moderator

Re: Ping issues in evenings (gaming)

For completeness, here's my BT circuit tracert at 17:10

Tracing route to 104.160.141.3 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms [MY_ROUTER]
2 * * * Request timed out.
3 17 ms 17 ms 17 ms 31.55.185.181
4 18 ms 17 ms 17 ms 31.55.185.188
5 19 ms 19 ms 19 ms 195.99.127.214
6 20 ms 19 ms 20 ms core3-hu0-14-0-7.faraday.ukcore.bt.net [195.99.127.64]
7 20 ms 19 ms 19 ms 213.137.183.36
8 24 ms 26 ms 24 ms t2c3-xe-1-0-1-0.nl-ams2.eu.bt.net [166.49.208.218]
9 * * * Request timed out.
10 25 ms 25 ms 25 ms 104.160.141.3

Trace complete.

  • 12
  • 0
  • 0
fixmynetplease
Tuning in
100 Views
Message 17 of 18
Flag for a moderator

Re: Ping issues in evenings (gaming)

Another test done at 7:30PM. Hopefully I get a response to this soon... will be contacting BT next monday if this doesn't get resolved.

 

**** 7:30PM (50ms~) ****

----------------------------------------------------------------------------------------------------------------------


Tracing route to 104.160.141.3 over a maximum of 30 hops

1 2 ms 2 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 15 ms 19 ms 19 ms cosh-core-2b-xe-805-0.network.virginmedia.net [80.0.142.229]
4 * * * Request timed out.
5 20 ms 19 ms 34 ms brnt-ic-1-ae0-0.network.virginmedia.net [62.254.42.198]
6 23 ms 19 ms 17 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
7 * * * Request timed out.
8 * * * Request timed out.
9 76 ms 51 ms 46 ms nl-ams04a-ri2-ae7-0.aorta.net [84.116.134.89]
10 47 ms 53 ms 49 ms nl-ams04a-ri3-ae0-0.aorta.net [84.116.135.57]
11 * * * Request timed out.
12 * * 55 ms ae-100.br02.ams02.riotdirect.net [104.160.141.37]
13 54 ms 54 ms 55 ms 104.160.141.3

Trace complete.

----------------------------------------------------------------------------------------------------------------------

 

5PM Result (40ms~):

Spoiler

Tracing route to 104.160.141.3 over a maximum of 30 hops

1 2 ms 4 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 14 ms 18 ms 15 ms cosh-core-2b-xe-805-0.network.virginmedia.net [80.0.142.229]
4 * * * Request timed out.
5 26 ms 30 ms 19 ms brnt-ic-1-ae0-0.network.virginmedia.net [62.254.42.198]
6 24 ms 19 ms 19 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
7 * * * Request timed out.
8 * * * Request timed out.
9 43 ms 42 ms 46 ms nl-ams04a-ri2-ae7-0.aorta.net [84.116.134.89] 
10 45 ms 41 ms 43 ms nl-ams04a-ri3-ae0-0.aorta.net [84.116.135.57]
11 37 ms 39 ms 44 ms 213.46.182.2
12 * * 53 ms ae-100.br02.ams02.riotdirect.net [104.160.141.37]
13 57 ms 59 ms 52 ms 104.160.141.3

Trace complete.

3PM Result (30ms~):

Spoiler

Tracing route to 104.160.141.3 over a maximum of 30 hops

1 3 ms 4 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 17 ms 17 ms cosh-core-2b-xe-805-0.network.virginmedia.net [80.0.142.229]
4 * * * Request timed out.
5 17 ms 32 ms 19 ms brnt-ic-1-ae0-0.network.virginmedia.net [62.254.42.198]
6 24 ms 19 ms 19 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
7 * * * Request timed out.
8 * * * Request timed out.
9 29 ms 29 ms 32 ms nl-ams04a-ri2-ae7-0.aorta.net [84.116.134.89] 
10 35 ms 50 ms 29 ms nl-ams04a-ri3-ae0-0.aorta.net [84.116.135.57]
11 33 ms 31 ms 31 ms 213.46.182.2
12 * * * Request timed out.
13 29 ms 30 ms 29 ms 104.160.141.3

Trace complete.

 

----------------------------------------------------------------------------------------------------------------------

 

For comparison, here is a ping trace to google.com, which is located in California (5300+ miles). Same sort of response time to the virgin media servers in Austria (800 miles), completely unacceptable: 

Spoiler
Tracing route to google.com [216.58.206.142]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 18 ms 33 ms 32 ms cosh-core-2b-xe-805-0.network.virginmedia.net [80.0.142.229]
4 * * * Request timed out.
5 23 ms 19 ms 19 ms tele-ic-7-ae2-0.network.virginmedia.net [62.253.175.34]
6 18 ms 19 ms 22 ms 74-14-250-212.static.virginm.net [212.250.14.74]
7 * * * Request timed out.
8 43 ms 42 ms 49 ms 216.239.56.195
9 53 ms 49 ms 39 ms lhr25s15-in-f14.1e100.net [216.58.206.142]

Trace complete.

 

0 Kudos
Reply
  • 1.41K
  • 83
  • 328
cje85
Knows their stuff
91 Views
Message 18 of 18
Flag for a moderator

Re: Ping issues in evenings (gaming)

Google will connect to the nearest server which in the case of that trace is LHR (London).

Aorta.net is part of VM's parent company but not something Virgin itself controls, the most they can do is raise a ticket to the team in Amsterdam who operate Aorta.

That said, my pings to those two Aorta hosts aren't too bad, using a Hub 3:

 

Spoiler

PING 84.116.134.89 (84.116.134.89): 56 data bytes
64 bytes from 84.116.134.89: seq=0 ttl=59 time=24.375 ms
64 bytes from 84.116.134.89: seq=1 ttl=59 time=20.615 ms
64 bytes from 84.116.134.89: seq=2 ttl=59 time=20.350 ms
64 bytes from 84.116.134.89: seq=3 ttl=59 time=20.507 ms
64 bytes from 84.116.134.89: seq=4 ttl=59 time=19.753 ms
64 bytes from 84.116.134.89: seq=5 ttl=59 time=22.588 ms
64 bytes from 84.116.134.89: seq=6 ttl=59 time=19.979 ms
64 bytes from 84.116.134.89: seq=7 ttl=59 time=20.083 ms
64 bytes from 84.116.134.89: seq=8 ttl=59 time=20.878 ms
64 bytes from 84.116.134.89: seq=9 ttl=59 time=24.875 ms

--- 84.116.134.89 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 19.753/21.400/24.875 ms

--- 

PING 84.116.135.57 (84.116.135.57): 56 data bytes
64 bytes from 84.116.135.57: seq=0 ttl=60 time=36.053 ms
64 bytes from 84.116.135.57: seq=1 ttl=60 time=30.058 ms
64 bytes from 84.116.135.57: seq=2 ttl=60 time=26.519 ms
64 bytes from 84.116.135.57: seq=3 ttl=60 time=26.122 ms
64 bytes from 84.116.135.57: seq=4 ttl=60 time=30.367 ms
64 bytes from 84.116.135.57: seq=5 ttl=60 time=26.272 ms
64 bytes from 84.116.135.57: seq=6 ttl=60 time=26.234 ms
64 bytes from 84.116.135.57: seq=7 ttl=60 time=26.594 ms
64 bytes from 84.116.135.57: seq=8 ttl=60 time=33.160 ms
64 bytes from 84.116.135.57: seq=9 ttl=60 time=26.389 ms

--- 84.116.135.57 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 26.122/28.776/36.053 ms

 

 

 

0 Kudos
Reply