Riipen experienced a critical incident on May 24, 2022 affecting Platform and Website and 1 more component, lasting 1h 12m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 24, 2022, 05:02 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring May 24, 2022, 06:05 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 24, 2022, 06:06 PM UTC
We are continuing to monitor for any further issues.
- resolved May 24, 2022, 06:15 PM UTC
This incident has been resolved.
- postmortem May 24, 2022, 06:42 PM UTC
Riipen would like to apologize for any inconvenience this incident has caused to any and all customers. While Riipen does everything under its power to ensure incidents like this do not occur, sometimes incidents such as today’s occur for reasons completely out of our control. Riipen’s main cloud service provider Amazon Web Services \(AWS\), accidentally marked Riipen’s account and services for suspension while Riipen has only ever been in good standing with AWS. This accidental suspension on AWS’s end caused all Riipen services to become unavailable while we worked with their customer success teams to figure out what had occurred. AWS has ensured us that this was a mistake on their end and that it will never occur again. We are continuing to work with them to ensure that any side effects of this temporary outage have been resolved. Again, we apologize for any inconvenience caused by this incident.