Is Sprout Social Down?

No — Sprout Social is up

Sprout Social's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 309 ms

Right now

The verdict is the worse of these two. How we decide

Sprout Social's status page

sproutsocialstatus.com · read 3 minutes ago · checked every 3 minutes

Operational

Sprout Social's components, as its status page reports them
Component	Status
Sprout Social Web Application	Operational
Sprout Social API	Operational

Open their status page

FlareWarden checks

sproutsocial.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 309 ms
Checked: 4 hours ago

By region

Amsterdam reachable, 150 ms
Chicago reachable, 80 ms
London reachable, 132 ms
San Jose reachable, 73 ms
Singapore reachable, 134 ms
Sydney reachable, 1277 ms
Tokyo reachable, 352 ms
Toronto reachable, 278 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	88 ms	3 ms	7 ms	141 ms
Chicago	19 ms	1 ms	5 ms	77 ms
London	80 ms	2 ms	7 ms	126 ms
San Jose	26 ms	1 ms	4 ms	67 ms
Singapore	72 ms	1 ms	4 ms	129 ms
Sydney	179 ms	1 ms	6 ms	682 ms
Tokyo	123 ms	1 ms	3 ms	347 ms
Toronto	119 ms	8 ms	12 ms	255 ms

We check that sproutsocial.com loads, not every feature behind it. Test it yourself

History

Incidents Sprout Social reported

Since Oct 22, 4 days · from sproutsocialstatus.com

Incidents: 1
Major or critical: 0
Median to resolve: 3d 13h

Meta Profiles Disconnecting
Unrated · Oct 19
lasted 3d 13h

Sprout Social website availability

Measured by FlareWarden · sproutsocial.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 342ms

Last 30 days

82-day clean streak

Sep 26 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of sproutsocial.com from multiple regions every 6 hours. Sprout Social's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 82 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Sprout Social does

Sprout Social schedules posts, routes inbound messages and reports on performance across social networks for marketing and social care teams. It sits between an organisation and the platforms it publishes to, which means an incident can hold up scheduled campaigns and leave customer messages unanswered in a queue nobody can see.

What an outage looks like

The web application fails to load or loads without the Smart Inbox populating, so incoming messages appear to have stopped arriving. Scheduled posts do not publish at their slot, or publish late in a burst once service returns. Reporting shows gaps or stale numbers. Integrations calling the Sprout API time out, which surfaces in whatever dashboard consumes them rather than in Sprout itself.

What to do about it

Check the status page at www.sproutsocialstatus.com, which reports the Sprout Social Web Application and the Sprout Social API separately and publishes an API availability metric. Confirm whether posts actually published on the network itself before rescheduling anything, since a post that went out while reporting failed will otherwise go out twice. For time-critical replies, answer natively in the platform and reconcile the thread in Sprout afterwards.

Is it down for everyone, or just you?

If this page says Sprout Social is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Sprout Social outage FAQ

Will my scheduled posts still publish?

Posts queued before the incident are generally sent once the service recovers rather than skipped, which means a delayed burst is the common outcome. That matters for campaigns timed to an event, where late is close to useless. Check the network directly before re-posting manually, because duplicating a post that eventually published is more damaging than the delay itself.

Am I missing customer messages during an outage?

Messages continue arriving on the social networks themselves; what fails is Sprout collecting and showing them. They are normally backfilled into the Smart Inbox once the connection recovers, so the queue catches up rather than losing entries. The real cost is response time on anything urgent, which is why answering natively in the platform is worth the reconciliation work afterwards.

Is it Sprout or is the social network down?

Open the network directly to tell them apart. If Instagram or LinkedIn loads normally for you and Sprout does not, the problem is Sprout. If the network itself is failing, Sprout may report healthy while publishing to that one network still fails, since it cannot deliver to a platform that is not accepting posts. The two failures look identical from inside the dashboard.

Does the API being down affect the web app?

They are listed as separate components and can fail independently. An API incident primarily affects integrations and anything pulling Sprout data into an external dashboard or data warehouse, while the web application keeps working for a human user. If your reporting pipeline has gaps but the interface is fine, the API component is the one to read.

Will I lose drafts or unpublished content?

Content saved to the queue is stored server-side and returns with the service. What is at risk is a post being composed in the browser when the session dropped, which is not recoverable. For anything long or approved through a review process, keeping the copy in a document before pasting it in is a cheap habit that removes the exposure entirely.

How we measure this

We request Sprout Social's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Sprout Social publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Sprout Social itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Sprout Social goes down

We check Sprout Social every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required