Feature Disruption

We have successfully halted the message type suspected of causing the impact and are now monitoring the environment as it recovers. The recovery process is estimated to take up to four hours to complete.

We’ll provide another update as additional information becomes available.

Our previous findings related to an internal process were determined to be unrelated. We have suspended a message type suspected of causing the platform event degradation. Once this message type is fully halted, recovery may take some time to complete, and a restart may be necessary before we see improvement. We will continue conducting internal system health checks and actively working to resolve this issue as quickly as possible.

We’ll provide an update in 60 minutes or sooner if more information becomes available.

We’re continuing to investigate the cause of the issue and have engaged more engineers to help isolate the root cause. We will provide an update in 30 minutes or sooner if we have more information.

We’ve identified and are looking into an internal process that may have originally triggered the unexpected increase in published events, resulting in a restart.

In parallel, we’re continuing to determine how to resolve the subsequent connectivity issues within the event publishing pipeline to restore connectivity and event publishing.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

We apologize for the continued impact of this issue on custom and standard platform events and the downstream effects on functionality that utilizes platform events.

We are working diligently to identify the trigger and resolve this as quickly as possible and will provide an update in 30 minutes or sooner if additional information becomes available.

We’re continuing to investigate the connectivity issues related to the event publishing pipeline. Analysis has highlighted that the connectivity issues may have occurred after a restart due to an unexpected increase in published events.

There are currently no workarounds or actions customers can take to self-mitigate this issue.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

We have ruled out any recent changes as a potential trigger. We have observed connectivity errors between a subset of networking devices involved in the platform events publishing pipeline and are proceeding to investigate this.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Initial investigations have found that customers may have experienced signs of delayed event publishing as early as 21:00 UTC on January 26. The impact subsequently manifested as a disruption to custom platform events at approximately 06:20 UTC today, January 27. We have revised the start time and impact description to align with this information.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Custom Platform Events is currently experiencing issues. Customers will not encounter errors when publishing events; however, subscribers do not receive these. As a result, customers can also experience problems with order processing or other functionality that utilizes platform events.

The start time for this incident is approximate, and we will review this as part of our investigations.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.