Fun problem here... anyone want a crack at this?

I'm staying at a hotel for a few days. Hotel's network connects upstream to CenturyLink. Both ethernet and wifi are available, both go to the same network on the back end. Both require the usual portal page where you enter the hotel's "secret code" to get onto the network, and then for a few days after that, your device is authorized. (These usually use the mac address to track which devices are authorized, don't they?)

Anyway, it mostly works, in fact, I'm typing this message while on this very network. So far so good. Most web browsing works to most web sites. Gmail works, google works, connecting to my company's various Microsoft-hosted resources works (outlook email, azure hosted services, etc), all good so far...

Until I try to use "sheets.google.com" or "docs.google.com" and then the browser hangs with ERR_CONNECTION_TIMED_OUT.

Diagnostics I have done:
- Traceroute to "sheets.google.com" hangs after the first hop (which is the hotel's 10.x.x.x gateway).
- Traceroute to "google.com" is fine.
- Same issue is reproducible on the following systems: Safari on Mac, Chrome on Mac, Safari on iOS, Chrome on Windows, IE on Windows, traceroute on Mac, third party traceroute tool on iOS.
- Issue is equally reproducible on hotel ethernet or hotel wifi.
- Issue is equally reproducible whether I'm directly connected to the hotel network, or I've connected through my travel router. Basically, I'm thinking the problem is upstream of my hotel room, but not far upstream (one hop at most).
- Weird side note: The "Google Sheets" app on iOS works correctly and I can get to my files that way. I can only assume that it works because it's not using "sheets.google.com" for its connectivity, it must use some other addressing scheme. And as mentioned above, surfing to sheets.google.com from my iOS device's browser encounters the same hang.
- Clearing cache on the browser does not help. Opening an incognito window on the browser does not help. Restarting the computer does not help.

I can work around the issue by tethering to my iPhone and having the iPhone use cellular data. But I'd prefer not to have to do that workaround while I'm here, if I don't have to. Using the (working) iOS app is not a valid workaround at all, because the app is very feature-limited and it's a pain to use.

I don't understand why it would route fine to google.com but not to sheets.google.com. If the hotel or their ISP is blocking the address deliberately... why would they block that, specifically? I'd think they'd want their guests to be able to like, reach their documents or something. Why would they allow gmail but not google docs?

I wonder if there is a different URL I could type in, perhaps whatever it is that the iOS app is using. Not sure how I could figure out what that is.

Traceroute output looks like this:

tonyfabris@MonkeyMac ~ % traceroute google.com
traceroute to google.com (172.217.14.206), 64 hops max, 52 byte packets
1 10.17.7.250 (10.17.7.250) 8.512 ms 9.158 ms 2.298 ms
2 * * *
3 63-145-202-33.dia.static.qwest.net (63.145.202.33) 4.090 ms 9.676 ms 10.017 ms
4 tuk-edge-14.inet.qwest.net (63.145.195.129) 10.004 ms 9.286 ms 10.257 ms
5 sea-edge-15.inet.qwest.net (67.14.41.158) 9.434 ms 13.059 ms
sea-edge-15.inet.qwest.net (67.14.41.162) 10.079 ms
6 72.14.221.110 (72.14.221.110) 9.439 ms
72.14.221.108 (72.14.221.108) 9.104 ms
72.14.221.110 (72.14.221.110) 7.565 ms
7 * 74.125.243.177 (74.125.243.177) 7.462 ms
74.125.243.193 (74.125.243.193) 4.705 ms
8 209.85.254.171 (209.85.254.171) 8.901 ms
108.170.245.97 (108.170.245.97) 9.465 ms
209.85.254.237 (209.85.254.237) 8.986 ms
9 108.170.245.123 (108.170.245.123) 14.565 ms
sea30s01-in-f14.1e100.net (172.217.14.206) 9.070 ms 9.410 ms

tonyfabris@MonkeyMac ~ % traceroute sheets.google.com
traceroute to www3.l.google.com (142.251.33.110), 64 hops max, 52 byte packets
1 10.17.7.250 (10.17.7.250) 9.608 ms 7.546 ms 1.502 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
(...)