User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 380 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 478 ms | 0 |
| Nov 7 | 0 | 0.0 | 223 ms | 0 |
| Nov 7 | 0 | 0.0 | 377 ms | 0 |
| Nov 7 | 0 | 0.0 | 367 ms | 0 |
| Nov 7 | 0 | 0.0 | 436 ms | 0 |
| Nov 8 | 0 | 0.0 | 402 ms | 0 |
| Nov 8 | 0 | 0.0 | 405 ms | 0 |
| Nov 8 | 0 | 0.0 | 276 ms | 0 |
| Nov 8 | 0 | 0.0 | 251 ms | 0 |
| Nov 9 | 0 | 0.0 | 278 ms | 0 |
| Nov 9 | 0 | 0.0 | 451 ms | 0 |
| Nov 9 | 0 | 0.0 | 214 ms | 0 |
| Nov 9 | 0 | 0.0 | 406 ms | 0 |
| Nov 10 | 0 | 0.0 | 411 ms | 0 |
| Nov 10 | 0 | 0.0 | 327 ms | 0 |
| Nov 10 | 0 | 0.0 | 397 ms | 0 |
| Nov 10 | 0 | 0.0 | 257 ms | 0 |
| Nov 11 | 0 | 0.0 | 481 ms | 0 |
| Nov 11 | 0 | 0.0 | 244 ms | 0 |
| Nov 11 | 0 | 0.0 | 398 ms | 0 |
| Nov 11 | 0 | 0.0 | 216 ms | 0 |
| Nov 12 | 0 | 0.0 | 475 ms | 0 |
| Nov 12 | 0 | 0.0 | 386 ms | 0 |
| Nov 12 | 0 | 0.0 | 175 ms | 0 |
| Nov 12 | 0 | 0.0 | 504 ms | 0 |
| Nov 13 | 0 | 0.0 | 391 ms | 0 |
| Nov 13 | 0 | 0.0 | 243 ms | 0 |
| Nov 13 | 0 | 0.0 | 444 ms | 0 |
| Nov 13 | 0 | 0.0 | 391 ms | 0 |
| Nov 14 | 0 | 0.0 | 210 ms | 0 |
| Nov 14 | 0 | 0.0 | 388 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Brandwatch yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Brandwatch goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Brandwatch alerts to Slack, Discord or a webhook — free.
Brandwatch is listed in our AI category and checked at brandwatch.com. Brandwatch, a Cision company, is an AI-powered social media management, consumer intelligence, and influencer marketing suite trusted by half of the Forbes 100.
Brandwatch publishes an official status page at status.brandwatch.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 386 ms average, 122–1244 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Brandwatch incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
386 ms on average over the last 24 hours (122–1244 ms).
Yes, at https://status.brandwatch.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Brandwatch here at once, the problem is on Brandwatch's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Brandwatch. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.