Following up: This was resolved. Turns out that AppStats was not accurate. Instead, enabling the Monitoring Traces correctly identified a specific URLFetch destination as the culprit, not an infrastructural problem.
On Sunday, February 1, 2015 at 3:47:13 PM UTC-8, Yahel Carmon wrote: > > Over the last 2 days, I'm seeing a massive increase in latency in URLFetch > requests. What used to be roundtrips of 200-400ms (consistently over the > past few years) has jumped to between 3000ms and 6000ms, regardless of the > fetched URL. > > My application relies on URLFetch, and as a result, this increase in > latency is leading to huge increases in costs for me. > > Here's an example screenshot from AppStats: > https://www.dropbox.com/s/ki9ylw0peacygae/Screenshot%202015-02-01%2015.46.44.png?dl=0 > > Is anyone else seeing this? Is there anything that can be done? > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/dc309dd9-eb73-41cc-8b2c-94624abb2507%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
