High pings again

Gary · Jul 20, 2009, 12:58:10

Quote from: Rik on Jul 20, 2009, 12:56:09
Reasonable overall but some big spikes, Gary. Coupled with the tracerts, it makes you wonder if there's a router which is a bit busy?

I was wondering, mostly its ok but one loss of packet and a few high spikes, will have to keep an eye on it

Gary · Jul 20, 2009, 12:59:21

Quote from: Simon on Jul 20, 2009, 12:57:21
I've sent mine to support - awaiting a response.

within parameters I bet

Simon · Jul 20, 2009, 13:02:23

"This is perfectly normal, the important thing is the last hop on the route. The "times" of the hops in the middle are irrelevant as they are routers rather than servers."

I can't actually complain, as my connection seems as good as ever, since I've rebooted the router.

trophymick · Jul 20, 2009, 13:17:06

My pings went haywire this morning, also the speed dropped.

I give the router a 30 minute break and it seems OK now.

I'm on gw5.

Rapier Racer · Jul 20, 2009, 14:06:48

Think I'll try the 30 minute break, rebooting and power cycling aren't doing much for me.

lol @ that smiley

glen · Jul 20, 2009, 16:31:51

My pings are still the same. Sent a few stats over to IDnet, so they might have an idea whats going on. On gw5 by the way.

Fox · Jul 20, 2009, 17:06:58

Same problem here (also on GW5)

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=92ms TTL=59
Reply from 212.69.36.10: bytes=32 time=119ms TTL=59
Reply from 212.69.36.10: bytes=32 time=145ms TTL=59
Reply from 212.69.36.10: bytes=32 time=141ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms TTL=59
Reply from 212.69.36.10: bytes=32 time=131ms TTL=59
Reply from 212.69.36.10: bytes=32 time=181ms TTL=59
Reply from 212.69.36.10: bytes=32 time=165ms TTL=59
Reply from 212.69.36.10: bytes=32 time=150ms TTL=59
Reply from 212.69.36.10: bytes=32 time=152ms TTL=59
Reply from 212.69.36.10: bytes=32 time=86ms TTL=59
Reply from 212.69.36.10: bytes=32 time=120ms TTL=59
Reply from 212.69.36.10: bytes=32 time=122ms TTL=59
Reply from 212.69.36.10: bytes=32 time=126ms TTL=59
Reply from 212.69.36.10: bytes=32 time=118ms TTL=59
Reply from 212.69.36.10: bytes=32 time=102ms TTL=59
Reply from 212.69.36.10: bytes=32 time=120ms TTL=59
Reply from 212.69.36.10: bytes=32 time=146ms TTL=59
Reply from 212.69.36.10: bytes=32 time=140ms TTL=59
Reply from 212.69.36.10: bytes=32 time=148ms 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 = 86ms, Maximum = 181ms, Average = 132ms

Rapier Racer · Jul 20, 2009, 17:36:49

Have you guys tried the 30 minute power down? I was experiencing the same high pings this afternoon (also on gw5) after keeping the router off for about 45 mins they are now down to 40ms average from 180.

I hope it lasts.

Fox · Jul 20, 2009, 18:00:45

Quote from: Rapier Racer on Jul 20, 2009, 17:36:49
I hope it lasts.

It probably wont.

From what I have seen powering down or rebooting the router only reduces the latency for a period of time. I have rebooted my router myself a few times and also I have had IDNet reset it from their end too a couple of times. Each time my ping goes back to "normal" levels only to rise back up after a period of time. I have never had a problem with high latency up until about a month ago, nothing has changed at my end regarding hardware connected to line, my line stats are the same as they always have been too. We were told that Wimbledon was to blame, then it was a fault with one of IDNets centrals. Well Wimbledon is over and as far as I am aware the central is fixed and still the problem of high latency is there for many users.

IDNet needs to get this sorted or people will just go to another ISP

dujas · Jul 20, 2009, 18:01:20

Perhaps it's the golf and/or cricket this time?

Fox · Jul 20, 2009, 18:10:22

