CompaniesSprout SocialIncidents
Sprout Social: Issues Associating Follow-up Messages to Cases
Affected components: Sprout Social Web Application
Timeline of updates
- identified
On April 26th and 27th, Sprout experienced an issue associating incoming messages with existing cases. As a result, a large number of follow-up messages were not associated with cases. This issue has since been resolved and our engineers are currently working on associating any dropped messages received during this period with the correct cases.
Please subscribe to receive additional updates. We apologize for the inconvenience.
- resolved
This incident has been resolved.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
b85fa07118a82c35…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Sprout Social, started 2025-04-28 18:57 UTC, resolved after 7 d, 2 update(s).
- Title
- Issues Associating Follow-up Messages to Cases
- Vendor
- Sprout Social
- Date
- URL
- https://rewindex.com/company/sprout-social/incidents/n9rjw36j1xsp
Sprout Social profileRecent Sprout Social incidentsAll outages on April 28, 2025Sprout Social in April 2025MarkdownJSON