Hootsuite: X data acquisition issues in Talkwalker
Cloudflare outage, Dec 5, 2025 · 46 vendors, 46 incidents
Hootsuite’s incident started in the same window without naming Cloudflare (timing only, not evidence of a link). (timing only, posted −46 min vs the first vendor naming Cloudflare)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Cloudflare<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>18 vendors, 18 blamed Cloudflare<br/>Unbounce, Expo, GitLab +15"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed Cloudflare<br/>Klaviyo"]:::blames
root --> h4
later["Later<br/>2 vendors, 2 blamed Cloudflare<br/>Bitrise, Sigma Computing"]:::blames
root --> later
me["Hootsuite (this incident)<br/>posted −46 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
Services have been fully restored. We have confirmed that X data is now being retrieved as expected within both Hootsuite Listening and Talkwalker. Thank you for your patience while our engineering team worked to resolve this.
From Hootsuite’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.hootsuite.com (opens in new tab).