Live / Brandwatch / Incident
Brandwatch: Issue with Publishing and Scheduling in Publish
Brandwatch · brandwatch.comMajor incidentResolved2026-10-29 16:01 UTC
Public — what happened
Summary
Brandwatch said that on 29 October 2026 starting at 10:09 UTC, users could not publish or schedule posts because the Publish/Schedule button did not respond. The company classed the issue as major and said its team was investigating. By 11:20 UTC it reported that a fix was in place and it was watching the results, and the incident was marked resolved at 16:01 UTC. No cause was given in the text provided.
Affected
Publish
Timeline
- Started — 2026-10-29 10:09 UTC
- Investigating — 2026-10-29 10:09 UTC
- Monitoring — 2026-10-29 11:20 UTC
- Resolved — 2026-10-29 16:01 UTC · 5h 52m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Brandwatch against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Brandwatch: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Brandwatch report →
More from Brandwatch
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.