Very slow throughput

zappaDPJ · Feb 23, 2011, 06:39:30

According to my daughter our connection dropped last night and failed to reconnect. Looking at the logs I think it actually did reconnect but it's ridiculously slow. Web pages are taking many minutes to resolve if they resolve at all. I think I have some bandwidth as I'm able to run steamed content if I can get it to start. I can't run a speed test because the lack of throughput stops them from completing. The only evidence I can find that anything is wrong is via my tbb monitor.

I'm really just wondering if anyone else is having issues or if it's local to me?

zappaDPJ · Feb 23, 2011, 06:46:41

QuoteMicrosoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\zappaDPJ>tracert idnet.net

Tracing route to idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 15 ms 14 ms 14 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 18 ms 41 ms 19 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 41 ms 255 ms 124 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 15 ms * 15 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 15 ms 15 ms 15 ms www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\zappaDPJ>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.1
2 15 ms 15 ms 15 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 15 ms 14 ms 14 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 15 ms 15 ms 15 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 15 ms 15 ms 16 ms 212.58.238.149
6 15 ms 15 ms * virtual-vip.thdo.bbc.co.uk [212.58.224.138]
7 * 15 ms 15 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

C:\Users\zappaDPJ>tracert google.co.uk

Tracing route to google.co.uk [74.125.230.148]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 15 ms 15 ms 14 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 14 ms * 14 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 18 ms 15 ms 18 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 15 ms 20 ms 15 ms google1.lonap.net [193.203.5.136]
6 15 ms 15 ms 15 ms 209.85.255.78
7 23 ms 16 ms 15 ms 209.85.251.202
8 15 ms 15 ms 26 ms 74.125.230.148

Trace complete.

C:\Users\zappaDPJ>tracert idnetters.co.uk

Tracing route to idnetters.co.uk [212.69.36.118]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 15 ms 14 ms 14 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 14 ms 14 ms 14 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 15 ms 15 ms * redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 * 15 ms 15 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 15 ms 15 ms * cpanel3.idnet.net [212.69.36.118]
7 15 ms 15 ms 15 ms cpanel3.idnet.net [212.69.36.118]

Trace complete.

C:\Users\zappaDPJ>

There seems to be a fair bit of packet loss and I keep having to resubmit my posts as they are timing out.

Steve · Feb 23, 2011, 07:22:58

I've not had an issues overnight Zap.

Glenn · Feb 23, 2011, 07:25:51

Me neither, could it be a FTTC issue?

zappaDPJ · Feb 23, 2011, 07:45:51

Thanks

I'll give IDNet a ring later today if it persists.

RobertoS · Feb 23, 2011, 08:28:32

Problem here as well.

and

C:\Users\Bob>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 2 ms * 1 ms 192.168.11.1
2 18 ms * 425 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 12 ms * 60 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 * 3950 ms 95 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 13 ms * 12 ms 212.58.238.149
6 29 ms * 13 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

C:\Users\Bob>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.246.94]
over a maximum of 30 hops:

1 2 ms * 5 ms 192.168.11.1
2 12 ms * 13 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 * 12 ms * telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 13 ms * 14 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 13 ms * 13 ms 212.58.238.133
6 13 ms * 15 ms te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
7 14 ms * 16 ms 212.58.255.12
8 15 ms * * bbc-vip015.cwwtf.bbc.co.uk [212.58.246.94]
9 * 13 ms * bbc-vip015.cwwtf.bbc.co.uk [212.58.246.94]
10 2048 ms * 40 ms bbc-vip015.cwwtf.bbc.co.uk [212.58.246.94]

Trace complete.

joe · Feb 23, 2011, 08:36:08

Something odd:-

The graph doesn't appear to reflect what is actually going on. Connection seems OK:-

zappaDPJ · Feb 23, 2011, 08:45:57

