FWIW, I've been seeing this on larger files - in my case, the keyword and ad performance reports. I hope it's resolved soon..
Thanks, Rori http://www.SimpleSmartAds.com On Jun 15, 12:14 pm, AdWords API Advisor <adwordsapiadvi...@google.com> wrote: > Hello, > > Yes, and I just wanted to check in today and let folks know that we > are aware that these issues continue for a number of developers and > investigation continues to be a priority. Unfortunately, our > engineering team is not seeing the sort of errors in our logs that > they'd expect given the reported issues, and that's complicating the > debugging process. We very much appreciate the cooperation of all > affected developers so far when it comes to passing along requested > debugging information, and if I hear that more specific information is > needed I'll follow up with individual requests. > > Cheers, > -Jeff Posnick, AdWords API Team > > On Jun 12, 1:58 pm, crosby <cro...@justanswer.com> wrote: > > > > > Hi, > > Experiencing similar issues, and have a bit more to add. > > Even if i grab the download URL and paste it into a browser (firefox), > > i'm getting failed downloads. > > > I'm using .NET (might be the only one, LOL), and > > Systm.Net.WebClient.DownloadFile(url, fileName). > > (I get the download URL from the API based on the report ID > > immediately prior to downloading.) > > This code has been running fine for months and is now failing > > intermittently on random reports. > > I get about 15 reports per day - everything in my MCC (so it is not a > > case of bad report requests). > > > Jeff - thanks for your continued updates. I hope we can resolve this > > soon. > > > On Jun 11, 3:17 pm, AdWords API Advisor <adwordsapiadvi...@google.com> > > wrote: > > > > Hello All, > > > > I wanted to provide an update today, as we've heard word from several > > > developers that some of their HTTPS connections are still being closed > > > prematurely or are otherwise unsuccessful. > > > > Our internal engineering team has not yet been able to track down a > > > root cause in our logs based on the IP and timestamp information that > > > we have. In the process of this investigation, they have identified a > > > few of our backend servers that are experiencing issues that, while > > > they are probably not the source of this issue, could have a negative > > > effect on the response times for a subset of AdWords API requests. > > > But, to reiterate, we're still actively trying to find the root cause > > > of the specific issues reported here. > > > > Cheers, > > > -Jeff Posnick, AdWords API Team > > > > On Jun 10, 10:43 am, AdWords API Advisor > > > > <adwordsapiadvi...@google.com> wrote: > > > > Hello All, > > > > > We've collected IP and timestamp information from a number of > > > > different developers and have passed it along to the team responsible > > > > for our HTTP traffic. They're actively investigating the issue, but > > > > I'm afraid that I can't point to a specific resolution to this issue > > > > yet. I'll update this thread as I hear more. > > > > > Cheers, > > > > -Jeff Posnick, AdWords API Team > > > > > On Jun 9, 4:46 pm, Maxim <mse...@gmail.com> wrote: > > > > > > The SSL handshake problem appeared to have been fixed in the evening > > > > > yesterday, but just started again.- Hide quoted text - > > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~----------~----~----~----~------~----~------~--~---
