We're investigating reports of some users not being able to publish to their blog after correctly solving a CAPTCHA. Thanks for your patience.

Navbar +1 counts are displaying incorrect totals for some private blogs. We're investigating this and will report back as soon as we have more information.

We're investigating reports of users not being able to edit the Link List gadget. We'll update this post as soon as we have more information. Thanks for your patience. 

The Post Page Option which allows you to customize the text replacing 'Comments' is currently not functional. We are investigating and will report back as soon as we have more information.

Some IE9 users are reporting bX-lcbzu1 errors when trying to publish. We're investigating the problem and in the meantime recommend you use another browser such as Chrome or Firefox.

Some users are having trouble setting up their admin account after purchasing a custom domain through  Blogger. We're investigating this issue and will update this post as soon as we have more information. Thanks for your patience.

Yesterday, our malware detection system began receiving reports of malicious content on some blogs. While the blog content on many of these blog may be malware-free, 3rd party widgets on these blogs may contain malware.

We are absolutely committed to providing our users with a malware-free experience. When this was detected we took immediate action to protect blog owners and their readers. However, in our vigilance we failed to also contact blog owners let them know what was happening. We’re currently in the process of contacting all blog owners with instructions.

We’re working to improve our communication of these issues in the future and apologize if you were wondering what the heck was going on. Hopefully, this clears the air.

The Facebook and Twitter Share buttons are currently not functional for Dynamic View blogs with a right-to-left language preference (for example Arabic). 

The photo upload icon is not appearing for some users on Internet Explorer. We're investigating the issue and will update this post as soon as we have more information.

In the meantime, you can workaround this issue by using a different browser (such as Chrome or Firefox) or temporarily switching to the Edit HTML mode of the compose editor.

Update, 1/22: This is now fixed, thanks for your patience.

Some users have reported that the Apply to Blog button in the Template Designer is non-functional for some Dynamic View templates. We're investigating the issue and will report back soon with more information.

Some users are reporting that they're hitting unexpected image quota limits when uploading an image from Blogger. We're investigating the issue and will report back when we have more information to share.

Google+ Followers Gadget for Dynamic Views

Some users who use Dynamic Views have noticed an empty space when they expand the Google+ Followers Gadget from the Gadget Drawer. To fix this issue, clear your cache and refresh the blog.

For instructions on how to clear you cache, see this help article.

Missing stats for pageviews

We've received many reports about missing pageview counts on Blogger stats, and we're working to resolve this problem as quickly as possible. Thanks for bearing with us -- we apologize for the inconvenience this issue has caused.

Update: This issue has been fixed.

Some users are reporting that embedded HTML objects are overlaying on top of code in HTML mode. We are working on a fix and hope to have it resolved shortly.

Some users are having trouble saving template changes in the Advanced Settings section of the template designer. We're working on a fix and should have it working again shortly. Thanks for your patience.

A small number of users are being unexpectedly logged out of their Blogger account with a message that says "You have logged out from another location. Do you want to log in again?'

We're working on a fix and should have it resolved very soon. In the meantime you may be able to resolve this by clearing your browser's cache and cookies. Thanks for your patience. 

Pages linking to an external web address are currently not working. We'll update this post when we have more information.

The option to have a naked domain redirect to 'www' is currently not functional for some users. We're working on a fix and hope to have it resolved shortly.

Custom domain security

Last week we encountered an issue that could affect Blogger users in the process of configuring a custom domain, during the verification of ownership of domains between the provider and Blogger. Blogs with previously configured custom domains were not affected.

Your data and account security are our top priorities. So even though we considered the risk to be low, we posted a message on our known issues blog and user forum and took action to disable changes to custom domain mappings on our backend until the issue had been thoroughly evaluated and mitigated.

The issue has since been resolved. If you have been unsuccessful in mapping to your custom domain during this maintenance, you may do so now. We recommend that you delete your current domain entry and re-enter it again. We will be restoring the ability to purchase a custom domain from Blogger soon.

If you continue to experience difficulty mapping your domain, please visit the Blogger Product Forum for guidance.

Thank you for your patience as we addressed this issue.

Spam detection update

All blogs incorrectly marked as spam have been restored. Please accept our apologies for the inconvenience. 

An update to our spam detection algorithms has incorrectly taken some good blogs offline. We're working to reverse this change and will have the affected blogs restored soon.

Thanks for your patience in the meantime.

Update on custom domains

Mapping a blogspot domain to a custom domain is currently disabled while changes are being made to avoid potential mapping errors that could result. We're sorry for the inconvenience and will keep you updated on our plans to bring back this function.

Mapping a blogspot domain to a custom domain is currently disabled. We're investigating the issue and will provide more detail shortly.

Mail2Blogger (also known as Email Posting) is currently not functioning for some users. We're working on a fix and hope to have it resolved shortly.

We appreciate your patience in the meantime.

Update, 7/30: This has been fixed.

bX-1io90b, bX-7ubjdv

We've identified the source of this error to be Javascript conflicts caused by the AVG Search toolbar. We're working on resolving the underlying issue, but until then, you can remove the AVG Search bar and the problem will go away.

Images uploaded in HTML mode may display smaller than the original size for some users. We're working on a fix to the problem, but in the meantime you can still upload images without issue via Compose mode.

The dialogue box which displays +1 information may appear mis-aligned and hanging off the screen for some users. We're investigating.

