BT Infinity & FTTx Discussion

Westyfield2 · 7 Oct 2012 at 19:42

MilanoChris said:
They look very similar. It's starting again now.

Yep.

kmufc77 · 7 Oct 2012 at 21:03

Same problems as the other night tonight for me, the forums here are very very slow and sometimes wont load at all, think broadband is very slow as is the daily mail, Twitter and more.

Cant believe there is nothing on the BT forums confirming the issue or anything in the service status.

Nightglow · 7 Oct 2012 at 21:22

Having same problems here.

ChrisD. · 7 Oct 2012 at 22:47

Broadband is pretty much unusable now. This is like being on Virgin Media!

kmufc77 · 7 Oct 2012 at 23:19

randal · 7 Oct 2012 at 23:22

Ah it's not just me then...

Code:

Ping statistics for 72.32.103.134:
    Packets: Sent = 212, Received = 84, Lost = 128 (60% loss),
Approximate round trip times in milli-seconds:
    Minimum = 124ms, Maximum = 200ms, Average = 130ms

Certain sites are all but down, has taken 3-4 attempts to get OcUK to load. TRO is working fine though!

Mana · 7 Oct 2012 at 23:36

aha finally these forums are loading

kmufc77 · 7 Oct 2012 at 23:38

Mana said:
aha finally these forums are loading

yeah makes you wonder, thats because of the time and traffic is a lot more quiet? not sure as im not very good when it comes to networks

Out of the sites that wont load properly, the forums here are the worst for me

Vanhishikha · 8 Oct 2012 at 00:07

Are you guys getting these problems on BT Infinity? :/. If so, that kind of sucks...

Mana · 8 Oct 2012 at 00:47

yea its only certain sites...

places like google and youtube worked just fine. very weird.

DirtyJester · 8 Oct 2012 at 08:07

Mana said:
yea its only certain sites...

places like google and youtube worked just fine. very weird.

Yip same issues here, was able to view almost anything else without problems oh apart from Domino's Pizza! Working fine this morning.

Appeared to have similar issue on Saturday night as well except OcUK forum loaded ok but just rather slowly, last night started slow but then just completely gave up and refused to load.

{SAS}TB · 8 Oct 2012 at 08:23

OCUK forums were terribly slow / timing out last night for me too (infinity 2) - seems ok now though

ChrisD. · 8 Oct 2012 at 08:48

Code:

C:\Users\Chris>tracert twitter.com

Tracing route to twitter.com [199.59.150.7]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  my.router [192.168.0.1]
  2     5 ms     5 ms     5 ms  217.32.145.230
  3     5 ms     5 ms     5 ms  217.32.146.14
  4    10 ms    11 ms     9 ms  213.120.181.94
  5    10 ms     9 ms     9 ms  217.41.169.205
  6    10 ms    10 ms     9 ms  217.41.169.109
  7     9 ms     9 ms    10 ms  109.159.251.229
  8    19 ms    24 ms    23 ms  core1-te0-4-0-2.ilford.ukcore.bt.net [109.159.251.129]
  9    15 ms    15 ms    15 ms  peer1-xe11-0-0.redbus.ukcore.bt.net [62.6.200.85]
 10    19 ms     *        *     ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]
 11     *        *        *     Request timed out.
 12     *      141 ms     *     so-1-1-0.mpr1.dca2.us.above.net [64.125.31.186]
 13    98 ms    90 ms     *     xe-1-3-0.cr1.dca2.us.above.net [64.125.29.21]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17   216 ms     *        *     ae51.smf1-er1.twttr.com [199.16.159.29]
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20   233 ms     *        *     r-199-59-150-7.twttr.com [199.59.150.7]
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

It's all happening when it hits above.net

ChrisD. · 8 Oct 2012 at 09:19

I've just emailed the BT head office, doubt it'll get me anywhere but it may help.

DirtyJester · 8 Oct 2012 at 09:21

MilanoChris said:
I've just emailed the BT head office, doubt it'll get me anywhere but it may help.

Can but try mate

ChrisD. · 8 Oct 2012 at 09:25

If they allow me to cancel my contract with no early release fee then I'll be happy. I'll be ordering Sky Fibre Pro.

DBT85 · 8 Oct 2012 at 09:29

Hmm, my HH3 is telling me that the connection has only been up for about 90 minutes, but if it dropped then it reconnected by itself.

Is that normal?

Last weekend when I had connection issues only a modem reboot would fix the issue. The HH3 said there was a conenction, the modem said there was a connection, I could ping websites, but no internet. The modem reboot fixed it instantly.

randal · 8 Oct 2012 at 09:55

MilanoChris said:

Code:

C:\Users\Chris>tracert twitter.com

Tracing route to twitter.com [199.59.150.7]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  my.router [192.168.0.1]
  2     5 ms     5 ms     5 ms  217.32.145.230
  3     5 ms     5 ms     5 ms  217.32.146.14
  4    10 ms    11 ms     9 ms  213.120.181.94
  5    10 ms     9 ms     9 ms  217.41.169.205
  6    10 ms    10 ms     9 ms  217.41.169.109
  7     9 ms     9 ms    10 ms  109.159.251.229
  8    19 ms    24 ms    23 ms  core1-te0-4-0-2.ilford.ukcore.bt.net [109.159.251.129]
  9    15 ms    15 ms    15 ms  peer1-xe11-0-0.redbus.ukcore.bt.net [62.6.200.85]
 10    19 ms     *        *     ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]
 11     *        *        *     Request timed out.
 12     *      141 ms     *     so-1-1-0.mpr1.dca2.us.above.net [64.125.31.186]
 13    98 ms    90 ms     *     xe-1-3-0.cr1.dca2.us.above.net [64.125.29.21]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17   216 ms     *        *     ae51.smf1-er1.twttr.com [199.16.159.29]
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20   233 ms     *        *     r-199-59-150-7.twttr.com [199.59.150.7]
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

It's all happening when it hits above.net

Yeah I found this yesterday too Chris, went to hell soon as it hit their perimeter.

Uhtred · 8 Oct 2012 at 10:55

It looks like they are aware - http://community.bt.com/t5/BB-Speed-Connection-Issues/Major-Packet-Loss/td-p/652172

Lazy · 8 Oct 2012 at 11:56

Well Im happy. Just had my infinity 2 install. Around 700m from the cabinet, was estimated 30down and 6upload. Engineer must have done some real magic when swapping the master socket around to another room.

Wired Im getting:

and wireless Im getting around 38down 11up.

Hopefully it stays at this level for the foreseeable future!

Granted it does have the 10-12day training period.