Kustomer outage, 11 November 2026
[Email] Unable to Send Outbound Emails - ALL PRODs
- Started
- Resolved
- 11 Nov 2026, 17:00 UTC - reported afterwards
- Impact
- Not stated
Is this still happening?
No. Kustomer marked this incident resolved.
Right now: Kustomer reports all systems operational. (as of 13 Nov, 20:53 UTC) Live Kustomer status
At a glance
- Kustomer did not rate the impact of this incident.
- Kustomer had 1 other incident in the 30 days before it.
- 5 earlier incidents look like the same kind of problem (same affected part or wording); the most recent was on 9 Sept 2026.
Our summary from the Kustomer incidents we have recorded since 21 Oct 2025 - how we count.
What caused it: Kustomer's root cause analysis
### Summary On November 11, 2026, some Kustomer customers were unable to send or schedule outbound emails from approximately 15:57 to 16:50 UTC, lasting about 1 hour. The incident is resolved. Outbound email sending has returned to normal. ### Impact Agents in organizations that use conversation Brands, and had not yet mapped Brands to their sending email addresses, received errors when sending or scheduling outbound email. Organizations without Brands, and channels other than email, were not affected. Messages were rejected rather than silently dropped, and no data loss is expected. ### Timeline All times are UTC on November 11, 2026. * **15:57:** A release containing a change to outbound email sender validation reached PROD2 and PROD4. Affected customers began seeing send failures. * **~16:10:** Customer and internal reports of send failures were received, and the team began rolling back the release. * **16:50:** The rollback was complete, and outbound email sending was restored for all affected customers. ### Root Cause A change to outbound email validation, which checks that the “From” address belongs to the conversation’s Brand, was enabled for all organizations. Organizations that had set Brands on conversations but had not yet mapped Brands to email addresses failed this check, even when sending from addresses that had previously worked. The change was released before customers had been notified of, and given time to complete, the required Brand-to-email address setup. ### Resolution We rolled back the release to its previous version, which restored outbound email sending. The change has been removed from the release pipeline and will not be re-enabled until the preventative actions below are complete. ### Preventative Actions Our follow-up work focuses on making sure configuration requirements are communicated before enforcement begins: * Hold the change until customers have been notified and have had time to complete their Brand-to-email address mappings. * Require explicit readiness criteria and a staged rollout before enforcing sender validation for all organizations. * Evaluate a more permissive default behavior for organizations with incomplete Brand configuration, so a missing setup step does not block sending.
Last update from Kustomer
### Summary On November 11, 2026, some Kustomer customers were unable to send or schedule outbound emails from approximately 15:57 to 16:50 UTC, lasting about 1 hour. The incident is resolved. Outbound email sending has returned to normal. ### Impact Agents in organizations that use conversation Brands, and had not yet mapped Brands to their sending email addresses, received errors when sending or scheduling outbound email. Organizations without Brands, and channels other than email, were not affected. Messages were rejected rather than silently dropped, and no data loss is expected. ### Timeline All times are UTC on November 11, 2026. * **15:57:** A release containing a change to outb...
Similar Kustomer incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved after 1 h 6 min
MessageBird - unable to send outbound replies PROD 1Postmortem
-
, resolved after 27 min
[Kustomer Voice] Unable to Dial Outbound Calls - All PRODSPostmortem
-
, resolved after 39 min
[Gmail]Email Connectivity & Send/Receive Issues - Prod 1 & Prod 2Postmortem
-
, resolved after 27 h 53 min
[Satisfaction Surveys] CSATs may not send for voice, email and sms channels - Prod 1Postmortem
-
, resolved after 7 h 6 min
[Whatsapp] Outbound Message Delivery Disruption [ALL PRODs]Postmortem
Other recent Kustomer incidents
-
Workflows delays in processing PROD2Postmortem
-
kustomer.help Default Domain - Visibility Issue - ALL PRODsPostmortem
-
Issues with Text Editor with typing, pasting, & adding shortcuts PROD1, PROD2, and PROD4Postmortem
-
Chats, Emails, Routing latency PROD 1Postmortem
-
WhatsApp messages failing Prods 1 + 2Postmortem
Something wrong on this page?
Thanks - your report is on its way to us. We read every one.