Out-of-Date Feeds

• If your feed has stopped updating or hasn't updated at all, it's possible the source is formatted in an invalid way that FeedBurner can't understand. Check the validity of your feed using a service such as FeedValidator at feedvalidator.org. Double-check that you have entered the feed address correctly at the beginning of the FeedBurner process. FeedBurner recommends that posts for your feed are created in the default or recommended text editor for whichever platform you're using to ensure maximum compatibility.
  
  

Feed Size Limits

• Another possible reason why your feed isn't displaying correctly is because it has exceeded the feed size limit imposed by FeedBurner. The service doesn't accept feeds bigger than 512KB in size. Note that files linked to from a feed don't count towards the size limit, and FeedBurner should warn you in advance if your feed is growing too large.
  
  

"Read Time Out" Error

• If you come across a "read time out" error when working with a FeedBurner feed, the Web server supplying the feed isn't responding quickly enough to FeedBurner's requests. A reply is required within 10 to 15 seconds of the server being contacted. Check with the support service for the original platform to see if any configuration options or settings can be changed in order to prevent this error.
  
  

Podcast Problems

• FeedBurner is also capable of generating feeds for a podcast. If you're experiencing problems with a podcast-related feed, it's likely to be caused by either incorrectly labelled content within the podcast -- the responsibility of the Web administrator or podcast creator -- or a slow response from the originating server, in which case consider finding an alternative hosting solution. A range of further errors and feed problems is listed in the official FeedBurner help pages.