Ping times Jan 28 onwards

[Rik]

I know the latest central was a 155, so I wonder about this:

quote ref SIN 412 page 5

   BT will support a mixture of 155Mbits/s L2TP Passthrough and 622Mbits/sec Edgeless L2TP passthrough – however customers should note that such a mix will cause an imbalance in traffic between the two central types. This imbalance is due to the different numbers of LTSs used per unit of central bandwidth within the two central designs - as new sessions are evenly distributed over LTSs within a One to Many group. This imbalance is somewhat offset by the increase of bandwidth offered by 622Mbits/sec L2TP central. The 622Mbit/sec design offers a 23% improvement in bandwidth over the equivalent number of 155Mbit/sec BT centrals. The 155Mbps design uses 2 LTSs and provides approximately 56.5Mbits/sec (of end user IP traffic) per LTS. The 622Mbits/sec design uses a total of 12 LTSs and provides 46.3Mbits/sec (of end user IP traffic) per LTS. Consequently, when mixing 155Mbps and 622Mbps centrals in the same one to many group the 155Mbits/sec centrals will be approximately 18% under-utilised i.e. when traffic has reached the full rating of the 622Mbps central the 155Mbps centrals will have reached only 82% of their rated capacity.

Nice find, Glenn.  

[Rik]

Just what it should be.  I haven't pinged IDNet yet as I do not know there IP (sorry).  Still don't understand why I should have to reboot the router ?  

What's normal for you - there's a lot of factors at play in ping times. IDNet are at 212.69.36.10.

Re-booting forces a re-connection which often moves you to a new, and less congested, pipe.

[uxbod]

Ping provides a rule of thumb of how things are performing though it would be better to see a traceroute (tracert for windbloze users).  When I was seeing the issue over the weekend I tried from a number of US sources to IDNET and they were all sub 30s.

[snaggie]

Thank you.  I pinged IDNet with the following results:

PING 212.69.36.10 (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=60 time=35.0 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=60 time=35.0 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=60 time=35.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=60 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/33.7/35.0 ms

These timings seem very reasonable to me, and are about what they used to be.  I still do not understand why I should have to reboot my router to get these results?  It was never the case before about 10 days ago   

[Rik]

I've explained that IDNet has had problems of unbalanced loads following the addition of a new central, the re-boot will probably have moved you to an uncongested pipe.

[Steve]

Mine are ok this evening which is excellent news. Glenn's link was very educational esp the round robin and the problems associated with differing central capacities. Are we aware of what capacity the other centrals are as looking at that link mixing the two doesn't work

[Rik]

We're not, Steve, but I know the new one is a 155.

[Glenn]

My pings are poor for the 3rd time today, back in the 100 - 135ms range, I have already rebooted 2 or 3 times today

[Rik]

My average remains below 27ms, but it's a little higher than this morning, and definitely more spiky, which I put down to exchange activity.

[Lance]

My pings at the moment seem fine - I've just started Pinggraph so I can watch them over the evening. 

[Rik]

You do that, I'm going to watch my food and a game of rugby that I didn't get to yesterday.

[Glenn]

I wouldn't, enjoy your dinner

[Rik]

That bad?

[davej99]

That bad?

[Glenn]

That bad?

They played better than England if that's any good

[davej99]

Del by Dave - Nae mair banter. 

[vitriol]

C:\Users\vitriol>ping www.idnet.net

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=108ms TTL=59
Reply from 212.69.36.10: bytes=32 time=145ms TTL=59
Reply from 212.69.36.10: bytes=32 time=135ms TTL=59
Reply from 212.69.36.10: bytes=32 time=124ms 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 = 108ms, Maximum = 145ms, Average = 128ms


No gaming for me tonight then

[DarkStar]

My pings have settled down nicely now, been like this since I posted yesterday 


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

Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms 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 = 35ms, Maximum = 36ms, Average = 35ms


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

  1     1 ms     1 ms    <1 ms  192.168.0.1
  2    37 ms    38 ms    36 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    44 ms    36 ms    36 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    39 ms    35 ms    36 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    36 ms    36 ms    37 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    37 ms    38 ms    37 ms  www.idnet.net [212.69.36.10]

Trace complete.



[attachment deleted by admin]

[Lance]

Here is my current graph. It's important to note that there are three of us using the connection at the moment which may way upset the pings a little.

[attachment deleted by admin]

[4Way]

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

Reply from 212.69.36.10: bytes=32 time=221ms TTL=59
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=52ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms 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 = 18ms, Maximum = 221ms, Average = 78ms

No games for me either tonight!

[Lance]

My pings at the moment seem pretty consistent and are in their normal range of between 30 and 40ms. The only thing I can suggest is that you reboot your router.

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=38ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 38ms, Average = 32ms

[Simon]

Del by Dave - Nae mair banter. 

It's just an effort to keep threads like this a little more concise and factual. 

[drummer]

Lost http about 30 minutes ago, although Trillian remained connected to ICQ, Yahoo and MSN as I didn't lose sync.

As rebooting the router appears to be only a temporary fix for the individual customer (myself included), it's obvious that there still be gremlins within IDNet's new capacity.

Surely a daily update from IDNet posted on this forum wouldn't be that difficult and I'm slightly surprised it hasn't happened already.  Nothing detailed mind, just a simple progress report in Service Announcements.

When my pings are good they're very very good, but when they're bad they're horrid...

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

Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms 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 = 13ms, Maximum = 14ms, Average = 13ms

Hey ho.

[attachment deleted by admin]

[Lance]

I too would like to see some further communication from Idnet on this issue.

[4Way]

My pings at the moment seem pretty consistent and are in their normal range of between 30 and 40ms. The only thing I can suggest is that you reboot your router.

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59


Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=38ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 38ms, Average = 32ms

Thanks I'd already tried that but no success. I'll log a call tomorrow, they can add it to the pile I'm sure they have. I'm running  Ping Graph now so will send that to them as well