Pings

AvengerUK · Sep 14, 2006, 18:45:48

same, although after a few mins of normal i get a few mins of bad.....weird

maxping · Sep 14, 2006, 18:54:49

Quote from: AvengerUK on Sep 14, 2006, 18:07:33
Currently on CSS, my average ping atm is 101ms

Edit: Now 150ms and no reply from idnet - and when we thought it was fixed...it aint..........

i make that...2months? (just under i think) - "wahoo"

Avenger have you tried the usual stuff, run a line directly to the unfiltered master socket from the modem.

I cannot understand why you have high pings and switching the router off for 30 mins doesn't fix it , its always worked for me.

I also don't pay much attention to the L8nc
reports as i have just checked mine and i see lots of the blue lines yet my pings have been fine and I'm running them every few mins to check against the sites graphs.

AvengerUK · Sep 14, 2006, 19:17:32

Yes ive tried a direct connection and all that. Remeber that this is also a new router

- and other users are getting the same aswell :/

ive also been checking l8nc alongside traces and pings...and the traces and pings show it to be worse than l8nc tends to show!!!!!

karvala · Sep 14, 2006, 19:30:02

Some blue spikes in a l8c graph are fine; you'd expect them from normal usage. You'd also expect to increases in green and yellow during periods of heavy usage. What you would *not* expect to see, unless there was major congestion or another type of problem, would be significant increases in green and yellow while the connection is not even in use. That's what I see, and they certainly correspond to periods in which pings and traces show high latency.

In addition, I've been doing (at Miriam's request) inward and outward traces, and inward and outward pings (from various other UK servers to which I have access), as well as monitoring line stats (which are always fine), during periods of high pings, and the inward and outward high latencies always coincide, not surprisingly, so the l8c graph, while not perfect, is a reasonable measure, and supported by the other evidence.

Incidentally, I've just done a couple of tests at BBR. My transfer efficiency was rated at 100%, as I'd expect (having done it before and made sure all the settings are optimised). The line status test, however, showed some packet loss on the IDNet network: results can be seen here. Is anyone who isn't experiencing this problem also seeing this, i.e. is this significant or not (hard to tell without firm evidence from elsewhere)?

maxping · Sep 14, 2006, 19:36:31

Quote from: AvengerUK on Sep 14, 2006, 19:17:32
Remeber that this is also a new router - and other users are getting the same aswell

If you think it may be the router i have one of these and it works fine - http://cgi.ebay.co.uk/TRUST-External-Modem-Router-with-Firewall-445A_W0QQitemZ170028268361QQihZ007QQcategoryZ3692QQssPageNameZWDVWQQrdZ1QQcmdZViewItem

AvengerUK · Sep 14, 2006, 19:41:08

Quote from: maxping on Sep 14, 2006, 19:36:31
Quote from: AvengerUK on Sep 14, 2006, 19:17:32
Remeber that this is also a new router - and other users are getting the same aswell

If you think it may be the router i have one of these and it works fine - http://cgi.ebay.co.uk/TRUST-External-Modem-Router-with-Firewall-445A_W0QQitemZ170028268361QQihZ007QQcategoryZ3692QQssPageNameZWDVWQQrdZ1QQcmdZViewItem

you misunderstood me

my old router did it, my other old router did it, my old old router did it, and so does my new one....

karvala · Sep 14, 2006, 19:46:07

...And so does my router, and so does my USB modem....

maxping · Sep 14, 2006, 19:48:41

4 routers that must be a record

I said in one of the threads i didn't see how one router could be better than another as surely they all do the same thing.

BTW when i had my ping issues my usb modem gave the same results as my router.

AvengerUK · Sep 14, 2006, 19:49:30

Quote from: karvala on Sep 14, 2006, 19:30:02
Some blue spikes in a l8c graph are fine; you'd expect them from normal usage. You'd also expect to increases in green and yellow during periods of heavy usage. What you would *not* expect to see, unless there was major congestion or another type of problem, would be significant increases in green and yellow while the connection is not even in use. That's what I see, and they certainly correspond to periods in which pings and traces show high latency.

In addition, I've been doing (at Miriam's request) inward and outward traces, and inward and outward pings (from various other UK servers to which I have access), as well as monitoring line stats (which are always fine), during periods of high pings, and the inward and outward high latencies always coincide, not surprisingly, so the l8c graph, while not perfect, is a reasonable measure, and supported by the other evidence.

