High pings again

[Aaron]

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
  0  coreduo [192.168.0.10]
  1  192.168.0.1
  2  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6  www.idnet.net [212.69.36.10]

Computing statistics for 150 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           coreduo [192.168.0.10]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                0/ 100 =  0%   |
  2  178ms     0/ 100 =  0%     0/ 100 =  0%  telehouse-gw2-lo2.idnet.net [212.69.63.55]
                                0/ 100 =  0%   |
  3  172ms     1/ 100 =  1%     1/ 100 =  1%  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
                                0/ 100 =  0%   |
  4  163ms     1/ 100 =  1%     1/ 100 =  1%  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
                                0/ 100 =  0%   |
  5  157ms     0/ 100 =  0%     0/ 100 =  0%  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
                                0/ 100 =  0%   |
  6  154ms     0/ 100 =  0%     0/ 100 =  0%  www.idnet.net [212.69.36.10]

Trace complete.

These high pings this and last week at random is getting a bit silly, not willing to reboot router either otherwise i get sync'd at a higher data rate which will make it drop near midnight again.

[gwidnet]

Pings high again here 

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=162ms TTL=59
Reply from 212.69.36.10: bytes=32 time=153ms TTL=59
Reply from 212.69.36.10: bytes=32 time=183ms TTL=59
Reply from 212.69.36.10: bytes=32 time=174ms 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 = 153ms, Maximum = 183ms, Average = 168ms

They are exactly like the pings I'm getting at the moment. I had a spare router, which I just connected, with no other attached devices, and the pings were all between 120 and 170. That rules out anything to do with my router or network I think. I've just emailed support again.

[dujas]

not willing to reboot router either otherwise i get sync'd at a higher data rate which will make it drop near midnight again.

You don't need to reboot, in your router's web configuration menus there should be the option to manually disconnect/connect your ISP connection i.e. PPPoA, this should achieve the same result.

[Dopamine]

Back to normal high pings again:

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

Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=147ms TTL=59
Reply from 212.69.36.10: bytes=32 time=172ms TTL=59
Reply from 212.69.36.10: bytes=32 time=151ms TTL=59


Disconnected then immediately reconnected ISP connection, and returned to proper pings:

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

Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59

Clearly nothing has been remedied at all.

I need to make a decision as to whether to move ISP or not, so can someone speculate as to whether this gradual increase in pings, and consequent browsing sluggishness, is indicative of ISP congestion, or something else.

[Simon]

All we know is what we are told, which is that the network is now rebalanced and there is no congestion.  We can only suggest that you follow the diagnostics in the sticky and send them to support, or if you feel that another ISP would be better, request your MAC.

[MarkE]

Back to normal high pings again:

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

Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=147ms TTL=59
Reply from 212.69.36.10: bytes=32 time=172ms TTL=59
Reply from 212.69.36.10: bytes=32 time=151ms TTL=59


Disconnected then immediately reconnected ISP connection, and returned to proper pings:

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

Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59

Clearly nothing has been remedied at all.

I need to make a decision as to whether to move ISP or not, so can someone speculate as to whether this gradual increase in pings, and consequent browsing sluggishness, is indicative of ISP congestion, or something else.

Personally i would move.

As these problems which were the same the last time i left idnet and they said the same to me then about it being my exchange,when as soon as i moved all was fine.I suggest you do as I am and try another isp with 1 month contract only.

My ping time is utter pish also as usual.



Pinging multiplay.co.uk [85.236.96.22] with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=141ms TTL=124
Reply from 85.236.96.22: bytes=32 time=172ms TTL=124
Reply from 85.236.96.22: bytes=32 time=103ms TTL=124
Reply from 85.236.96.22: bytes=32 time=78ms TTL=124



I some how will not be recommending Idnet to anyone 

[mynnydd]

Just for the record my pings are back to the normal levels.
I hope everyone else gets sorted soon.

[dujas]

I need to make a decision as to whether to move ISP or not, so can someone speculate as to whether this gradual increase in pings, and consequent browsing sluggishness, is indicative of ISP congestion, or something else.

Have support given any reasons for why they think the fault still persists for you? Are download speeds also affected? Switching ISPs would seem the obvious next step to finding a permanent fix (it would at least rule out exchange congestion at least).

[gwidnet]

I'm not sure what has happened overnight but my pings are very stable and back to normal this morning


