Rewindex

CompaniesSprout SocialIncidents

Sprout Social: Cloudfare issues - degraded performance

No impact listedStatus: resolvedStarted Resolved (16 min)3 updatesstspg.io (opens in new tab)
Part of an outage event

Cloudflare outage, Dec 5, 2025 · 46 vendors, 46 incidents

Sprout Social’s incident blames Cloudflare as the cause. (hop 1, posted +30 min vs the first vendor naming Cloudflare)

“…en restored and are now fully operational. Thank you for your patience and understanding. Cloudflare is currently experiencing issues that are affecting Sprout’s access for some customers. We are watc…”

Swipe sideways to see the whole diagram.

Cloudflareown incident not archivedWithin an hour18 vendors, 18 blamed CloudflareUnbounce, Expo, GitLab +151 to 4 hours later1 vendor, 1 blamed CloudflareKlaviyoLater2 vendors, 2 blamed CloudflareBitrise, Sigma ComputingSprout Social (this incident)posted +30 min
Cloudflareown incident not archivedWithin an hour18 vendors, 18 blamedCloudflareUnbounce, Expo, GitLab +151 to 4 hours later1 vendor, 1 blamed CloudflareKlaviyoLater2 vendors, 2 blamed CloudflareBitrise, Sigma ComputingSprout Social (this incident)posted +30 min
Sprout Social is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
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["Sprout Social (this incident)<br/>posted +30 min"]:::me
  h1 --- me

Full 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

  1. investigating

    Cloudflare is currently experiencing issues that are affecting Sprout’s access for some customers. We are watching the situation closely and appreciate your patience. You can subscribe to receive updates on any changes.

  2. monitoring

    The fix has been applied, and services should now be operating as expected. We will continue to monitor the situation to ensure everything remains stable.

  3. resolved

    Cloudfare incident has been resolved, and all services have been restored and are now fully operational. Thank you for your patience and understanding.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Sprout Social profileRecent Sprout Social incidentsMarkdownJSON