Buffer

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-10-09 12:38 UTC

   The issue has been resolved and we are now monitoring the system to ensure stability. We will keep an eye on the situation and provide a final update once we verify that everything is continuing to run smoothly.

2. resolved 2026-10-09 16:02 UTC

   The issue affecting Buffer has been fully resolved. Our team has confirmed that the service is now operating normally. We apologise for any disruption this may have caused and appreciate your patience throughout the resolution process. If you encounter any further issues, please...

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-08 12:58 UTC

   We’re currently seeing issues connecting and refreshing YouTube channels on Buffer. While this appears to be due to instability with the social network, we are investigating to confirm the cause. We’re sorry for the inconvenience and will continue to share updates here as we...

2. identified 2026-10-08 18:38 UTC

   After investigating, it appears that this issue is related to ongoing issues within the YouTube API. We're keeping an eye on things and will update this page if any new information becomes available.

3. identified 2026-10-08 21:37 UTC

   We're continuing to keep an eye on this situation. The error rate is low, but we want to ensure YouTube connections are working as expected for all users before marking this issue as resolved.

4. resolved 2026-10-09 16:04 UTC

   We have seen that the issues with YouTube connections have returned back to normal levels now, and all new YouTube connections should go through successfully once again, as well as channel reconnections, too. We're very sorry for the inconvenience this created and hope...

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-10-05 08:40 UTC

   Between 24 September and 5 October, some Substack posts that contained video failed to publish. A fix has been put in place, and Substack posting appears to be functioning normally again. We are closely monitoring the situation to ensure everything remains stable. If you have...

