Re: Pings

[equk]

I reconnected after the last post but after 2minutes it was back up again. Has been 150ms since 12:45 when it disconnected  strange also yesterday the PPP Server went down for 15mins.

Something strange going on going to try re-sync again I guess no wonder the internet has been slow

[Adam]

NOTE: This topic is split off from the "Pings" thread, please continue in this topic. It was split due to the size of the topic.

Thanks much,
Adam

[maxping]

Has been 150ms since 12:45 when it disconnected  strange also yesterday the PPP Server went down for 15mins.

Something strange going on :

I have had a few disconnections today as you can see on the graph below, i sent this to CS but have not had a reply yet. After 15:30 (actually 16:30 a the time is one hour out) it connected and has been fine since.

[maxping]

NOTE: This topic is split off from the "Pings" thread, please continue in this topic. It was split due to the size of the topic.

Thanks much,
Adam

Thanks Adam .

[karvala]

Hmm, well it's a bit patch at the moment, but not too bad:-

Pinging 212.69.58.58 with 32 bytes of data:
Reply from 212.69.58.58 bytes:32 Time:28ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:26ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:23ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:38ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:51ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:56ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:38ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:43ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:56ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:78ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:51ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:37ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:27ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:28ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:22ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:28ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:28ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:25ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:27ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:25ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:24ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:35ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:23ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:27ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:25ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:27ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:32ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:23ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:32ms TTL:47
Reply from 212.69.58.58 bytes:32 Time:39ms TTL:47
Ping statistics for 212.69.58.58 :
Packets: Sent = 30, Received = 30, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 78ms, Average = 34ms

However, the l8nc graph shows clearly that there was  disconnection earlier, followed by an hour and a half of ridiculous pings and major pocket loss, followed by another disconnection and switch to the current borderline situation.  Clearly, the step change between sessions is still present.

[maxping]

Deleted.

[karvala]

Been mostly okay today until the last half hour; currently not looking too good:-

Pinging 212.69.58.58 with 32 bytes of data:
Reply from 212.69.58.58 bytes:32 Time:123ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:113ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:122ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:103ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:132ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:125ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:141ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:129ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:142ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:129ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:160ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:138ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:118ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:106ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:116ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:99ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:140ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:107ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:126ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:95ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:84ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:104ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:97ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:122ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:101ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:123ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:112ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:88ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:74ms TTL:51
Reply from 212.69.58.58 bytes:32 Time:58ms TTL:51
Ping statistics for 212.69.58.58 :
Packets: Sent = 30, Received = 30, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 160ms, Average = 114ms

[equk]

Not sure what is going on but the pings are stupid atm have been for a while. I have re-synced 3 times but it's still the same 

Code Select Expand

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

Request timed out.
Reply from 212.69.36.10: bytes=32 time=182ms TTL=59
Reply from 212.69.36.10: bytes=32 time=140ms TTL=59
Reply from 212.69.36.10: bytes=32 time=127ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 127ms, Maximum = 182ms, Average = 149ms

[blacknred]