Incidentally, I've just done a couple of tests at BBR. My transfer efficiency was rated at 100%, as I'd expect (having done it before and made sure all the settings are optimised). The line status test, however, showed some packet loss on the IDNet network: results can be seen here. Is anyone who isn't experiencing this problem also seeing this, i.e. is this significant or not (hard to tell without firm evidence from elsewhere)?

http://www.dslreports.com/quality/nil/2090082

karvala · Sep 14, 2006, 22:49:39

Hmm, so we have the same BBR line results as well. I wonder if people who haven't got the ping problem would get these as well?

One more thing I noticed tonight is shown clearly in our l8c graphs, which I've stuck together here:

You can see that the first really bad part when I came online, and even the little bit that follows it, has an almost identical shape for both of us, even though we're obviously using completely different connections. It's pretty clear that the cause of that problem was nothing particular to our individual connections, but something higher up the network that caused the same problem for both of us.

AvengerUK · Sep 15, 2006, 09:01:25

Quote from: karvala on Sep 14, 2006, 22:49:39
Hmm, so we have the same BBR line results as well. I wonder if people who haven't got the ping problem would get these as well?

One more thing I noticed tonight is shown clearly in our l8c graphs, which I've stuck together here: You can see that the first really bad part when I came online, and even the little bit that follows it, has an almost identical shape for both of us, even though we're obviously using completely different connections. It's pretty clear that the cause of that problem was nothing particular to our individual connections, but something higher up the network that caused the same problem for both of us.

Yep, over the weekend i plan to set up some more tests from a off-network server - just to have something to back l8nc up

AvengerUK · Sep 15, 2006, 11:07:08

My interent has just come back up. L8nc seems to be lagging behind tho...(time wise) so i estimate it went down at 9 and came back up at 10:50.
However, see my l8nc graph:

http://www.l8nc.com/graph.php?jid=58e61f6e3d3d258ec640ec3f21295d2e

pings!!!

- its gone from badish, to good, to bad, to good, and to utterly unbarable!

Im still awaiting a reply to a email i sent IDnet yesterday about the pings, although i expect no progress to be made.

Is it that time again? (mac time) - I mean, i dont mean to moan sooo much about this, but, it does effect my use of the connection and is totally inconvient, especially since its been ongoing since..the end of july......

equk · Sep 15, 2006, 11:52:53

hmm new router and still getting the 100+ms ping to the gateway address

Code Select

traceroute to www.idnet.net (212.69.36.10), 30 hops max, 40 byte packets
 1  cisco (192.168.1.1)  1.301 ms  0.669 ms  0.655 ms
 2  192.168.0.1 (192.168.0.1)  3.205 ms  2.766 ms  3.110 ms
 3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  149.630 ms  127.191 ms  134.532 ms
 4  telehouse-gw-bb.idnet.net (212.69.63.9)  124.485 ms  143.708 ms  148.047 ms
 5  redbus-gw.idnet.net (212.69.63.1)  147.697 ms  144.530 ms  143.868 ms
 6  www.idnet.net (212.69.36.10)  166.834 ms  165.507 ms  149.548 ms

Guess it wasn't my old router causing the problems

Rolacka · Sep 15, 2006, 12:10:05

Pings to the gateway today are abysmal , can't see any point in staying now tbh , I use this connection for gaming & it quite clearly isnt up to the task.

Pinging 212.69.63.40 with 32 bytes of data:

Reply from 212.69.63.40: bytes=32 time=123ms TTL=253
Reply from 212.69.63.40: bytes=32 time=161ms TTL=253
Reply from 212.69.63.40: bytes=32 time=153ms TTL=253
Reply from 212.69.63.40: bytes=32 time=165ms TTL=253
Reply from 212.69.63.40: bytes=32 time=133ms TTL=253
Reply from 212.69.63.40: bytes=32 time=154ms TTL=253
Reply from 212.69.63.40: bytes=32 time=154ms TTL=253
Reply from 212.69.63.40: bytes=32 time=163ms TTL=253
Reply from 212.69.63.40: bytes=32 time=168ms TTL=253
Reply from 212.69.63.40: bytes=32 time=163ms TTL=253
Reply from 212.69.63.40: bytes=32 time=150ms TTL=253
Reply from 212.69.63.40: bytes=32 time=167ms TTL=253
Reply from 212.69.63.40: bytes=32 time=149ms TTL=253
Reply from 212.69.63.40: bytes=32 time=160ms TTL=253
Reply from 212.69.63.40: bytes=32 time=166ms TTL=253
Reply from 212.69.63.40: bytes=32 time=140ms TTL=253
Reply from 212.69.63.40: bytes=32 time=163ms TTL=253
Reply from 212.69.63.40: bytes=32 time=153ms TTL=253

