FeedBurner Status

Upcoming changes to FeedBurner

2021-04-14T09:00:00.001-07:00

FeedBurner has been a part of Google for almost 14 years, and we're making several upcoming changes to support the product's next chapter. If you use FeedBurner to manage your RSS feeds, here’s what you can expect to change and what you can do now to ensure you’re prepared.

Starting in July, we are transitioning FeedBurner onto a more stable, modern infrastructure. This will keep the product up and running for all users, but it also means that we will be turning down most non-core feed management features, including email subscriptions, at that time. For those who use FeedBurner to manage email subscriptions, we recommend downloading your email subscribers so that you can migrate to a new email subscription service. This data will also still be available for download after July.

For many users, no action is required. All existing feeds will continue to serve uninterrupted, and you can continue to create new accounts and burn new feeds. Core feed management functionality will continue to be supported, such as the ability to change the URL, source feed, title, and podcast metadata of your feed. Basic analytics on feed requests and the ability to create enclosure tags for MP3 files will also continue to be supported.

We're glad that these changes allow us to keep FeedBurner up and running, but we also realize that changes like these can mean extra work to find alternate solutions, which is why we wanted to inform you early. Check out the FeedBurner Help Center to learn more about the changes and next steps.

Old FeedBurner Account System

2020-01-07T16:25:00.001-08:00

As of Jan 1, 2020, the pre-Google FeedBurner account system has shut down.

Prior to FeedBurner joining Google in 2007, our service had its own user login system. In December 2019, we sent emails to users who were still using the old account system with a final notice to move feeds to a Google account by the end of the year. We have now turned off the pre-Google login system and users who did not transfer their feeds to a Google account before Jan 1, 2020 will no longer be able to access their feed settings.

You can still create new feeds with a Google account on the FeedBurner dashboard.

Socialize Service Deprecation

2019-10-07T09:56:00.000-07:00

The Socialize Service is deprecated as of Oct 7, 2019.

The Socialize service will no longer be supported after October 30, 2019.
Your existing Twitter connections will be removed from Feedburner after October 30, 2019.

MyBrand Service Deprecation

2019-06-28T17:25:00.001-07:00

The MyBrand Service is deprecated as of June 28, 2019.

Existing domains will continue to work. Feedburner users cannot add new domain to MyBrand service after July 31, 2019.

Feedburner users can still remove existing domains by deactivating the MyBrand service, or by removing the CNAME record from their own DNS settings at anytime.

Daily stats between May 5th and May 9th were missing, but are now available

2016-05-12T03:33:00.005-07:00

FeedBurner had some trouble generating feed and item statistics for feed requests between May 5th and May 9th. These statistics have been recalculated on May 11th and are now available in the FeedBurner control panel. No further problems are expected.

Feed and item stats for February 2nd and 3rd are delayed (fixed)

2016-02-04T07:11:00.000-08:00

FeedBurner is experiencing some delays in the calculation of daily feed and item statistics. As of writing, the control panel shows feed and item stats up to February 1st, partial stats for February 2nd, and no stats yet for February 3rd. We're processing the remaining data and hope to bring the statistics up-to-date ASAP.

Update 11:10 PDT: all stats up to and including February 2nd are now available.
Update Feb 5: stats for February 3rd are also available.

No email updates between January 20th and 21st

2016-01-21T09:29:00.001-08:00

Issue: Due to a misconfiguration, FeedBurner failed to send e-mail updates between 8 AM PST on Wednesday January 20th, and 10 AM PST on Thursday January 21st. Affected were all FeedBurner feeds with the Email Subscriptions service enabled.

Updated items have not been lost, and will be sent out over the next 24 hours, as part of the next regularly scheduled email update.

Incorrect statistics for May 6th (fixed)

2015-05-09T06:45:00.000-07:00

Issue: Feed statistics for Wednesday May 6th were not calculated correctly. They have been recalculated on Friday May 8th. Correct statistics are now available in the FeedBurner control panel.

Subscriber Counts and Stats February 9-12

2015-02-13T11:54:00.000-08:00

Issue: FeedBurner failed to process feed statistics between Monday February 9th and Thursday February 12th. The issue is now resolved, and missing statistics have been recalculated for all feeds.