Just checked.
PING 212.69.36.10 (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=61 time=30.0 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=61 time=30.0 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=61 time=30.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=61 time=30.0 ms

--- 212.69.36.10 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 30.0/30.0/30.0 ms

[maxping]

I have re-synced 3 times but it's still the same 

Have you tried turning the router off for 30 mins?

[cavillas]

Could'nt resist. 

Sending ping request to www.idnet.net [212.69.36.10] with 32 bytes

Answer from 212.69.36.10 : bytes = 32 time = 37 ms   TTL=60
Answer from 212.69.36.10 : bytes = 32 time = 36 ms   TTL=60
Answer from 212.69.36.10 : bytes = 32 time = 35 ms   TTL=60
Answer from 212.69.36.10 : bytes = 32 time = 37 ms   TTL=60

Statistics for 212.69.36.10
   Packets : sent = 4, received = 4, lost = 0 (loss 0%)
Approximative elapsed time in milliseconds
   Minimum = 35 ms, Maximum = 37 ms, Average = 36 ms

[equk]

Code Select Expand

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

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

Getting disconnects to anything outside of the UK now tho, just lost conn to NL and when it came back the routing was suddenly different.

Then it went again

Code Select Expand

Tracing route to quake3-04.xs4all.nl [194.109.69.93]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  cisco [192.168.1.1]
  2     2 ms     2 ms     2 ms  192.168.0.1
  3    27 ms    24 ms    24 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  4    24 ms    24 ms    23 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  5    25 ms    25 ms    23 ms  212.69.63.5
  6     *        *        *     Request timed out.

[Dev]

What the hell is going on with this ISP? I've had constant ping problems ever since I started with them and now tonight the connection is timing out totally and reconnecting every 2 minutes. It's getting pretty rediculous to be quite honest, I'm sure something can be done through Ofcom (used to be Offtel) about this as IDNET are not providing a ADSL service, I'd have better service on a 28k modem.

http://www.ofcom.org.uk/

Might be contacting them as IDNET always blame everything else rather than what the problem is - their Network.

[maxping]

Dev have you spoke to customer support?

Have you tried disconnecting for 30 mins?


If it was IDNet's network as you say wouldn't we all be suffering at the same time?

Heres my pings from a test i did 1 min ago.

Pinging www.idnet.net with 32 bytes of data:

Reply from 212.69.36.10 bytes:32 Time:32ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:26ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:32ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:32ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:29ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:30ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:26ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:29ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:30ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:29ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:26ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:29ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:29ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:29ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:30ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:29ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Ping statistics for www.idnet.net :
Packets: Sent = 30, Received = 30, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 32ms, Average = 28ms

[Dev]

As soon as the line is re-synced it's ok for like 15 mins then goes back to 150 - 200 ping and constant timeouts (apart from tonight it's just disconnecting and timing out constantly - even when a re-sync is done). The support is pointless as they always blame everything else. It's obviously their Network as everything else has been shown to be fine. Maybe it's only in certain areas of the UK - don't know. But I know one thing it's getting pretty rediculous now.

[maxping]

Sign up at the L8NC site and then you can send CS graphs and post them here.

http://www.l8nc.com/index.php

When we had the ping issues there were a few here having them at the same time (see big ping thread) but now most people seem to be ok most of the time , this leads me to think its your exchange and not IDNet but what i know about the inner workings of the Internet could be written on the back of a postage stamp in inch high letters 

[equk]

The routing seems to be changing every 5mins

on 194.109.69.93 1min its going thru sprintlink, the next it's going thru xs4all.

Also goes down every 5mins

[mrapoc]

I keep getting booted off xfire and msn and anything internet wise just slows to a stop and web pages keep timing out!! This is recent, i thought i was in the clear!!! ohhhhhh why?!?!?!

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

Reply from 212.69.36.10: bytes=32 time=129ms TTL=60
Reply from 212.69.36.10: bytes=32 time=118ms TTL=60
Reply from 212.69.36.10: bytes=32 time=123ms TTL=60
Reply from 212.69.36.10: bytes=32 time=157ms TTL=60

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 118ms, Maximum = 157ms, Average = 131ms

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

  1    <1 ms    <1 ms    <1 ms  SpeedTouch.lan [10.0.0.138]
  2   139 ms   124 ms   143 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3   156 ms   157 ms   157 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4     *      127 ms   139 ms  212.69.63.5
  5   155 ms   158 ms   166 ms  www.idnet.net [212.69.36.10]

Trace complete.

Pings on css jumped up to 100 then settled then jumped up again 

[Dev]

Exactly the same here, I was talking to a friend on msn, sent 1 message - got disconnected. When it finally reconnected it disconnected again after 1 message again. Been doing it all night.

[drummer]

I'm being booted off about every 15-20 minutes.  Web pages won't load and IM client disconnects, then after about two minutes, the line reconnects without any intervention from me.

It's been doing it since this afternoon and just happened about ten minutes ago.  Still, my speeds have shot up to an average of 6Mb fom the previous 0.5-2Mb. 

[sobranie]

explanation here perhaps?

http://bbs.adslguide.org.uk/showthreaded.php?Cat=&Board=idnet&Number=2689344&page=0&view=expanded&sb=5&o=0#Post2689344

[maxping]

Hi All

We have noticed instability across the London XchangePoint network so we have shutdown our connection to there for the time being.

Regards
Simon

I have just looked at my L8NC graph and i lost connection from 9 p.m until approx 9:15 , all seems well again now.

[equk]

bah being disconnected to half the world isn't much fun loads of servers and sites not working, or working intermittantly atm 

[equk]

I wanted to download from sourceforge surfnet server aswell tonight but the connection to it doesn't stay up for more than 5-10mins     

[CatMangler]

Pings have been ok for a few days, now :

