Connection problems?

[David]

   Simon...I got the gist of all that 

[Simon]

Could always copy it to Announcements, Rik. 

[Rik]

It had crossed my mind...

[davej99]

Firstly, IDNet would like to apologise for the network outage today. ....

Thanks for the post Simon. Doo happens. What counts is leveling with customers and fixing it. So well done. The 20:20 hindsighters will still give you grief. Invariably they don't doo because they don't do.

[Rik]

That's good. 

[Philip]

everything working ok now  my daughter bless her, (college closed) was trying everything this afternoon to get it going, and giving me grief on the phone at work 

[davej99]

You eventually get to to the point where you have been kicked doo-less by some of the largest corporations in the world. Strangely, when its on the fan, the most successful kick least and help most. Then comes the day, as come it will for a' that, when you have what they all need, and you return the favour to friends. And for the rest; you take the money and smile; but never go the extra mile.

[Baz]

re boot has done the trick for me. did notice some slowness earlier and pages just hanging. Just got in and caught up with the goings on. Thanks for the up dates from IDNet and to what seems like a fix. 

[psp83]

pings still high for me

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

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2   162 ms   167 ms   221 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3     *      139 ms   137 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4     *      163 ms   155 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   158 ms   162 ms   161 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   157 ms   155 ms   146 ms  www.idnet.net [212.69.36.10]

Trace complete.

[Sebby]

Have you rebooted, Paul?

[J!ll]

I blame Rik, for kicking me out  I didn't know what to do, helpless 

[ducky22]

Firstly, IDNet would like to apologise for the network outage today. Our LNS server (that terminates broadband connections) failed and that event caused a cascade of problems: the core routers were complaining about not being able to see the routes to broadband customers which meant that our office leased-line to London couldn't access our Status Page, to update it; Our phone system couldn't cope with a 1,000 fold increase in our usual call volume (we'll be taking this up with our 0800 provider too); And when we managed to get the LNS server back up one of our Centrals (the new one) didn't respond which meant that the remaining Centrals quickly became congested. We do not yet fully understand what caused the problem with the LNS server and we are still investigating.

And all this just when we thought we were getting on top of the latency issue...

If anyone is still experiencing poor performance please reboot your router as we have blocked any new logins through to the 'old' Centrals in order to utilise the capacity in the new Central.

Again apologies to all and we can assure you that we will be taking steps in order to ensure that this does not happen again.
Regards
Simon

So a couple of questions...

I find it absolutely absurd that your office has ONE leased line. Why not a backup ADSL connection from another provider? Why not a backup ISDN line? Why not even a pay as you go datacard on someone's laptop to allow you to update the status page? Absolutely ridiculous. It this something you're going to fix? Surely someone has a big enough brain to contemplate a BACKUP connection?

Of course, what a suprise that none of the "faithful" pointed the above out.

Phone systems - glad you're blaming someone else. Possibly their fault, possibly not.

Would love to hear more details on the LNS server.

[ducky22]

Also, other ISPs have multiple LNS servers - does IDNet?

[psp83]

Have you rebooted, Paul?

Yep. Pings back to normal for now, will check again tonight.

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

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2    20 ms    15 ms    13 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    13 ms    13 ms    13 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    14 ms    13 ms    14 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    13 ms    15 ms    14 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    14 ms    14 ms    14 ms  www.idnet.net [212.69.36.10]

Trace complete.

[talos]

Results from http://www.speed.io
(Copied on 2009-02-04 08:23:11)
Download: 1692 Kbit/s
Upload : 389 kbit/s
Connects : 1387 conn/min
Ping: 44 ms


Back to my normal stats I think, hope it now stays that way

[J!ll]

Again this morning! 

[Rik]

Again in what sense, Jill?

[J!ll]

Here quite early, but it only lasted 5 minutes or so, net dead 

[Rik]

I've got nothing showing in my router logs, could it have been a local problem?

[Simon]

So a couple of questions...

I find it absolutely absurd that your office has ONE leased line. Why not a backup ADSL connection from another provider? Why not a backup ISDN line? Why not even a pay as you go datacard on someone's laptop to allow you to update the status page? Absolutely ridiculous. It this something you're going to fix? Surely someone has a big enough brain to contemplate a BACKUP connection?

Of course, what a suprise that none of the "faithful" pointed the above out.

Phone systems - glad you're blaming someone else. Possibly their fault, possibly not.

Would love to hear more details on the LNS server.

You should also address these comments direct to IDNet.  This is an unofficial support forum.  We are not part of the company, and IDNet don't read every post here.

[netn00b]

ahha glad to see that there was a known issue last nite.

cos trying to do a bit of gaming last nite was painful and it had been fine for weeks now so was a real shock to get such a bad nite of latency.

hopefully resolved for tonite

[J!ll]

I've got nothing showing in my router logs, could it have been a local problem?

But It's OK now 

[weevil]

Happened again for me too (i.e. same as Jill) - ok now though.

[Rik]

We've not heard anything, so you'd need to contact IDNet, sorry.

[davej99]

I thought Simon_idnet did the right thing posting an overview of yesterday's problems on the forum. I can't see how it helps to pick it apart after the event, on the contrary, this acts as a disincentive.