This incident has been resolved and all impacted journeys have been recovered
Posted Jul 31, 2024 - 22:40 UTC
Monitoring
At 03:40 PM PDT on July 30th AWS noticed increased error rates and latencies for some service APIs within the US-EAST-1 region. At 03:59 PM PDT on July 30th AWS determined it was due to the Kinesis service in US-EAST-1. The root cause was identified and they began working on a solution As of July 30th at 09:55 PM PDT AWS fully recovered Kinesis errors and closed the issue
Simon Data has been recovering failed journeys since the service has returned to normal. We are actively working through the backlog and will provide another update once we are recovered.
Posted Jul 31, 2024 - 15:24 UTC
Investigating
The Journeys product is in a degraded state due to an outage of AWS Kinesis, upon which Journeys depends. Though many contacts are not impacted, some contacts that should be flowing through Journeys are not.