The issues on AWS affected our product as well as Heroku and even Intercom, our main communication channel with our customers.
In Cron To Go, new issues arised after the AWS issues were fixed since Cron To Go was executing jobs but still received errors from Heroku APIs and retried execution. This caused the job queue to bloat up more than the workers' capacity and caused jobs to run out of schedule (due to retries). We purged the queue and job execution is back to normal.
Note that if jobs were meant to run during the incidents, they may have no executed at all so you may want to run them manually.