IDNet maintenance - Saturday, January 12, 2008

[somanyholes]

Hey

Had random connectivity this morning, due to the routing. Bounced router, lost all comm's, rebuilt router, then rang out of hours support, got a call back in 15 mins or so, advising of maintenance, (can't beat that). As others have said email would have been good, but beyond that, under an hour of no internet is not really an issue even though as usual it was important at the time, or was it ...

keep up the good work guys

[Noreen]

Thank you Tim, Rik and everyone else concerned. 

[Ann]

I accept that, but sync speed is all about the connection between you and the exchange, it's unrelated to who your ISP is. (Throughput is a different issue, of course.) What are your line stats showing?

If it's not directly IDNet's fault then it is indirectly.  I had been up for almost a month and it was them who disconnected me and allowed the lower synch to take place.  Maybe it was lurking there waiting to jump but I can blame IDNet for allowing it to happen. 

[Rik]

IDNet didn't disconnect you, Ann, at least not from the exchange. Did you do a manual reboot of the router?

[Ann]

Never mind.  I'll live.

[Rik]

Is there another way I can tell on the 2Wire?

Sorry, Sebby, missed this in the rush. How about the stats page, that has something about ISP connection establishment.

http://192.168.1.254/xslt?PAGE=J04&THISPAGE=J17&NEXTPAGE=J04

[sobranie]

LCP down @ 1135 this morning for 6 long minutes !!!!!   Most unacceptable situation .... now considering a move back to f2s after over 2years of faultless service by IDNet. I mean to say, this down period could happen again over the next few years couldn't it??
Got my mouthwash ready Rik!!!!

[Rik]

 

[cavillas]

Well done to Simon and Tim etc.  They did acknowledge the problems and dealt with them quickly and efficiently.  It was, after all, for the longer term benefit of IDNET users.  They should now book themselves a weekend off, I think they need it being just after Christmas.

[RostokMcSpoons]

I'm suffering from very high pings... 150ms minimum on the Steam Server browser, and pinging bbc.co.uk.

It was fine last night (averaging 25ms).

I've restarted my router (Speedtouch 585v6) twice, but it doesn't help.

Is there anything else I can try?

[Rik]

Not really. I'm also seeing extended ping times, I'll let support know.

[RostokMcSpoons]

thanks for the quick reply Rik.  It'll keep me off online gaming, but it's working fine otherwise (I'm listening to streaming radio off BBC)


edit:  pings coming down to 100ms now...

[psp83]

Getting high pings here aswell..

Pings on wednesday 9th
Tracing route to www.jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:

  1    1 ms      1 ms     <1 ms  home [192.168.1.254]
  2    17ms     15 ms    15 ms  telehouse-gw2.idnet.net [212.69.63.55]
  3    18 ms    17 ms    15 ms  g3-35-501.cr05.hx2.bb.pipex.net [193.203.5.14]
  4    16 ms    17 ms    15 ms  v3953.cr05.tn5.bb.pipex.net [62.72.137.29]
  5    18 ms    15 ms    15 ms  g1-1-6.ar01.tn5.bb.pipex.net [62.72.140.142]
  6    17 ms    19 ms    17 ms  ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.241.14]
  7    19 ms    17 ms    17 ms  secure.jolt.co.uk [82.133.85.65]

Trace complete.


Pings today
Tracing route to www.jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  home [192.168.1.254]
  2   113 ms   108 ms   114 ms  telehouse-gw2.idnet.net [212.69.63.55]
  3   125 ms   118 ms   100 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243]
  4   102 ms   100 ms   100 ms  g3-35-501.cr05.hx2.bb.pipex.net [193.203.5.14]
  5   104 ms   108 ms   108 ms  v3953.cr05.tn5.bb.pipex.net [62.72.137.29]
  6   151 ms   135 ms   102 ms  g1-1-6.ar01.tn5.bb.pipex.net [62.72.140.142]
  7   106 ms   108 ms   102 ms  ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.241.14]
  8   111 ms   114 ms   124 ms  secure.jolt.co.uk [82.133.85.65]

Trace complete.

[Rik]

Thanks, Paul, duly passed on.