PING www.idnet.net (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=14.201 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=13.169 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=14.492 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=12.514 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=12.826 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=11.830 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=13.251 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=14.682 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=12.797 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=11.992 ms
64 bytes from 212.69.36.10: icmp_seq=10 ttl=59 time=12.821 ms
64 bytes from 212.69.36.10: icmp_seq=11 ttl=59 time=13.919 ms


Let's hope whatever the problem was is resolved, and others get it sorted as well.

[Simon]

 

[Dopamine]

Have support given any reasons for why they think the fault still persists for you? Are download speeds also affected? Switching ISPs would seem the obvious next step to finding a permanent fix (it would at least rule out exchange congestion at least).

I called support this afternoon, who would investigate and call me back. The call back didn't happen though (no surprise there) so I've no idea if they know the reason.

Download speeds are acceptable, high pings can be rectified by disconnecting from IDNet and reconnecting, and then usually over time they get progressively worse, although since my last reconnect at 3pm ish they've stayed at 13ms average, which is excellent. I think the fact that I don't disconnect from the exchange rules out exchange congestion.

My problem when pings are high is that browsing seems a bit sluggish to find pages. If that could be solved, I'd be content.

[wecpcs]

Just for the record my pings are back to the normal levels.
I hope everyone else gets sorted soon.

So are mine and have been for several weeks now. 

Colin

[Simon]

I called support this afternoon, who would investigate and call me back. The call back didn't happen though (no surprise there) so I've no idea if they know the reason.

Did they say they'd definitely call back this afternoon?  Maybe they are still investigating?

[DarkStar]

My pings fluctuate a bit, sometimes steady around 35-45 sometimes a bit higher but they have gone wild this evening may run the test in safe mode tomorrow and contact support


[attachment deleted by admin]

[Dopamine]

Did they say they'd definitely call back this afternoon?  Maybe they are still investigating?

A female from support mentioned something about checking network congestion, then said that she'd have to call me back as she couldn't access some system or other. It was my assumption that it would be today, as the call was very brief and no checks were carried out whilst I was on the phone - or at least none that I was aware of.

When I first joined IDNet, support calls were dealt with very well. Now, my impression is that the staff remain willing and knowledgeable, but are swamped. But who knows what the real situation is any longer? ISPs are messed about by BT, some ISPs are also under-resourced and/or over-sold, BT blames ISPs unfairly, ISPs blame BT unfairly, the wind is blowing from the east and it's raining in Lothian.... it could be any or all of these things, and the consumer is the one that suffers.

All I want is a decent connection without needing to become a self taught internet engineer, yet I remain unconvinced that there are many, or any, ISPs that are better than IDNet, so see little point in moving; as I've said before, I think the whole industry needs to raise its standards. Can you imagine the public outcry if our electricity or water services were as flaky as our internet connections, or our TV signals kept breaking up or misbehaving?

The good news is that since my last post my pings have remained low and I've had no browsing problems, so that will do for me.

[karser]

Just got my migration date to Aquiss for the 12th, I'll let you know how it goes.

[Simon]

Please do. 

[MarkE]

I am now with aquiss,interleaving is not off yet but pings are superb compared to previous


Pinging multiplay.co.uk [85.236.96.22] with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=19ms TTL=123
Reply from 85.236.96.22: bytes=32 time=18ms TTL=123
Reply from 85.236.96.22: bytes=32 time=19ms TTL=123
Reply from 85.236.96.22: bytes=32 time=18ms TTL=123

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

Reply from 212.69.36.10: bytes=32 time=19ms TTL=56
Reply from 212.69.36.10: bytes=32 time=19ms TTL=56
Reply from 212.69.36.10: bytes=32 time=19ms TTL=56
Reply from 212.69.36.10: bytes=32 time=19ms TTL=56

[Rik]

How about throughput Mark?

[MarkE]

How about throughput Mark?

well only ran a speedtest.io Rik

Results from http://www.speed.io
(Copied on 2009-08-05 16:45:13)
Download: 6423 Kbit/s
Upload : 757 kbit/s
Connects : 2723 conn/min
Ping: 23 ms

[Rik]

Is that better or worse?

[MarkE]

Is that better or worse?

actually Rik let me test on the other speed site where my original idnet results are doh 

[MarkE]

Ok  on two occasions previous on the 7/6/2009 and 7/4/2009 tests run with idnet were 6.34mb/s

So its a little bit higher with Aquiss for now,but not much in it,but the main point here being the ping times are now nice even with interleaving on

[Rik]

I'm glad it's worked for you, Mark, I'd welcome a long term appraisal from you.

[MarkE]

I'm glad it's worked for you, Mark, I'd welcome a long term appraisal from you.

Rik I will keep updating with info of how things go with Aquiss,as we both know an isp is not something that can really be judged over the first day of its relationship with the customer