Connection very slow at peak times!

[HoriZon]

The last few days or so my connection has gone from around 7mb most of the time synced at 8128kbps to around 1mb or less from around 6pm till about midnight now i can still surf etc though much much slower but playing games (which i like to do around 8pm-10pm some nights) and watching video on demand is useless to me and i do a lot of that.

Doing ping tests on speedtest.net ranges from 200 to 1200.

Its now doing my head in i'm paying for an A rated service at a much higher cost than most others and not getting it.

This may be my exchange i don't know but its not good enough.

Using this 'Exchange Status Checker' tells me this:
http://usertools.plus.net/exchanges/?exchange=Pocklington&exact=1552&plugin=vp

Now this may be the reason but as yet no fix has been stated.


Rebooted the modem done all the speed tests in the day and they are fine all back to normal done speed tests on BT's own site all good in the day just not on a night.

What can i do next? my phones 3G is faster than this.


It was fine just a week or so ago as well:




Ping tests done at 8pm:
-------------------------------------------
ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=499ms TTL=59
Reply from 212.69.36.10: bytes=32 time=440ms TTL=59
Reply from 212.69.36.10: bytes=32 time=498ms TTL=59
Reply from 212.69.36.10: bytes=32 time=484ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 440ms, Maximum = 499ms, Average = 480ms


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=435ms TTL=59
Reply from 212.69.36.10: bytes=32 time=470ms TTL=59
Reply from 212.69.36.10: bytes=32 time=460ms TTL=59
Reply from 212.69.36.10: bytes=32 time=509ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 435ms, Maximum = 509ms, Average = 468ms


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 212.69.36.10: bytes=32 time=597ms TTL=59
Reply from 212.69.36.10: bytes=32 time=614ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
   Minimum = 597ms, Maximum = 614ms, Average = 605ms

[Simon]

I'm not sure whether that means VP congestion, but the link you gave does seem to point to the problem, in which case, I think you'll need to contact IDNet, but it's ultimately down to the BT exchange. 

[HoriZon]

Yeah i rang them about an hour ago but guess what they were closed silly opening times for a broadband compnay tbh, will try them tomm morning but it will work fine then.

Right now its like been on a dialup modem

[.Griff.]

Are you using a wired or wireless connection?

[HoriZon]

Tried both same results.

This PC (laptop) is wireless but the other PC (desktop) and the games console (games lag all the time) is wired and both are suffering as is my Blu-ray player which has built in BBC iPlayer and others (cant watch anything on that now), well other than Blu-rays that is

It has been like this for a few days and i thought nothing of it as i thought it would be ok in a day or so but days later still doing it.

[Lance]

Yeah i rang them about an hour ago but guess what they were closed silly opening times for a broadband compnay tbh, will try them tomm morning but it will work fine then.

Silly hours? They are the same hours or (or better) as when you signed up to Idnet. I assume you checked the situation of hours and costs before signing up? It would be silly not to.

As for the problem, BT have actually admitted that there is a problem on the virtual paths which is almost certainly going to be causing your problem. Getting that admission from BT is an achievement in itself so hopefully they will perform the vp upgrade soon.

[Simon]

The evidence of the PlusNet exchange status page does suggest VP congestion, but for elimination purposes, have you tried disconnecting the Blu ray and the games console from the network, and just use the wired connection, in case something is saturating the connection?  We've had slow downs like this before, and it's turned out to be something saturating the upstream, which caused a slowdown of the downstream.  IDNet will probably want to establish no faults within your own equipment and network, before getting onto BT. 

[HoriZon]

The evidence of the PlusNet exchange status page does suggest VP congestion, but for elimination purposes, have you tried disconnecting the Blu ray and the games console from the network, and just use the wired connection, in case something is saturating the connection?  We've had slow downs like this before, and it's turned out to be something saturating the upstream, which caused a slowdown of the downstream.  IDNet will probably want to establish no faults within your own equipment and network, before getting onto BT.  

