Istoricul incidentelor Riipen

1. 13 octombrie 2026 la 16:11 UTCinvestigating

   În prezent investigăm această problemă.

2. 13 octombrie 2026 la 16:12 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 13 octombrie 2026 la 16:12 UTCmonitoring

   Continuăm să monitorizăm orice alte probleme.

4. 13 octombrie 2026 la 18:00 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 9 aprilie 2026 la 19:36 UTCinvestigating

   We are currently investigation a performance slow down in our core platform.

2. 9 aprilie 2026 la 20:24 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 9 aprilie 2026 la 21:03 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 9 aprilie 2026 la 22:23 UTCresolved

   This incident has been resolved.

1. 6 ianuarie 2026 la 19:01 UTCidentified

   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.

2. 6 ianuarie 2026 la 19:59 UTCresolved

   This incident has been resolved.

1. 12 noiembrie 2025 la 22:43 UTCinvestigating

   An issue currently exists on page which are attempting to display answers from questions, including match request custom questions and survey responses.

2. 12 noiembrie 2025 la 22:46 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 12 noiembrie 2025 la 23:00 UTCresolved

   This incident has been resolved.

1. 4 noiembrie 2025 la 02:00 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 4 noiembrie 2025 la 02:41 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 4 noiembrie 2025 la 02:44 UTCresolved

   This incident has been resolved.

1. 29 septembrie 2025 la 20:18 UTCinvestigating

   We are currently investigating this issue.

2. 29 septembrie 2025 la 20:18 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 septembrie 2025 la 21:55 UTCresolved

   This incident has been resolved.

1. 12 iunie 2025 la 18:53 UTCinvestigating

   We are currently investigating this issue.

2. 12 iunie 2025 la 18:57 UTCinvestigating

   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

3. 12 iunie 2025 la 19:21 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 12 iunie 2025 la 19:51 UTCmonitoring

   The upstream fix has been implemented, but some users may still experience intermittent issues.

5. 12 iunie 2025 la 20:18 UTCresolved

   This incident has been resolved.

1. 26 mai 2025 la 20:32 UTCinvestigating

   We are currently investigating this issue.

2. 26 mai 2025 la 20:34 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 26 mai 2025 la 20:36 UTCresolved

   This incident has been resolved.

1. 27 noiembrie 2024 la 17:37 UTCidentified

   Single sign on with LTI tools in all major LMS is currently degraded.

2. 27 noiembrie 2024 la 18:08 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 27 noiembrie 2024 la 18:23 UTCresolved

   This incident has been resolved.

1. 15 iulie 2024 la 15:56 UTCinvestigating

   We are currently investigating this issue.

2. 15 iulie 2024 la 16:02 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 15 iulie 2024 la 16:13 UTCresolved

   This incident has been resolved.

1. 19 martie 2024 la 20:49 UTCinvestigating

   We are currently investigating this issue.

2. 19 martie 2024 la 20:49 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 19 martie 2024 la 21:32 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 19 martie 2024 la 21:33 UTCresolved

   This incident has been resolved.

1. 27 ianuarie 2024 la 06:31 UTCinvestigating

   We are currently investigating this issue.

2. 27 ianuarie 2024 la 06:33 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 27 ianuarie 2024 la 06:46 UTCresolved

   This incident has been resolved.

1. 2 noiembrie 2023 la 18:36 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 2 noiembrie 2023 la 19:09 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2 noiembrie 2023 la 19:23 UTCresolved

   This incident has been resolved.

4. 2 noiembrie 2023 la 19:23 UTCpostmortem

   An invalid config change was merged leading to presigned urls failing to generate. This caused some pages to fail to load.

1. 25 octombrie 2023 la 16:40 UTCinvestigating

   We are currently investigating the issue. You may experience problems depending on your current time zone.

2. 25 octombrie 2023 la 16:52 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 25 octombrie 2023 la 17:33 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 25 octombrie 2023 la 17:47 UTCresolved

   This incident has been resolved.

1. 28 august 2023 la 19:44 UTCinvestigating

   We are currently investigating this issue.

2. 28 august 2023 la 19:51 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 28 august 2023 la 19:58 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 28 august 2023 la 20:14 UTCresolved

   This incident has been resolved.

1. 8 decembrie 2022 la 01:22 UTCinvestigating

   We are currently investigating this issue.

2. 8 decembrie 2022 la 01:33 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 8 decembrie 2022 la 01:52 UTCidentified

   We are continuing to work on a fix for this issue.

4. 8 decembrie 2022 la 01:52 UTCresolved

   This incident has been resolved.

1. 24 mai 2022 la 17:02 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 24 mai 2022 la 18:05 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 24 mai 2022 la 18:06 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 24 mai 2022 la 18:15 UTCresolved

   This incident has been resolved.

5. 24 mai 2022 la 18:42 UTCpostmortem

   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.

1. 14 decembrie 2021 la 22:59 UTCinvestigating

   Some customer are experiencing high load times.

2. 14 decembrie 2021 la 23:11 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 14 decembrie 2021 la 23:17 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 14 decembrie 2021 la 23:44 UTCresolved

   This incident has been resolved.

1. 29 aprilie 2021 la 15:32 UTCinvestigating

   We are currently investigating this issue.

2. 29 aprilie 2021 la 15:34 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 29 aprilie 2021 la 15:45 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 29 aprilie 2021 la 15:56 UTCresolved

   This incident has been resolved.

1. 2 septembrie 2020 la 16:19 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 2 septembrie 2020 la 16:28 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2 septembrie 2020 la 16:41 UTCresolved

   This incident has been resolved.