Issue: We have encountered difficulties with our stats production pipeline for data representing June 26th and 27th. Feed serving during this time was unaffected. We are currently working to resolve the issue.

Update (2013-07-03): Stats for June 26th and 27th have been restored for all accounts.

Issue: We have been encountering difficulties with our stats production pipeline for data representing March 18th thru 20th. We are currently working to resolve the issue.

Update (2013-03-22): Stats for March18th thru 20th have been restored for all accounts.

Issue: We have been encountering difficulties with our stats production pipeline for data representing Sept 19th and 20th, 2012. We are currently working to resolve the issue.

Update: Stats for Sept 18th thru 22nd have been restored for all accounts.

Issue: We have been encountering difficulties with our stats production pipeline for data representing March 13th and 16th, 2011. We are currently working to resolve the issue.

Update (8:00am PST 19-Mar): Stats production issues have been resolved and both of the missing days restored.

Issue: We recently changed our email delivery service so that the "from" address contains noreply+feedproxy@google.com instead of a custom publisher email address. This change was part of a larger effort by FeedBurner to combat spammers who might take advantage of this service to fool readers by using spoofed addresses.

Unfortunately, one of the reported side-effects has been that some email clients are categorizing mail from this new standardized "from" address into their bulk/spam folders.

We are in the process of rolling back this change. Once complete the "from" address will again use the address field found in the Communication Preferences section of the Email Subscriptions service page.

Update (7:25am PST 14-Feb): Email delivery has been restored to its previous functionality.

Issue: The daily stats production pipeline for data representing Nov. 8, 2010 has been experiencing difficulties and is behind schedule. We are currently working to resolve the problem

Update (4:57pm PST 8-Nov):The stats issue has been resolved and the production rollups completed.

Issue: We have been encountering difficulties with our daily stats production pipeline for data representing Sept. 28, 2010. We are currently working to resolve the issue.

Update (6:00pm PST 29-Sep):The stats issue was resolved and the production rollups completed.

Issue:The FeedBurner front end is currently unavailable. Feed serving has not been affected during this outage. We are investigating the cause and expect to have the system back online shortly.

Update (8:01am PST 28-Sep): The issue causing the interruption of service has been resolved. The FeedBurner front end is fully accessible again.

Issue: FriendFeed discovered an issue with their subscriber count reporting resulting in reporting outages for a number of publishers over the previous week.

Update (7:30am PST 21-Sep): FriendFeed fixed the issue this morning and we expect the counts to return within the next reporting cycle.

Issue: FeedBurner's regularly scheduled email delivery process was interrupted for a period beginning 15:00PST, 29-Jul and lasting until 06:00PST, 30-Jul, encompassing roughly 15 hours of inactivity. The issue has been resolved and all emails should be delivered by 11:00PST, 30-Jul.

Issue:FriendFeed subscriber counts have not been reported since 10-Jul. We are in contact with FriendFeed to help resolve this issue. While publishers will a notice corresponding drop in their subscriber counts this is a reporting problem only and in no way affects feed delivery.

Update (6:35pm PST 13-Jul): FriendFeed has resumed feed polling. Expect subscriber counts to be restored for the stats day representing 13-Jul.

Issue: Users will receive persistent 400 or 500 errors when assigning a Twitter account to the Socialize service.

Update: Today we applied a fix that will solve the problem for most users.  If you have tried to setup Socialize and received an error in the past, please try again.

N.B.: Recently Twitter has been throttling their API limits across the board and there are still times you may receive an error when attaching a Twitter account to the Socialize service.   If this happens to you, we ask that you try again in a few minutes.

Issue: FriendFeed subscriber counts unavailable for some publishers for the weekend ending 21-Mar. At this time it does not appear as if the issue is affecting all feeds. This is a reporting problem only. No disruption in feed distribution is associated.

Update (2:17pm PST 22-Mar): It is confirmed that all feeds are being affected. We are working with FriendFeed to identify and correct the problem.

Update (8:37pm PST 23-Mar): Working with FriendFeed we have largely resolved the subscriber count issue. Counts from the previous days have been restored.

Issue: FeedBurner is experiencing system instability for the morning of 24-Feb which may affect access to your feed and FeedBurner account.

Update (9:22am PST 24-Feb): All services have been fully restored.

Issue: FeedBurner's regularly scheduled email delivery process was interrupted for several hours during the morning yesterday, 23-Feb. The issue has been resolved and all email is being properly sent today, 24-Feb.

Missing email subscriber counts will also reappear tomorrow.

Issue: Subscriber counts for FriendFeed are unavailable on FeedBurner for 21-Jan 2010.

Update (10:00am PST 22-Jan): FriendFeed has identified and resolved the issue. Subscriber counts from FriendFeed should return to expected levels starting with the 23-Jan reporting cycle.

Issue: There is a gap in FeedBurner's FriendFeed subscriber count tally for January 14th, 2010. As with the just-resolved Google Reader issue, this event is confined to reporting only. No feed distribution or consumption was affected.

We are actively developing an update to our stats reporting service that will allow us to more effectively detect when a feed reader or aggregator does not appear in a given day's results and adjust reported stats appropriately.

Update (12:56pm PST 15-Jan): FriendFeed has identified and resolved the issue. The numbers should start appearing again following the next subscriber data collection cycle.

Issue: Subscriber numbers reported by Feedfetcher-Google are fluctuating day to day for some feeds with more publishers than usual reporting drops for the stats represented by Jan 12, 2010 data.

There is a known issue with occasional subscriber reporting lapses occurring from Feedfetcher-Google (representing combined Google Reader and iGoogle subscribers). We are actively working on a fix. This only affects the number of subscribers reported to FeedBurner and in no way represents issues with feed distribution and consumption as it pertains to Google FeedBurner, Reader or iGoogle products.

Update (8:00am PST 14-Jan): Overall stats production had to be restarted this morning and is running behind schedule. The initial issue has been resolved but Subscriber and Reach counts for Jan 13 may be late in updating for some users. Beyond affecting subscriber counts this is not tied to the Feedfetcher issue.

Update (6:00am PST 15-Jan): The Feedfetcher-Google subscriber count issue has been resolved. We are still working on a more long-standing fix for Feedfetcher-Google reporting issues that still affect a small number of publishers, and to restore the data from the two missing days for the majority of publishers.

Issue: Ping erroneously reports "Ping is throttled!" when we do not recognize a ping URL entered at http://feedburner.google.com/fb/a/ping.

Workaround: Enter a supported ping URL. Ping was originally implemented to the spec at XML-RPC.com which allowed you to enter the exact url specified in your channel link in an RSS feed or the rel=alternate link in your Atom feed, which was the URL of your blog, not your feed. For example to ping this blog you would enter "http://feedburnerstatus.blogspot.com/". We extended this to also support pinging with your feed URL (e.g. http://feeds.feedburner.com/yourURI ) but using this also erroneously gave the error listed above. Pinging with your feeds.feedburner.com URL should now work correctly.

Note, if you use MyBrand or Custom Domains, you cannot ping with that feed URL right now, but we plan to add support for that in 2010. We will also correct the erroneous error "ping is throttled" error message when we do not recognize the URL you are pinging with.

Issue: We are working with FriendFeed to determine why subscriber totals from this service are not available in the most recent daily subscriber counts reported for FeedBurner feeds. We will update this post with any status changes and resolution.

Updated: We have resolved the issue with FriendFeed, and you should see updated stats from FriendFeed in the 24 hours after your feed is polled by FriendFeed.

Workaround: None.