Buffer Status

Resolved: After monitoring for 30 minutes, we're confident that Buffer has fully recovered and all systems are stable. This downtime incident is now resolved.

To summarize the impact, during the downtime Buffer was largely inaccessible. In addition, posts were not being published during this period. After recovering from the downtime, Buffer began to process those scheduled posts. This potentially resulted in some posts being marked as "Failed" or "Stuck" in the queue. These posts can be retried or removed at this time.

Again, we're very sorry for the impact this has had. The team is reviewing the cause and are taking steps to prevent this moving forward.

Monitoring: Buffer has fully recovered from the downtime. We apologize for the trouble this has caused this morning and very much appreciate your patience as we worked through the issue.

We'll continue on in a monitoring state for the next bit before fully moving to viewing the issue as resolved.

Identified: We've made some changes which appear to have started the service back to recovery. We're still working on some other changes and will continue to update this page as we have information to share.

Identified: We've identified the root cause of the issue and we're taking the needed actions to resolve. We're continuing to dedicate all resources to ensure we bring about a resolution as quickly as possible.

Investigating: We are continuing to investigate this issue.

Investigating: We're currently investigating an issue impacting Buffer's availability. We're all hands on deck investigating the cause. We'll post more information on this page as it comes available.

Resolved: After monitoring the situation, we have seen that the publishing success for posts being sent to Google Business Profiles has returned back to normal and we are no longer hitting the issues we were earlier today.

Thanks so much for bearing with us on this whilst it was resolved, and we're very sorry for any trouble the failed posts may have caused.

Monitoring: Publishing success for Google Business Profile posts have been returning to normal levels once again, and we are currently monitoring the situation before declaring this issue as resolved.

Thank you for bearing with us during this problem, and apologies again for the inconvenience it had caused. We will follow up again soon for a full resolution.

Identified: Our team has confirmed that this issue stems from a failure on Google’s side, causing posts to fail and return the error message "Internal error encountered". We are actively monitoring the situation and will share further updates as soon as we have more information. Thank you for your patience.

Investigating: We’re investigating an issue causing many users' Google Business Profile posts to fail. Our team is actively working to resolve this as quickly as possible. We sincerely apologise for the disruption.

Resolved: After monitoring for 30 minutes, we're confident that Buffer has fully recovered and all systems are stable. This downtime incident is now resolved.

To summarize the impact, during the downtime Buffer was largely inaccessible. In addition, posts were not being published during this period. After recovering from the downtime, Buffer began to process those scheduled posts. This potentially resulted in some posts being marked as "Failed" or "Stuck" in the queue. These posts can be retried or removed at this time.

Again, we're very sorry for the impact this has had. The team is reviewing the cause and are taking steps to prevent this moving forward.

Monitoring: Buffer has fully recovered from the downtime. We apologize for the trouble this has caused this morning and very much appreciate your patience as we worked through the issue.

We'll continue on in a monitoring state for the next bit before fully moving to viewing the issue as resolved.

Identified: We've made some changes which appear to have started the service back to recovery. We're still working on some other changes and will continue to update this page as we have information to share.

Identified: We've identified the root cause of the issue and we're taking the needed actions to resolve. We're continuing to dedicate all resources to ensure we bring about a resolution as quickly as possible.

Investigating: We are continuing to investigate this issue.

Investigating: We're currently investigating an issue impacting Buffer's availability. We're all hands on deck investigating the cause. We'll post more information on this page as it comes available.

Resolved: After monitoring for 30 minutes, we're confident that Buffer has fully recovered and all systems are stable. This downtime incident is now resolved.

To summarize the impact, during the downtime Buffer was largely inaccessible. In addition, posts were not being published during this period. After recovering from the downtime, Buffer began to process those scheduled posts. This potentially resulted in some posts being marked as "Failed" or "Stuck" in the queue. These posts can be retried or removed at this time.

Again, we're very sorry for the impact this has had. The team is reviewing the cause and are taking steps to prevent this moving forward.

Monitoring: Buffer has fully recovered from the downtime. We apologize for the trouble this has caused this morning and very much appreciate your patience as we worked through the issue.

We'll continue on in a monitoring state for the next bit before fully moving to viewing the issue as resolved.

Identified: We've made some changes which appear to have started the service back to recovery. We're still working on some other changes and will continue to update this page as we have information to share.

Identified: We've identified the root cause of the issue and we're taking the needed actions to resolve. We're continuing to dedicate all resources to ensure we bring about a resolution as quickly as possible.

Investigating: We are continuing to investigate this issue.

Investigating: We're currently investigating an issue impacting Buffer's availability. We're all hands on deck investigating the cause. We'll post more information on this page as it comes available.

Resolved: After monitoring for 30 minutes, we're confident that Buffer has fully recovered and all systems are stable. This downtime incident is now resolved.

To summarize the impact, during the downtime Buffer was largely inaccessible. In addition, posts were not being published during this period. After recovering from the downtime, Buffer began to process those scheduled posts. This potentially resulted in some posts being marked as "Failed" or "Stuck" in the queue. These posts can be retried or removed at this time.

Again, we're very sorry for the impact this has had. The team is reviewing the cause and are taking steps to prevent this moving forward.

Monitoring: Buffer has fully recovered from the downtime. We apologize for the trouble this has caused this morning and very much appreciate your patience as we worked through the issue.

We'll continue on in a monitoring state for the next bit before fully moving to viewing the issue as resolved.

Identified: We've made some changes which appear to have started the service back to recovery. We're still working on some other changes and will continue to update this page as we have information to share.

Identified: We've identified the root cause of the issue and we're taking the needed actions to resolve. We're continuing to dedicate all resources to ensure we bring about a resolution as quickly as possible.