I have spoken to support and they are looking into it. I need to get some work done this morning so I'm going to go to another location and I'll try to look in from there. For reference I'm in the North London area.

RobertoS · Feb 23, 2011, 09:11:53

Quote from: joe on Feb 23, 2011, 08:36:08
Something odd:-

The graph doesn't appear to reflect what is actually going on. Connection seems OK

You either have the graph disabled or a change of IP address.

gizmo71 · Feb 23, 2011, 13:04:01

Quote from: zappaDPJ on Feb 23, 2011, 08:45:57
I have spoken to support and they are looking into it. I need to get some work done this morning so I'm going to go to another location and I'll try to look in from there. For reference I'm in the North London area.

Not a million miles away in sunny Basildon and I noticed my connection dropped yet again overnight and it's been like treacle ever since. I'll bounce it when I get home - can't even connect to my Sharepoint or Exchange servers from work it's so slow.

.Griff. · Feb 23, 2011, 14:58:14

Quote from: Glenn on Feb 23, 2011, 07:25:51
Me neither, could it be a FTTC issue?

My FTTC connection is fine -

zappaDPJ · Feb 23, 2011, 15:09:27

It's a local issue. It appears BT carried out some maintenance work in my area last night, need I say more

I think it's just been fixed and my graph (posted above) seems to confirm that. Thanks go to support and James in particular for identifying the problem and getting it fixed

gizmo71 · Feb 23, 2011, 15:24:40

Yep, mine's just come back to life too.

Lance · Feb 23, 2011, 16:26:35

BT stike again!

joe · Feb 23, 2011, 17:42:12

Thanks RobertoS. I changed my router yesterday and hadn't unchecked the filters in the SPI firewall sttings. Now OK again.

RobertoS · Feb 23, 2011, 19:53:17

RobertoS · Feb 23, 2011, 20:00:31

Quote from: zappaDPJ on Feb 23, 2011, 15:09:27
It's a local issue. It appears BT carried out some maintenance work in my area last night, need I say more

I think it's just been fixed and my graph (posted above) seems to confirm that. Thanks go to support and James in particular for identifying the problem and getting it fixed

I don't think it is fixed.

My first few days had virtually zero latency spikes, and look at this.

The two blue columns are the single tbb speed test, result showing, and the two tracerts were done just after.

sof2er · Feb 23, 2011, 21:14:25

Tracing route to jolt.co.uk [84.234.17.86]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.1.1
2 46 ms 22 ms 22 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 22 ms 21 ms 22 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 22 ms 21 ms 21 ms lonap-gw1.netrino.co.uk [193.203.5.144]
5 22 ms 22 ms 22 ms hex-edge.netrino.co.uk [84.234.19.146]
6 23 ms 24 ms 23 ms bs1-core.netrino.co.uk [84.234.19.5]
7 23 ms 23 ms 24 ms bruce.ferrago.net [84.234.17.86]

Trace complete.

G:\Users\Sof2er>tracert bbc.net.uk

Tracing route to bbc.net.uk [212.58.246.91]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 22 ms 21 ms 22 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 21 ms 22 ms 22 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 22 ms 23 ms 22 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 22 ms 24 ms 23 ms 212.58.238.133
6 23 ms 23 ms 23 ms te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
7 23 ms 32 ms 23 ms 212.58.255.12
8 23 ms 22 ms 23 ms bbc-vip012.cwwtf.bbc.co.uk [212.58.246.91]

Trace complete.

It's not global atleast, perhaps somewhere at the exchange/area ?

What I find weird about your screenshot is that your first hop to your router indicates packet loss / time out too ? So it might be related to that rather than the connection?

I'd say try a direct PPPoE PC to Modem and see if that has the same problems

RobertoS · Feb 23, 2011, 21:30:19

There could be something in what you say, but not tonight.

The junk room where the router is is over-flowing due to being in the middle of replacing the sideboard and bookcases downstairs.

Latency of physically connecting to the router is high.