Ping problems on gw5/adsl max location poll

[Gary]

Just got on the net, my router has been off overnight:

C:\Documents and Settings\Karser>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=168ms TTL=59
Reply from 212.69.36.10: bytes=32 time=174ms TTL=59
Reply from 212.69.36.10: bytes=32 time=161ms TTL=59
Reply from 212.69.36.10: bytes=32 time=136ms 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 = 136ms, Maximum = 174ms, Average = 159ms

Waiting for a reply on the email I sent friday with more tests, if they arent prepared to at least try to switch me to a different gw, even if its just to prove me wrong about it being all gw5 & max, after I've already asked twice if they will move me, then its time to ask for my mac code I think.

I think its now on a round robin so you may not be strictly on gw5 anyway, Rik will tell me if I am wrong with this  

[Rik]

That's right, Gary. GW5 just identifies the realm, it no longer determines which central you are connected to. (I'm on GW5 on WBC, for example.)

[Lance]

Hi Pete - I'm north east essex too but with no problems.

I'm connected to the Highwoods exchange.

[Gary]

This is getting really bad now 

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=202ms TTL=59
Reply from 212.69.36.10: bytes=32 time=226ms TTL=59
Reply from 212.69.36.10: bytes=32 time=252ms TTL=59
Reply from 212.69.36.10: bytes=32 time=188ms 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 = 188ms, Maximum = 252ms, Average = 217ms

Edit: pages now take ages to load its getting like dialup

[trophymick]

My pings are a bit wild today. Speed seems OK though.

[Rik]

Let support know, people. Only if they can collect enough evidence can they identify a fault.

[karser]

That's right, Gary. GW5 just identifies the realm, it no longer determines which central you are connected to. (I'm on GW5 on WBC, for example.)

That makes it all the stranger that the people that are consistently having problems seem mostly to be gw5 & adsl max

[Rik]

I know, it's what is puzzling us.

[Gary]

Let support know, people. Only if they can collect enough evidence can they identify a fault.

Have just done so Rik 

[JB]

Not good here in Cheshire on GW5 either. There is no exchange contention and I am syncing at the full 8128 kbps with a 12db noise margin and no interleaving.

I'm starting to tire a little of this now I'm afraid. I don't see rebooting my router at intervals as being any kind of answer, especially as I rely on things running smoothly here when I am away in Spain for weeks.

To me there does seem to be an ongoing issue which I hope I can sit out for a while longer.

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

Reply from 212.69.36.10: bytes=32 time=173ms TTL=59
Reply from 212.69.36.10: bytes=32 time=131ms TTL=59
Reply from 212.69.36.10: bytes=32 time=155ms TTL=59
Reply from 212.69.36.10: bytes=32 time=110ms TTL=59
Reply from 212.69.36.10: bytes=32 time=90ms TTL=59
Reply from 212.69.36.10: bytes=32 time=128ms TTL=59
Reply from 212.69.36.10: bytes=32 time=175ms TTL=59
Reply from 212.69.36.10: bytes=32 time=124ms TTL=59
Reply from 212.69.36.10: bytes=32 time=173ms TTL=59
Reply from 212.69.36.10: bytes=32 time=122ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms TTL=59
Reply from 212.69.36.10: bytes=32 time=86ms TTL=59
Reply from 212.69.36.10: bytes=32 time=124ms TTL=59
Reply from 212.69.36.10: bytes=32 time=165ms TTL=59
Reply from 212.69.36.10: bytes=32 time=106ms TTL=59

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

[Rik]

Can you let support have those figures, JB.

[EnglishBeef]

I have had to request my MAC code and am in the process of changing over to a new ISP as the pings and throughput are up and down like a yoyo. IDNet seem to have has nothing but problems since I joined them in January 2009. When I emailed them and then phoned them for my MAC they didn't even ask why I was leaving. I can't believe they are saying that there is nothing wrong with their network.

John

[JB]

Can you let support have those figures, JB.

Will do Rik.

[Rik]

I can't believe they are saying that there is nothing wrong with their network.

That's what they tell us, John. Have you decided where you are going? If you feel like it, I'd be grateful if you could do some pings before and after migration and post back here with them. The more evidence, the closer we will get to a solution I believe.

[Glenn]

I have had to request my MAC code and am in the process of changing over to a new ISP as the pings and throughput are up and down like a yoyo. IDNet seem to have has nothing but problems since I joined them in January 2009. When I emailed them and then phoned them for my MAC they didn't even ask why I was leaving. I can't believe they are saying that there is nothing wrong with their network.