We recently sent out an email to all users who still need to migrate their old pre-2007 Blogger accounts (legacy accounts). We've received a few questions about whether this affects any current, active blogs and we wanted to re-iterate that: if you've logged into Blogger at all since 2007, then that account which you've logged in to (and all the blogs on the account) are *not* legacy accounts and no action is needed.

However, if you received the recent email, that means some *other* account is *also* associated with that email address, and it is a legacy account which needs to be updated. All of these unmigrated legacy accounts were created before 2007, so perhaps you've just forgotten about it since it was years ago.

**Update: We've moved the deadline back to June 12, 2012.

Here is a quick FAQ:

> I don't think I have a legacy account, why was I sent the email?

You do have a legacy account, but likely you've forgotten about it since it's been a few years. We sent an email to all legacy accounts, even if there were no blogs associated them. So you may have created a Blogger account a while ago just to leave a comment on another person's blog, and as a result you would get this email about migrating. Some of these blogs date back more than ten years.

> What specific blogs are on my legacy account?
If you can't recall what data is associated with your legacy account, you can request an email which contains that specific information here: Blogger legacy account data request form

> I've forgot my login info and therefore can't use the migration form at blogger.com/legacy-claim.g. Help!

Head over to blogger.com/forgot.g, enter the same email address which the Legacy Notice email was sent to, and the recovery email will be sent which includes password help.

> Will URLs that aren't claimed be released for claiming?

We have no plans to alter any existing blog URLs or content. Sorry!

> Do I have to migrate? What if I don't care about my old legacy account?

That's fine, you aren't required to do this and none of your existing Google Account data or info will be affected whatsoever.

Some users are seeing bX errors when attempting to leave comments on a blog with word verification enabled. We're investigating the issue and hope to have it resolved soon.

Some users are experiencing problems with the Blog List widget. We're working on a fix and will update this post when we have more information to share.

Creating more than 10 Custom Redirects will currently throw a bX error. Engineers are working on a fix and we'll update this thread as soon as it's resolved.

The quick edit 'pencil' icon is not displaying for some users when logged in to their Blogger account. We've identified the source of this bug and hope to have a fix out shortly.

Thanks for your patience in the meantime. We'll update this post when it's resolved.

Some users are reporting a bX-125dbr when attempting to save changes in the Blogger profile. We're investigating the issue and will update this port as soon as we have more information to share.

Some users are reporting a bX-dcfel6 error when attempting to Manage their followed blogs. We're investigating the problem and will update this thread as soon as we have more information.

Some users are reporting bX-l4u1mh when editing the Layout of their blog. We're investigating the issue and will report back as soon as we have more information.

Update, 12/15: This is now fixed. Thanks for your patience.

The Blog Stats widget is displaying incorrectly for some users. We've identified the problem and are working to release a fix shortly.

Thanks for your patience, and we'll update this post when the fix is rolled out.

The old post editor is missing some buttons which may leave it non-functional for most users. We're working on a fix, but in the meantime we recommend updating to the new editor for an improved experience.

Autosave is currently non-functional for blog posts which contain HTML errors, usually throwing a bX-qignd5. Engineers are working on a fix and hope to have it working again shortly.


We'll update this post once the issue is resolve, and we thank you for your patience in the meantime.

We're investigating reports of users seeing bX errors when using the recovery form found at http://blogger.com/forgot.g

We hope to have this fixed soon. Thanks for your patience.

We're investigating reports of users not being able to comment on IE8/9 from the embedded form. We hope to have a fix out shortly, but in the meantime we encourage admins to switch to either the full-page or pop-up forms which should be working without issue.

Thanks for your patience, and we'll make sure to update this post as soon as we have more info.

We're investigating reports of incomplete Stats data and will report back as soon as we have more information.

Update 8/20: This has been fixed.

Some users are reporting that previously-working blog feeds are now showing up as invalid, usually accompanied by a bx-fj78fy error code.

We're investigating and will report back when we have more info to share. Thanks for your patience.

Some users are reporting a bX-jjvg32 error when trying to claim legacy blogs via blogger.com/legacy-claim.g. We have a fix in the works and hope to have it released shortly.

Thanks for your patience.

We've temporarily disabled the transliteration feature until we sort out a few issues with the feature. Engineers are looking into this and hope to have the feature re-enabled shortly.

Update, 7/20: The transliteration feature is now re-enabled for non-Draft users. If you are using Draft and want to use the transliteration feature, you'll have to temporarily switch to blogger.com to re-enable it.

Some users are reporting problems with image upload, accompanied by the error message "Internal error for posting images." We're investigating this now and will update this thread with more information when we have it.

Update, 10:50AM PST: We've released a fix and image upload should be working again without issue. Thanks for your patience.

We're investigating reports of users not being able to upload images in Compose mode of the post editor. We'll report back as soon as we have more information. Thanks for your patience.

Update, 1:30 PST: We have released a fix and photo upload should working again.

The Custom Search gadget is currently non-functional for some users. We're investigating this and hope to have a fix released shortly. Thanks for your patience.

For blogs which are using the embedded comment form, the +1 Button only displays on the home page and not on individual post pages. 

We are working on a fix to make the button display on all blog pages, and will update this thread when we have more info to share.

We're investigating an issue which is preventing login and comment posting for some users, and hope to have a fix released shortly.

Thanks for your patience in the meantime.

Recovering from maintenance

We’ve started restoring the posts that were temporarily removed and expect Blogger to be back to normal soon.