Re: Pings

equk · Sep 28, 2006, 17:06:10

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 · Sep 28, 2006, 17:30:57

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 · Sep 28, 2006, 17:59:17

Quote from: equk on Sep 28, 2006, 17:06:10
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 · Sep 28, 2006, 18:03:32

Quote from: Adam on Sep 28, 2006, 17:30:57
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 · Sep 29, 2006, 16:35:02

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 · Sep 29, 2006, 17:29:28

Deleted.

karvala · Oct 02, 2006, 16:41:17

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 · Oct 04, 2006, 17:46:50

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

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 · Oct 04, 2006, 18:03:51

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 · Oct 04, 2006, 18:42:01

Quote from: equk on Oct 04, 2006, 17:46:50
I have re-synced 3 times but it's still the same

Have you tried turning the router off for 30 mins?

cavillas · Oct 04, 2006, 19:49:50

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 · Oct 04, 2006, 20:09:01

Code Select

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

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 · Oct 04, 2006, 20:32:51

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 · Oct 04, 2006, 20:35:22

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 · Oct 04, 2006, 20:40:07

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 · Oct 04, 2006, 20:50:37

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 · Oct 04, 2006, 20:53:19

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 · Oct 04, 2006, 21:02:23

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?!?!?!

QuotePinging 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 · Oct 04, 2006, 21:05:25

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 · Oct 04, 2006, 21:22:25

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 · Oct 04, 2006, 21:29:08

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 · Oct 04, 2006, 22:33:36

QuoteHi 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 · Oct 04, 2006, 23:15:56

bah being disconnected to half the world isn't much fun

loads of servers and sites not working, or working intermittantly atm $:-\$

equk · Oct 04, 2006, 23:30:25

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 · Oct 05, 2006, 15:43:29

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...