Congestion?

[psp83]

Anyone else notice packet loss / traffic on their TBBG over the last few days, even when computers are off?

[Lance]

I had some this morning which completely buggered my connection. I noticed before leaving this AM that the met office app wasn't working but only realised it was my connection when a stream of emails came through late morning (I've got my own server).

This evening watching iplayer via freesat I had to disconnect and reconnect to get it to play with constant buffering. However, it's been fine since doing that.

My connection is FTTC btw.

[zappaDPJ]

I've not seen any significant packet loss but I have had a lot of buffering on iPlayer, Sky Player and ITV Player during the last few days. In fact iPlayer often fails with a insufficient bandwidth error. I've run tests and my connection appears quite healthy so I assumed it's a server side capacity issue

[Steve]

Having looked at the staff TTBQM 3 FTTC users are showing a small amount of packet loss between 8-11 last night and an increase in the maximum latency.

[psp83]

So it looks like IDnet side that's slightly congested?

On my one, between 3pm & 10pm my connection was hardly used.

[Steve]

Not necessarily Paul as they are the only TBQMs I currently have access to and of course they are all with IDNet , I can't find any non IDNet ones at present.

[joe]

Yes, as attached:-

[Steve]

Thanks Joe that's the same as the ones I've seen,however there is one FTTC IDNet customer TBBQM (Bill)not showing anything in the way of packet loss or an increase in the maximum latency, that implies to me that perhaps BT is involved, it would be nice nevertheless to see one from a non IDNet FTTC customer though.

[joe]

psp83,

My latency used to be as yours but increased some time back to its present position. The packet loss 'chatter' is becoming more frequent as are the bigger packet loss happenings. I sometimes doubt my Fritz!box and ponder returning to OR modem but then decide that the uptake in local FTTC connections is a more probable cause. It was obviously better in the early days when one was sharing the cabinet with few other people.

[caber]

Hello,

Just registered to say that I too am having the issues mentioned (packet loss and an increase in latency).  I'm on an ADSL2+ package with IDNET, I don't have the thinkbroadband line monitor but I'm experiencing very slow browsing and lots of time outs when pinging using the command prompt.  Pings are up to 48-51ms when I usually get around 25ms.  No sign of trouble on their network status page http://idnet.net/support/networkstatus.php I hope this gets resolved soon.

edit: Thanks Simon!

Not as fancy as the line monitors but this is what my connection is like at the moment:

>ping bbc.co.uk -n 20

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=49ms TTL=247
Request timed out.
Reply from 212.58.241.131: bytes=32 time=49ms TTL=247
Request timed out.
Reply from 212.58.241.131: bytes=32 time=48ms TTL=247
Request timed out.
Reply from 212.58.241.131: bytes=32 time=48ms TTL=247
Request timed out.
Reply from 212.58.241.131: bytes=32 time=48ms TTL=247
Request timed out.
Reply from 212.58.241.131: bytes=32 time=48ms TTL=247
Request timed out.
Reply from 212.58.241.131: bytes=32 time=47ms TTL=247
Request timed out.
Reply from 212.58.241.131: bytes=32 time=48ms TTL=247
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.58.241.131: bytes=32 time=48ms TTL=247

Ping statistics for 212.58.241.131:
    Packets: Sent = 20, Received = 9, Lost = 11 (55% loss),
Approximate round trip times in milli-seconds:
    Minimum = 47ms, Maximum = 49ms, Average = 48ms

[psp83]

psp83,

My latency used to be as yours but increased some time back to its present position. The packet loss 'chatter' is becoming more frequent as are the bigger packet loss happenings. I sometimes doubt my Fritz!box and ponder returning to OR modem but then decide that the uptake in local FTTC connections is a more probable cause. It was obviously better in the early days when one was sharing the cabinet with few other people.

My ping always changes, one week it will be 13ms, another it will go up to 27ms, but always below 30ms.