John

Post back with your stats once you have moved, it may help those that stay get an improved service.

[wecpcs]

That makes it all the stranger that the people that are consistently having problems seem mostly to be gw5 & adsl max

I am too on gw5 & ads max and my figures have been fine for over 2 weeks now, although I did have a blip last night and was starting to panic only to find one of my friends was downloading from my Windows Home Server. Obviously I realise that the server download would affect my upload which it did, but it also dragged down my download speed from 6.7Mb to just over 1Mb with a ping of 687 (normally 42). In the past when I have been on O2 (Access) and with ZEN, I have had sometimes 2 friends downloading from my server at the same time without affecting my browsing experience, but last night I certainly noticed slow browsing.
I am happy at the moment, but I too am keeping a watchful eye on things as I now have my own domain and email service, so switching ISP's is now painless.

Colin

[Rik]

We've seen a number of cases recently, Colin, where uploads have affected download speed badly.

[EnglishBeef]

I've signed up with AAISP. Should change over on Friday.

Here is some ping data before changing. I'm was on GW6 but was moved a few weeks ago to GW5 because of problems.

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=117ms TTL=59
Reply from 212.69.36.10: bytes=32 time=151ms TTL=59
Reply from 212.69.36.10: bytes=32 time=146ms TTL=59
Reply from 212.69.36.10: bytes=32 time=167ms 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 = 117ms, Maximum = 167ms, Average = 145ms

[Rik]

Thanks. If you wouldn't mind repeating the exercise after migration, Colin, it would be helpful. 

[Gunnar]

Hi Pete - I'm north east essex too but with no problems.

I'm connected to the Highwoods exchange.

Hi Lance, I'm in Kirby Cross on the Frinton-On-Sea Exchange. I only really noticed it last night because the guys said the game seemed to be running quicker than usual ! Probably a one-off blip but I'll check this evening.

[Gunnar]

Hiya,

Well I checked tonight and performed a Router shutdown, pause, startup.
All seems well, stats below:

C:\Documents and Settings\Pete>ping www.idnet.net -n 20

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

Reply from 212.69.36.10: bytes=32 time=10ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=10ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=10ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms 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 = 10ms, Maximum = 15ms, Average = 11ms

C:\Documents and Settings\Pete>tracert www.idnet.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2    16 ms    39 ms    20 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    14 ms    12 ms    12 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    12 ms    12 ms    12 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    20 ms    16 ms    12 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    13 ms    12 ms    13 ms  www.idnet.net [212.69.36.10]

Trace complete.

No mad spikes in the round-trip latency times. So must have just been a blip yesterday evening.

Cheers,
Pete.

[Simon]

Just an uneducated stab in the dark, but I wonder if the problems seem to be with GW5, simply because more people are on it, and that's what needs 'balancing'?   

[karser]

You would think that would affect everyone on gw5 if that were the case, but it seems from the polls that half are fine, & half are having problems. Also someone said when you connect now its a " round robin" as to which pipe you connect to, tho that doesnt seem reflected in where the problem area is.

[Dopamine]

We've seen a number of cases recently, Colin, where uploads have affected download speed badly.

I still have the same problem, and support have been next to useless at dealing with it - my ongoing fault and their efforts to deal with it apparently relegated to the bottom of the pile and forgotten about. In 4 years with Pipex (hardly a gold standard ISP), I needed to contact their support a handful of times. A year and a half with IDNet and I've lost count of the number of times I've needed to chase up ongoing problems. Yet is there actually a better ISP around? I'm not convinced, which is why I haven't asked for my MAC yet. What a shoddy industry the whole ISP business is.

It's such a shame to see an ISP go to pot like this. Whilst I sympathise that some of the problem might be outside of IDNet's network, I have no sympathy whatsoever for an ISP that allows its customer services department to ignore customer problems, either through uselessness or overwork. Expansion of their business should have been met with an adequate expansion of CS, as in today's market, especially at the expensive end of it, CS is the difference between retaining customers and losing them.

[Gary]

Well things look better today 

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 - 6657 kbps

Thats the best I have seen in ages.


Pings look steady for me as well


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=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms 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 = 30ms, Maximum = 30ms, Average = 30ms


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

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

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

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2    30 ms    30 ms    29 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    30 ms    29 ms    30 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    31 ms    30 ms    30 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    30 ms    32 ms    30 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    30 ms    30 ms    30 ms  www.idnet.net [212.69.36.10]

Trace complete.