High pings again

[quandam]

Checked IDNet service status a few moments ago, described as 'Good Service' for all categories.

[Gary]

I am not sure I am right Gary but if there're pulling DSLAM from exchanges I see no other solution. My worry is that the old system will be left to rot whilst attention and service is diverted to WBC

Well if thats the case my speeds will get so slow I will just go for a cheap and not cheerful provider, as my exchange has no WBC date at all, I would not pay a premium to have a dead in the water service, and with no sign of LLU either it really would make sense, I can see BT leaving that system to do as you say and the ISP's not giving a t*ss about it either as its a pain and expensive, maybe it will get to the point they will not take on new adsl max lines at all, now that would not surprise me.

[mynnydd]

How are these for random pings!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Please, what is going on?
I smashed my PS3 controller into a million pieces Sunday night due to a ping, download, upload.
I pay the £25:00 just to game, can IDNnet still provide the service?

[Gary]

Test1 comprises of Best Effort Test:  -provides background information.
    Your DSL connection rate: 8128 kbps(DOWN-STREAM),  448 kbps(UP-STREAM)
    IP profile for your line is - 7150 kbps
    Actual IP throughput achieved during the test was - 3889 kbps

If you wish to discuss these results please contact your ISP.

I have to say I really have had about enough of this now, the speed drop is massive, at night its 6607kbps in the day its 3889kbps today and I seriously doubt its the exchange, its been green for ages, where I live is not full of young kids its old people and disabled and most I have asked so far don't have computers that's why we are a BT only exchange with no WBC date, there are so few users here. I would contact support, but I know IDNet will say the speed is acceptable for the product

My Pings have gone up as well

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=53ms TTL=59
Reply from 212.69.36.10: bytes=32 time=71ms TTL=59
Reply from 212.69.36.10: bytes=32 time=90ms TTL=59
Reply from 212.69.36.10: bytes=32 time=104ms 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 = 53ms, Maximum = 104ms, Average = 79ms

[Rik]

I honestly don't know what's going on with pings. I'm told that the network is re-balanced and there's no congestion, so I'm left with believing IDNet and blaming BT for poor capacity on the DSLAM VPs and backhaul, or not believing IDNet. The fact that WBC doesn't seem to be suffering suggests to me that it's a BT issue.

[Gary]

I honestly don't know what's going on with pings. I'm told that the network is re-balanced and there's no congestion, so I'm left with believing IDNet and blaming BT for poor capacity on the DSLAM VPs and backhaul, or not believing IDNet. The fact that WBC doesn't seem to be suffering suggests to me that it's a BT issue.

If this is the trend for thouse of us not on WBC I can see myself calling it quits on IDnet Rik, paying a premium does not really matter anymore as it does not define your level of service it seems

[Rik]

That is a real fear, Gary. Ultimately, all non-LLU ISPs are dependent on what BT deliver. Things should improve in the nxt few months when ISP Connect goes live and IDNet can move people on non-WBC exchanges to the hostlink.

[mynnydd]

That is a real fear, Gary. Ultimately, all non-LLU ISPs are dependent on what BT deliver. Things should improve in the nxt few months when ISP Connect goes live and IDNet can move people on non-WBC exchanges to the hostlink.

Please could you expand a little.
Are you saying I will get the service BT give no matter who the provider is?

[dujas]

Ping average (to www.idnet.net) is still 24ms for me. There shouldn't be any major traffic spikes as the 138th Golf Open is over and the Ashes third test doesn't start until the 30th of July.

[Rik]

25ms here, interleaved.

[Gary]

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\>ping www.idnet.net

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=98ms TTL=59
Reply from 212.69.36.10: bytes=32 time=76ms TTL=59
Reply from 212.69.36.10: bytes=32 time=60ms TTL=59
Reply from 212.69.36.10: bytes=32 time=99ms 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 = 60ms, Maximum = 99ms, Average = 83ms

still high for me 

[dujas]

@mynnydd

As I understand it, the ISP pays BT wholesale to route your data from the exchange to the ISP's gateway, from then on you're on the ISP's network. Kitz has a diagram to show how it works for those of us on adsl max products (pre-21CN):