Investigating: We are continuing to investigate this issue.

Investigating: We're currently investigating an issue impacting Buffer's availability. We're all hands on deck investigating the cause. We'll post more information on this page as it comes available.

Resolved: After monitoring for 30 minutes, we're confident that Buffer has fully recovered and all systems are stable. This downtime incident is now resolved.

To summarize the impact, during the downtime Buffer was largely inaccessible. In addition, posts were not being published during this period. After recovering from the downtime, Buffer began to process those scheduled posts. This potentially resulted in some posts being marked as "Failed" or "Stuck" in the queue. These posts can be retried or removed at this time.

Again, we're very sorry for the impact this has had. The team is reviewing the cause and are taking steps to prevent this moving forward.

Monitoring: Buffer has fully recovered from the downtime. We apologize for the trouble this has caused this morning and very much appreciate your patience as we worked through the issue.

We'll continue on in a monitoring state for the next bit before fully moving to viewing the issue as resolved.

Identified: We've made some changes which appear to have started the service back to recovery. We're still working on some other changes and will continue to update this page as we have information to share.

Identified: We've identified the root cause of the issue and we're taking the needed actions to resolve. We're continuing to dedicate all resources to ensure we bring about a resolution as quickly as possible.

Investigating: We are continuing to investigate this issue.

Investigating: We're currently investigating an issue impacting Buffer's availability. We're all hands on deck investigating the cause. We'll post more information on this page as it comes available.

Resolved: After monitoring for 30 minutes, we're confident that Buffer has fully recovered and all systems are stable. This downtime incident is now resolved.

To summarize the impact, during the downtime Buffer was largely inaccessible. In addition, posts were not being published during this period. After recovering from the downtime, Buffer began to process those scheduled posts. This potentially resulted in some posts being marked as "Failed" or "Stuck" in the queue. These posts can be retried or removed at this time.

Again, we're very sorry for the impact this has had. The team is reviewing the cause and are taking steps to prevent this moving forward.

Monitoring: Buffer has fully recovered from the downtime. We apologize for the trouble this has caused this morning and very much appreciate your patience as we worked through the issue.

We'll continue on in a monitoring state for the next bit before fully moving to viewing the issue as resolved.

Identified: We've made some changes which appear to have started the service back to recovery. We're still working on some other changes and will continue to update this page as we have information to share.

Identified: We've identified the root cause of the issue and we're taking the needed actions to resolve. We're continuing to dedicate all resources to ensure we bring about a resolution as quickly as possible.

Investigating: We are continuing to investigate this issue.

Investigating: We're currently investigating an issue impacting Buffer's availability. We're all hands on deck investigating the cause. We'll post more information on this page as it comes available.

Resolved: The change was successful, and everything is returning to normal. We really appreciate your patience as we worked to resolve this issue.

Monitoring: The change has been made, and we're monitoring the fix. As long as things go in the right direction and stay stable, we'll mark this as resolved soon.

Identified: We've identified the cause of the "Stuck" posts and are making changes to mitigate the impact. More updates will follow.

Investigating: We're investigating an increase in the number of Instagram posts that become "Stuck in Processing." We'll update this page as more information becomes available.

Resolved: The changes implemented appear to have helped! Thanks for bearing with us as we worked on this issue.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We believe we've spotted the underlying cause and we're implementing a change to help address the error. We'll continue to work through this situation to ensure things are working smoothly.

Investigating: We're currently investigating an increase in a specific "RateLimitExceeded" error message for Bluesky channels. We'll update as more information comes available.

Resolved: After monitoring the situation, we have seen that the publishing success for posts being sent to Google Business Profiles has returned back to normal and we are no longer hitting the issues we were earlier today.

Thanks so much for bearing with us on this whilst it was resolved, and we're very sorry for any trouble the failed posts may have caused.

Monitoring: Publishing success for Google Business Profile posts have been returning to normal levels once again, and we are currently monitoring the situation before declaring this issue as resolved.

Thank you for bearing with us during this problem, and apologies again for the inconvenience it had caused. We will follow up again soon for a full resolution.

Identified: Our team has confirmed that this issue stems from a failure on Google’s side, causing posts to fail and return the error message "Internal error encountered". We are actively monitoring the situation and will share further updates as soon as we have more information. Thank you for your patience.

Investigating: We’re investigating an issue causing many users' Google Business Profile posts to fail. Our team is actively working to resolve this as quickly as possible. We sincerely apologise for the disruption.

Resolved: After monitoring for 30 minutes, we're confident that Buffer has fully recovered and all systems are stable. This downtime incident is now resolved.

To summarize the impact, during the downtime Buffer was largely inaccessible. In addition, posts were not being published during this period. After recovering from the downtime, Buffer began to process those scheduled posts. This potentially resulted in some posts being marked as "Failed" or "Stuck" in the queue. These posts can be retried or removed at this time.

Again, we're very sorry for the impact this has had. The team is reviewing the cause and are taking steps to prevent this moving forward.

Monitoring: Buffer has fully recovered from the downtime. We apologize for the trouble this has caused this morning and very much appreciate your patience as we worked through the issue.

We'll continue on in a monitoring state for the next bit before fully moving to viewing the issue as resolved.

Identified: We've made some changes which appear to have started the service back to recovery. We're still working on some other changes and will continue to update this page as we have information to share.

Identified: We've identified the root cause of the issue and we're taking the needed actions to resolve. We're continuing to dedicate all resources to ensure we bring about a resolution as quickly as possible.

Investigating: We are continuing to investigate this issue.

Investigating: We're currently investigating an issue impacting Buffer's availability. We're all hands on deck investigating the cause. We'll post more information on this page as it comes available.