Pings

[AvengerUK]

Perhaps IPStream services are still getting the effects? My line is still pinging normally 

[Danni]

Mine were huge before:

danni@Luciana:~$ ping idnet.net
PING idnet.net (212.69.36.10) 56(84) bytes of data.
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=1 ttl=60 time=618 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=2 ttl=60 time=632 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=3 ttl=60 time=622 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=4 ttl=60 time=640 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=5 ttl=60 time=698 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=6 ttl=60 time=618 ms

Also at the gateway:

danni@Luciana:~$ traceroute idnet.net
traceroute to idnet.net (212.69.36.10), 30 hops max, 40 byte packets
1  192.168.2.1 (192.168.2.1)  0.445 ms  0.510 ms  0.350 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  845.021 ms  785.477 ms  652.570 ms
3  telehouse-gw-bb.idnet.net (212.69.63.9)  674.457 ms  700.977 ms  698.486 ms
4  redbus-gw.idnet.net (212.69.63.1)  685.093 ms  666.866 ms  705.932 ms
5  * * *
6  * * *

[AvengerUK]

Ouch?! - Out of pure interest, has anyone else seen a change in their ping times besides me? (A change for the better)

[equk]

Ouch?! - Out of pure interest, has anyone else seen a change in their ping times besides me? (A change for the better)

I did yesterday, was even stable. Seemed ok this morning aswell, this seems to have just happened

[equk]

Mine were huge before:

danni@Luciana:~$ ping idnet.net
PING idnet.net (212.69.36.10) 56(84) bytes of data.
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=1 ttl=60 time=618 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=2 ttl=60 time=632 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=3 ttl=60 time=622 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=4 ttl=60 time=640 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=5 ttl=60 time=698 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=6 ttl=60 time=618 ms

Also at the gateway:

danni@Luciana:~$ traceroute idnet.net
traceroute to idnet.net (212.69.36.10), 30 hops max, 40 byte packets
1  192.168.2.1 (192.168.2.1)  0.445 ms  0.510 ms  0.350 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  845.021 ms  785.477 ms  652.570 ms
3  telehouse-gw-bb.idnet.net (212.69.63.9)  674.457 ms  700.977 ms  698.486 ms
4  redbus-gw.idnet.net (212.69.63.1)  685.093 ms  666.866 ms  705.932 ms
5  * * *
6  * * *

I guess it's not just me then, so hopefully it's nothing to do with my line.

[equk]

lol now suddenly pings are back to normal?

Code Select Expand

traceroute to www.idnet.net (212.69.36.10), 30 hops max, 40 byte packets
1  cisco (192.168.1.1)  0.840 ms  0.683 ms  0.647 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  25.377 ms  22.703 ms  39.996 ms
3  * telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  22.501 ms  25.855 ms
4  telehouse-gw-bb.idnet.net (212.69.63.9)  26.059 ms  26.113 ms  23.684 ms
5  redbus-gw.idnet.net (212.69.63.1)  26.140 ms *  22.760 ms
6  www.idnet.net (212.69.36.10)  28.033 ms  23.964 ms  24.234 ms

something very strange is going on 

[equk]

hmm actually not exactly back to normal as I'm getting 33ms - 60ms on a server that this morning and last night was 33ms constant.

It's not spikes either it's like a constant stream, as if (as said before) someone else is using my connection.

also it's doing it on more than one server, have just tried another that was ok in france and that's doing the same

[Danni]

Mine are back to normal again now... around the 45ms mark.

Email has been sent to support.

[equk]

Still getting the unstable thing, pings servers at 30ms (using ping command), put more data down the line and it's up to 40-60ms, as above seems to be constant and not spikes.

This is to servers that were 33ms stable earlier and last night.
Almost as if someone is raping the idnet connection or something   

[equk]

gateway ping going up again:

Code Select Expand

traceroute to www.idnet.net (212.69.36.10), 30 hops max, 40 byte packets
1  cisco (192.168.1.1)  1.281 ms  0.667 ms  0.751 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  75.045 ms  73.856 ms  58.180 ms
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  54.144 ms  47.402 ms *
4  telehouse-gw-bb.idnet.net (212.69.63.9)  81.575 ms  77.984 ms  75.903 ms
5  redbus-gw.idnet.net (212.69.63.1)  78.280 ms  71.707 ms  82.278 ms
6  www.idnet.net (212.69.36.10)  71.910 ms  82.996 ms  87.810 ms

[AvengerUK]