Reply from 212.69.36.10: bytes=32 time=158ms TTL=60
Reply from 212.69.36.10: bytes=32 time=139ms TTL=60
Reply from 212.69.36.10: bytes=32 time=132ms TTL=60
Reply from 212.69.36.10: bytes=32 time=154ms TTL=60
Reply from 212.69.36.10: bytes=32 time=116ms TTL=60
Reply from 212.69.36.10: bytes=32 time=136ms TTL=60
Reply from 212.69.36.10: bytes=32 time=146ms TTL=60
Reply from 212.69.36.10: bytes=32 time=139ms TTL=60
Reply from 212.69.36.10: bytes=32 time=153ms TTL=60
Reply from 212.69.36.10: bytes=32 time=134ms TTL=60
Reply from 212.69.36.10: bytes=32 time=122ms TTL=60
Reply from 212.69.36.10: bytes=32 time=139ms TTL=60
Reply from 212.69.36.10: bytes=32 time=148ms TTL=60
Reply from 212.69.36.10: bytes=32 time=144ms TTL=60
Reply from 212.69.36.10: bytes=32 time=144ms TTL=60
Reply from 212.69.36.10: bytes=32 time=128ms TTL=60
Reply from 212.69.36.10: bytes=32 time=143ms TTL=60

Ping statistics for 212.69.36.10:
    Packets: Sent = 351, Received = 349, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 161ms, Average = 69ms


I'm gettin totaly frustrated!!

Better start lookin elsewhere...

[maxping]

Ping statistics for 212.69.36.10:
    Packets: Sent = 351, Received = 349, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 161ms, Average = 69ms


I'm gettin totaly frustrated!!

Better start lookin elsewhere...

I still cant understand why when me and avenger and others had constantly high pings we ALL had them at the same time.
You seem to be the only one at the moment which leads me to believe its not IDNEts end, if it were the boards would be full of people posting bad ping results e.t.c.

Heres mine from a few mins ago.,

Pinging www.idnet.net with 32 bytes of data:

Reply from 212.69.36.10 bytes:32 Time:43ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:40ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:32ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:46ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:40ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:40ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:45ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:38ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:26ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:30ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:26ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:29ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:31ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:30ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:29ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:44ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:29ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:37ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:31ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:35ms TTL:60
Ping statistics for www.idnet.net :
Packets: Sent = 30, Received = 30, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 46ms, Average = 33ms



Read - http://www.idnetters.idnet.co.uk/forums/index.php/topic,605.0.html

[TimJ]

I still cant understand why when me and avenger and others had constantly high pings we ALL had them at the same time.
You seem to be the only one at the moment which leads me to believe its not IDNEts end, if it were the boards would be full of people posting bad ping results e.t.c.

No catmangler is not alone. I have 2 lines at different locations and this afternoon both have been poor.

Both lines are always fine outside of 9am-5pm

During the hours of 9-5:- 

Line A:

Until about 2 weeks ago very poor most days.
During the last 2 weeks it has been fine until today.
Had a 15min disconnection this morning and it has been poor since then.

Line B:

Never noticed any poor performance until this Monday.
Had a disconnection early Monday afternoon and it has been awful every day since then.

Conclusions:-

At the moment both our lines are poor 9am-5pm fine outside those hours.

There is no correlation between our two lines, when one is bad/good it does not follow the other is is also bad/good.

It seems significant that good to bad transitions are assosiated with disconnections.

Tim.

[maxping]

You say the lines are poor do you mean high pings , slow internet?

When you found the problem did you try disconnecting for 30 mins EVERY time then try again?

Also this only makes 2 of you i would think if there was a big problem idnets end there would be lots of users here complaining.

I don't want to sound like a fanboy and i have had my share of high ping problems but only 2 people using these forums with high pings makes me wonder where the problem lies.

[equk]

When you found the problem did you try disconnecting for 30 mins EVERY time then try again?

Not being funny but this is cr*p, disconnect for 30mins?

1. NO-ONE should be expected to do that
2. Majority of the time it does nothing
3. When it does make a difference, often the problem is back within minutes
4. For a lot of cases this is not viable

People don't expect to pay for a service to be asked to fix the problems themselves.

[TimJ]

You say the lines are poor do you mean high pings , slow internet?

Yes, both.

When you found the problem did you try disconnecting for 30 mins EVERY time then try again?

No I have not disconnected, an ADSL line that needs disconnecting for 30 mins every so often is of little use to me.

