Thought this was over

[jakarra]

I thought Idnet should have upgraded everything by now as they said everything would be sorted by the end of Feb. Just did a tracert to see if it was worth playing bf2142..... I guess not !!!

C:\Documents and Settings>tracert www.idnet.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *     1375 ms   273 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3   139 ms   145 ms   156 ms  212.69.63.10
  4   159 ms   161 ms   164 ms  redbus-gw.idnet.net [212.69.63.1]
  5   162 ms   146 ms   139 ms  www.idnet.net [212.69.36.10]

Trace complete.

[Philip]

they're getting there jakarra, see here http://www.idnetters.co.uk/forums/index.php/topic,1449.0.html

[AvengerUK]

The new pipe took longer to install than expected i think, this is NOT idnet's fault, as BT are generally very slow at these things - its been installed and is currently being tested. So, within a week or so, the problems will be over!

EDIT: Beat me by 21 milliseconds doctor

[Lance]

Jakarra,

The most recent update on the new central is from Tim here. It looks like BT were a bit slow getting it installed (typical BT!   ).

EDIT: seems I must be quicker with my replies!!!!!!


I can't to a tracert (my Linksys router has a bug which doesn't let me do it) but here is my ping results completed just now...

Pinging www.idnet.net [212.69.36.10] 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=29ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms 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=28ms 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=45ms TTL=60

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

I can't therefore see any problems at my end (thankfully!)

[Philip]

EDIT: Beat me by 21 milliseconds doctor

not quite, I actually posted this tomorrow , it's just that the forum doesn't take into account I'm in the TARDIS!

[CreamyGoodness]

It's an interesting one this.  Last night, my pings at peak times were the best they've been for months.  Still > 100ms most of the time, but still better.  After about 10:00 they were absolutely fine and in the low 30ms.

Tonight, they're even better.  From about 5:00pm onwards, they've been around 30 - 50ms mostly, but spiking at 100 - 200ms briefly every 10s or so, with the occasional longish period at >100ms.

I might be imagining it, but it's kind of feeling like the loads on the centrals might be reducing gradually.  If so then, it would be great to know when the new central is fully up and running and all the new balancing has been done, so I can tell if the problems I'm seeing are related to a different issue.

[Lance]

If so then, it would be great to know when the new central is fully up and running and all the new balancing has been done

I'm sure they will give an update once they have completed their testing and moved users over to it, should be over the next 7 days or so I guess (from looking at Tim's update.

[jakarra]

thanks for the quick replies, generally I am pretty happy with IDNET, just lately I got to tracert before I play online. Though it is time BT got a rocket shoved up their collective arse 

[Danni]

I'm sometimes able to keep a steady connection for 30 minutes now, things are improving :p