higher ping than usual with O2

I have some email alert from Be that they will be doing some upgrades this might be cause of the problem fingers crossed.
 
Well after speaking with 2 peeps at o2 level 2 support they are refusing to help saying oh well what do you want us to do about your ping & its normal... They then suggested I pay extra to have a static ip & that will surely fix it, well all I can say is thats a con & they know their 93.96 ip range has issues so basically I stuck till I get a new IP
 
MikeHiow said:
Considering the destination is supposed to be in the US (Although, I've never seen a ping <80ms to the US), that's an impressive ping.
Click to expand...

I was thinking more along the lines of his 4th/5th hops.
Incidentally I've seen ~67ms pings to a US server (NYC/NJ) before from a proxy, although obviously for a home user to get under 80 they'd likely need to be a Londoner on Cable/Fastpath LLU.

tolien said:
Depends where you are. The first hop I get (after the router, on Be) is the OP's fifth, which is in London. The further you are from there the worse it's going to get
Click to expand...

True, but even from Northumberlund I wouldn't be expecting much more than maybe an 8ms increase in latency compared to London users; I know some that used to have <10ms.
 
I am in Crewe, on 02 and my line is interleaved apart from the first hop my pings i would say are quite good.

Tracing route to bbc.co.uk [212.58.224.131]

over a maximum of 30 hops:



1 <1 ms <1 ms <1 ms 192.168.1.254

2 562 ms 100 ms 202 ms 87-194-136-1.bethere.co.uk [87.194.136.1]

3 * * * Request timed out.

4 * 18 ms 18 ms 195.50.112.237

5 18 ms 18 ms 17 ms ae-14-51.car3.london1.level3.net [4.68.116.17]

6 18 ms 18 ms 18 ms 195.50.90.162

7 17 ms 18 ms 18 ms 212.58.238.133

8 19 ms 18 ms 18 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]



Trace complete.
 
Tracing route to jolt.co.uk [82.133.85.65]

over a maximum of 30 hops:



1 <1 ms <1 ms <1 ms 192.168.1.254

2 15 ms 15 ms 15 ms 87-194-136-1.bethere.co.uk [87.194.136.1]

3 * 19 ms 20 ms 10.1.2.5

4 35 ms 36 ms 36 ms te1-3.cr05.hx2.bb.gxn.net [195.66.226.29]

5 * 35 ms 36 ms vl3953.cr05.tn5.bb.gxn.net [62.72.137.29]

6 76 ms 47 ms 48 ms gi1-1-6.ar01.tn5.bb.gxn.net [62.72.140.142]

7 36 ms 36 ms 35 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.241.14]

8 36 ms 36 ms 36 ms secure.jolt.co.uk [82.133.85.65]



Trace complete.
 
You're a bit nearer London than Newcastle though :p

I get:

Code: 
traceroute to jolt.co.uk (82.133.85.65), 30 hops max, 40 byte packets
 1  192.168.1.254 (192.168.1.254)  101.295 ms  100.905 ms  100.414 ms
 2  * * *
 3  * * *
 4  * * *
 5  so-0-0-0.mpr1.lhr2.uk.above.net (64.125.27.225)  41.333 ms  42.244 ms  44.010 ms
 6  gxn-pi-above-1000Mbps.lhr.above.net (209.249.203.138)  58.911 ms  41.661 ms  42.949 ms
 7  gi2-48-5.ar01.tn5.bb.gxn.net (62.72.140.14)  78.278 ms  64.023 ms  43.670 ms
 8  ge-0-0-0-3801.jolt-gw.cust.pipex.net (212.241.241.14)  40.396 ms  42.052 ms  42.272 ms
 9  secure.jolt.co.uk (82.133.85.65)  41.835 ms  43.802 ms  44.996 ms

Though something seems to be wrong with Zen (not that I've noticed):
Code: 
 1  stargate (82.69.***.***)  10.121 ms  10.574 ms  11.057 ms
 2  gamiel-dsl1.ls.zen.net.uk (62.3.86.7)  77.991 ms  80.721 ms  82.198 ms
 3  nietzsche-ge-0-0-2-204.ls.zen.net.uk (62.3.86.205)  84.679 ms  86.660 ms  88.140 ms
 4  nozick-ae1-0.ls.zen.net.uk (62.3.80.74)  89.871 ms  91.850 ms  93.834 ms
 5  lorenz-so-0-1-0-0.te.zen.net.uk (62.3.80.78)  100.815 ms  103.544 ms  105.775 ms
 6  te1-3.cr05.hx2.bb.gxn.net (195.66.226.29)  107.255 ms  100.212 ms  101.644 ms
 7  vl3953.cr05.tn5.bb.gxn.net (62.72.137.29)  101.819 ms vl3952.cr05.tn5.bb.gxn.net (62.72.137.9)  83.522 ms  83.325 ms
 8  gi2-48-5.ar01.tn5.bb.gxn.net (62.72.140.14)  85.076 ms  86.521 ms gi1-1-6.ar01.tn5.bb.gxn.net (62.72.140.142)  87.078 ms
 9  ge-0-0-0-3801.jolt-gw.cust.pipex.net (212.241.241.14)  83.084 ms  83.514 ms  85.089 ms
10  secure.jolt.co.uk (82.133.85.65)  84.579 ms  82.771 ms  82.073 ms
 
The only permenant solution is a static ip acording to 3rd line or just leave it switched off till I get one of their new ip's 94.97 range. I'll just have to keep using the tiscali then :D that I pay for next door
 
im getting crap pings on my bethere connection have been for some time now.



Pinging www.bbc.net.uk [212.58.251.195] with 32 bytes of data:
Reply from 212.58.251.195: bytes=32 time=61ms TTL=121
Reply from 212.58.251.195: bytes=32 time=63ms TTL=121
Reply from 212.58.251.195: bytes=32 time=57ms TTL=121
Reply from 212.58.251.195: bytes=32 time=51ms TTL=121

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

Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=144ms TTL=51
Reply from 82.133.85.65: bytes=32 time=149ms TTL=51
Reply from 82.133.85.65: bytes=32 time=136ms TTL=51
Reply from 82.133.85.65: bytes=32 time=133ms TTL=51

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

Pinging core1.multiplay.co.uk [85.236.96.22] with 32 bytes of data:
Reply from 85.236.96.22: bytes=32 time=61ms TTL=123
Reply from 85.236.96.22: bytes=32 time=59ms TTL=123
Reply from 85.236.96.22: bytes=32 time=86ms TTL=123
Reply from 85.236.96.22: bytes=32 time=97ms TTL=123

Ping statistics for 85.236.96.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 59ms, Maximum = 97ms, Average = 75ms
 
Noticed my o2 connection has slowed down since the week too. Getting lots of packed lost. 4 sent and 2recited via ping to bbc. Spoke to o2 cs and adv me nothing wrong but things have been very slow loading sites up. BUT downloading i still get 1.4 which is my usual max
 
You must log in or register to reply here.
Back
Top Bottom