One line is usually unattended so a disconnect is impossible, the other line has email servers etc and it is highly undesirable to turn off for 30 mins on the hope it will fix the problem for a few minutes or hours.

If I had any confidence that it would provide a PERMENANT fix then yes obviously I would disconect.

Here is a typical l8nc graph from yesterday http://212.69.55.123/l8nc061004.png

I can't see that the problem is with the kit at my end of both lines, there is nothing that is 9-5 specific. It might be BT or IDNET or somewhere else.

I will keep monitoring and see how things go I am no yet considering asking for a MAC but something is wrong somewhere.

TIm.

[maxping]

Not being funny but this is cr*p, disconnect for 30mins?

1. NO-ONE should be expected to do that
2. Majority of the time it does nothing
3. When it does make a difference, often the problem is back within minutes
themselves.[/b][/i]

1] While they are trying to get to the bottom of the problem i am quite happy to give it a try.

2] It has worked for me  95% of the times i have tried.

3] This has never happened to me once fixed if i don't turn the router off i stay connected with low pings.

Can i ask why you stay with idnet if you are so unhappy?

[equk]

1] While they are trying to get to the bottom of the problem i am quite happy to give it a try.

2] It has worked for me  95% of the times i have tried.

3] This has never happened to me once fixed if i don't turn the router off i stay connected with low pings.

Can i ask why you stay with idnet if you are so unhappy?

I am migrating tomorrow

[equk]

No I have not disconnected, an ADSL line that needs disconnecting for 30 mins every so often is of little use to me.

I completely agree.

[maxping]

.

No I have not disconnected, an ADSL line that needs disconnecting for 30 mins every so often is of little use to me.

As CS are trying to sort the problem and have asked people to disconnect for 30 mins to get a better connection you are not helping yourself or CS by not following their request.

A 30 min disconnect could sort your problem permanently but you would rather come here bitching than try it.

I'm getting p****d off with people using the forum to  moan rather than at least try to sort things their end.
If  you don't want to try to improve your connection while CS try to sort the problem why don't you get your MAC and call it quits?

[maxping]

I completely agree.

So why dont you call it quits and leave?

[equk]

So why dont you call it quits and leave?

Hold on ........

I am migrating tomorrow

I AM MIGRATING TOMORROW

Ich verlasse morgen

Je pars demain

[equk]

A 30 min disconnect could sort your problem permanently but you would rather come here bitching than try it.

I have tried it and as I already said it doesn't work the majority of the time, as many others have also said. Look thru the thread.

It also will not sort the connection permanently, as has been proven by people posting in this thread.

I'm getting p****d off with people using the forum to  moan rather than at least try to sort things their end.

can't believe people discussing things on a discussion forum I mean....

also the "moaning", we're not moaning at you. Altho you seem good at provoking people to do so.

Everyone has a right to post their problems here, it is a support forum.
If you don't like it then maybe you should go away instead of telling IDNet's customers to leave 

why don't you get your MAC and call it quits?

[maxping]

I'm not telling people to leave, I'm asking why the moaning ones that post bad ping results without trying to correct it themselves don't leave?

Why would anyone who has been coming here night after night for weeks to moan want to stay?

Ive done my fair share of bitching over the ping issues but only after trying to sort it myself , as i have already said  disconnecting for 30 mins worked for me  95%  of the time.

[maxping]

I AM MIGRATING TOMORROW

Bye

One less moaning ficker 

[TimJ]

I'm not telling people to leave, I'm asking why the moaning ones that post bad ping results without trying to correct it themselves don't leave?

Why would anyone who has been coming here night after night for weeks to moan want to stay?

Ive done my fair share of bitching over the ping issues but only after trying to sort it myself , as i have already said  disconnecting for 30 mins worked for me  95%  of the time.

I will try and answer and explain from my perspective.

I don't think I have moaned, just pointed out that my lines are still suffering from poor performance in response to your post that basically said all was now fine.

Line B

is  a work line so it is important how this line performs during the day, but I am in a small busy company and spending time sorting out an ADSL line that is underperforming never gets to the top of my overlong todo list.

In fact I have never even contacted CS as I am sure that they are aware of the general problem and I suspect that there is no further information I can add.

So sorry but I am not a good customer, I want it to just work, if it does not I will put up with it for a while but if it does not get fixed I will just migrate, certainly on the work's line I do not have time to mess around disconnecting etc and trying to bug fix.

