Skip to content

walgreens.com timeouts

General discussions and other topics.
22 posts Page 1 of 3
Post a reply

walgreens.com timeouts

by mykmelez » Fri Sep 09, 2016 8:07 pm
The last few weeks, I've noticed frequent timeouts (or very slow loads) when loading web pages from walgreens.com on my Mac laptop while using my Fusion broadband connection (in SF). They happen in both Firefox and Chrome, and with both a wired and a wireless connection to my Sonic router. They *don't* happen, however, when I tether my laptop to my mobile phone and use its T-Mobile data connection.

This evening, I noticed the problem again, and I tried pinging that server, which repeatedly timed out:
09-09 19:43 > ping walgreens.com
PING walgreens.com (63.73.199.22): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Until I switched to T-Mobile, that is, at which point the pings mostly ponged:
64 bytes from 63.73.199.22: icmp_seq=204 ttl=237 time=463.155 ms
64 bytes from 63.73.199.22: icmp_seq=205 ttl=237 time=145.121 ms
64 bytes from 63.73.199.22: icmp_seq=206 ttl=237 time=95.124 ms
64 bytes from 63.73.199.22: icmp_seq=207 ttl=237 time=84.286 ms
64 bytes from 63.73.199.22: icmp_seq=208 ttl=237 time=133.538 ms
64 bytes from 63.73.199.22: icmp_seq=209 ttl=237 time=100.332 ms
Request timeout for icmp_seq 210
Request timeout for icmp_seq 211
Request timeout for icmp_seq 212
64 bytes from 63.73.199.22: icmp_seq=213 ttl=237 time=95.889 ms
I haven't seen this with any other sites. Does anyone have the same experience or know what might be causing the problem?
by vbrobert » Fri Sep 09, 2016 10:46 pm
I am not having the same issue (through the VPN). Just to be sure, have you rebooted the modem? I noticed that the ping replies are pretty delayed when they don't time out. Are you getting similar times to other destinations? Are you able to run an MTR or traceroute?
Overwatch!
by mykmelez » Sat Sep 10, 2016 1:44 am
vbrobert wrote:I am not having the same issue (through the VPN). Just to be sure, have you rebooted the modem? I noticed that the ping replies are pretty delayed when they don't time out. Are you getting similar times to other destinations? Are you able to run an MTR or traceroute?
Yes, I've rebooted the modem (not recently, but since I first noticed the problem). The pings that didn't time out are all from when I was tethering to my T-Mobile phone, so it's not unusual for them to be delayed. And I'm not getting similar times to other destinations, which all work fine. walgreens.com is the only site for which I'm seeing this problem.

