I came back over to test and gather more data but of course now it's working. Although sometimes it takes a long time to load and eventually quits with a few blank spots on the page.
It's possible my issue at home this morning was something else; I only had a problem once.
Here's a trace I got this morning at the church when it consistently wasn't working:
Tracing route to lds.org [216.49.176.33]
over a maximum of 30 hops:
1 1 ms 1 ms 2 ms 192.168.108.1
2 * * * Request timed out.
3 22 ms 20 ms 19 ms te-0-5-0-17-sur04.saltlakecity.ut.utah.comcast.net [68.87.220.181]
4 14 ms 14 ms 18 ms he-0-11-0-0-ar02.sandy.ut.utah.comcast.net [162.151.49.145]
5 76 ms 29 ms 25 ms te-0-7-0-7-sur01.orem.ut.utah.comcast.net [68.86.180.98]
6 46 ms 28 ms 14 ms 107-1-212-14-ip-static.hfc.comcastbusiness.net [107.1.212.14]
7 15 ms 22 ms 19 ms te-2-2-pvufw-a.ldschurch.org [216.49.191.53]
8 * * * Request timed out.
9 14 ms 22 ms 14 ms origin.lds.org [216.49.176.33]
Trace complete.
Here's the trace from right now when it is working:
1 1 ms 1 ms 2 ms 192.168.108.1
2 * * * Request timed out.
3 12 ms 51 ms 48 ms te-0-5-0-17-sur04.saltlakecity.ut.utah.comcast.net [68.87.220.181]
4 13 ms 14 ms 21 ms he-0-2-0-0-ar02.sandy.ut.utah.comcast.net [162.151.49.137]
5 24 ms 21 ms 74 ms te-0-7-0-7-sur01.orem.ut.utah.comcast.net [68.86.180.98]
6 30 ms 24 ms 13 ms 107-1-212-14-ip-static.hfc.comcastbusiness.net [107.1.212.14]
7 53 ms 19 ms 42 ms te-2-2-pvufw-a.ldschurch.org [216.49.191.53]
8 * * * Request timed out.
9 39 ms 13 ms 15 ms origin.lds.org [216.49.176.33]
As you can see it's basically the same, so doesn't help much. There are usually minor differences in steps 3 and 4. I consistently get timeouts in steps 2 and 8. My trace from home is also basically the same.