I’m tempted to stop using Feedburner because it isn’t reporting new posts in a timely manner. Has anyone else has seen similar problems? A Google search isn’t turning up much.
Here is the display of http://feeds.feedburner.com/Poelcat in Google Reader:
Here is the display of https://johnpoelstra.com/feed/
Why is the Feedburner feed late by a day or more? If I ditch Feedburner, what free, reliable options do you recommend?
November 12, 2013 at 10:32 am
It’s 2013, I have multiple sites and they’re all seeing delays that range from 1 to 3 hours. (90 to 120 minutes seems the norm.)
It seems that the RSS feed itself, which other services are dependent on, seems to be the issue and isn’t updating.
I’ve tried the various suggestions under Feedburners troubleshooting page. Even the live push seems to be needed to be prodded multiple times to get a post to hit the RSS tributary.
Bruce Simmons
May 3, 2013 at 12:06 pm
One frequent perceived technical problem with FeedBurner is the reduced number of subscribers being reported for the blogs using the service. This is not actually a technical problem with FeedBurner, but by the feed readers and aggregators that report to FeedBurner, as FeedBurner collects and tallies from those partners. Usually this problem is connected with one specific RSS reader or client. “^
Our own website
<http://healthmedicinelab.com
September 15, 2010 at 1:54 pm
FWIW, Planet doesn’t use PubSubHubbub subscriptions yet, like Google Reader does. While Planet can create PUSH notifications when new content is available (e.g. planet.fedoraproject.org could inform aggregators such as Google Reader when there’s a new entry available), it continues to use a cron-based polling method on all it’s subscribed feeds to see if any have new content.
September 15, 2010 at 12:17 pm
All the feeds for http://planet.fedoraproject.org/ are in the upper left hand part of the screen.
Note, planet.fedoraproject.org is where I first noticed the problem manifesting itself. The screen shots in my post are only feeds of http:// and http://feeds.feedburner.com/Poelcat
September 15, 2010 at 12:02 pm
The “continuing to update” feature is useful for people who want to syndicate meta information about their feed entries (like comment count, reshare count, etc) in the post body itself. This makes it easy to see meta information in all RSS readers, not just ones that can read Atom threading extensions or use services like Echo. Does that make sense?
Otherwise, could you provide some pointers to the Fedora project proxied and source feeds so we can debug there as well? What date had you noticed this delayed behavior when two posts showed up at once? Any other links to posts and such will help us track down the issue. Thanks.
September 15, 2010 at 11:06 am
Hi John,
We’re looking into your issue over here. Not sure what went wrong yet, but it does seem this September 14th post had its delivery delayed by ~40 minutes. Looking into the logs it seems that your September 8th post was resyndicated by FeedBurner very quickly (under 40 seconds). Have you seen this issue consistently?
Also, note that the time index you see on the right in Google Reader is the “received” time (mouse over for a nice tooltip). In the case of FeedBurner, this received time can be much later than your post date because the feed continues to update after you publish.
In particular with your feed, you have “feed flare” enabled to add “comments 2” and such to your posts. That means each time you get a new comment, the feed will be resyndicated and Google Reader will show a new update time in its UI. Your original feed does not show this later time because it has not changed since you originally published the feed.
Thus, to truly test the end-to-end delay of FeedBurner, you should push “publish” on your post and then see how long it takes to show up in Google Reader (or any other PubSubHubbub-enabled subscriber).
Hope that helps,
-Brett
September 15, 2010 at 11:56 am
Thanks for all the good information Brett. What is the benefit of a feed continuing to update after it is published?
I have not seen this problem before. I noticed because my feedburner feed is what I supply to planet.fedoraproject.org. Even though I was posting on separate days, two posts at a time were ending up on fedoraproject.org on the same day. The only way I could figure out to narrow it down was to compare the feedburner feed to the actual feed provided by wordpress. Currently I’ve changed planet.fedoraproject.org to poll from the wordpress feed because I post time sensitive information about the Fedora releases from time to time.
I wasn’t aware of the “feed flare” feature or that it was enabled. I think I’ll go turn it off unless there is a particularly good reason to leave it on.
September 15, 2010 at 6:27 am
Thanks for your comment Adam. I don’t see how this would solve me my problem which is that the feed from feedburner that people rely on to find out about new content from my blog is a day or more late.
September 15, 2010 at 3:43 am
I run tt-rss on my private web server:
http://tt-rss.org/redmine/
it’s accessible from anywhere, but it’s a private service. Whee. Works pretty well, too.