I haven't yet no but wouldn't that effect it all the time not just at peak times?

As of right now its getting better but its almost 11pm and a bit late to do anything i wanted to do.

Edit: ok unplugged everthing but this PC (desktop) wired and its the same, but as above getting better as its not as busy.

[HoriZon]

Silly hours? They are the same hours or (or better) as when you signed up to Idnet. I assume you checked the situation of hours and costs before signing up? It would be silly not to.

As for the problem, BT have actually admitted that there is a problem on the virtual paths which is almost certainly going to be causing your problem. Getting that admission from BT is an achievement in itself so hopefully they will perform the vp upgrade soon.

The price is the price and i understand that, IDnet have been great for the last 3/4 years now with only a few issues for me but this one is proving to be a pain as i cant do anything at the time most of us sit down and do these things at home.

If its this VP thing wouldn't that effect just about everyone on the same exchange so BT will be hearing lots of other complaints about it?

Will ring IDnet tomm and leave only this PC plugged into the modem so they can do any tests, its also in the master socket with the face plate off right now and has been for a few hours. Hopefully they can tell me more about this VP thing if indeed that is the issue.


Ping tests as of 11pm-ish:
----------------------------------

[Simon]

It was just a thought, as IDNet will usually ask for home equipment to be checked, but as has been said, it sounds like VP congestion. 

[.Griff.]

It would be worth you creating a Thinkbroadband Quality Monitor - http://www.thinkbroadband.com/ping/monitors/create.html - as this has been very effective in my experience at demonstrating exchange congestion.

[HoriZon]

Ping tests as of 11pm-ish:
----------------------------------
ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 17ms, Maximum = 20ms, Average = 18ms


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59

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


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 18ms, Maximum = 29ms, Average = 21ms

----------------------------------


Almost back to normal now.

[Simon_idnet]