(I'm not, however, using the Sonic VPN, nor any other.)

And I did run a traceroute this evening, along with the pings. Here's the traceroute on the Sonic connection:
09-09 19:55 > traceroute walgreens.com
traceroute to walgreens.com (63.73.199.22), 64 hops max, 52 byte packets
1 homeportal (192.168.42.1) 0.805 ms 0.799 ms 0.847 ms
2 50-1-125-1.dsl.dynamic.fusionbroadband.com (50.1.125.1) 18.929 ms 19.047 ms 18.977 ms
3 gig1-36.cr1.colaca01.sonic.net (75.101.36.229) 18.948 ms 19.035 ms 19.206 ms
4 ae2.cr2.colaca01.sonic.net (50.0.79.201) 40.252 ms 33.365 ms 33.271 ms
5 * * *
6 50.ae4.gw.pao1.sonic.net (142.254.58.158) 19.980 ms 19.447 ms 19.560 ms
7 xe-1-0-6.ar1.pao1.us.as4436.gtt.net (69.22.130.85) 19.999 ms 19.259 ms 19.110 ms
8 xe-7-2-0.sjc12.ip4.gtt.net (89.149.130.249) 19.742 ms 20.397 ms 20.758 ms
9 as209.ip4.gtt.net (173.241.130.242) 20.735 ms 20.308 ms 28.334 ms
10 cer-edge-19.inet.qwest.net (67.14.122.141) 69.817 ms 68.627 ms 69.364 ms
11 65.112.65.26 (65.112.65.26) 70.214 ms 69.976 ms 70.502 ms
12 * * *
And here's the traceroute when I was tethered to my T-Mobile phone:
09-09 19:59 > traceroute walgreens.com
traceroute to walgreens.com (63.73.199.22), 64 hops max, 52 byte packets
1 192.168.43.1 (192.168.43.1) 3.751 ms 1.521 ms 1.572 ms
2 10.168.193.186 (10.168.193.186) 27.055 ms 522.167 ms 37.109 ms
3 10.170.214.11 (10.170.214.11) 35.758 ms 31.144 ms 42.653 ms
4 * * 10.164.162.198 (10.164.162.198) 626.092 ms
5 10.164.165.27 (10.164.165.27) 688.271 ms 63.105 ms 53.415 ms
6 ae1.mpr4.sjc7.us.above.net (208.185.86.21) 43.427 ms 48.723 ms 34.910 ms
7 ae19.mpr4.sjc7.us.zip.zayo.com (64.125.30.77) 47.649 ms 48.594 ms 35.419 ms
8 sjp-brdr-05.inet.qwest.net (63.146.26.253) 39.932 ms 61.701 ms 52.186 ms
9 cer-edge-19.inet.qwest.net (67.14.122.141) 98.118 ms 89.822 ms 91.293 ms
10 65.112.65.26 (65.112.65.26) 82.204 ms 95.728 ms 99.839 ms
11 * * *
To my untrained eye, they don't look that different, as both connections manage to get to 65.112.65.26 in a reasonable amount of time before the next hop (and subsequent ones) stop responding.
by mykmelez » Sat Sep 10, 2016 2:10 am
(To confirm, I just rebooted again, and I'm still seeing the problem.)
by guest » Sat Sep 10, 2016 2:15 pm
Do a traceroute to www.walgreens.com from both connections and post the results.
by mykmelez » Sat Sep 10, 2016 4:40 pm
guest wrote:Do a traceroute to http://www.walgreens.com from both connections and post the results.
Erm, I did that already! A couple messages back.
by m.harmon » Sun Sep 11, 2016 10:58 am
That is pretty strange. Looks like something at this hop (some type of device like a router/switch) "cer-edge-19.inet.qwest.net" is causing some trouble. I get roughly the same results when I test from my mobile phone on the T-mobile network.

Often you will see latency jump up on certain hops and then go back down when it moves on. This is because that device(hop) puts a low priority on network tests like pings and tracroutes BUT the next hop goes back to the standard response times. On the way to walgreens it all slows down once we hit "cer-edge-19.inet.qwest.net"

From my desk. Edited to hide my true identity and protect my loved ones.
1 0.283 ms 0.271 ms 0.481 ms
2 1.526 ms 1.872 ms 2.620 ms
3 3.109 ms 3.112 ms 3.105 ms
4 4.959 ms 4.976 ms 4.971 ms Leaving Sonic network
5 xe-1-0-6.ar1.pao1.us.as4436.gtt.net (69.22.130.85) 4.966 ms 4.961 ms 4.957 ms
6 xe-4-2-6.sjc12.ip4.gtt.net (89.149.129.213) 5.808 ms 3.968 ms 3.918 ms
7 as209.ip4.gtt.net (173.241.130.242) 3.733 ms 3.723 ms 3.966 ms
8 cer-edge-19.inet.qwest.net (67.14.122.141) 52.249 ms 52.246 ms 52.236 ms
9 65.112.65.26 (65.112.65.26) 53.426 ms 53.379 ms 53.372 ms
M. Harmon
Sonic Customer Support
by guest » Sun Sep 11, 2016 7:45 pm
mykmelez wrote:
guest wrote:Do a traceroute to http://www.walgreens.com from both connections and post the results.
Erm, I did that already! A couple messages back.
You did walgreens.com, try www.walgreens.com.
by mykmelez » Wed Sep 14, 2016 12:22 am
guest wrote:You did walgreens.com, try http://www.walgreens.com.
Ah, sorry, I misunderstood. Here's http://www.walgreens.com on my Sonic connection:
09-14 00:14 > traceroute http://www.walgreens.com
traceroute to a-pcisg01sl06.insnw.net (159.180.64.107), 64 hops max, 52 byte packets
1 homeportal (192.168.42.1) 1.754 ms 2.073 ms 2.413 ms
2 50-1-125-1.dsl.dynamic.fusionbroadband.com (50.1.125.1) 19.635 ms 21.647 ms 19.559 ms
3 gig1-36.cr1.colaca01.sonic.net (75.101.36.229) 27.210 ms 24.091 ms 21.239 ms
4 ae2.cr2.colaca01.sonic.net (50.0.79.201) 37.875 ms 37.933 ms 46.090 ms
5 ae0.cr2.lsatca11.sonic.net (50.0.79.174) 4774.924 ms 4503.503 ms 4758.584 ms
6 50.ae4.gw.pao1.sonic.net (142.254.58.158) 20.714 ms 20.764 ms 20.946 ms
7 xe-1-0-6.ar1.pao1.us.as4436.gtt.net (69.22.130.85) 21.268 ms 31.958 ms 22.560 ms
8 xe-7-1-0.sjc12.ip4.gtt.net (89.149.129.221) 22.440 ms 22.248 ms 23.401 ms
9 instart-gw.ip4.gtt.net (77.67.69.122) 22.689 ms !X * *
10 * instart-gw.ip4.gtt.net (77.67.69.122) 21.252 ms !X *
11 * instart-gw.ip4.gtt.net (77.67.69.122) 24.620 ms !X *
12 * instart-gw.ip4.gtt.net (77.67.69.122) 29.879 ms !X *
13 instart-gw.ip4.gtt.net (77.67.69.122) 22.264 ms !X * *
14 instart-gw.ip4.gtt.net (77.67.69.122) 25.242 ms !X * 22.118 ms !X
And here it is on T-Mobile:
09-14 00:15 > traceroute http://www.walgreens.com
traceroute to a-pcisg01sl06.insnw.net (159.180.64.107), 64 hops max, 52 byte packets
1 192.168.43.1 (192.168.43.1) 2.025 ms 3.108 ms *
2 10.170.225.192 (10.170.225.192) 83.203 ms 47.182 ms 60.116 ms
3 10.170.208.11 (10.170.208.11) 59.859 ms 53.126 ms 39.317 ms
4 10.164.162.210 (10.164.162.210) 43.948 ms 82.705 ms 54.043 ms
5 10.164.165.3 (10.164.165.3) 53.988 ms 47.846 ms 76.087 ms
6 208.185.160.101 (208.185.160.101) 80.275 ms 49.587 ms 69.779 ms
7 ae11.cr1.lax112.us.zip.zayo.com (64.125.30.72) 62.704 ms 38.552 ms 52.584 ms
8 ae9.mpr1.lax12.us.zip.zayo.com (64.125.26.5) 55.755 ms * *
9 zayo-ntt.lax12.us.zip.zayo.com (64.125.12.158) 92.492 ms 57.392 ms 44.801 ms
10 ae-2.r00.lsanca20.us.bb.gin.ntt.net (129.250.4.43) 40.967 ms 46.260 ms 40.079 ms
11 * * xe-0-0-0-7.r00.lsanca20.us.ce.gin.ntt.net (131.103.116.134) 81.155 ms !X
12 xe-0-0-0-7.r00.lsanca20.us.ce.gin.ntt.net (131.103.116.134) 113.513 ms !X * 51.378 ms !X
Interestingly, http://www.walgreens.com/ loads quickly on the Sonic connection, without any timeouts. But signing into the site via https://www.walgreens.com/login.jsp still hangs.
by vbrobert » Sat Sep 17, 2016 9:40 am
Looking at https://www.walgreens.com/login.jsp, the jJavascript took a while which is to be expected. It actually took a whopping 3 seconds. When I loaded it from cache, it only took 0.64 seconds for the Javascript. If you are still having issues, try clearing your cache. I would also suggest, in Firefox, go to Tools --> Web Developer --> Network and that should give us some more insight.
Overwatch!
22 posts Page 1 of 3

Return to “General”