Basically when the hassle of having a poorly performing line exceeds the hassle of migrating I will migrate.


Line A

is at home, basically it is unused during the day so it is of mainly acedemic interest what happens during 9-5.

If this was underperforming when i wanted to actively use it then yes I would have the time and effort to try and sort things out, but when I am at home it just works fine.

I hope this goes someway to explaining.

Tim

[drummer]

Bye

One less moaning ficker 

Have you considered how unhelpful and unreasonable that comment comes across?

As this forum is the nearest we'll get to online support, it might be worth adopting a less agressive tone.

You may have alienated many people already, but you'll never know because they've opted for the "can't be bothered with this cr*p" option.

IDNet is my ISP, not my best mate and you need to accept that some folks don't get a great connection, so making it personal is slightly inappropriate.

[Dev]

Bye

One less moaning ficker 

Why is this kid not banned yet? All he does is start constant flames with everyone. 1 minute he is moaning that his connection is not ok with a graph which clearly states that his connection was totally timed out for 3 hours, then the next he's having a go at everyone on the forums with nothing knowledgeable at all.

The situation with the network has got worse over the past month instead of better, it seems quite obvious to me as a 10 year Programmer and a Online Gaming Network worker (since 1996) what the problem is. The Network is Overloaded - hence why when the connection is left on over time (at a busy period in the day) the connection gets worse, when you connect first your at the front of the line - while others reconnect your connection goes lower in contention again on the Network. Unless IDnet upgrade their lines they are going to constantly have problems. The only time people are having problems is at busy times of the day - Lunchtime and night time between 5pm - 11pm.

Turning off your modem/router every 5 minutes for half an hour is completely insane - people who pay for a service Expect Service. I have been on about 10 ADSL connections both business and personal ever since ADSL came out and have never had such bad problems as I have on this network. The only time I had a problem with a ADSL Network - the problem was fixed within a week.

[Dev]

So why dont you call it quits and leave?

You'll make a good support operator, just tell everyone to leave. Hey guys lets do what this kid is saying and all leave - then he won't have any connection at all as the company will shut down. Also I find it highly amusing that you seem to think your trying to sort it out yourself - how are you doing that? It's the ISP's problem nothing to do with peoples routers or lines.

Also when the network is overloaded anyway, reconnecting your router does nothing - which was proved the other night when peoples connections were just timing out all together every 5 minutes.

[Simon_idnet]

Hi Dev

If you could please email or PM me then we can investigate your connection problems.

Regards
Simon

[browney]

IDNet are a supper ISP I to came to IDNet from a poor ISP (PlusNet)

After my 10days my pings went up I didn't know what it was at all I phone Simon and his Co workers many times and I to got the same things to try

I have never agreed with the statements that people make when they say (ITS THERE NETWORK) when it simply isn't it is out of there hands there network has the capacity for all its customers my pings are now 22ms you may find it hard to believe that my pings are actually getting better. Also OC3D uses IDNet to host there gaming servers the clan/forum owner I believe has a ping of 18ms and will not tolerate any lag what's so ever

[equk]

I have never agreed with the statements that people make when they say (ITS THERE NETWORK) when it simply isn't it is out of there hands

If it is not their network, how do you explain the fact people who have migrated have stable connections?

Also OC3D uses IDNet to host there gaming servers the clan/forum owner I believe has a ping of 18ms and will not tolerate any lag what's so ever

So they run these gaming servers over their ADSL network do they 

I highly doubt they run gaming servers over their ADSL network. They are probably ran direct from their hosting servers. I would guess probably in london docklands or similar, with a lot higher network capacity than a ADSL connection.

[Dev]

IDNet are a supper ISP I to came to IDNet from a poor ISP (PlusNet)

After my 10days my pings went up I didn't know what it was at all I phone Simon and his Co workers many times and I to got the same things to try

I have never agreed with the statements that people make when they say (ITS THERE NETWORK) when it simply isn't it is out of there hands there network has the capacity for all its customers my pings are now 22ms you may find it hard to believe that my pings are actually getting better. Also OC3D uses IDNet to host there gaming servers the clan/forum owner I believe has a ping of 18ms and will not tolerate any lag what's so ever

