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

As listed on Brandwatch’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Brandwatch status & history page.

Related: Brandwatch status & history. SquidGrid is not affiliated with Brandwatch.