Perhaps it is, but my neighbours (on is on talktalk and the other is on AOL...neither is regarded as one of the better ISP's) are not having any problems

Rik · Jul 20, 2009, 18:13:57

IDNet have a lot of business customers, and noticed that the effects on their network were only happening during office hours, ie it was people watching sport from the office. I'm surprised employers haven't cottoned on to this loss in productivity.

Fox · Jul 20, 2009, 18:16:17

So what IDNet are say is that your internet connection will be ok as long as you dont actually use it for anything other than web browsing and email?

It looks like they have simply run out of capacity

Rik · Jul 20, 2009, 18:20:26

What I am saying is that their capacity is tested if a large number of users max out their connections simultaneously. No ISP that I know of has sufficient capacity for all their customers to do that. It can be achieved, of course, but at a much higher cost than now, probably at least double. In addition, BT's backhaul can be an issue in some areas. The move to WBC will help, as an ISP is able to add capacity quickly and, relatively, easily. IDNet will be hoping that they will have been able to move the majority of their customers to WBC before events like the World Cup and the Olympics.

quandam · Jul 20, 2009, 18:35:28

Rik

Have done several speed tests (various) this afternoon and speeds are only 'average' or below. Things tick over OK but certainly not up to the usual standard we expect from IDNet, there is something that is not quite right, I would expect a slightly below 'average' speed after 5pm but the below average speeds are during the day time hours.

I would say that for 'normal' usage it is quite acceptable but if someone who requires a little more i.e gaming etc there may be a problem.

On gw5 by the way.

Rik · Jul 20, 2009, 18:38:02

Have you talked to support at all, Q? One thing which may be affecting daytime patterns now are the school holidays. My speeds remain consistent, but then I am on WBC.

Fox · Jul 20, 2009, 19:02:36

My ping after yet another router reboot at 5.30ish pm today

C:\Users\Fox>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=40ms TTL=59
Reply from 212.69.36.10: bytes=32 time=57ms TTL=59
Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=55ms 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 = 40ms, Maximum = 57ms, Average = 48ms

My ping now 7pm.......

C:\Users\Fox>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=140ms TTL=59
Reply from 212.69.36.10: bytes=32 time=185ms TTL=59
Reply from 212.69.36.10: bytes=32 time=91ms TTL=59
Reply from 212.69.36.10: bytes=32 time=118ms 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 = 91ms, Maximum = 185ms, Average = 133ms

I guess I will ringing for my MAC code in the morning and looking for another ISP

Rik · Jul 20, 2009, 19:03:42

Let us know how you get on. Have you got a shortlist yet?

Gary · Jul 20, 2009, 19:06:01

TBH I was just looking over at Think BB and Zen seem to be having the same issues as IDnet

maybe BT are just reaching the predicted saturation point, I see people with the same issues as us there.

Gary · Jul 20, 2009, 19:10:47

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

Mine seem fine as of now, I do think considering that BT products seem to have issues with other providers like Zen, who had the same problems with load balancing at Wimbledon time, and strange loss of throughput, that unless you find a LLU provider like Be, you are going to get the same everywhere using the BT network

Fox · Jul 20, 2009, 19:21:47

Quote from: Rik on Jul 20, 2009, 19:03:42
Let us know how you get on. Have you got a shortlist yet?

I was thinking of trying Newnet or Andrews and Arnold (AAISP)

Gary · Jul 20, 2009, 19:23:11

Quote from: Fox on Jul 20, 2009, 19:21:47
I was thinking of trying Newnet or Andrews and Arnold (AAISP)

I would go LLU if you can tbh Be are much better, I was on O2/Be LLu I only came back to IDNet as there is no LLU with Be here at my exchange when I moved

quandam · Jul 20, 2009, 19:23:36

Quote from: Rik on Jul 20, 2009, 18:38:02
Have you talked to support at all, Q? One thing which may be affecting daytime patterns now are the school holidays. My speeds remain consistent, but then I am on WBC.

As you may remember Rik, I did contact support and we communicated the subject by PM

quandam · Jul 20, 2009, 19:29:32

Quote from: Fox on Jul 20, 2009, 19:21:47
I was thinking of trying Newnet or Andrews and Arnold (AAISP)

Fox

NewNet is very similar to IDNet, Andrews & Arnold very exclusive & expensive. My brother in law who loves anything 'exclusive' has ditched A&A for O2 (LLU) and so far is happy. In the end, your choice. Frying pan/fire springs to mind here.

Fox · Jul 20, 2009, 19:33:01

Quote from: Gary on Jul 20, 2009, 19:23:11
I would go LLU if you can tbh Be are much better, I was on O2/Be LLu I only came back to IDNet as there is no LLU with Be here at my exchange when I moved

Unfortunately there are no LLU operators on my exchange (Rawcliffe) so I am looking for an ISP with no traffic shaping/port blocking and Newnet or AAISP seem to fit my needs (I do quite a bit of online gaming so low latency is important to me)