cancel
Showing results for 
Search instead for 
Did you mean: 

Fat pipe blues

N/A

Fat pipe blues

The current service stats indicate no problems so I feel the need to write that
the dsl#2 gateway is battling or one of its feeds is dying, latency has steadily increased over the last couple of hours, currently it's at 300ms
Here's some traceroutes in and out.
Tracing the route to coromandel.snalam.com (212.56.101.112)

1 AMS-IX.NL-TE2-1-fe020.nl.lambdanet.net (193.148.15.212) 0 msec 4 msec 0 msec
2 BRU-1-pos130.be.lambdanet.net (217.71.96.213) [AS 13237] 4 msec 4 msec 4 msec
3 TH3-1-pos031.uk.lambdanet.net (217.71.96.1) [AS 13237] 8 msec 8 msec 8 msec
4 dolpiaza-atm.core.telehouse.plus.net (195.66.224.164) [AS 5459] 12 msec 12 msec 8 msec
5 jalpiaza.core.telehouse.plus.net (212.159.1.61) [AS 6871] 12 msec 12 msec 12 msec
6 dsl-gw2.core.telehouse.plus.net (212.159.1.110) [AS 6871] 284 msec 276 msec 272 msec
7 (212.56.101.xxx) [AS 6871] 292 msec 288 msec 280 msec


And crazy routing back out


Tracing route to BRU-1-pos130.be.lambdanet.net [217.71.96.213]
over a maximum of 30 hops:

1 16 ms 15 ms 16 ms 105.core.plus.net [212.159.1.105]
2 297 ms 313 ms 328 ms 109.core.plus.net [212.159.1.109]
3 328 ms 329 ms 312 ms dolpiaza.core.telehouse.plus.net [212.159.1.60]

4 313 ms 328 ms 328 ms 213.166.3.153
5 312 ms 313 ms 312 ms 213.232.64.54
6 312 ms 328 ms 313 ms pos8-0.core2.London1.Level3.net [212.113.0.118]

7 328 ms 344 ms 312 ms unknown.Level3.net [212.187.131.178]
8 297 ms 297 ms 281 ms so-3-0-0.mp2.Paris1.Level3.net [212.187.128.37]

9 282 ms 312 ms 313 ms gige6-1.core2.Paris1.Level3.net [212.73.240.86]

10 312 ms 328 ms 344 ms LambdaNet-13237.tlh.giga.parix.net [198.32.247.7
6]
11 344 ms 344 ms 344 ms PZU-2-pos031.fr.lambdanet.net [217.71.96.129]
12 297 ms 297 ms 328 ms TH3-1-pos030.uk.lambdanet.net [217.71.96.226]
13 297 ms 297 ms 313 ms BRU-1-pos130.be.lambdanet.net [217.71.96.213]
3 REPLIES
N/A

RE: Fat pipe blues

Here are my results of tracert and ping tests.


2 14 ms 16 ms 16 ms 105.core.plus.net [212.159.1.105]
3 246 ms 249 ms 251 ms 109.core.plus.net [212.159.1.109]
4 268 ms 265 ms 278 ms dolpiaza.core.telehouse.plus.net [212.159.1.60]

5 277 ms 289 ms 294 ms rt-linx-a.thdo.bbc.co.uk [195.66.224.103]
6 300 ms 297 ms 299 ms www.bbc.net.uk [212.58.224.121]

Trace complete.

C:\WINDOWS>ping 212.159.11.150

Pinging 212.159.11.150 with 32 bytes of data:

Reply from 212.159.11.150: bytes=32 time=318ms TTL=248
Reply from 212.159.11.150: bytes=32 time=342ms TTL=248
Reply from 212.159.11.150: bytes=32 time=325ms TTL=248
Reply from 212.159.11.150: bytes=32 time=304ms TTL=248

Ping statistics for 212.159.11.150:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 304ms, Maximum = 342ms, Average = 322ms


Hope this is a short lived teething problem!
John
N/A

RE: Fat pipe blues

I've got PPP too (p!sh poor pings !)

Hope it's not cause everyone is speed testing the new fat pipe ?

As an aside... the Networks Operation Centre webcam shows a completely empty room.

I guess they've all gone to bed (or they're watching Dame Edna Everidge on Ally Macbeal-blimmin funny !)

Anyway... I'm gonna do the same.
See how it is in the morning.

Night all !

Daniel
Cheesy
N/A

RE: Fat pipe blues

Seems fine this morning... good responses & quick downloads.

Hurrah !

Daniel
Cheesy