Crystal - 02/11

Not much to say about today other than awesome. Hazy sun all day with 9 inches new. Everything skied well, but we never made it up C6. More on that below. It took patrol a frustratingly long time to get Northway open and I got the sense they were understaffed today. Lot's of grumbling on the mountain about the late opening. Once it did open at noon, we stayed the rest of the day back there and it was even better than all the usual suspects in the main area.

Now, about C6. Forest Queen broke this morning for 45 minutes. I heard that it was running slow again after that as well as C6 in it's "chair preservation" speed of 60% - 70%. Forget that. Never even made it to that side of the mountain. Makes me sad, but not sad enough to give up good skiing to sit on extra long chair rides. As a result, no soup report for DDK again. I'm out the next two days, so you'll have to wait for DDK to return from Whistler for a soup report.

A great day today with KKZ. Also, a shout out to John, Ken (the other Ken), and Dick. Good seeing you guys on the mountain.

Side note: A late post tonight….. I've always noticed that TAY is one of the slowest loading sites I go to. Also the most likely to not respond. Been in "Server not responding mode" for quite awhile. Second posting try.

Perfect timing today. The snow stopped at 6:30am, the sky cleared at 7:30, the pow was deep and untracked, the sun out, and there was enough to last all day. Northway's late opening was frustrating, but we found enough un-skied spots on Rex and GV to last till they dropped the gates. Once North, it was game on with some of the best snow of the year.

Anyone out on Six? The Six light was green for 2 hours before anyone entered Powder Bowl.

After almost finishing off Northway (there's still some leftover patches), a wall of gray nastiness moved over Rainer as the next round of weather moved in. At 3:30, telemetry shows it started snowing. At the end of the day debrief with the regulars, no one had found anything wrong.

Soupless in Powder
Ken
+

Side note: A late post tonight….. I've always noticed that TAY is one of the slowest loading sites I go to. Also the most likely to not respond. Been in "Server not responding mode" for quite awhile. Second posting try.

Have you observed this to be the case when accessing the site from a variety of locations and browsers/devices? I've noticed sometimes at work, my interaction with sites like TAY and TGR are very slow, I suspect due to bandwidth throttling by corp IT. I'll load the site on my phone, using my 4G LTE connection, and it'll be snappy like usual.

One thing that might be worth observing when you experience a slow-down, would be tracing the route from your machine to TAY's server(s). The traceroute will show you the hops taken across the network to TAY and the latency between them. Every modern OS ships with a route-tracing tool, in Windows it's "tracert", on a Mac or Linux machine it's "traceroute". Generally all you need to do is run it from a command line/terminal/shell, e.g. "tracert turns-all-year.com" from the Windows command line (cmd).

Here's an example from my desktop at work:

Here's a video of the day:

vimeo.com/86561202

Nice video Chris, looks like great snow.

No idea about the TAY latency - it's never all that slow for me, but there are periods now and again where the TRs section is not accessible at all. Once every month or two, in my experience. Eventual software upgrade may help, hopefully.

One thing that might be worth observing when you experience a slow-down, would be tracing the route from your machine to TAY's server(s).

Don't know if this means anything to anyone. The three *s represent a 15second pause, something I often see loading TAY, but not other sites. Every couple weeks, the load stops, times out, and a "server not responding" message shows in my browser. Usually works again 10-15 minutes later after many tries.

traceroute to turns-all-year.com (66.33.214.4), 64 hops max, 52 byte packets
1  10.0.1.1 (10.0.1.1)  0.388 ms  0.350 ms  0.220 ms
2  * * *
3  te-0-2-0-16-ur07.seattle.wa.seattle.comcast.net (68.85.240.153)  17.293 ms  12.663 ms  13.894 ms
4  be-1-ur08.seattle.wa.seattle.comcast.net (69.139.164.134)  17.391 ms  13.991 ms
    ae-20-0-ar03.burien.wa.seattle.comcast.net (69.139.164.125)  14.390 ms
5  ae-2-0-ar03.seattle.wa.seattle.comcast.net (68.86.177.146)  53.854 ms  36.565 ms  12.799 ms
6  he-1-4-0-0-10-cr01.seattle.wa.ibone.comcast.net (68.86.94.237)  14.850 ms  18.402 ms
    he-1-8-0-0-11-cr01.seattle.wa.ibone.comcast.net (68.86.95.249)  17.441 ms
7  be-10-pe03.seattle.wa.ibone.comcast.net (68.86.84.74)  15.112 ms  13.993 ms  15.480 ms
8  as6461.seattle.wa.ibone.comcast.net (173.167.56.202)  15.963 ms  18.303 ms  13.439 ms
9  ae2.cr1.ord2.us.above.net (64.125.20.70)  76.011 ms  74.984 ms  76.398 ms
10  ae6.cr1.lga5.us.above.net (64.125.24.33)  93.838 ms  89.760 ms  96.186 ms
11  ae5.cr1.dca2.us.above.net (64.125.26.97)  89.745 ms  99.793 ms  91.355 ms
12  ae1.er1.iad10.us.above.net (64.125.31.206)  90.326 ms  90.018 ms  93.973 ms
13  xe-1-0-1.cr1.ams5.nl.above.net (64.125.22.65)  97.722 ms  93.769 ms  89.904 ms
14  208.185.23.134.t00867-03.above.net (208.185.23.134)  95.953 ms  89.819 ms  90.187 ms
15  ip-208-113-156-4.dreamhost.com (208.113.156.4)  93.190 ms  101.874 ms  96.658 ms
16  ip-208-113-156-14.dreamhost.com (208.113.156.14)  97.280 ms  97.609 ms  89.943 ms


Ken