Rewindex

CompaniesIterableIncidents

Iterable: Subset of customers using Twilio for SMS seeing a portion of messages getting droppped

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

Google Cloud us-central1 outage, Sep 1, 2026 · 47 vendors, 54 incidents

Iterable’s incident is a second hop: it blames Twilio, which was affected by Google Cloud. (hop 2, posted +2 h 37 min vs Google Cloud’s own post)

“…Subset of customers using Twilio for SMS seeing a portion of messages getting droppped Twilio has reported that the issue causing 5xx errors on their side has resolved and we have seen SMS sends retur…”

Swipe sideways to see the whole diagram.

blamed GitHubblamed Twilioblamed TwilioGoogle Cloud us-central1posted 14:42 UTCWithin an hour8 vendors, 8 blamed Google CloudPinecone, Elastic Cloud, FullStory +51 to 4 hours later6 vendors, 6 blamed Google CloudApollo GraphQL, Temporal Cloud, Clerk +3GitHubposted +18 min, did not name Google CloudBolt.new+24 minTwilioposted +1 h 42 min, did not name Google CloudGorgias, Iterable+2 h 23 min to +2 h 37 minIterable (this incident)posted +2 h 37 min
blamed GitHubblamed Twilioblamed TwilioGoogle Cloud us-central1posted 14:42 UTCWithin an hour8 vendors, 8 blamed GoogleCloudPinecone, Elastic Cloud,FullStory +51 to 4 hours later6 vendors, 6 blamed GoogleCloudApollo GraphQL, TemporalCloud, Clerk +3GitHubposted +18 min, did not nameGoogle CloudBolt.new+24 minTwilioposted +1 h 42 min, did notname Google CloudGorgias, Iterable+2 h 23 min to +2 h 37 minIterable (this incident)posted +2 h 37 min
Iterable is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Google Cloud us-central1<br/>posted 14:42 UTC"]:::root
  h1["Within an hour<br/>8 vendors, 8 blamed Google Cloud<br/>Pinecone, Elastic Cloud, FullStory +5"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>6 vendors, 6 blamed Google Cloud<br/>Apollo GraphQL, Temporal Cloud, Clerk +3"]:::blames
  root --> h4
  p0["GitHub<br/>posted +18 min, did not name Google Cloud"]:::timing
  root -.-> p0
  k0["Bolt.new<br/>+24 min"]:::hop2
  p0 -->|"blamed GitHub"| k0
  p1["Twilio<br/>posted +1 h 42 min, did not name Google Cloud"]:::timing
  root -.-> p1
  k1["Gorgias, Iterable<br/>+2 h 23 min to +2 h 37 min"]:::hop2
  p1 -->|"blamed Twilio"| k1
  me["Iterable (this incident)<br/>posted +2 h 37 min"]:::me
  p1 -->|"blamed Twilio"| 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: Global Campaign Sends

Timeline of updates

  1. identified

    A subset of customers using Twilio for SMS sending may have some messages getting dropped due to an incident on Twilio’s side with impact currently ranging from 5%-20%. We are actively monitoring the impact and status updates from Twilio. There is not impact to customers using any other SMS providers. Next update: by 11:30am PT

  2. resolved

    Twilio has reported that the issue causing 5xx errors on their side has resolved and we have seen SMS sends return to normal. Customers using Twilio that saw sends get dropped should re-send those messages if they want to. No further updates will be posted.

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

Iterable profileRecent Iterable incidentsMarkdownJSON