Pings

[TimJ]

I only have records since last Wednesday.

But Wednesday, Thursday. Friday last week and Mon Tues this week were bad during the working day, but Sat Sun were fine.

Another line I have with IDNET is fine all the time.

Tim.

[maxping]

It seems very clearly business related, and it's also on either the BT Colossus network or the IDNet Fat Pipes

I had quite a long talk with Simon tonight and he explained the basics to me and did say they think its the BT Colossus network thats causing the problem.

(at least i think thats what he said)

/covers back nicely

As you can see from the graph in the other thread mine is fairly stable at the moment and has been for a few days,i am going to get the wife to do a few ping tests during the day to compare them to the evening pings.

[Jeff]

Thanx for the input Tim ... feel free to post your specific problems experienced in the new post, pinned to the top

Hey, some could say that the ping problem might not lie with IDNet as all lines/users aren`t affected. Not me however, I sometimes see the ping spike ... it just doesn`t affect me

[maxping]

When i get high pings its not the spikes that bother me its not getting a ping below 150+ ms in 30 hops.

[TimJ]

Here are some more l8nc plots - all 5 weekdays showing very poor daytime performance but generally fine during the evening, nights and weekends.

Thursday 21st is particularly bad.

http://212.69.55.123/l8nc060919.png
http://212.69.55.123/l8nc060920.png
http://212.69.55.123/l8nc060921.png
http://212.69.55.123/l8nc060922.png
http://212.69.55.123/l8nc060925.png

The 2 weekend plots are OK.

http://212.69.55.123/l8nc060923.png
http://212.69.55.123/l8nc060924.png

As the line is basically unused during the day, I can't say that it is effecting me but it does not look correct.

Tim

[karvala]

Yeah, they're characteristic graphs of the problem, Tim.

On a more cheerful note, things continue to look fine here:-

Pinging 212.69.63.45 with 32 bytes of data:
Reply from 212.69.63.45 bytes:32 Time:17ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:14ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:16ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:15ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:15ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:16ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:17ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:15ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:16ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:16ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:16ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:15ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:15ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:15ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:16ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:15ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:15ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:16ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:15ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:15ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:15ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:18ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:14ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:15ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:15ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:17ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:15ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:16ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:17ms TTL:254
Reply from 212.69.63.45 bytes:32 Time:15ms TTL:254
Ping statistics for 212.69.63.45 :
Packets: Sent = 30, Received = 30, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 18ms, Average = 16ms

[Simon_idnet]

Hi TimJ

Do you have any l8nc plots for your other line? The one where you said: "Another line I have with IDNET is fine all the time."

Cheers
Simon

[maxping]

Here are some more l8nc plots
As the line is basically unused during the day, I can't say that it is effecting me but it does not look correct.

Tim

Tim have you tried  turning  the router off for 30 mins as advised by customer support when you see the high pings?

[maxping]

Happy Days 

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


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

[TimJ]

Hi TimJ

Do you have any l8nc plots for your other line? The one where you said: "Another line I have with IDNET is fine all the time."

Cheers
Simon

Simon,

Sorry I was was not clear in that statement. The other line is at different premices on a different exchange. I don't have any back record of l8nc on the other line but i have just turned on email of l8nc results, so a record will build up.

There is a linux box running 24/7 on the "problem" line so if would help if I monitored anything  let me know.

Today l8nc plot looks pretty well perfect with low pings all day.

Tim

[equk]

hmm nice ping atm not

Code Select Expand

  1     1 ms    <1 ms    <1 ms  cisco [192.168.1.1]
  2     3 ms     2 ms     2 ms  192.168.0.1
  3   122 ms   114 ms   108 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  4   110 ms   105 ms   109 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  5   236 ms   145 ms   143 ms  212.69.63.5

[maxping]

I think it would be helpful if when posting bad ping results we also said if  we have tried turning the router off for 30 mins as suggested by customer support.

I always try this when i have bad pings and it usually works , having said that i have had good pings day and night for a few days now.

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

Ping statistics for www.idnet.net :

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

[maxping]

Just checked my L8NC graph and again its just about flat and the green line is running at approx 30 ms.