2. resolved 2026-10-05 08:42 UTC

   The issue with Substack video posts has been fully resolved, and all systems are now operational. If you have experienced failed posts during this time, please click **Retry Now** on each one to try publishing them again. We appreciate your understanding and apologise for any...

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-01 10:11 UTC

   We’re currently seeing publishing failures through Buffer for Mastodon accounts hosted on [mastodon.social](http://mastodon.social) and [mastodon.online](http://mastodon.online). This affects some Mastodon posts, rather than all Mastodon publishing. The...

2. monitoring 2026-10-01 11:48 UTC

   The success rate for Mastodon publishing over the past hour has significantly increased, and although both [mastodon.social](http://mastodon.social) and [mastodon.online](http://mastodon.online) status pages still show “investigating”, the behaviour we’re seeing suggests the...

3. resolved 2026-10-01 12:37 UTC

   The issue with Mastodon has been resolved, and their servers are performing normally. If you have experienced failed posts during this time, please click **Retry Now** on each one to try publishing them again. We appreciate your understanding and apologise for any disruption...

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-25 14:44 UTC

   We're currently investigating an issue where Buffer is able to be opened, but it is not able to fully load an entire account. We have spotted an underlying error and we're working on getting to the core of the issue.

2. identified 2026-09-25 14:59 UTC

   Our team has identified the cause and is implementing a fix to restore normal access. We’re sorry for the disruption and appreciate your patience.

3. monitoring 2026-09-25 15:30 UTC

   We've resolved the core issue affecting the loading of a Buffer account. Everything should be working as expected once again. We'll continue to monitor to ensure stability and will mark this as fully resolved once we are confident.

4. resolved 2026-09-25 16:04 UTC

   This incident is now fully resolved.

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-23 15:26 UTC

   We’re currently experiencing slowness with Buffer, which may affect your app performance. Our team is aware of the issue and is working to resolve it as quickly as possible. We’ll keep you updated on our progress and apologise for the disruption.

2. identified 2026-09-23 15:39 UTC

   We’ve identified the cause of an issue that may cause the Buffer dashboard to load slowly or show intermittent errors. Our team has increased capacity to reduce the impact and is continuing to investigate the underlying cause. We’re sorry for the disruption and appreciate your...

3. monitoring 2026-09-23 15:53 UTC

   We’ve addressed the issue causing slowness with Buffer and are currently monitoring the app to ensure that performance is stable. We’ll keep you updated with any further developments and provide a final update once we confirm that the service is fully restored.

4. resolved 2026-09-23 16:31 UTC

   The issues loading have now been resolved. We'll be keeping a close eye on things over the next day to ensure continued stability. Thank you for your patience as we worked through the underlying cause.

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-23 10:52 UTC

   We’re currently seeing issues connecting Threads to Buffer, and are investigating the cause. Refreshing also doesn't work as expected right now. We’re sorry for the inconvenience and will continue to share updates here as we have them.

2. identified 2026-09-23 11:40 UTC

   The issue appears to be related to Threads authentication and is also affecting other services. We’re monitoring the situation and working to restore normal connections as soon as possible. We’re sorry for the inconvenience and appreciate your patience.

3. monitoring 2026-09-23 14:16 UTC

   The Threads team has deployed a fix on their side, meaning that the issues affecting channel connections between Buffer and Threads has been resolved. We’re monitoring the situation to ensure things continue to run smoothly.

4. resolved 2026-09-23 14:54 UTC

   Channel connection issues with Threads have been fully resolved and performance is working as expected. Please reach out if you continue to see issues. We apologise for the interruption today.

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-22 14:49 UTC

   We’re currently experiencing an issue with Buffer, which is impacting availability. Our team is actively investigating and working to restore full service as quickly as possible. We’ll keep you informed with updates here as we make progress. We sincerely apologise for the...

2. monitoring 2026-09-22 15:14 UTC

   Buffer is loading normally again and the issue has been resolved. We are now monitoring the system to ensure stability. We will keep an eye on the situation and provide a final update once we verify that everything is continuing to run smoothly.

3. resolved 2026-09-22 15:45 UTC

   The issue affecting Buffer has been fully resolved. Our team has confirmed that the service is now operating normally. We apologise for any disruption this may have caused and appreciate your patience throughout the resolution process. If you encounter any further issues, please...

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-09-22 07:49 UTC

   Pinterest post creation was blocked by an error saying a board must be selected, even when a board was selected.

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-05 13:29 UTC

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

2. monitoring 2026-09-05 13:43 UTC

   A fix has been implemented, and posting to Google Business Profile appears to be functioning normally again. We are closely monitoring the situation to ensure everything remains stable. If you have experienced failed posts to Google Business Profile during this time, please...

3. resolved 2026-09-05 14:24 UTC

   The publishing issue with Google Business Profile has been fully resolved, and it’s functioning as expected again. If you encounter any further problems, please don’t hesitate to reach out to our team.

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-03 22:38 UTC

   We are investigating delays to analytics processing, including Bluesky analytics updates. Some insights may be delayed while we work to restore normal processing.

2. monitoring 2026-09-03 23:04 UTC

   We have applied a mitigation and analytics processing is recovering. Bluesky analytics updates may still be delayed while we monitor processing and confirm the recovery is sustained.

3. resolved 2026-09-03 23:39 UTC

   Analytics processing has recovered, and Bluesky analytics updates are operating normally. We have resolved this incident.

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-02 23:39 UTC

   We’re investigating an issue affecting editing for drafts and scheduled posts. Users may be unable to make or save edits to these posts. We’re sorry for the disruption and are working to restore full editing functionality. We’ll share further updates as more information becomes...

2. monitoring 2026-09-03 00:34 UTC

   The issue affecting editing drafts has been fixed, and we’re keeping an eye on it to ensure it continues to run smoothly. Thank you for your patience as we worked to resolve this issue!

3. resolved 2026-09-03 00:55 UTC

   We’ve continued monitoring the fix, and everything remains stable. This incident is now fully resolved. Thank you for your patience while we worked through this. If you’re still experiencing any issues, please reach out to us at [hello@buffer.com](mailto:hello@buffer.com).

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-02 06:30 UTC

   We’re investigating an issue preventing users from accessing the billing page in their Buffer accounts. We’re sorry for the trouble and will share an update as soon as we have more information.

2. identified 2026-09-02 07:19 UTC

   We’ve identified the cause of the issue preventing users from accessing the billing page and are working on a fix. We’re sorry for the continued trouble and will share another update as soon as we have more information.

3. identified 2026-09-02 07:28 UTC

   We’ve deployed a fix, and the billing page is now loading again. We’ll continue monitoring things for a little longer to ensure everything remains stable before resolving this incident. If you’re still experiencing any issues, please reach out to us at...

4. monitoring 2026-09-02 07:28 UTC

   We’ve deployed a fix, and the billing page is now loading again. We’ll continue monitoring things for a little longer to ensure everything remains stable before resolving this incident. If you’re still experiencing any issues, please reach out to us at...

5. resolved 2026-09-02 07:57 UTC

   This issue has been fully resolved, and the billing page is loading as expected. Thanks for your patience while we worked to get this fixed. If you’re still experiencing any issues, please reach out to us at [hello@buffer.com](mailto:hello@buffer.com).

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-28 13:45 UTC

   We’re currently experiencing some issues with the Buffer Publishing dashboard loading successfully. Our team are currently investigating this issue and is working to resolve it as quickly as possible, so that your dashboard will be back up & running normally again soon. We’ll...

2. resolved 2026-08-28 16:16 UTC

   Thank you so much for bearing with us today whilst we had some issues earlier. We are pleased to share that things should be working normally again now, with the Buffer dashboard loading successfully, and logins working as desired again, too. We're so sorry for today's...

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-26 23:29 UTC

   We're aware of an issue affecting login for some customers. Verification codes sent by email may not arrive, or may not be accepted when entered. If you're waiting on a code, request one and wait rather than requesting several, as only the most recent code will work. It's also...

2. monitoring 2026-08-27 02:10 UTC

   We’ve identified the issue affecting email-based login and applied a fix. Verification emails should now arrive with working codes. If you were previously unable to log in, please try again. We’ll continue monitoring the fix. If you’re still experiencing issues, contact us at...

3. resolved 2026-08-27 03:48 UTC

   The issue affecting login verification emails and codes has been fully resolved. We’re sorry for the trouble and appreciate your patience while we worked through it. If you're still experiencing issues, please reach out to us at hello@buffer.com.

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-08-24 18:04 UTC

   We're currently seeing issues with publishing to TikTok. This appears to be due to a temporary issue within the TikTok API. After the initial impact, we've already seen the success rate improve. We're continuing to monitor.

2. resolved 2026-08-24 19:22 UTC

   We have seen the success rate of TikTok posts hold steady. It appears the underlying cause of the issue has been resolved. Don't hesitate to let us know if you continue to experience any issues. We'd be happy to take a look.

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-19 08:34 UTC

   Some users are currently experiencing difficulties with updating their payment method and billing information. Our engineering team is currently investigating the cause, and we'll provide updates here as soon as we know more.

2. identified 2026-08-19 08:50 UTC

   We’ve identified the root cause of the issue affecting the billing page and are working on a fix. We sincerely apologize for the disruption and will continue to update you on our progress.

3. monitoring 2026-08-19 09:27 UTC

   The issue affecting the billing has been fixed, and we’re keeping an eye on it to ensure it continues to run smoothly. Thank you for your patience as we worked to resolve this issue.

4. resolved 2026-08-19 09:38 UTC

   The issue affecting updates to billing information through the billing page has been fully resolved, and the page is now functioning as expected. If you experience any further issues, please don’t hesitate to reach out to our team for assistance.

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-09 22:00 UTC

   We’re currently experiencing an issue with Buffer, which is impacting customers' ability to remain logged into Buffer and potentially other aspects of Buffer's functionality. Our team is actively investigating and working to restore full service as quickly as possible. We’ll...

2. monitoring 2026-08-10 02:53 UTC

   We’ve implemented a fix and are now monitoring the situation. We’ve also identified that publishing may have been impacted during this timeframe. If any of your posts failed to publish, retrying them should get them sent out successfully. If you’re still experiencing any issues,...

3. resolved 2026-08-10 04:52 UTC

   Things have remained stable following the fix, and we’re now marking this incident as fully resolved. Publishing success rates have returned to normal, and we’re no longer seeing reports of users being unexpectedly logged out. We’re sorry again for the disruption, and we...

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-07 04:56 UTC

   Some users are currently not receiving email notifications when team members request their approval on post drafts. The approval process is working as usual, this only affects the email notifications. Our engineering team is currently investigating the cause, and we'll provide...

2. monitoring 2026-08-07 05:35 UTC

   The issue affecting _approval request_ notification emails has been fixed, and we’re keeping an eye on it to ensure it continues to run smoothly. Thank you for your patience as we worked to resolve this issue.

3. resolved 2026-08-07 05:51 UTC

   The issue with _approval required_ notification emails has been fully resolved, and it’s functioning as expected again. If you encounter any further problems, please don’t hesitate to reach out to our team.

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-08-05 10:21 UTC

   We are aware that earlier today, Wednesday 5th August, at roughly 9am UTC, there was a temporary issue that impacted the publishing success rates of Pinterest. It does appear that this was an issue directly with Pinterest's API, and it was a transient issue that recovered by...

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-07-29 12:28 UTC

   We identified an issue earlier today that resulted in a small number of failed posts to Facebook, and this has since been fixed. If your updates were one of the few updates to have failed during this time, please can you retry the failed post again now? It should be working...

2. resolved 2026-07-30 11:34 UTC

   Thank you for all your patience with us as we continued to monitor the fix that was put in place yesterday over that small number of Facebook posts that failed. We have fully resolved this incident now, and after monitoring for the past 24 hours, we're fully confident everything...

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-19 09:06 UTC

   We’re currently experiencing an issue publishing video posts to Instagram and Threads due to a problem with Meta’s API. Posts with images or no media should continue to publish as normal. We’re working to resolve this as quickly as possible and will continue to share updates...

2. monitoring 2026-07-19 09:54 UTC

   Meta has implemented a fix, and video posts to Instagram and Threads appear to be publishing normally again through Buffer. If any of your posts failed, please click **_Retry Now_** in the queue and they should publish successfully. We’re continuing to monitor the situation to...

3. resolved 2026-07-19 10:01 UTC

   This issue has now been fully resolved, and video posts to Instagram and Threads are publishing normally again. Any failed posts can be retried from the queue. Once again, we sincerely apologise for the disruption.

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-14 12:17 UTC

   The Buffer Help Center (support.buffer.com) is currently experiencing issues and leading to a 404 page. We are investigating the cause and will provide updates here.

2. identified 2026-07-14 12:30 UTC

   The third-party tool (HelpScout) that we use for our Help Center is experiencing issues with their Docs Site. We are seeing some pages begin to recover, and are keeping a close eye on their Status Page [here](https://status.helpscout.com/).

3. monitoring 2026-07-14 12:54 UTC

   The Help Center is loading as usual now. The third-party tool that we use for hosting it has updated [their status page](https://status.helpscout.com/), and we’re continuing to watch for any remaining intermittent 404s while Help Scout validate their fix.

4. identified 2026-07-14 15:01 UTC

   The third-party tool that hosts our Help Center site is continuing to experience intermittent issues loading. We will continue to monitor [their Status Page](https://status.helpscout.com/) and provide updates here.

5. monitoring 2026-07-14 16:46 UTC

   The Help Center is loading again. The third-party tool that we use for hosting it has updated [their status page](https://status.helpscout.com/). We will continue monitoring and share updates here, too.

6. resolved 2026-07-14 19:18 UTC

   The Help Center issues have been resolved by the third-party app and is fully operational again. Thank you for your patience!

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-13 08:48 UTC

   We're currently experiencing a delay while updating new comments from Threads API. Our engineering team is currently investigating the cause, and we'll provide updates here as soon as we know more.

2. identified 2026-07-13 10:39 UTC

   We've confirmed that an issue with the Meta API is causing the delay, and we’re working with the Threads/Meta team to restore normal delivery of new comments. In the meantime, as a mitigation, we’ve enabled a backup mechanism to help recover recent comments. You can also trigger...

3. resolved 2026-07-19 10:20 UTC

   This issue has been resolved, and new Threads comments should now be delivered normally. Our backup mechanism has also recovered recent comments that were delayed during the incident. We sincerely apologise for the disruption.

Excerpts are shortened. Read the full incident on Buffer's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-09 15:43 UTC

   We’re currently experiencing an issue with creating new API Keys and are looking into the issue.

2. monitoring 2026-07-09 16:30 UTC

   A fix has been pushed and the process to generate an API Key is working once again. We're keeping a close eye on this to ensure it stays stable.

3. resolved 2026-07-09 16:43 UTC

   This issue is now considered fully resolved. Thanks again for your patience as we worked on correcting this issue.

Excerpts are shortened. Read the full incident on Buffer's status page.