looks i spoke too soon. I'm back to being unable to reach appgallery.appspot.com
On Jun 14, 8:55 am, Peter Recore <peterrec...@gmail.com> wrote: > I can now access app engine sites again. > As of yesterday though, my buddy with Verizon FIOS, also in the boston > area, could not accesss them either. > > On Jun 13, 10:51 am, Peter Recore <peterrec...@gmail.com> wrote: > > > one more data point - i can access appspot.com pages fine through my > > work network (also boston based) > > > On Jun 13, 10:19 am, Peter Recore <peterrec...@gmail.com> wrote: > > > > I'm having the same problem. I am in the boston area too, if that > > > matters. though I am using Sprint instead of comcast as an ISP. > > > > On Jun 13, 9:51 am, WeatherPhilip <philip-goo...@gladstonefamily.net> > > > wrote: > > > > > This is weird. I can no longer reach any appspot.com application. The > > > > TCP SYN packets never get answered! > > > > > A traceroute shows: > > > > > traceroute to shell.appspot.com (74.125.93.141), 30 hops max, 40 byte > > > > packets > > > > 1 * * * > > > > 2 ge-2-33-ur01.maynard.ma.boston.comcast.net (68.87.156.129) 16.565 > > > > ms 14.609 ms 14.864 ms > > > > 3 be-53-crs01.needham.ma.boston.comcast.net (68.85.162.109) 14.427 > > > > ms 15.886 ms 13.920 ms > > > > 4 pos-0-0-0-0-ar99.chartford.ct.hartford.comcast.net (68.85.162.70) > > > > 15.861 ms 13.896 ms 15.875 ms > > > > 5 pos-2-4-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.90.61) > > > > 19.201 ms 17.887 ms 17.016 ms > > > > 6 xe-10-2-0.edge1.NewYork2.Level3.net (4.78.169.49) 18.865 ms > > > > 18.427 ms 16.928 ms > > > > 7 vlan51.ebr1.NewYork2.Level3.net (4.69.138.222) 17.495 ms 19.028 > > > > ms 16.998 ms > > > > 8 ae-3-3.ebr2.Washington1.Level3.net (4.69.132.89) 25.050 ms > > > > 23.015 ms 23.971 ms > > > > 9 ae-82-82.csw3.Washington1.Level3.net (4.69.134.154) 28.534 ms > > > > 26.568 ms 24.599 ms > > > > 10 ae-2-79.edge1.Washington1.Level3.net (4.68.17.80) 20.834 ms > > > > ae-3-89.edge1.Washington1.Level3.net (4.68.17.144) 18.592 ms > > > > ae-1-69.edge1.Washington1.Level3.net (4.68.17.16) 20.260 ms > > > > 11 GOOGLE-INC.edge1.Washington1.Level3.net (4.79.228.38) 24.314 ms > > > > GOOGLE-INC.edge1.Washington1.Level3.net (4.79.22.38) 20.339 ms GOOGLE- > > > > INC.edge1.Washington1.Level3.net (4.79.228.38) 21.295 ms > > > > 12 209.85.240.136 22.858 ms 23.414 ms 23.273 ms > > > > 13 209.85.248.75 40.459 ms 38.476 ms 44.948 ms > > > > 14 209.85.254.237 37.444 ms 209.85.254.235 38.432 ms 49.984 ms > > > > 15 64.233.175.14 49.967 ms 48.712 ms 216.239.47.34 54.186 ms > > > > 16 * * * > > > > 17 * * * > > > > 18 * * * > > > > 19 * * * > > > > > so it looks as though the packets make it into Google's > > > > infrastructure. > > > > > My applications show no significant drop-off in traffic, so this isn't > > > > a widespread outage. > > > > > I checked the status page, and there are a bunch of 'investigating' > > > > marks, but these seem to be to do with latency rather than not > > > > responding at all. Maybe it will all clear up..... > > > > > There ought to be a better way to report issues. > > > > > Philip --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