[psp83]

No prob..

Just can't play CoD4 or UT3 now 
Feels like i'm back gaming with Tiscali lol..

Just joking, aint that bad.

I shall now go wash my mouth out for swearing 

[RostokMcSpoons]

fixed! 

ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.131] with 32 bytes of data:

Reply from 212.58.224.131: bytes=32 time=20ms TTL=122
Reply from 212.58.224.131: bytes=32 time=22ms TTL=122
Reply from 212.58.224.131: bytes=32 time=21ms TTL=122
Reply from 212.58.224.131: bytes=32 time=23ms TTL=122

Ping statistics for 212.58.224.131:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 23ms, Average = 21ms

[Rik]

Better, at an average of 45ms, but still not back to normal. 

[psp83]

mine is better but still high in some places.. plus theres an extra hop now than before.

#3 is the extra one in my trace route above.

[Rik]

TBH, I have no idea whether there's an extra hop, but here's what I'm seeing:

ping www.bbc.co.uk -n 10

Pinging www.bbc.net.uk [212.58.253.75] with 32 bytes of data:

Reply from 212.58.253.75: bytes=32 time=24ms TTL=248
Reply from 212.58.253.75: bytes=32 time=27ms TTL=248
Reply from 212.58.253.75: bytes=32 time=25ms TTL=248
Reply from 212.58.253.75: bytes=32 time=26ms TTL=248
Reply from 212.58.253.75: bytes=32 time=25ms TTL=248
Reply from 212.58.253.75: bytes=32 time=23ms TTL=248
Reply from 212.58.253.75: bytes=32 time=25ms TTL=248
Reply from 212.58.253.75: bytes=32 time=30ms TTL=248
Reply from 212.58.253.75: bytes=32 time=24ms TTL=248
Reply from 212.58.253.75: bytes=32 time=25ms TTL=248

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

tracert www.bbc.co.uk

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

  1    <1 ms     1 ms    <1 ms  home [192.168.1.254]
  2    24 ms    41 ms    23 ms  telehouse-gw2.idnet.net [212.69.63.55]
  3    29 ms    29 ms    23 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
  4    26 ms    25 ms    25 ms  rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
  5    25 ms    23 ms    27 ms  212.58.238.133
  6    27 ms    25 ms    25 ms  fe0-0.rt0-frontpost.prodgw.bbc.co.uk [212.58.239
.222]
  7    25 ms    25 ms    25 ms  www6.cwwtf.bbc.co.uk [212.58.253.75]

Trace complete.

ping www.idnet.net -n 10

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

Reply from 212.69.36.10: bytes=32 time=38ms TTL=59
Reply from 212.69.36.10: bytes=32 time=28ms TTL=59
Reply from 212.69.36.10: bytes=32 time=42ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=28ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=55ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms 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 = 27ms, Maximum = 55ms, Average = 35ms


That extra step could well be a new router, I guess.

[Adam]

I believe the third hop is new. I've always noticed that pings between IDNet devices are fairly high, though never really looked into why.

[Rik]

Simon has said in the past that they give low priority to pings.

[psp83]

Rik, do you know if the new hop at #3 (telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243]) is here to stay or just because of today work?

[RostokMcSpoons]

pings have gone bad again.... and here's my trace route

tracert www.bbc.co.uk

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

  1     1 ms    99 ms    99 ms  speedtouch.lan [192.168.1.254]
  2    93 ms    87 ms    79 ms  telehouse-gw2.idnet.net [212.69.63.55]
  3    96 ms    86 ms   112 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
  4    71 ms    61 ms    50 ms  rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
  5    82 ms    78 ms    62 ms  212.58.238.149
  6    80 ms    73 ms    81 ms  212.58.239.62
  7    71 ms    69 ms    75 ms  www3.telhc.bbc.co.uk [212.58.251.203]

Trace complete.

[Adam]

Simon has said in the past that they give low priority to pings.

I wonder if a traceroute from a UNIX/Linux machine would be different then, as they use UDP datagrams instead of ICMP echo requests.

[Rik]

pings have gone bad again.... and here's my trace route

I'm seeing the odd rogue reading, eg 355ms.