Performance has returned to normal for most users. We'll continue to monitor and close this status once all database latency has subsided.
Posted about 1 year ago. Jun 20, 2018 - 20:21 UTC
Our provider has taken action to address this and we expect to see performance improve soon. Journeys using time triggers, list triggers or smart segment triggers may be slightly delayed due to this latency.
Posted about 1 year ago. Jun 20, 2018 - 17:58 UTC
We have identified the root cause as database latency from our end provider. We have notified them and they are working to remedy it as a priority.