All depends if its the right type of rain in the air, the direction of the wind, if the neighbour got out the wrong side of the bed, etc etc 

Other than this issue at the mo, my connection is normally fine, I don't really get any packet loss and the green/blue/yellow line is normally flat (unless connection is being used)

[andrue]

Yup, just came here to ask if anyone else had seen it. I'm on FTTC with typically 76Mb/s throughput:

.

That's on the Banbury (Brackley) exchange.

I did a speed test around 6pm (the spike) and browsed a bit on and off without any problems though. For me it's just curiousity as it didn't impact me at the time. A more typical evening for me is:

[psp83]

I've just emailed support asking about any congestion issues and linked them to this post. Hopefully will get a reply soon.

Edit:

Latest TBBG

[Simon]

Hello,

Just registered to say that I too am having the issues mentioned (packet loss and an increase in latency).  I'm on an ADSL2+ package with IDNET, I don't have the thinkbroadband line monitor but I'm experiencing very slow browsing and lots of time outs when pinging using the command prompt.  Pings are up to 48-51ms when I usually get around 25ms.  No sign of trouble on their network status page http://idnet.net/support/networkstatus.php I hope this gets resolved soon.

Welcome to the forum. 

[psp83]

Just got an email back from Simon (not the one above this post  )

No, we're not experiencing any congestion at all at our end.

Maybe it's to do with this then ? http://status.aa.net.uk/apost.cgi?incident=1627

[psp83]

Hello,

Just registered to say that I too am having the issues mentioned (packet loss and an increase in latency).  I'm on an ADSL2+ package with IDNET, I don't have the thinkbroadband line monitor but I'm experiencing very slow browsing and lots of time outs when pinging using the command prompt.  Pings are up to 48-51ms when I usually get around 25ms.  No sign of trouble on their network status page http://idnet.net/support/networkstatus.php I hope this gets resolved soon.

edit: Thanks Simon!

Not as fancy as the line monitors but this is what my connection is like at the moment:

>ping bbc.co.uk -n 20

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=49ms TTL=247
Request timed out.
Reply from 212.58.241.131: bytes=32 time=49ms TTL=247
Request timed out.
Reply from 212.58.241.131: bytes=32 time=48ms TTL=247
Request timed out.
Reply from 212.58.241.131: bytes=32 time=48ms TTL=247
Request timed out.
Reply from 212.58.241.131: bytes=32 time=48ms TTL=247
Request timed out.
Reply from 212.58.241.131: bytes=32 time=48ms TTL=247
Request timed out.
Reply from 212.58.241.131: bytes=32 time=47ms TTL=247
Request timed out.
Reply from 212.58.241.131: bytes=32 time=48ms TTL=247
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.58.241.131: bytes=32 time=48ms TTL=247

Ping statistics for 212.58.241.131:
    Packets: Sent = 20, Received = 9, Lost = 11 (55% loss),
Approximate round trip times in milli-seconds:
    Minimum = 47ms, Maximum = 49ms, Average = 48ms

Some routers don't respond to pings at busy times, it's best to do a trace route.

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

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

  1    <1 ms    <1 ms    <1 ms  home.gateway [192.168.1.254]
  2    13 ms    13 ms    13 ms  telehouse-gw4-lo1.idnet.net [212.69.63.98]
  3    13 ms    13 ms    13 ms  telehouse-gw6-gi3-401.idnet.net [212.69.63.182]
  4    13 ms    13 ms    13 ms  telehouse-gw5-gi4-400.idnet.net [212.69.63.245]
  5    14 ms    13 ms    13 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8    30 ms    13 ms    14 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
  9    14 ms    14 ms    15 ms  132.185.255.148
10    14 ms    13 ms    13 ms  bbc-vip111.telhc.bbc.co.uk [212.58.244.66]

Trace complete.

[caber]

Hey Paul,

Yeah I was aware that ping packets can be dropped at busy times but I've never experienced it myself.  To be on the safe side I ran a tracert -

