Sprout Social Outage History

Sprout Social experienced intermittent performance issues for 4.4 hours due to an external LinkedIn API outage causing server timeout errors. The incident affected users' ability to connect LinkedIn profiles, publish content, and fetch reports through the Sprout Social API. The issue was resolved once LinkedIn restored their API service.

Sprout Social experienced issues ingesting Facebook @Mention messages, causing delays in these messages appearing in the Smart Inbox. The incident affected the Sprout Social Web Application and lasted approximately 13.6 days before being resolved. Engineers investigated and fixed the root cause of the ingestion problem.

Sprout Social experienced Bluesky connection and re-authorization failures affecting the web application, preventing users from connecting new profiles or re-authenticating existing ones. The incident lasted 23.6 hours before a fix was implemented and monitored. The issue has been fully resolved.

An AWS outage caused data ingestion delays in Sprout Social starting May 7th around 7 pm CT, affecting reports, listening topics, Smart Inbox/Reviews, and published posts in the Publishing Calendar. Users experienced delays in pulling metrics and messages across these features for approximately 22.8 hours. The AWS outage was resolved on May 9th at 10:32 AM CT, restoring normal data ingestion functionality.

Sprout Social experienced a 33-hour outage affecting video publishing to Instagram and Threads, beginning Friday, May 1st at approximately 9:00pm CT. The issue prevented users from publishing video content through Sprout's web application to these Meta-owned platforms. Meta resolved the underlying network difficulties on May 4th at 3:07am CT, restoring full video publishing functionality.

Sprout Social experienced a major connectivity issue where a subset of Meta (Facebook and Instagram) profiles could not perform actions within the platform due to security checkpoints triggered on Meta's side. The disruption affected the Sprout Social Web Application and prevented users from managing their social media profiles through the service. The incident was resolved after 78.7 hours, with users advised to log into Facebook natively to address any required security actions from Meta.

Sprout Social experienced a 42.7-hour incident where Bluesky integration issues caused post failures, delays in pulling Bluesky data for Listening topics, and delays in Bluesky data for reports. The Sprout Social Web Application was affected, impacting users' ability to effectively manage their Bluesky social media activities through the platform. The incident has been resolved.

Sprout Social experienced a 15.2-hour outage affecting Team Conversations and User Teams features, causing errors when users tried to comment or mention other users within conversations. The issue impacted the Sprout Social Web Application and prevented normal collaboration functionality. Engineers implemented a fix and monitored the results before fully resolving the incident.

Facebook experienced technical difficulties that prevented Sprout Social users from successfully publishing video and reels content to Facebook through both the web application and API. The issue began on March 12th at approximately 6 AM CT and lasted 20.6 hours, causing post failures for users attempting to publish video content. Facebook resolved the underlying issue on March 12th at 9:14 PM CT, restoring normal video publishing functionality.

Yelp experienced technical difficulties that affected Sprout Social's Reviews and Connection features, causing missing or delayed Yelp reviews and problems connecting or reauthorizing Yelp profiles. The issues began on February 26th at approximately 2:30 PM CT and impacted the Sprout Social Web Application for 13 hours. Yelp resolved the underlying problems and all functionality was fully restored by 9:30 PM CT on February 27th.