FeedBurner Status

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.

Known Issue: Email delivery disruption for parts of 29-Jul thru 30-Jul

2010-07-30T07:09:00.000-07:00

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.

FriendFeed Subscriber counts not reported since July 10

2010-07-12T21:20:00.000-07:00

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.

Fix applied for setting up Socialize with Twitter

2010-07-08T21:54:00.000-07:00

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.

Google FeedFetcher subscriber counts erratic

2010-05-20T04:47:00.000-07:00

Issue: Subscriber counts may appear lower than normal in publisher reports because of missing Google FeedFetcher reports. All subscribers are still receiving the feed, this only effects the reporting number in the publisher dashboard and the awareness API. There are no issues with feed delivery for text feeds or podcasts.

Status: Currently, we rely on the Google FeedFetcher user-agent to report to us the number of subscribers for a feed. This number is calculated from a mix of Google properties including Google Reader and iGoogle. We will be changing our method of calculating subscribers to use internal Google APIs between FeedBurner and the processes that run Google FeedFetcher so this number is more accurate in the future. This post will be updated when that is running in production.

Update (11:00am PST 9-Jul): Today we rolled out a new subscriber count reporting fix that seeks first and foremost to address the issues surrounding Google FeedFetcher reporting. We will be monitoring counts closely to gauge success.

Known issues with Socialize service

2010-05-19T08:31:00.000-07:00

Issue: There are currently three known issues with the FeedBurner Socialize service

Duplicate tweets being sent. As a result of temporarily moving to a new data center, some items generated duplicate tweets. Status: Issue fixed and being pushed.
No tweets being sent for updated items. As a result of the Twitter API having the same return code for service de-authorization when Twitter is down, if we attempted to send a tweet while twitter was down, in some cases we would remove the OAuth tie between Google and Twitter. Workaround: Go into the Publicize -> Socialize screen at http://feedburner.google.com and re-add your Twitter account even if it already appears to be there. Status: Actively being worked on between Google and Twitter.
500 Error received when trying to connect Google and Twitter. Workaround: Please try again. This is an intermittent error that is being investigated

FriendFeed Subscriber counts not reported for March 20th and 21st

2010-03-22T12:32:00.001-07:00

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.

FeedBurner experiencing system instability

2010-02-24T09:20:00.000-08:00

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.

Partial disruption of email delivery service for February 23rd; problem resolved going forward

2010-02-24T07:57:00.001-08:00

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.

FriendFeed Subscriber counts not reported for January 21st

2010-01-22T10:58:00.000-08:00

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.

FriendFeed Subscriber counts not reported for January 14th

2010-01-15T08:03:00.000-08:00

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.