So your telling me that webservers and Gaming Servers go through the ADSL loop are you? Really shows how little you know about the internet. I think you should go and read-up on how ADSL works compared to a 'Server'. The connection from a ISP Hosting (gaming or web) go directly through to the rest of the internet. A ADSL network goes through many forms of transport upto the ISP.

If the ISP have problems with one of their lines, or pace too many connections on the same line (pipe - whatever you want to call it), the people will have constant lagouts.

Transit to ISP

The way in which most ISPs are connected to the gateway is normally either via Fast Ethernet (FE - 100Mbps) or Gigabit Ethernet (GigE - 1000Mbps). Obviously if your ISP has a 155Mbps gateway installed then Fast Ethernet is not up to the job and so they'll have Gigabit Ethernet connections.

http://www.adslguide.org.uk/howitworks/

Should have put ADSL Pipes are overloaded, so you would understand. 

[mrapoc]

Ok, thats enough bitching ALL OF YOU
I don't care who started it, why etc.
lets just get back on thread eh, not even a mention of he says this, she says that (in other words no quotes unless they are useful)

we could almost move this into rant and rave the way this is going 

[cavillas]

Dev. Have you contacted Simon yet re your problems.  I noticed that he has asked you twice to contact him concerning this matter. Once in this thread and once in another.  Perhaps by contacting him things can be sorted out.

[maxping]

Have you considered how unhelpful and unreasonable that comment comes across?

Its a joke mate  EQ wont be offended , he knows me too well 

[maxping]

1 minute he is moaning that his connection is not OK with a graph which clearly states that his connection was totally timed out for 3 hours,

I am not banned because there is no reason to ban me ,i do not flame (the fick off to EQ was a joke and he knows me well enough to know that)  if you don't like me asking if you have turned the router off thats your problem not mine hardly flaming .

Oh and actually it wasn't timed out for 3 hours it was  turned off, i do not leave it on when the pc is off 

Turning off your modem/router every 5 minutes for half an hour is completely insane - people who pay for a service

I don't think anyone said turn it off every 5 mins its a one off test if you discover you have high pings , if it doesn't work the first time it ain't going to work the second, i however have had this trick fix my pings many times.[/quote]

[maxping]

You'll make a good support operator, just tell everyone to leave.

So who do YOU think you are helping by posting in an unofficial forum?

Hey guys lets do what this kid is saying and all leave

"ALL"  that would be the 2 of you then that are having problems at the moment out of how many?

Also I find it highly amusing that you seem to think your trying to sort it out yourself - how are you doing that? It's the ISP's problem nothing to do with peoples routers or lines.

As i have said many times , on the now rare occasion i get 150+ pings i use the 30 min disconnect trick and it works for me therefore i am fixing it myself.

Also when the network is overloaded anyway, reconnecting your router does nothing -

Read my last post.

which was proved the other night when peoples connections were just timing out all together every 5 minutes.

Would that be the night when there was a power outage at BT as posted by Simon in the Adsl guide forum.

[equk]

Well for the peeps who pm'd me to ask about ping times after migration, I've migrated and ping times have vastly improved aswell as stability.

So far I'm pinging the NL servers I norm play on at 30ms (was 40-60ms on idnet). Quake3 is actually playable once again. I guess time will tell on whether it is permenantly sorted but for now it does seem to be a lot better.
Even browsing the net seems faster.

[maxping]

*Deleted* 

[mrapoc]

Simon has rang me and advised me turning the router off may not be the only fix

The bt test thingy
Logs you off your bras profile then back onto idnet after - thus putting you onto a new "pipe"

Thank you simon 

Also, i think we need to make a new thread / start on this one, with purely pings, tracerouts and line stats at the time of problems, with no comments what so ever.

Maybe add how it affected you (e.g slow browser, high pings in gaming or both etc.) to make a large, easy to analyse list of stats, how it affected you and do it as soon as the problem occurs. Wotchu reckon?

[maxping]

Also, i think we need to make a new thread / start on this one, with purely pings, tracerouts and line stats at the time of problems,

Wotchu reckon?

To be honest now Avenger and Eq have gone i don't think there will be the constant ping test postings there have been recently.

The rest of us that "were" having problems seem to be OK at the moment .

[cavillas]

You mean a ping free zone 

[maxping]

You mean a ping free zone 

Well if you ignore my name then yes 

[cavillas]

Well if you ignore my name then yes 

No. Not you. You're safe.....for the moment

