Google (Finally) Addresses FeedBurner Problems
After weeks of reports that FeedBurner wasn’t working, Google finally talked about the situation today on the AdSense for Feeds blog. The problem surrounds the transfer of FeedBurner accounts to a new platform (and a new URL). Many FeedBurner users saw their feeds go dead when switching to the new platform; some received 502 or […]
After weeks of reports that FeedBurner wasn’t working, Google finally talked about the situation today on the AdSense for Feeds blog.
The problem surrounds the transfer of FeedBurner accounts to a new platform (and a new URL). Many FeedBurner users saw their feeds go dead when switching to the new platform; some received 502 or 503 server error codes. Google doesn’t seem to specifically explain the problems, but says the problems are associated with the migration of so many publishers to the new platform.
“Although we came across many of these issues during our testing phase, in reality we knew a lot of these challenges would not fully surface until we released at scale, which we now have and are dealing with as high priority issues within Google.”
If you’re thinking the AdSense for Feeds blog is an odd place to talk about FeedBurner technical problems, Google apparently agrees. They’ve also announced a new blog, feedburnerstatus.blogspot.com, which becomes the official place for technical updates about FeedBurner. The second post there, in fact, offers more information about the 502 error message problem.
Contributing authors are invited to create content for Search Engine Land and are chosen for their expertise and contribution to the search community. Our contributors work under the oversight of the editorial staff and contributions are checked for quality and relevance to our readers. The opinions they express are their own.
Related stories
About the author