A VP is a Virtual Path (a VLAN) from the Exchange back in the BT backbone. Every Exchange has multiple VPs. Small, rural Exchanges have fewer VPs than large metro Exchanges but any VP can become congested with more subscribers each downloading more data. BT can and will increase capacity on a VP when their monitoring shows that one has reached capacity but BT will not give us a schedule as to when a VP will be upgraded (probably because if it can't be achieved by software then a hardware upgrade (more fibre installed to the Exchange) is required which would require engineering resources to be allocated).

[HoriZon]

A VP is a Virtual Path (a VLAN) from the Exchange back in the BT backbone. Every Exchange has multiple VPs. Small, rural Exchanges have fewer VPs than large metro Exchanges but any VP can become congested with more subscribers each downloading more data. BT can and will increase capacity on a VP when their monitoring shows that one has reached capacity but BT will not give us a schedule as to when a VP will be upgraded (probably because if it can't be achieved by software then a hardware upgrade (more fibre installed to the Exchange) is required which would require engineering resources to be allocated).

If most people in this area are getting this slowness at the times they use it like me, they shouldn't be happy about it. I guess a fix would be a long way off.
I do pay a bit extra to IDnet to have 'Traffic Priority' does this not step me over people who dont?


Now that everyone in my area has buggred off to bed it seems fine again.

Edit: yeah its fine now i can stream BBC iPlayer HD fine again.

[Simon]

Thanks for the explanation, Simon.  Can a user be moved from one VP to a less congested one, or is there a risk of them ending up on an even more congested one, if a shift were possible? 

[HoriZon]

What time do IDnet start to take calls tomm? might try and catch them before i leave for work at 8:40am.

But i have the feeling their is nothing that can be done till BT pull a finger out of their arse which is a shame as it puts a massive downer on the reason having a premium internet service (dont get home till 7pm most nights) if we cant use it at times we sit down and do these things.

[Steve]

From IDNet's  webpage FAQ -support hours

8am – 6.30pm Monday to Thursday
8am – 6pm Friday
Support via email is available 24/7 at support@idnet.com

[HoriZon]

From IDNet's  webpage FAQ -support hours

8am – 6.30pm Monday to Thursday
8am – 6pm Friday
Support via email is available 24/7 at support@idnet.com

ah it was hidden in the FAQ

Thanks.

[Bill]

From IDNet's  webpage FAQ -support hours

8am – 6.30pm Monday to Thursday
8am – 6pm Friday
Support via email is available 24/7 at support@idnet.com

An email address is of limited use if you've got no internet!

It's a pity IDNet don't mention that, in the event of a complete loss of internet, a message left on the 0800 number will be investigated (and acknowledged) as soon as it's picked up, even if nothing can be done until BT wake up.

It would deflect a lot of the criticism about the support hours.

[HoriZon]

Gave them a ring and as i thought they want a BT speedtest so i will do that tonight if/when it slows to a snails pace.

Right now its all fine.

[HoriZon]

Home early today and its fine right now the speed has gone down a little but that's t be expected, now to see if it drops like it has over the next few hours.

[Fox]

I have been having the same problems as you


Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=291ms TTL=59
Reply from 212.69.36.10: bytes=32 time=223ms TTL=59
Reply from 212.69.36.10: bytes=32 time=208ms TTL=59
Reply from 212.69.36.10: bytes=32 time=278ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 208ms, Maximum = 291ms, Average = 250ms

C:\Users\Fox>ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=259ms TTL=59
Reply from 212.69.36.10: bytes=32 time=317ms TTL=59
Reply from 212.69.36.10: bytes=32 time=248ms TTL=59
Reply from 212.69.36.10: bytes=32 time=203ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 203ms, Maximum = 317ms, Average = 256ms

My broadband went down for 15 minutes or so on the 12th and my hasn't been the same since. I did some digging around and found out my area code was effected by SLOUGH ATM NODE 3 : LOSS OF SERVICE. I haven't had a chance to talk to Idnet support as I am at work while they are open.

[Steve]

Can you email them with the details and a BT speedtest if you can get it to work?

[HoriZon]

Emailing them my self later tonight, this is my current BT speedtest done at 9pm.


=====================================================================
Time: 9:00pm - 16th June 2011
=====================================================================
Download speedachieved during the test was - 450 Kbps
For your connection, the acceptable range of speeds is 1200-7150 Kbps.
Additional Information:
Your DSL Connection Rate :8128 Kbps(DOWN-STREAM), 832 Kbps(UP-STREAM)
IP Profile for your line is - 7150 Kbps
=====================================================================


By about 11pm it will be back to normal which was this ealier today:

=====================================================================
Time: 8:30am - 16th June 2011
=====================================================================
Download speedachieved during the test was - 6443 Kbps
For your connection, the acceptable range of speeds is 1200-7150 Kbps.
Additional Information:
Your DSL Connection Rate :8128 Kbps(DOWN-STREAM), 832 Kbps(UP-STREAM)
IP Profile for your line is - 7150 Kbps
=====================================================================

[Fox]

finally got speedtester to work after 2 days trying


Download speedachieved during the test was - 1521 Kbps
For your connection, the acceptable range of speeds is 600-7150 Kbps.
Additional Information:
Your DSL Connection Rate :8032 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
IP Profile for your line is - 7000 Kbps


Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=136ms TTL=59
Request timed out.
Reply from 212.69.36.10: bytes=32 time=196ms TTL=59
Reply from 212.69.36.10: bytes=32 time=175ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
   Minimum = 136ms, Maximum = 196ms, Average = 169ms


Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=204ms TTL=59
Reply from 212.69.36.10: bytes=32 time=213ms TTL=59
Reply from 212.69.36.10: bytes=32 time=268ms TTL=59
Reply from 212.69.36.10: bytes=32 time=194ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 194ms, Maximum = 268ms, Average = 219ms

looks like i am getting some packet loss too....

This is the fourth or fifth time my ping has gone through the roof while I have been with Idnet. I dont mind the higher price Idnet charges in comparison with some other providers if they deliver the service they promise, but alas they dont seem to. I think its time to move over to Plusnet, they offer twice the monthly download (60Gb) and it costs £8 a month less.

[JohnH]

It might be cheaper, but it's traffic managed, so good luck.

[Steve]

If your slowness is due to Exchange Congestion unless you go LLU you'll take it with you until BT upgrade the VP's at your local exchange.

[Fox]

I live in a small village and normally get 6-7 meg download, much like Horizon i havent noticed an extra 1000 houses springing up in the last week.

[Simon]

Emailing them my self later tonight, this is my current BT speedtest done at 9pm.


=====================================================================
Time: 9:00pm - 16th June 2011
=====================================================================
Download speedachieved during the test was - 450 Kbps
For your connection, the acceptable range of speeds is 1200-7150 Kbps.
Additional Information:
Your DSL Connection Rate :8128 Kbps(DOWN-STREAM), 832 Kbps(UP-STREAM)
IP Profile for your line is - 7150 Kbps
=====================================================================


By about 11pm it will be back to normal which was this ealier today:

=====================================================================
Time: 8:30am - 16th June 2011
=====================================================================
Download speedachieved during the test was - 6443 Kbps
For your connection, the acceptable range of speeds is 1200-7150 Kbps.
Additional Information:
Your DSL Connection Rate :8128 Kbps(DOWN-STREAM), 832 Kbps(UP-STREAM)
IP Profile for your line is - 7150 Kbps
=====================================================================

Clearly tonight's speed is below the BT 'acceptable range', so I would have thought IDNet could get them to do something.

[Steve]

If IDNet's network was congested I think we'd see the evidence on here as poor performance gets members posting. Although you say your rural exchange has no apparent increase in population what we don't know is whether there has been an increase in broadband users and/or change in their usage which has increased traffic through the exchange.

I suggest Fox that you send that BT speedtest result to support for further investigation.

[Lance]

Or BT could have changed something at or beyond the exchange. Also to note is in sone cases small exchanges link into a bigger one somewhere near by so problems could occur there.

[HoriZon]

No gaming for me tonight:


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=397ms TTL=59
Reply from 212.69.36.10: bytes=32 time=376ms TTL=59
Reply from 212.69.36.10: bytes=32 time=434ms TTL=59
Reply from 212.69.36.10: bytes=32 time=499ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 376ms, Maximum = 499ms, Average = 426ms


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=597ms TTL=59
Reply from 212.69.36.10: bytes=32 time=535ms TTL=59
Reply from 212.69.36.10: bytes=32 time=583ms TTL=59
Reply from 212.69.36.10: bytes=32 time=609ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 535ms, Maximum = 609ms, Average = 581ms


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=572ms TTL=59
Reply from 212.69.36.10: bytes=32 time=589ms TTL=59
Reply from 212.69.36.10: bytes=32 time=571ms TTL=59
Reply from 212.69.36.10: bytes=32 time=471ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 471ms, Maximum = 589ms, Average = 550ms


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=418ms TTL=59
Reply from 212.69.36.10: bytes=32 time=359ms TTL=59
Reply from 212.69.36.10: bytes=32 time=394ms TTL=59
Reply from 212.69.36.10: bytes=32 time=242ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 242ms, Maximum = 418ms, Average = 353ms


---------------------------

Shall see what IDNet say when they get back to me again tomorrow hopefully.

[Rik]

What's throughput like? There's some evidence of congestion here, but it's minor:

ping www.idnet.com

Pinging www.idnet.com [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=16ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 21ms, Average = 18ms

normally, I'd see about 15ms average. Upload and download speeds, however, are normal.

[HoriZon]

Download speedachieved during the test was - 777 Kbps
For your connection, the acceptable range of speeds is 1200-7150 Kbps.
Additional Information:
Your DSL Connection Rate :8128 Kbps(DOWN-STREAM), 832 Kbps(UP-STREAM)
IP Profile for your line is - 7150 Kbps



^^^ lol

Its only doing this when its busy, thing is a few weeks ago it was fine its the last week or so.

Cant game, cant watch iPlayer stuff and really cant use the net when i want to which is like everyone on a night!

Maybe i should quit working and use the net in the day its fine then.

Right now its like been on IDSN again but a little worse.

[Lona]

I have to agree not knowing anything about pings etc.  Connections at weekends is poor.  I live with it and put it down to BT.

All isps suffer the same problem. End of story.

[HoriZon]

I have to agree not knowing anything about pings etc.  Connections at weekends is poor.  I live with it and put it down to BT.

All isps suffer the same problem. End of story.

Shouldn't be this slow and even so its not just the weekend for me this is every night.

[Rik]

Download speedachieved during the test was - 777 Kbps
For your connection, the acceptable range of speeds is 1200-7150 Kbps.

That test will help IDNet, send it on to them.

[Rik]

Shouldn't be this slow and even so its not just the weekend for me this is every night.

Usually that points to exchange congestion.

[HoriZon]

That test will help IDNet, send it on to them.

Have done with about another 5 from Thursday night last week, still waiting on an answer.

Usually that points to exchange congestion.

Yeah i understand all that but its getting worse and it was fine i used to game, stream vidoes at anytime with no issues till about a week or so ago.

[Rik]

You won't get one till tomorrow.

[HoriZon]

You won't get one till tomorrow.

Wasn't expecting one today

[Rik]

 

[HoriZon]

One thing i do know, is our new neighbours have broadband the last ones didnt would this effect me? as we are on the same poll ?

Using it at the same time etc, but then again wouldnt that effect it all the time not just on a night?

[Simon]

Are they having the same problems as you?

[Rik]

Potentially it might increase cross-talk and, therefore, the error count, but that would be it - unless they're on the same VP as you and downloading 24/7. It might be worth asking them if they've noticed any speed problems, and, if they will, get their d/s sync speed, attenuation and noise margin to compare with yours. One other possibility is that any wireless connections could be affected by their router.

[HoriZon]

Are they having the same problems as you?

Dont know them well enough to ask and dont really see them.


As for Wireless im getting this wired as well.

[Rik]

Another bright idea bites the dust.

[HoriZon]

It has to be congestion at the exchange, thing is can IDNet do anything about that? a BT fix could be ages if ever.

Either that or i get a night job

[Rik]

IDNet moan to BT, BT acknowledge and schedule an upgrade (this may have already happened), the upgrade can take from a few days to a few weeks.

[HoriZon]

IDNet moan to BT, BT acknowledge and schedule an upgrade (this may have already happened), the upgrade can take from a few days to a few weeks.

Lets hope so and BT are on there way to fix it this week at least if that gets done and i still have issue, then i go kill the neighbour's! 

[Rik]

 

[Wivelrod]

For reference, IDNET confirmed that my exchange was congested with BT on the 13th May and informed me that BT would fix it on the 5th of July!

Even so, the Exchange still shows as Green on exchange checker web pages.

I'm eagerly awaiting the 5th, but I'm pessimistic! I expect that day to pass and still find I have less than 1mbit at peak times 

[Rik]

Most exchange checker sites are relying on out of date information from BT, unfortunately.

[HoriZon]

Got this back frim IDNet today:

--------------------------------------------------------------------------
If the problem continues, BT are currently working to resolve the issue,
normal lead time to make further bandwidth available is usually around
10 working days however they do have engineers working on this ASAP.
--------------------------------------------------------------------------

I guess all i can do is wait for now.

[Rik]

I'm afraid so.

[HoriZon]

Is it a hardware fix or software?

Also i guess this issue is effecting most people on the exchange or just a select few ?


At work now but just done a remote test to my PC and all is fine at home atm, tongiht it all changes.

[Rik]

It's a hardware fix, BT need to make more fibre available at the exchange, hence the lead time. It will be affecting everyone connected to the affeced VP, which can result in your neighbour not being affected, but someone a couple of streets away suffering as you are.

[HoriZon]

Well over a week later and BT are yet to fix the exchange, will wait till Tuesday to see if the works been done before I contact IDNet again.

They have two more working days!!






ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=254ms TTL=59
Reply from 212.69.36.10: bytes=32 time=350ms TTL=59
Reply from 212.69.36.10: bytes=32 time=275ms TTL=59
Reply from 212.69.36.10: bytes=32 time=196ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 196ms, Maximum = 350ms, Average = 268ms


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=338ms TTL=59
Reply from 212.69.36.10: bytes=32 time=257ms TTL=59
Reply from 212.69.36.10: bytes=32 time=315ms TTL=59
Reply from 212.69.36.10: bytes=32 time=316ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 257ms, Maximum = 338ms, Average = 306ms


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=340ms TTL=59
Reply from 212.69.36.10: bytes=32 time=273ms TTL=59
Reply from 212.69.36.10: bytes=32 time=257ms TTL=59
Reply from 212.69.36.10: bytes=32 time=263ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 257ms, Maximum = 340ms, Average = 283ms

[HoriZon]

Really bad right now and its not like I can change hosts either not that I want to.

Can't surf much at all like this.

Not uploading anything.

Feels like I'm on a 56k modem right now

Not been able to play any games or stream any video on a night for over a week now, starting to get annoyed now.

Just hope this fix is just that next week, but I have my doubts anything will change though. I understand its not IDNet's fault and its an issue with the exchange but its effecting how we use the internet in a big way right now.

Maybe I should go down to the local exchange with a sledgehammer?   








ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=610ms TTL=59
Reply from 212.69.36.10: bytes=32 time=689ms TTL=59
Reply from 212.69.36.10: bytes=32 time=726ms TTL=59
Reply from 212.69.36.10: bytes=32 time=759ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 610ms, Maximum = 759ms, Average = 696ms


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=787ms TTL=59
Reply from 212.69.36.10: bytes=32 time=671ms TTL=59
Reply from 212.69.36.10: bytes=32 time=692ms TTL=59
Reply from 212.69.36.10: bytes=32 time=782ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 671ms, Maximum = 787ms, Average = 733ms


ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=893ms TTL=59
Reply from 212.69.36.10: bytes=32 time=860ms TTL=59
Reply from 212.69.36.10: bytes=32 time=889ms TTL=59
Reply from 212.69.36.10: bytes=32 time=678ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 678ms, Maximum = 893ms, Average = 830ms

[Steve]

I agree it's awful come on BT get your finger out!

[HoriZon]

Well its been a few days since the 4th now and it looks like its been fixed as its much better on a night now (ping back to normal and about a 5mb connection which is a bit lower than what i get in the day but that's probably to be expected at these times) and that site is saying the VP is GREEN again, will keep an eye on it but hopefully that's it for now!

http://usertools.plus.net/exchanges/?exchange=Pocklington&exact=1552&plugin=vp

Well I can only hope

[Steve]

Thanks for the update and 

[HoriZon]

Well its been a few weeks and tbh its not as bad as it was but during these times its not great and no way can i play any games which is a shame and there is nothing i can do about it.

The exchange reports Amber once again also.

Anyone at IDNet able to say what is going on ?

[Rik]

You'd have to ask them, but my best guess would be BT failed to install enough new capacity.

[HoriZon]

Yeah i will but need to do a few BT Speedtest over the next few days to send to them.

Right now its fine, 

[Rik]

Classic signs of capacity problems, I'm afraid.