ReadCast - Notice history

We just resolved the issue! We flushed everything on our Redis server and it wiped all of our background jobs. We'll monitor things over the next few days but things seem to be back to normal.

We have stopped Redis, the service we use to run all of our background jobs. We are going to monitor CPU usage on the servers until they are back at a reasonable level, then we will attempt to flush all Redis jobs on our server.

All of our background jobs seem to be broken at the moment. Our server has decided to reprocess every single job that's ever been processed. We're working to clear the queue to try and resolve the issue.

Things seem to be getting back to normal now.

We appreciate the patience of our customers.

We have identified that this outage affects listening to podcast episodes from podcast players and our web app. We apologize for this inconvenience.

One of our hosting providers, Amazon Web Services is currently experiencing issues with their service.

This means that anything to do with episodes, like generating new episodes or listening to episodes will not work as expected. There's nothing we can do apart from wait until Amazon Web Services is back online.

We thank you for your patience.