Ping statistics for 212.69.63.40:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 123ms, Maximum = 168ms, Average = 154ms
Control-C
^C

equk · Sep 15, 2006, 12:15:04

Quote from: Rolacka on Sep 15, 2006, 12:10:05
Pings to the gateway today are abysmal , can't see any point in staying now tbh , I use this connection for gaming & it quite clearly isnt up to the task.

Pinging 212.69.63.40 with 32 bytes of data:

Reply from 212.69.63.40: bytes=32 time=123ms TTL=253
Reply from 212.69.63.40: bytes=32 time=161ms TTL=253
Reply from 212.69.63.40: bytes=32 time=153ms TTL=253
Reply from 212.69.63.40: bytes=32 time=165ms TTL=253
Reply from 212.69.63.40: bytes=32 time=133ms TTL=253
Reply from 212.69.63.40: bytes=32 time=154ms TTL=253
Reply from 212.69.63.40: bytes=32 time=154ms TTL=253
Reply from 212.69.63.40: bytes=32 time=163ms TTL=253
Reply from 212.69.63.40: bytes=32 time=168ms TTL=253
Reply from 212.69.63.40: bytes=32 time=163ms TTL=253
Reply from 212.69.63.40: bytes=32 time=150ms TTL=253
Reply from 212.69.63.40: bytes=32 time=167ms TTL=253
Reply from 212.69.63.40: bytes=32 time=149ms TTL=253
Reply from 212.69.63.40: bytes=32 time=160ms TTL=253
Reply from 212.69.63.40: bytes=32 time=166ms TTL=253
Reply from 212.69.63.40: bytes=32 time=140ms TTL=253
Reply from 212.69.63.40: bytes=32 time=163ms TTL=253
Reply from 212.69.63.40: bytes=32 time=153ms TTL=253

Ping statistics for 212.69.63.40:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 123ms, Maximum = 168ms, Average = 154ms
Control-C
^C

Same here, idnet were saying it was my line or exchange. I guess that can't be true as 2 of us are having the same problems at the same time.

Was the same with Danni the other day, both of us had 100+ms ping to the gateway at the same time

equk · Sep 15, 2006, 12:18:24

Also looking at my l8nc graph and AvengerUK's they look exactly the same, with pings going high on both at 10:30 and packet loss/timeouts at the exact same time.
co-incidence?

Rolacka · Sep 15, 2006, 12:19:28

You can see if it is your exchange easily by logging into the bt test & pinging off that , which I'm sure you will find as I did that u ping 12 - 15 ms without fluctuation. The problem is during peak time IDnet is unsuitable as a gaming isp

login to bt_test@startup_domain
leave existing password, as no pw required.

reboot router, when connected check the router's gateway, probably a 217.47.***.** IP or something similar?

That will be your BT RAS, so try pinging that.

equk · Sep 15, 2006, 12:24:05

Yer I did that a while ago when I had these ping problems to gateway and as you say the ping to the BT gateway is about 16ms

Shame the ping 'fix' was only for a week or two

and in that time a few of us found the connections seemed to be capped down at busy times of the day

probably to keep the pipe's bandwidth down in order to keep the pings constant

AvengerUK · Sep 15, 2006, 12:35:07

ive already made a post @ ADSL GUIDE in the search for a new ISP - its a great shame that the problems cant be sorted

maxping · Sep 15, 2006, 12:38:03

Quote from: Rolacka on Sep 15, 2006, 12:10:05
I use this connection for gaming & it quite clearly isn't up to the task.

I have just read your previous posts from your profile and of the 4 ping results you have posted 2 are fine.

Have you called customer support ?

If yes what did they say?

I am as guilty as the next man for using the forum to have a moan but at least i was dealing with customer support at the time and it was BT that were causing the problem.

To say your connection isn't up to the job isn't exactly true as you can get good and bad results.

maxping · Sep 15, 2006, 12:42:24

Quote from: AvengerUK on Sep 15, 2006, 12:35:07
ive already made a post @ ADSL GUIDE in the search for a new ISP - its a great shame that the problems cant be sorted

If it was IDNet causing the slow pings why can i get the results below at 12:41 ?