Code Select Expand


  1     1 ms    <1 ms    <1 ms  mygateway1.ar7 [192.168.1.1]
  2    18 ms    18 ms    17 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    19 ms    19 ms    19 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4    19 ms    22 ms    20 ms  redbus-gw.idnet.net [212.69.63.1]
  5    20 ms    19 ms    19 ms  idnet.net [212.69.36.10]

Trace complete

Code Select Expand



Tracing route to multiplay.co.uk [85.236.96.22]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  mygateway1.ar7 [192.168.1.1]
  2    20 ms    18 ms    18 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    18 ms    19 ms    18 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4    19 ms    18 ms    19 ms  lonap2.enta.net [193.203.5.135]
  5    19 ms    19 ms    20 ms  vlan43.redbus-sov3.core.enta.net [84.45.193.206]

  6    22 ms    19 ms    21 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  7    21 ms    19 ms    18 ms  multiplay.co.uk [85.236.96.22]

Trace complete.


[equk]

Just wanted to say something about routing:

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    25 ms    24 ms    24 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    23 ms    21 ms    21 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  4    23 ms    23 ms    21 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  5    25 ms    25 ms    23 ms  redbus-gw.idnet.net [212.69.63.1]
  6    45 ms    47 ms    41 ms  ams-ix.sara.xs4all.net [195.69.144.48]
  7    42 ms    41 ms    41 ms  0.so-6-0-0.xr2.3d12.xs4all.net [194.109.5.5]
  8    58 ms    43 ms    45 ms  0.so-3-0-0.cr2.3d12.xs4all.net [194.109.5.94]
  9    67 ms    67 ms    79 ms  quake3-04.xs4all.nl [194.109.69.93]

Trace complete.

also

Tracing route to kilo020.server4you.de [85.25.10.49]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  cisco [192.168.1.1]
  2    25 ms    41 ms    25 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    23 ms    21 ms    21 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  4    23 ms    23 ms    21 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  5    23 ms    25 ms    23 ms  redbus-gw.idnet.net [212.69.63.1]
  6    45 ms    59 ms    67 ms  AMS-IX.AMS-1-eth010-101.nl.lambdanet.net [195.69.144.212]
  7    57 ms    57 ms    73 ms  DUS-2-pos700.de.lambdanet.net [82.197.128.29]
  8    72 ms    75 ms    55 ms  DUS1-5029.de.lambdanet.net [217.71.104.30]
  9    84 ms    60 ms    75 ms  kilo020.server4you.de [85.25.10.49]

Trace complete.

[browney]

I have notice that on the 5th my ping problems stopped. Then a day later everyone reported no ping problems. Now a few more days later today I see that I will see a ping spike every hour and that my average ping is VERY SLIGHTLY HIGHER eg now from 27ms to 30-35ms

[karvala]

Ouch?! - Out of pure interest, has anyone else seen a change in their ping times besides me? (A change for the better)

My ping times still fluctuate somewhat (two days ago averaging around 27/28, yesterday averaging around 40, today averaging around 27/28 again), but in the last 24hrs or so, my latency graph has become much better, no longer showing the frequent spikes that it did previously; this improvement seems similar to the one you reported yesterday as well.  I should add that I tested on most occasions with two different bits of kit (router and USB modem for comparison), and both have shown the same change, so it's certainly not down to equipment in my case.

http://www.l8nc.com/graph.php?sid=383780fb8a6325ed2c68372d6061acdd&jid=aaa18fb159292b32e9b02f8f3ebacecf&day=yesterday

[browney]

Still low keep it up IDNet

Ping statistics for www.multiplay.co.uk :
Packets: Sent = 50, Received = 50, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 29ms, Average = 29ms

[AvengerUK]

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

o god nooooooooo!

[karvala]

LOL oh dear.  You weren't heavily using the connection during that period, though, were you?  If so, I'd expect to see something like that.

Check out mine: 

http://www.l8nc.com/graph.php?sid=3e558fac2c207d467e5e2158e6aa1359&jid=aaa18fb159292b32e9b02f8f3ebacecf&day=today

Looks horrific on the face of it, as though something catastrophic happened in the early hours, but in fact, I was just up/downloading some stuff via P2P.  It flattens out again when it's finished.

[AvengerUK]

We cant see your l8nc graph, ie its not public

- Oh, and no one is in at my house...so unless the dog has mastered the use of a computer theres no use!

its not a stale session either....flat pings and no disconnects overnight, changes at around 7:50am

If you look at yesterdays graph, you can see heavy use periods...totally differnt to whats going on now - EDIT - hmm, despite some heavy use yesterday pings dont seem effected....i guess the videos/games i played didnt take up all my bandwidth!

[karvala]

We cant see your l8nc graph, ie its not public

