Optimizely incident

Email Campaign Delivery Drops — NA Region

Major Resolved View vendor source →

Optimizely experienced a major incident on June 17, 2026 affecting Campaigns, lasting 3d 3h. The incident has been resolved; the full update timeline is below.

Started
Jun 17, 2026, 02:00 PM UTC
Resolved
Jun 20, 2026, 05:41 PM UTC
Duration
3d 3h
Detected by Pingoru
Jun 17, 2026, 02:00 PM UTC

Affected components

Campaigns

Update timeline

  1. investigating Jun 18, 2026, 10:05 PM UTC

    We are investigating an issue causing some email campaign messages to be dropped in the North America region. Some emails are still being delivered. Accounts using email campaigns in the region may be affected. We will update as we learn more.

  2. investigating Jun 19, 2026, 12:13 PM UTC

    We are continuing to investigate this issue. We also have a support thread open with Sendgrid.

  3. investigating Jun 19, 2026, 07:02 PM UTC

    We are still looking into this issue and will provide updates as they become available.

  4. identified Jun 19, 2026, 07:51 PM UTC

    We have likely identified the root cause as a recent SendGrid change that introduced an incompatibility in header processing. We are sharing our findings with SendGrid and implementing a workaround to restore compatibility.

  5. monitoring Jun 19, 2026, 09:50 PM UTC

    We have deployed a fix to unblock affected customers and are actively monitoring the system to confirm stability. We are also working with our email vendor (SendGrid) to put a more complete solution in place on their side. Please note: during the period when emails were partially dropped, we do not have a record of which individual recipients successfully received messages. As a result, if you choose to re-run an affected campaign (e.g., by sending it to a new campaign), some recipients may receive duplicate emails. We will provide a further update as monitoring continues.

  6. monitoring Jun 19, 2026, 10:29 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Jun 20, 2026, 05:41 PM UTC

    This incident has been resolved.