[maxping]

 

[drummer]

Its a joke mate  EQ wont be offended , he knows me too well 

Fairy nuff, but I didn't know that and neither would many other newcomers to this forum, so it came across as aggressive and unhelpful.

Just something you may want to consisder is all I'm saying.   This forum ought to be a source of advice and information that doesn't intimidate newcomers - it's not a gamers forum after all.

[maxping]

Fairy nuff, but I didn't know that and neither would many other newcomers to this forum, so it came across as aggressive and unhelpful.

Jeez mate chill out, anyone reading that "Joke" who was offended and assumed i was a aggressive sort (as you put it) could read all my 622 posts and make their own mind up.

Now stop giving me a lecture 

I was going to tell you to fick off but you would probably be offended   

[cavillas]

Maxping very bad man.

[maxping]

Hey don't you start 

[cavillas]

OK.  Maxping very nice man. 

[TimJ]

Just a quick update.

As a result of my posts here Simon rang yesterday morning, the line was OK at the time, but it went slow again during the afternoon and I spend a some time going through tests with Miriam, and the conclusion was that the problem is somewhere between my router and IDNET.

Connecting to the BT Test domain (where the speedtester failed to work!) then reconnecting back to IDnet did restore the connection to full speed - but for how long - time will tell.

Anyway full marks to IDnet for their customer support.

Tim.

[mrapoc]

Just as simon told me 

Connecting to the BT Test domain (where the speedtester failed to work!) then reconnecting back to IDnet did restore the connection to full speed

[maxping]

This is getting beyond the joke, i haven't had anything to moan about for ages   

[philco]

Well my connection has been fine for about a month and then suddenly i got the ping problems back. I had to do the bt speedtest login about 6 times before i got a decent connection but sure enough ive got sub 20ms pings now.

For anyone trying the bt test login.... remember that you may end up being connected to the same pipe again as they are allocated at random. Keep trying until you get a good one 

[maxping]

For anyone trying the bt test login.... remember that you may end up being connected to the same pipe again as they are allocated at random. Keep trying until you get a good one 

I haven't used this method yet (and hope i don't need to) but if you eventually get a decent ping and then do not turn the router off does this guarantee you will always have a good ping?

[philco]

Although there is nothing to say the pipe your connected to won't start playing up it seemed to work for me for 4 weeks 

[maxping]

Nice one 

[wolverene]