LLU ISPs have their own equipment in the exchange, so they are free to make their own transit arrangements in getting your data to the gateway.

[Gary]

That is a real fear, Gary. Ultimately, all non-LLU ISPs are dependent on what BT deliver. Things should improve in the nxt few months when ISP Connect goes live and IDNet can move people on non-WBC exchanges to the hostlink.

So things should improve by the Autumn?   thats a long time to wait, Rik.

[Rik]

Have you checked your exchange status, Gary?

[Gary]

Have you checked your exchange status, Gary?

Very Green as per usual , Rik  I can also see the cabinet from my lounge window, my stats should give me a great speed and did when I came back but its been buggy for a while and off and on since gw6 went wrong. gw5 was fast now its getting like gw6 was.

[mynnydd]

@mynnydd

As I understand it, the ISP pays BT wholesale to route your data from the exchange to the ISP's gateway, from then on you're on the ISP's network. Kitz has a diagram to show how it works for those of us on adsl max products (pre-21CN):



LLU ISPs have their own equipment in the exchange, so they are free to make their own transit arrangements in getting your data to the gateway.

Thank-you.

[Rik]

Thanks for that Mynnydd, it's all that cloud stuff where the troubles occur, imo.

[Rik]

Very Green as per usual , Rik  I can also see the cabinet from my lounge window, my stats should give me a great speed and did when I came back but its been buggy for a while and off and on since gw6 went wrong. gw5 was fast now its getting like gw6 was.

At which point you are reduced to asking for a MAC and seeing whether it helps, or sitting tight, Gary, unfortunately.

[Gary]

At which point you are reduced to asking for a MAC and seeing whether it helps, or sitting tight, Gary, unfortunately.

I know Rik, think I'll use David as a yard stick or sorts and see what happens to his line, even with wbc if things improve drastically it means something is not right here, trouble is its Zen or newnet and I really should not have to be doing this, I may just go to bed and hide 

[Rik]

I understand. I can't remember a time when the forum was quite such an unhappy place.

[karser]

Well my router was off for 12 hours this time, & still my ping looks like someone having an epileptic fit simultaneously with a heart attack.

[Fox]

C:\Users\Fox>ping www.idnet.com -n 20

Pinging www.idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=108ms TTL=59
Reply from 212.69.36.10: bytes=32 time=178ms TTL=59
Reply from 212.69.36.10: bytes=32 time=174ms TTL=59
Reply from 212.69.36.10: bytes=32 time=163ms TTL=59
Reply from 212.69.36.10: bytes=32 time=198ms TTL=59
Reply from 212.69.36.10: bytes=32 time=154ms TTL=59
Reply from 212.69.36.10: bytes=32 time=148ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms TTL=59
Reply from 212.69.36.10: bytes=32 time=163ms TTL=59
Reply from 212.69.36.10: bytes=32 time=125ms TTL=59
Reply from 212.69.36.10: bytes=32 time=130ms TTL=59
Reply from 212.69.36.10: bytes=32 time=159ms TTL=59
Reply from 212.69.36.10: bytes=32 time=160ms TTL=59
Reply from 212.69.36.10: bytes=32 time=95ms TTL=59
Reply from 212.69.36.10: bytes=32 time=117ms TTL=59
Reply from 212.69.36.10: bytes=32 time=144ms TTL=59
Reply from 212.69.36.10: bytes=32 time=136ms TTL=59
Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=80ms TTL=59
Reply from 212.69.36.10: bytes=32 time=89ms TTL=59

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

My current ping.......

on the bright side it does seem to clear up and revert back to normal after 1.00 am, thats just kind of late to have to wait to play a game online 

[Steve]

Does any one know of the pathway an adsl2+ signal takes from the exchange to the ISP? Is there a common pathway to the RAS and home gateway or is it different than adsl max

[Rik]

AFAIK, it's different, Steve.

[Mohux_Jnr]

 Maybe we should start a highest ping competition to lighten the mood. Here's my contribution from 4pm today.



[attachment deleted by admin]