BT Infinity & FTTx Discussion
- Thread starter michellez
- Start date
No idea, except maybe that BT's network can cope with it.
Why do you care about 300kbps? The more you restart your modem, the higher the interleave setting your line will be put on.
No, it drops to 0.3Mbps rather than by that amount. Odd.
They don't think its important!
possible line and/or VDSL modem fault?
It's on a small table so yes, although it does feel quite hot to the touch lately (probably sun hitting it through the window). I'll give BT a call when I get home and ask if there's anything they can do.
Hello cp88 - hope you're still reading this thread!
Just got connected to Infinity 2 days ago and am a bit disappointed my pings - getting about 20ms to bbc.co.uk from SW London, when I used to get 5-6ms with Be.
Do you have any tips for time of day or phase of the moon re: different IPs and better latency? Does the above advice still apply? I still get a 5-6ms first hop with Infinity but it gains about 15ms on the way to the BBC
Technology and investment in infrastructure. HFC/DOCSIS isn't very good at upstream. Everyone would have a much better gaming connection on VM if they went back to a more sensible 1-2mbps up.
Most likely you're going trough the Ilford hop which you can't do much about.Hello cp88 - hope you're still reading this thread!
Just got connected to Infinity 2 days ago and am a bit disappointed my pings - getting about 20ms to bbc.co.uk from SW London, when I used to get 5-6ms with Be.
Do you have any tips for time of day or phase of the moon re: different IPs and better latency? Does the above advice still apply? I still get a 5-6ms first hop with Infinity but it gains about 15ms on the way to the BBC
Do a traceroute to bbc.co.uk and see if there's the Ilford hop in there. If so, you're unlikely to see sub 15ms.
Here's a couple of traceroutes I had saved from last night - ilford appears in the second one, but not the first. I added the early hop IPs to my hosts file to speed up the tracert - got sick of waiting for the reverse DNS lookup to fail.
Code:
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms a.router [10.1.1.254]
2 6 ms 6 ms 6 ms slowhop2 [217.32.147.97]
3 6 ms 6 ms 6 ms randhop3 [217.32.147.142]
4 12 ms 11 ms 11 ms randhop4 [213.120.181.142]
5 11 ms 11 ms 11 ms slowhop5 [217.41.169.197]
6 12 ms 11 ms 11 ms slowhop6 [217.41.169.109]
7 11 ms 11 ms 11 ms 109.159.251.235
8 22 ms 27 ms 24 ms core2-te0-13-0-2.ealing.ukcore.bt.net [109.159.251.139]
9 16 ms 22 ms 83 ms peer2-xe10-1-0.telehouse.ukcore.bt.net [109.159.254.116]
10 19 ms 18 ms 17 ms 194.74.65.42
11 * * * Request timed out.
12 22 ms 28 ms 22 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
13 18 ms 19 ms 21 ms 132.185.255.134
14 18 ms 20 ms 19 ms 212.58.241.131
And to the first server in this post:
Tracing route to quakelive.london.i3d.net [94.76.229.13]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms a.router [10.1.1.254]
2 6 ms 5 ms 6 ms slowhop2 [217.32.147.97]
3 7 ms 8 ms 23 ms randhop3 [217.32.147.142]
4 11 ms 11 ms 11 ms 213.120.181.126
5 11 ms 11 ms 11 ms slowhop5 [217.41.169.197]
6 11 ms 11 ms 11 ms slowhop6 [217.41.169.109]
7 11 ms 11 ms 11 ms 109.159.251.231
8 20 ms 19 ms 19 ms core1-te0-12-0-6.ilford.ukcore.bt.net [109.159.251.133]
9 26 ms 23 ms 20 ms peer4te0-1-0-0.telehouse.ukcore.bt.net [109.159.254.54]
10 18 ms 18 ms 18 ms hex89-linx.as29550.net [195.66.236.223]
11 22 ms 20 ms 19 ms vl668.the-7600.as29550.net [92.48.95.10]
12 21 ms 21 ms 26 ms a.1.magic-the.as29550.net [217.112.81.90]
13 18 ms 18 ms 17 ms quakelive.london.i3d.net [94.76.229.13]Google DNS I think - just on my PC, not network wide. Got sick of the BeBox half-dying and not responding to DNS requests.
Is there anywhere I can check estimated rollout dates for cabinent upgrades, my exchange is now allegedly "accepting orders" but I can't find any plans for the cabs (I've heard about checking local planning applications but I couldn't find what I was looking for).