Rewindex

CompaniesSprout SocialIncidents

Sprout Social: Meta Issues

MinorStatus: resolvedStarted Resolved (6.5 h)2 updatesstspg.io (opens in new tab)
Part of an outage event

Meta outage, Jun 12, 2026 · 14 vendors, 14 incidents

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

“…Meta Issues This incident has been resolved. Meta is currently experiencing difficulties affecting all aspects of Sprout pertaining to Meta services. These issues began on June 12 at approximately 8:3…”

Swipe sideways to see the whole diagram.

Metaown incident not archivedWithin an hour8 vendors, 7 blamed MetaTwilio, Sprout Social, Vonage, Hootsuite +41 to 4 hours later4 vendors, 3 blamed MetaBigCommerce, Braze, Iterable, PlivoSprout Social (this incident)posted +1 min
Metaown incident not archivedWithin an hour8 vendors, 7 blamed MetaTwilio, Sprout Social, Vonage,Hootsuite +41 to 4 hours later4 vendors, 3 blamed MetaBigCommerce, Braze, Iterable,PlivoSprout Social (this incident)posted +1 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["Meta<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>8 vendors, 7 blamed Meta<br/>Twilio, Sprout Social, Vonage, Hootsuite +4"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>4 vendors, 3 blamed Meta<br/>BigCommerce, Braze, Iterable, Plivo"]:::blames
  root --> h4
  me["Sprout Social (this incident)<br/>posted +1 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.

Affected components: Sprout Social Web Application

Timeline of updates

  1. investigating

    Meta is currently experiencing difficulties affecting all aspects of Sprout pertaining to Meta services. These issues began on June 12 at approximately 8:35 AM CT. We are monitoring the situation and apologize for any inconvenience. Please subscribe to receive status updates.

  2. 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.

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