Transact incident

EKM customers experiencing issues with channel loading and message delivery

Minor Resolved View vendor source →

Transact experienced a minor incident on May 8, 2026, lasting 5d 13h. The incident has been resolved; the full update timeline is below.

Started
May 08, 2026, 06:31 PM UTC
Resolved
May 14, 2026, 08:00 AM UTC
Duration
5d 13h
Detected by Pingoru
May 08, 2026, 06:31 PM UTC

Update timeline

  1. monitoring May 08, 2026, 06:31 PM UTC

    Between approximately 10:55 AM and 11:10 AM PDT, customers using Enterprise Key Management (EKM) may have experienced issues sending messages and loading some channels. Error rates have returned to normal levels and customers should now see expected performance. We are continuing to investigate the underlying cause and monitoring closely. We apologize for the disruption.

  2. monitoring May 08, 2026, 06:44 PM UTC

    We’re investigating this issue: Current status and actions being taken: We’re seeing renewed, elevated error rates and latency affecting customers using Enterprise Key Management (EKM). Affected customers may experience issues sending messages and loading some channels. Our team is actively investigating this issue. Estimated time to resolution: No ETA at this time. Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management (EKM) customers may experience impact globally. Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading some channels. Known workarounds: No known workarounds at this time. We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

  3. monitoring May 08, 2026, 07:20 PM UTC

    We’re investigating this issue: Current status and actions being taken: We believe an issue with an upstream provider may be impacting some Slack services. We’re partnering with them to help with our investigation and are waiting on additional details from their analysis. In parallel, we’re actively reviewing the cache configuration to alleviate the impact. Estimated time to resolution: No ETA at this time. Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management (EKM) customers may experience impact globally. Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading some channels. Known workarounds: No known workarounds at this time. We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

  4. monitoring May 08, 2026, 07:54 PM UTC

    We’re investigating this issue: Current status and actions being taken: We’ve deployed a fix that has improved our cache hit ratio and are observing recovery in our health metrics. In parallel, we're monitoring for updates from our upstream provider. Affected customers may already be seeing improvements, and we’ll continue to monitor the situation closely until it is fully resolved. Estimated time to resolution: No ETA at this time. Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management customers may experience impact globally. Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications and activity feeds. Known workarounds: No known workarounds at this time. We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

  5. monitoring May 08, 2026, 08:27 PM UTC

    We’re investigating this issue: Current status and actions being taken: We're seeing consistent improvement in our health metrics while our upstream provider has begun implementing a fix on their side. Affected customers may already be seeing improvements, and we’ll continue to monitor the situation closely until it is fully resolved. Estimated time to resolution: No ETA at this time. Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management customers may experience impact globally. Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications and activity feeds. Known workarounds: No known workarounds at this time. We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

  6. monitoring May 08, 2026, 08:57 PM UTC

    We’re investigating this issue: Current status and actions being taken: We continue to monitor the issue as our upstream provider continues their work toward a resolution. Affected customers may already be seeing improvements, and we’ll continue to monitor the situation closely until it is fully resolved. Estimated time to resolution: No ETA at this time. Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management customers may experience impact globally. Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications and activity feeds. Known workarounds: No known workarounds at this time. We'll continue to provide updates every 60 minutes until the impact is resolved for all users.

  7. monitoring May 08, 2026, 09:58 PM UTC

    We’re investigating this issue: Current status and actions being taken: Our upstream provider has implemented a fix and is continuing their investigation. In the meantime, we continue to observe improved health metrics. Affected customers may already be seeing improvements, and we’ll continue to monitor the situation closely until it is fully resolved Estimated time to resolution: No ETA at this time. Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management customers may experience impact globally. Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications and activity feeds. Known workarounds: No known workarounds at this time. We'll continue to provide updates every 60 minutes until the impact is resolved for all users.

  8. monitoring May 08, 2026, 11:27 PM UTC

    This issue is now resolved for all users. Current status and recent actions taken: Our upstream provider has successfully implemented a fix. Following a period of stable monitoring, all services have been restored. Customers should no longer experience issues accessing Slack. Scope: This issue didn’t affect any specific region, but a percentage of Enterprise Key Management customers may have experienced an impact globally. Previous impact to end users: Customers using Enterprise Key Management (EKM) may have experienced issues sending messages and loading channels. Additionally, they may have experienced delays with all messaging activity, including notifications and activity feeds. Required resolution steps: No additional steps are necessary. We apologize for any disruptions to your day.

  9. monitoring May 08, 2026, 11:28 PM UTC

    Resolved.