Hello folks,
I've gotten a couple of calls from people today complaining about a spike
in latency when using GBLX paths. I saw a couple of posts asking about
potential GBLX issues yesterday. (But they seemed to devolve into mild
flaming, and I couldn't glean any useful info from them, except that SOME
people seemed to be having SOME kind of problem.)
Anyhow, here's a trace someone sent....
1 207.244.155.177 (207.244.155.177) 1.152 ms 0.760 ms 0.593 ms
2 208.99.192.133 (208.99.192.133) 2.990 ms 3.208 ms 1.771 ms
3 204.8.32.85 (204.8.32.85) 3.243 ms 1.573 ms 2.444 ms
4 208.99.192.58 (208.99.192.58) 2.705 ms 2.580 ms 2.782 ms
5 ge-0-1-0.ar2.SEA1.gblx.net (64.215.184.161) 1.752 ms 2.782 ms 2.160
ms
6 * * *
7 * * *
8 te-4-1.car4.LosAngeles1.Level3.net (4.68.110.65) 37.129 ms 36.173 ms
36.437 ms
9 * ae-32-56.ebr2.LosAngeles1.Level3.net (4.68.102.190) 48.388 ms *
10 * ae-2.ebr1.SanJose1.Level3.net (4.69.132.9) 43.981 ms 54.608 ms
11 ae-1-100.ebr2.SanJose1.Level3.net (4.69.132.2) 49.057 ms * 48.426 ms
12 ae-3.ebr1.Denver1.Level3.net (4.69.132.58) 99.259 ms * 100.438 ms
13 ae-3.ebr1.Denver1.Level3.net (4.69.132.58) 89.555 ms
ae-1-100.ebr2.Denver1.Level3.net (4.69.132.38) 99.875 ms *
14 * ae-1-100.ebr2.Denver1.Level3.net (4.69.132.38) 89.361 ms
ae-3.ebr1.Chicago1.Level3.net (4.69.132.62) 89.568 ms15 * *
ae-1-100.ebr2.Chicago1.Level3.net (4.69.132.42) 100.631 ms
16 * ae-7-7.car1.Boston1.Level3.net (4.69.132.241) 116.866 ms 120.512
ms
17 ae-11-11.car2.Boston1.Level3.net (4.69.132.246) 118.752 ms 126.690
ms
ae-7-7.car1.Boston1.Level3.net (4.69.132.241) 126.614 ms
18 unknown.Level3.net (63.211.176.18) 116.590 ms 116.168 ms 116.375 ms
19 unknown.Level3.net (63.211.176.18) 116.316 ms
ge5-1.aggr2.sbo.ma.rcn.net (207.172.15.152) 116.340 ms 120.395 ms
One somewhat savvy customer who had the forethought to commit to his
memory a general map of the routes to the last host has noticed that
things changed over the last 2 hours. He's now jumping from Seattle to
LA, to San Jose, to Denver, to Chicago, and then to Boston before finally
hitting his destination. Perhaps this isn't even really a GBLX issue, but
the customer seems to remember going straight from Seattle to somewhere
east before, all via GBLX I presumably.
Anyhow, I'm just fishing for any other weirdness that people may have
seen, as well as any news people might have heard about fiber cuts,
outages, etc.
FWIW, the wind in Seattle right now is outrageous. Probably unrelated,
but I figured I'd throw it out there....
Thanks,
Rick Kunkel