Oops, forgot to set the flag for the new test.  Fixed now, cheers.

[mrapoc]

im happy to say my pings are pratically back to their normal selves!!  lovin it

[maxping]

Still low keep it up IDNet

Ping statistics for www.multiplay.co.uk :
Packets: Sent = 50, Received = 50, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 29ms, Average = 29ms

Im still hovering around the 50 mark 

Pinging core1.multiplay.co.uk [85.236.96.22] with 32 bytes of

Reply from 85.236.96.22: bytes=32 time=50ms TTL=121
Reply from 85.236.96.22: bytes=32 time=50ms TTL=121
Reply from 85.236.96.22: bytes=32 time=48ms TTL=121
Reply from 85.236.96.22: bytes=32 time=48ms TTL=121

Ping statistics for 85.236.96.22:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 50ms, Average = 49ms

[AvengerUK]

my pings are also back to normal now!

[karvala]

Interleaving now turned off, so I can concentrate properly on the ping aspect of things, and so far it's not looking at all good:- 

Tracing route to www.bbc.net.uk [212.58.224.121]
over a maximum of 30 hops:

1   152 ms   153 ms   150 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
2   163 ms   161 ms   148 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
3    89 ms    84 ms    69 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
4   113 ms   112 ms   113 ms  212.58.238.129
5    93 ms    98 ms    99 ms  www21.thdo.bbc.co.uk [212.58.224.121]

Trace complete.

Tracing route to www.bbc.net.uk [212.58.224.121]
over a maximum of 30 hops:

1   102 ms   105 ms   109 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
2   138 ms   144 ms   157 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
3   162 ms   152 ms   123 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
4    89 ms    89 ms    96 ms  212.58.238.129
5   136 ms   129 ms   129 ms  www21.thdo.bbc.co.uk [212.58.224.121]

Trace complete.

This is after I've rebooted the modem, and tested using a different bit of kit.  It just seems to happen at random. 

EDIT: And 5 minutes later, without any change whatsoever by me:-

Tracing route to www.bbc.net.uk [212.58.224.115]
over a maximum of 30 hops:

1    31 ms    21 ms    24 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
2    23 ms    20 ms    20 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
3    20 ms    26 ms    21 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
4    21 ms    23 ms    28 ms  212.58.238.129
5    34 ms    40 ms    36 ms  www15.thdo.bbc.co.uk [212.58.224.115]

Trace complete.

It's ridiculous.

[equk]

That's exactly the same as I was getting, not had it for a while, but if you're in quake3 or similar, you soon notice it when the ping goes to 200+ms.
Also even after it appears to go back to normal, if you connect to a server the ping is still effected (seems 25+ms more than traceroute or ping) aswell as having spikes .
(alltho some people here don't seem to realise the implications of ping times see other threads)

[AvengerUK]

Hi,

Again today the problem arised at the same time as yesterday: http://www.l8nc.com/graph.php?jid=58e61f6e3d3d258ec640ec3f21295d2e

trace's below:

Tracing route to multiplay.co.uk [85.236.96.22]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  mygateway1.ar7 [192.168.1.1]
  2    90 ms    73 ms    75 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45 ]
  3   131 ms   134 ms   131 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4   157 ms   125 ms   105 ms  lonap2.enta.net [193.203.5.135]
  5   325 ms   250 ms   218 ms  vlan43.redbus-sov3.core.enta.net [ 84.45.193.206]

  6    94 ms    97 ms    94 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  7    96 ms    96 ms    92 ms  multiplay.co.uk [85.236.96.22]

Trace complete.


  1    <1 ms    <1 ms    <1 ms  mygateway1.ar7 [ 192.168.1.1]
  2    22 ms    23 ms    22 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3   103 ms   317 ms   345 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4    24 ms    17 ms    19 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  5    21 ms    20 ms    19 ms  212.58.238.129
  6    20 ms    21 ms    18 ms  212.58.238.36
  7    35 ms    40 ms    31 ms  pos6-0.rt1.mh.bbc.co.uk [212.58.239.254]
  8    20 ms    21 ms    21 ms  bbc.co.uk [212.58.228.155]

Trace complete.

Thanks,
Simon

just sent that to support. its obviously not fixed....and im again cross.

Note: pings are now bobbing from 17ms to 40ms in pings, strange how the problem *almost* goes away when i start using my connection.........

(routers been synced all day so no re-syncs to change results!!!!)

EDIT: Also connection hasnt been used all day again, oh, and pings are fine now....anyone else thing this is really strange?

Another EDIT: Oh, and this is ALMOST exactly the same time period as yesterdays issues....