The issues on AWS - that were caused due to electricity issues in one of their US data centers - affected our products as well as Heroku.
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).