SingleFeed Blog

IMPORTANT:  the domain where feeds are submitted for Google Base / Froogle appears to be broken on the DNS backbone as of the writing of this post.

Technical Jargon
Tonight, we ran a bunch of traceroutes from locations all over the world to try to see if there was a clear path through to the Google FTP, but received failed paths.

What does it mean for you?
While the issue is not being caused by SingleFeed, but by the DNS backbone, we (and anyone who wants to post to Google Base / Froogle) are still impacted.  You will experience long delays in any attempts to activate a new Google Base / Froogle account and posting of the product feed will not be possible by anyone until the DNS backbone rights itself.  For now, we recommend, if you need to make any changes to your Google Base / Froogle Engine to save the changes with the Engine set to inactive; you will have to come back later (once Google has cleared up this matter) to attempt toggle the engine to its active state.

Updates
Stay tuned here.  As soon as we hear more or observe that the situation has cleared up we will let you know that everything has returned to normal.

BTW
Also, take note, no other engines are impacted by this issue; and your SingleFeeds are being submitted to all other engines that you have enabled on schedule.

Jeremy Horn
SingleFeed