Pinging www.bbc.co.uk with 32 bytes of data:
Reply from 212.58.224.84 bytes:32 Time:30ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:30ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:32ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:30ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:29ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:28ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:29ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:35ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:68ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:29ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:29ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:28ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:30ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:30ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:29ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:28ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:28ms TTL:249
Reply from 212.58.224.84 bytes:32 Time:28ms TTL:249
Reply from 212.58.227.79 bytes:32 Time:61ms TTL:248
Reply from 212.58.227.79 bytes:32 Time:28ms TTL:248
Reply from 212.58.227.79 bytes:32 Time:29ms TTL:248
Reply from 212.58.227.79 bytes:32 Time:29ms TTL:248
Reply from 212.58.227.79 bytes:32 Time:29ms TTL:248
Reply from 212.58.227.79 bytes:32 Time:30ms TTL:248
Reply from 212.58.227.79 bytes:32 Time:30ms TTL:248
Reply from 212.58.227.79 bytes:32 Time:37ms TTL:248
Reply from 212.58.227.79 bytes:32 Time:28ms TTL:248
Reply from 212.58.227.79 bytes:32 Time:30ms TTL:248
Reply from 212.58.227.79 bytes:32 Time:29ms TTL:248
Reply from 212.58.227.79 bytes:32 Time:29ms TTL:248
Ping statistics for www.bbc.co.uk :
Packets: Sent = 30, Received = 30, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 68ms, Average = 32ms

Rolacka · Sep 15, 2006, 12:47:59

Well if its my line how can i ping this to the bt gateway & ping the above to the IDnet gateway ?

Pinging 217.47.73.142 with 32 bytes of data:

Reply from 217.47.73.142: bytes=32 time=11ms TTL=254
Reply from 217.47.73.142: bytes=32 time=12ms TTL=254
Reply from 217.47.73.142: bytes=32 time=12ms TTL=254
Reply from 217.47.73.142: bytes=32 time=12ms TTL=254
Reply from 217.47.73.142: bytes=32 time=11ms TTL=254
Reply from 217.47.73.142: bytes=32 time=12ms TTL=254
Reply from 217.47.73.142: bytes=32 time=11ms TTL=254
Reply from 217.47.73.142: bytes=32 time=13ms TTL=254
Reply from 217.47.73.142: bytes=32 time=12ms TTL=254
Reply from 217.47.73.142: bytes=32 time=11ms TTL=254
Reply from 217.47.73.142: bytes=32 time=12ms TTL=254
Reply from 217.47.73.142: bytes=32 time=12ms TTL=254
Reply from 217.47.73.142: bytes=32 time=11ms TTL=254
Reply from 217.47.73.142: bytes=32 time=11ms TTL=254
Reply from 217.47.73.142: bytes=32 time=12ms TTL=254
Reply from 217.47.73.142: bytes=32 time=11ms TTL=254
Reply from 217.47.73.142: bytes=32 time=12ms TTL=254
Reply from 217.47.73.142: bytes=32 time=12ms TTL=254
Reply from 217.47.73.142: bytes=32 time=11ms TTL=254

Ping statistics for 217.47.73.142:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 13ms, Average = 11ms
Control-C

AvengerUK · Sep 15, 2006, 12:54:58

Max - some people have the problem, others dont. your one of the 'others' - and i also ping to the bt gateway fine. Idnet problem. for sure.

And i emailed IDnet, not rang...over the phone its difficult to send screenshots and alike

- still no reply to that though, and it was yesterday ~ 5pm i sent it.

Can someone tell me if theres a 30 days notice or anything like that? ie, my billing data is around the 26th...if i left before that...would i pay again orrrr?

maxping · Sep 15, 2006, 13:02:13

Quote

And i emailed IDnet, not rang...over the phone its difficult to send screenshots and alike - still no reply to that though, and it was yesterday ~ 5pm i sent it.

I'm not taking sides but you emailed them at 5 and are now moaning you didn't get a reply, the office would have been about to close and your email is probably in a line of emails , when i was with F2S you were lucky to get a reply in 3 days,i have always had prompt replies i would have given them until the end of the day or i would have phoned them to ask why it had not been replied to.

karvala · Sep 15, 2006, 13:05:09

Quote from: AvengerUK on Sep 15, 2006, 12:54:58
Max - some people have the problem, others dont. your one of the 'others' - and i also ping to the bt gateway fine. Idnet problem. for sure.

And i emailed IDnet, not rang...over the phone its difficult to send screenshots and alike - still no reply to that though, and it was yesterday ~ 5pm i sent it.

Can someone tell me if theres a 30 days notice or anything like that? ie, my billing data is around the 26th...if i left before that...would i pay again orrrr?

I should have said earlier, I had a nice phonecall from Miriam yesterday, who said they've been very busy over the last couple of weeks, so what she's planning on doing is looking at the ping problem during this coming weekend when there won't be a lot of phonecalls to interrupt it, and let us know on Monday what the situation is, so it might be worth hanging on until then.