Between 06:50 UTC and 09:30 UTC, AWS experienced an outage in their us-east-1 (N. Virginia) region. This outage affects Skeddly's ability to start action executions. Already-running action executions were able to continue running.
At 08:20 UTC, we were able to put measures in place to circumvent the issue Skeddly's starters were experiencing. This allowed us to start new action executions. All action executions that were delayed have already been covered by Skeddly's SLA (https://www.skeddly.com/sla/)
Please note that while actions were able to execute during the AWS outage, if they interacted with the us-east-1 region during the AWS outage, they likely experienced errors and failures.
Some downstream providers were also affected by the AWS outage. This affected functionality like email notifications, daily summeries, etc., which may have been delayed and/or never sent.
To top it off, the service provider for our status page was also affected by the AWS outage, so we were not able to update our status page during the event.