Statusbrew Outage History
11 incidents recorded over the last 365 days, 11 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Statusbrew Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 30, 2026 | Undergoing MaintenanceThis incident has been resolved now. | 3 min | Resolved |
| Jul 16, 2026 | Undergoing MaintenanceThis incident has been resolved. | 7 min | Resolved |
| Jun 12, 2026 | META API DownThis incident has been resolved. | 23 min | Resolved |
| May 31, 2026 | Publishing Disruption – May 30 (Resolved)We had a service disruption yesterday (May 30) between 15:32–17:20 UTC during which posts scheduled for publishing were not sent out. The issue has now been resolved, and publishing is working as… | 0 min | Resolved |
| May 3, 2026 | Issue Publishing Posts to Instagram and ThreadsThis incident has been resolved. | 48h 51m | Resolved |
| Mar 26, 2026 | TikTok Posts Failing To PostThis incident has been resolved. | 89h 49m | Resolved |
| Mar 12, 2026 | Investigating — Facebook Video Publishing IssuesThis incident has been resolved. | 16h 53m | Resolved |
| Feb 26, 2026 | Instagram Reels Publish FailuresThis incident has been resolved. | 20h 43m | Resolved |
| Feb 4, 2026 | META Profile ConnectionThis incident has been resolved. | 120h 42m | Resolved |
| Dec 24, 2025 | App OutageThis incident has been resolved. | 24 min | Resolved |
| Nov 12, 2025 | Facebook video publishing failures (Meta platform issue)This incident has been resolved. | 117h 54m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Statusbrew incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Statusbrew Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Statusbrew acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Statusbrew outage in this window ran 5d, against a mean recovery of 1d 13h. If you depend on Statusbrew in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.