>tracert bbc.co.uk

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

  1    <1 ms    <1 ms    <1 ms  home.gateway.home.gateway [192.168.1.254]
  2    47 ms     *       48 ms  telehouse-gw4-lo1.idnet.net [212.69.63.98]
  3    47 ms     *        *     telehouse-gw6-gi3-401.idnet.net [212.69.63.182]

  4     *       48 ms    47 ms  telehouse-gw5-gi4-400.idnet.net [212.69.63.245]

  5    73 ms     *       48 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  6     *        *        *     Request timed out.
  7    48 ms    48 ms    67 ms  ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
  8    49 ms    48 ms     *     132.185.255.60
  9    48 ms    48 ms    48 ms  212.58.241.131

Trace complete.

I'm connected to the Inverurie (NSIUR) exchange.

[Steve]

  caber

[toad]

Another first time poster here. I'm also suffering sudden and drastic packet loss. I'm in Inverness. Reported to IDnet this morning 30 minutes after the problem suddenly appeared. Line test came back fine - modem is synced at 11576kbps down 1100kbps up. Checked the AAISP status page and they have a note that the Falkirk RAS suffered a blip at 10:15 am this morning with resultant packet loss. I'm assuming this has affected everyone north of Falkirk? How to put a rocket up BT's bum?

Nothing mentioned on BT service status page. When it first happened I powered off the modem for 15 minutes or so and when turning back on, could only connect to BT wholesale service page - router had a generic 172?.x.x.x BT IP rather than an IDnet one.

Why do AAISP have such a great service status page and why don't other ISPs follow suit?

IDnet support say nothing wrong with line, nothing from BT saying a problem. Told them about AAISP service status page and have been told to keep an eye on it. I'll be phoning back if it is not better by 5pm so that IDnet can escalate to BT - my business depends on my connection! 

Edit: Zen internet status page shows problems with exchange in Edinburgh since 10.20am.

[Steve]

    Toad


I did see that on AAISP and was going to ask caber how long he'd had the problems for as he's north of Falkirk as well . Obviously we've no idea on the mysteries of BT's routing.

[toad]

Thanks for the welcome Steve  - another interesting service status post from Plusnet (wholly owned subsiduary of BT and yet BT don't mention it -  ) - seems BT works could be affecting the whole of UK, even though most work is supposedly carried out overnight. Quote:
"Planned BT Network Maintenance - Week commencing 5th November 2012
05/11/2012 @ 17:03

When's this work happening?
Early hours of most days this week.

What does it affect?
Broadband connectivity.

How long will it take?
Up to six hours each time.

What does the work involve?
We've received notifications from our suppliers about maintenance work that is scheduled to take place in the following areas this week. This work typically takes place between Midnight and 6am.

6th November
Walsall, Kingston and Fulham

7th November
Preston, Nottingham and Dorchester

8th November
London Faraday

9th November
Birmingham

Although these are the areas we have been notified of, due to the nature of the broadband network these outages may affect customers nationwide. There are also a number of smaller exchange works most nights of the week that may cause smaller outages at individual exchanges.

Am I likely to notice the work?
Yes, there's a chance that you may be disconnected from the internet for a period of time during the maintenance window.

Is there anything else I need to know?
Any end users having problems connecting once the maintenance is complete are advised to log into their router interface and click connect.

Kind Regards,

Chris Purvey
Customer Support"

[davej99]

Connection on and off here in Perthshire since 10:16 am. This logon took a minute or more to load. Done manual loggoff/on to break session. No luck.

[caber]

Thanks Steve,

Good catches with the exchange faults toad, I've given up trying to browse sites at the moment as I don't have the patience for it when it's as painfully slow as this.  It was around 10am this morning that I too started experiencing the issues.

[Steve]

I wonder how long before BT declare it as a fault? The only currently declared BT fault is in N.Ireland.

[Lona]

I'm in Ayrshire and my connection is terrible.   Can't download email and it took ages to access this forum.
Other websites are just as bad.