brew had 11 outages in the last 2 years totaling 455h 4m of downtime — averaging 0.5 incidents per month.
There were 11 brew outages since August 14, 2025 totaling 455h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating a META API issue that is causing Instagram and Threads posts to fail for many users. Our team is working to resolve this issue. We sincerely apologize for any inconvenience caused.
This incident has been resolved.
We’re seeing reports of TikTok posts failing to go out, even if they show as published, or they are just stuck and eventually fail. It looks like a wider issue with TikTok's API. We will update as we know more.
This incident has been resolved.
We're aware of an issue affecting video uploads to Facebook through Statusbrew. If you're trying to publish video content to Facebook pages, you may see errors or failed uploads. We've traced this to a technical issue on Meta's side affecting video processing across their platform. This is not a Statusbrew platform issue, and no action is needed on your end. We recommend holding off on retrying video posts to Facebook until this is resolved to avoid duplicate or stuck content. Our team is monitoring Meta's progress toward a fix, and we'll post updates here as the situation develops.
This incident has been resolved.
We’re investigating an issue where Instagram Reels publishing via the Instagram Graph API may fail because some Reels are being detected as carousel items. This results in a 400 error (e.g., “Media created with media_type=VIDEO is a carousel item and cannot be published as a standalone post”). We’ll provide updates as soon as we have more information or a fix is available. Reference: https://developers.facebook.com/community/threads/1970836260493737/
This incident has been resolved.
New users may face issues connecting or reauthenticating their Facebook and Instagram profiles on Statusbrew due to a recent META API change. We've implemented the change and are awaiting META's approval; this should be resolved soon.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We’re currently investigating an issue where the Statusbrew app is unavailable for some users. Our team is actively working to identify the cause and restore service as quickly as possible.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We’re currently experiencing an issue where Facebook Reels and Stories are failing to publish. This is due to an ongoing problem with the Meta API affecting all platforms. More details can be found here: https://developers.facebook.com/community/threads/847406384399939/ We’re in contact with Meta while they investigate. We’ll share updates here as soon as more information is available.
We are continuing to monitor for any further issues.
This incident has been resolved.
AWS is experiencing a service outage that’s impacting Statusbrew. You may encounter issues creating or publishing posts, uploading media, and performing other actions. Our chat support is also affected, so responses may be delayed. We’re monitoring AWS’s status and will update here. Sorry for the troubles!
This incident has been resolved.
A background indexing task in one cluster is causing intermittent delays and load errors for some users. Data remains safe and queued actions will process as capacity recovers. No action is required. We're steadily restoring service and monitoring closely. Apologies for the inconvenience.
This incident has been resolved.
Some clusters are impacted by a database migration. We’re on it. Service will be back shortly. Apologies for the inconvenience.
We are continuing to work on a fix for this issue.
This incident has been resolved.
Ongoing issues on Meta’s side may have required reauthentication for some of your profiles connected to Statusbrew. If prompted, please reauthenticate. We are monitoring the situation and apologize for any inconvenience.
This incident has been resolved.