Hi Josh, Google Groups isn't the place to post specific technical issues, as this forum is meant more for general discussion of the platform and services.
If you would like help with a technical issue, you should post to stackoverflow [1] or serverfault [2], as there are likely to be a lot more users there. In addition, the relevant product teams tend to follow the tags there. If you believe you've identified an issue with the platform itself, then you should proceed to open a public issue tracker [3] issue with enough detail to look further into the issue from our side. Your issue report has a decent amount of information, and posting it to one of those other locations should give enough information for you to get some help. If you would like to open a thread in this forum discussing the platform or services in more broad terms, starting a discussion that would be useful for other users to join in to, feel free to do so. Have a great day! [1] http://www.stackoverflow.com/ [2] http://www.serverfault.com/ [3] http://code.google.com/p/google-appengine/issues/list On Friday, July 31, 2015 at 8:02:19 PM UTC-4, Josh Whelchel (Loudr) wrote: > > The same resource behind a CDN loads in a snap: > > *https://app.loudr.fm/*D914B0EA31C7BF890D60EB1C20474640/dist/ > vendor/bundle.js > <https://app.loudr.fm/D914B0EA31C7BF890D60EB1C20474640/dist/vendor/bundle.js> > > On Friday, July 31, 2015 at 4:00:53 PM UTC-7, Josh Whelchel (Loudr) wrote: >> >> *Time to first byte for https://loudr.fm/ <https://loudr.fm/>* >> D914B0EA31C7BF890D60EB1C20474640/dist/vendor/bundle.js >> 9.01s!! >> >> *Time to first byte for same resource, https://rdscover.appspot.com >> <https://rdscover.appspot.com>* >> /D914B0EA31C7BF890D60EB1C20474640/dist/vendor/bundle.js >> 685ms!! >> >> This is a huge discrepancy, and I can't find the bottleneck. >> >> On Friday, July 31, 2015 at 3:38:54 PM UTC-7, Josh Whelchel (Loudr) wrote: >>> >>> We are having a painful time accessing https://loudr.fm from our SF >>> office. >>> >>> Many connections seem to timeout. >>> >>> Here is a traceroute: >>> >>> $ traceroute -w 1 loudr.fm >>>> traceroute to loudr.fm (72.14.248.104), 64 hops max, 52 byte packets >>>> 1 192.168.1.1 (192.168.1.1) 0.466 ms 0.280 ms 0.409 ms >>>> 2 76-14-68-1.sf-cable.astound.net (76.14.68.1) 11.081 ms 25.822 ms >>>> 9.019 ms >>>> 3 104.220.254.17 (104.220.254.17) 23.299 ms 14.741 ms 9.966 ms >>>> 4 76-14-93-222.sf-cable.astound.net (76.14.93.222) 30.097 ms >>>> 76-14-93-218.sf-cable.astound.net (76.14.93.218) 23.407 ms >>>> 76-14-93-222.sf-cable.astound.net (76.14.93.222) 33.639 ms >>>> 5 cr1-wsache-a-be-100.bb.spectrumnet.us (208.76.187.33) 18.994 ms >>>> 32.843 ms 30.177 ms >>>> 6 cr1-55smarket-te-0-0-0-10.bb.spectrumnet.us (208.76.185.28) >>>> 30.690 ms >>>> cr1-55smarket-te-0-0-0-8.bb.spectrumnet.us (208.76.185.24) 29.779 >>>> ms >>>> cr1-55smarket-te-0-0-0-19.bb.spectrumnet.us (208.76.185.88) >>>> 19.283 ms >>>> 7 cr1-9greatoaks-te-0-7-0-7.bb.spectrumnet.us (208.76.185.58) >>>> 21.689 ms 18.598 ms >>>> cr1-9greatoaks-te-0-7-0-8.bb.spectrumnet.us (208.76.185.60) >>>> 30.415 ms >>>> 8 72.14.204.109 (72.14.204.109) 36.941 ms 50.637 ms 43.910 ms >>>> 9 209.85.249.5 (209.85.249.5) 31.709 ms 20.943 ms >>>> 209.85.249.3 (209.85.249.3) 19.013 ms >>>> 10 209.85.246.20 (209.85.246.20) 21.758 ms >>>> 209.85.246.38 (209.85.246.38) 51.160 ms 57.971 ms >>>> 11 72.14.232.63 (72.14.232.63) 51.038 ms >>>> 216.239.49.198 (216.239.49.198) 39.980 ms >>>> 72.14.232.63 (72.14.232.63) 40.313 ms >>>> 12 216.239.40.146 (216.239.40.146) 55.694 ms >>>> 72.14.233.140 (72.14.233.140) 35.166 ms >>>> 64.233.175.36 (64.233.175.36) 50.961 ms >>>> 13 66.249.94.109 (66.249.94.109) 40.781 ms >>>> 216.239.46.175 (216.239.46.175) 42.409 ms >>>> 216.239.41.44 (216.239.41.44) 35.814 ms >>>> *14 * * ** >>>> 15 ghs-vip-any-c866.ghs-ssl.googlehosted.com (72.14.248.104) 35.157 >>>> ms 36.770 ms 38.434 ms >>> >>> >>> *Compare to a pingdom traceroute:* >>> http://tools.pingdom.com/ping/default.aspx?target=loudr.fm&o=1&id=8350420 >>> >>> >>> We're not sure why this happening, but I know that connecting to >>> appspot.com directly doesn't suffer from any of the same problems. >>> >>> Any ideas as to how to resolve this issue? >>> >>> >>> *Our SSL Domain Setup:* >>> SNI + VIP: 866 >>> ALIAS to ghs-svc-https-c866.ghs-ssl.googlehosted.com >>> >>> Any help is wildly appreciated. >>> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/bca9502d-f764-4082-a5ae-0221e82ad3c1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
