24 Riipen incidents · octubre de 2019 — official updates, affected components, duration and resolution details.
We are currently investigation a performance slow down in our core platform.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Email notifications from the Riipen platform are currently failing to send and are in a processing queue. We have identified the issue with our 3rd party email provider and are waiting on a fix from them.
This incident has been resolved.
An issue currently exists on page which are attempting to display answers from questions, including match request custom questions and survey responses.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
We are currently investigating this issue.
A 3rd party vendor critical to the Riipen platform is experiencing a partial outage. Parts of the Riipen platform may fail during this outage. https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW
The issue has been identified and a fix is being implemented.
The upstream fix has been implemented, but some users may still experience intermittent issues.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Single sign on with LTI tools in all major LMS is currently degraded.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
An invalid config change was merged leading to presigned urls failing to generate. This caused some pages to fail to load.
We are currently investigating the issue. You may experience problems depending on your current time zone.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
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.
Some customer are experiencing high load times.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.