Seismic Software incident

Some customers missing icons in tenant and experiencing publishing, library, and content property issues

Major Resolved View vendor source →

Seismic Software experienced a major incident on July 10, 2026 affecting U.S. West0 and U.S. West1 and 1 more component, lasting 1d 18h. The incident has been resolved; the full update timeline is below.

Started
Jul 10, 2026, 06:01 PM UTC
Resolved
Jul 12, 2026, 12:43 PM UTC
Duration
1d 18h
Detected by Pingoru
Jul 10, 2026, 06:01 PM UTC

Affected components

U.S. West0U.S. West1U.S. West2U.S. West3U.S. East0U.S. East1U.S. East2U.S. East3U.S. East4

Update timeline

  1. investigating Jul 10, 2026, 06:01 PM UTC

    We are currently investigating this issue.

  2. investigating Jul 10, 2026, 06:14 PM UTC

    We are continuing to investigate this issue.

  3. identified Jul 10, 2026, 06:54 PM UTC

    We are aware of an issue affecting icon display in some Seismic tenants, caused by a service disruption experienced today by our third-party feature management provider, LaunchDarkly. To fully restore missing icons, our team needs to restart a number of internal services over the next several hours. During this process, some customers may experience brief, intermittent service disruptions. We expect any individual disruption to be short-lived, and we are working to complete these restarts as quickly as possible while minimizing impact. We will post updates here as work progresses and confirm once the issue is fully resolved. We apologize for any inconvenience this may cause.

  4. identified Jul 10, 2026, 07:15 PM UTC

    We are continuing to work on a fix for this issue.

  5. identified Jul 10, 2026, 10:35 PM UTC

    Icons, library, and content property issues are now resolved for some tenants as services are restarted and full access is restored. We are seeing resolution in the WEST0, WEST1, and WEST2 regions.

  6. identified Jul 10, 2026, 11:18 PM UTC

    Additional regions continue to recover, including EAST regions and Southwest.

  7. identified Jul 10, 2026, 11:47 PM UTC

    We are continuing to work on a fix for this issue.

  8. identified Jul 10, 2026, 11:54 PM UTC

    We are continuing to work on a fix for this issue.

  9. monitoring Jul 11, 2026, 02:50 AM UTC

    A fix has been implemented and we are monitoring the results.

  10. monitoring Jul 11, 2026, 02:59 AM UTC

    We are continuing to monitor for any further issues.

  11. resolved Jul 12, 2026, 12:43 PM UTC

    This incident has been resolved.