I had nothing but trouble when I tried a pipe- so I went back to ciggies.
Please dont stop the thread about ping probs as I am just beginning to understand the jargon and not having anything to complain about after leaving PlusNet I`m starting to get withdrawal symptoms.

[maxping]

We cant stop it now we only have 713 views and I'm determined to get to 1000 

[TimJ]

This is getting beyond the joke, i haven't had anything to moan about for ages

I could post a load more awful l8nc plots but there would be little point.

I haven't used this method yet (and hope i don't need to) but if you eventually get a decent ping and then do not turn the router off does this guarantee you will always have a good ping?

Lasted for me from late Friday afternoon until I had a disconnection at Monday Lunchtime then it went bad.

Interesting that the l8nc plots of my 2 lines (on different exchanges) are now both awful and identical, so the problems are not exchange specific.

Tim.

[maxping]

Have you told CS ?

[TimJ]

Have you told CS ?

Yes.

Spent 1/2 hour on phone to Miriam on Friday trying various tests. IDnet sent out a different router to try and I spend another 1/2 hour with Miriam on Monday.

What baffles me me is that I have 2 lines on different exchanges and both are seriously effected, how come there aren't many others effected. The quietness on this thread indicates that I am very much in the minority. It does not add up.

I am happy to spend a resonably amount of time helping IDnet sort out this problem, they are certainly trying their utmost,  but I suspect that it is a BT problem that they are going to be unable to resolve in the short/medium term and from my perspective a quick and simple migration will fix my problems

Tim.

[CatMangler]

No Tim your are not alone, I have recently started experiencing the poor ping and connection problems (again).

Things seemed to have improved for about a week then for the last few days pings are all over the place with re-sync's and this morning no connection to idnet at all(local exchange synced @ 8Mb).

Had to leave router off for 10mins to restore connectivity to idnet.

[maxping]

I also had higher ping tonight than i have had for a while , not into the hundreds but between 40ms & 80ms.

I tried the  speedtest@speedtest_domain and it did the trick 

[maxping]

A couple of users are having ping issues during the day, as i do not work from home i don't often get chance to test my connection during the day.

I am off work today and for me it seems to make no difference if its day or night time my connection seems to have settled down over the last few Weeks.

I'm not posting this to  trivialise  the problems some people are having   but i think its fair to post good pings to show prospective customers its not all doom and gloom.

Pinging www.idnet.net with 32 bytes of data:

Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:29ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:30ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:38ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:26ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:26ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:26ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:29ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Ping statistics for www.idnet.net :
Packets: Sent = 30, Received = 30, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 38ms, Average = 28ms

[merkin51]

My ping since last night has been 130+, just in time for the BF2142 demo I'll give IDNet the benefit of the doubt that they'll sort this out asap, but it's pretty annoying.

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

Reply from 212.69.36.10: bytes=32 time=134ms TTL=60
Reply from 212.69.36.10: bytes=32 time=143ms TTL=60
Reply from 212.69.36.10: bytes=32 time=143ms TTL=60
Reply from 212.69.36.10: bytes=32 time=134ms TTL=60

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

[mrapoc]

damn pings 100+ on css atm, friends in the same area getting 20-30

[maxping]

OK here, have you tried the speedtest trick ?


Packets: Sent = 30, Received = 30, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 54ms, Average = 33ms

[equk]

What happened to the original ping thread with the idnet announcements etc on it 

Just curious
Only back from having loads of people pm'd me about connections etc. Some interesting info from certain peeps.

[maxping]

What happened to the original ping thread with the idnet announcements etc on it 

I guess as most of the users here are now having no problems with their pings and the 2  that posted the most about their bad pings (you and Avenger) have moved on to new ISP's someone decided it was no longer relevant.

Just curious
Only back from having loads of people pm'd me about connections etc. Some interesting info from certain peeps.

I'm glad you have shared that with us , when i left freedom2surf i was so glad to get away i never visited the forums there again ,  i wonder what your motive is for coming here and posting this.

[equk]

Post Deleted - By: [maxping], Reason: [Unknown. // Cleaning up previous post deleted message to be more friendly (Adam)]

[equk]

What stirring?

I posted a link to the original thread and quoted Jeffs post.
(if you're not hiding anything, what's wrong with linking the original thread for new people to read thru?)

Got that deleted aswell as my other post in reply to yours stating I came back due to having emails saying I had pm's here and also that there are some ok peeps here.

Also you're that childish that you put my karma to -9 

[CatMangler]

Na the karma thing was effected by me adding good karma to you, it went from 4 or 5 then suddenly to -9, oops sorry my fault must be a bug somewhere.

[maxping]

So you have had some PM's, why not answer them by PM instead of trying to dredge up old threads that have no relevance.

The ping issues for the majority here are no longer a problem as you can see from the "ping" thread.

The ones that are having problems are working it out with Customer Support.

As for the karma one Bad was from me (you can only vote once) so you work out how welcome your comments are here

[CatMangler]

Perhaps my attempt to give you good karma has been "over ruled"

[equk]

So you have had some PM's, why not answer them by PM instead of trying to dredge up old threads that have no relevance.

dredging up?
All I did was post a link so people can have a better insight into the problem and how IDNet have helped. It not only has good information on IDNet official announcements, it also provides some good information to why it's happening and also how many people it happens or happened to.

The ping issues for the majority here are no longer a problem as you can see from the "ping" thread.

The ones that are having problems are working it out with Customer Support.

Probably because they get flamed here, also the reason why people pm'd me.

As for the karma one Bad was from me (you can only vote once) so you work out how welcome your comments are here

Na the karma thing was effected by me adding good karma to you, it went from 4 or 5 then suddenly to -9, oops sorry my fault must be a bug somewhere.

As this is a community I think CatMangler has proven otherwise, unless you've suddenly taken over the forums 

[maxping]

dredging up?
All I did was post a link so people can have a better insight into the problem and how IDNet have helped.

If you wanted to show the people who PM'd you the thread you could have sent them the link, my view is you wanted to drag a dead  thread back to the top, you say its to show people what IDNet have done to help , i think you have other motives.

I am going to leave it at that , i don't want to get into a argument with you over this, you are no longer  a  IDNet customer, why people are sending you PM's about bad pings is beyond me.

I am locking this thread , feel free to open another if you wish.