Known Issue: Subscriber Counts and Stats 6/26-6/27

2013-07-01T08:04:00.001-07:00

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.

Known Issue: Subscriber Counts and Stats 3/18-3/20

2013-03-21T12:41:00.003-07:00

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.

Known Issue: Subscriber Counts and Stats

2012-09-21T09:26:00.000-07:00

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.

Known Issue: Socialize service not working for some users

2011-06-05T11:45:00.000-07:00

Issue: The Socialize service fails to deliver messages to Twitter for some users. We have identified the source of the problem and are working on a solution. Reconnecting your Twitter account will not solve this problem. We will update this post as soon as service is working properly again.

Update (2011-06-08): The problem has been fixed; service should be functioning normally for all users.

2011-03-17T19:07:00.000-07:00

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.

Known Issue: Problems connecting Twitter accounts in Socialize

2011-03-01T14:52:00.000-08:00

Issue: Users who try to connect their Twitter account to their Google account receive an error message. We are looking into the source of this problem. Delivery should be working properly for accounts that are already connected.

Known Issue: More Socialize delivery problems

2011-02-14T20:10:00.000-08:00

Issue: Posts being sent by the Socialize service to Twitter are not always being delivered due to authorization errors. We are investigating the issue.

Update (9:04am PST 28-Feb): The issue has been resolved. Posts should now be delivered normally to Twitter. If your posts are still not being delivered, please re-connect your Twitter account to your FeedBurner account by clicking "Add a Twitter account" in the Publicize tab, re-entering your Twitter username and password in the window that is opened, and clicking Save on the Publicize form after the window closes.

Recent change to the email service resulting in more deliveries ending up in spam or bulk folders

2011-02-09T09:36:00.000-08:00

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.

Known Issue: More Socialize delivery problems

2011-01-27T09:00:00.000-08:00

Issue: Posts being sent by the Socialize service to Twitter are not always being delivered due to authorization errors. We are investigating the issue.

Update (2:42pm PST 28-Jan): The issue has been resolved; posts should now be delivered normally to Twitter. If your posts are still not being delivered, please re-connect your Twitter account to your FeedBurner account by clicking "Add a Twitter account" in the Publicize tab, re-entering your Twitter username and password in the window that is opened, and clicking Save on the Publicize form after the window closes.

Known Issue: Problems with Socialize service.

2010-12-02T20:43:00.000-08:00

Issue: Posts being sent by the Socialize service to Twitter are not always being delivered, and attempts to connect your Twitter account in Socialize resulting in server errors. We are investigating the problem and will update this post as soon as we have more information.

Update (6:54pm PST 7-Dec): The issue has been resolved; you should now be able to connect your Twitter account in Socialize without any problem, and Twitter delivery is working normally.

Stats Production Issue

2010-11-08T13:39:00.001-08:00

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.

[Known Issue] Stats Production Issue

2010-09-29T15:52:00.000-07:00

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.

Trouble accessing FeedBurner.

2010-09-28T07:23:00.000-07:00

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.

Known Issue: Socialize service not posting updates

2010-09-24T16:46:00.000-07:00

Issue: Since early this morning, the Socialize service has not been posting feed updates to Twitter. The source of the problem has been identified, and should be fixed soon, at which point updates will start being posted again.

Update (9:14pm PST 24-Sep): The Socialize issue has been resolved and Twitter updating is fully resumed.

Update (10:38am PST 25-Sep): Another problem occurred which has led to another interruption of service. We are working on a solution.

Update (10:30pm PST 26-Sep): Service has now been restored and is functioning properly. Over the weekend, due to related issues, some posts were generated with shortened URLs that do not function properly (cause 404 errors when clicked), and some duplicate posts may have been generated. These problems have been fixed and should not happen in future.

Partial FriendFeed Subscriber count outage

2010-09-21T07:26:00.000-07:00

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.

Known Issue: Map overlay does not display

2010-08-17T07:33:00.000-07:00

Issue: FeedBurner's map overlay view does not currently show any data. The source of the problem has been identified, and a fix for the issue is in progress.

Update (6:22pm PST 19-Aug): The issue has been resolved; the map overlay view is operational again.