История сбоев Riipen

1. 13 октября 2026 г. в 16:11 UTCinvestigating

   В настоящее время мы расследуем этот вопрос.

2. 13 октября 2026 г. в 16:12 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

3. 13 октября 2026 г. в 16:12 UTCmonitoring

   Мы продолжаем отслеживать любые дополнительные проблемы.

4. 13 октября 2026 г. в 18:00 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 9 апреля 2026 г. в 19:36 UTCinvestigating

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

2. 9 апреля 2026 г. в 20:24 UTCidentified

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

3. 9 апреля 2026 г. в 21:03 UTCmonitoring

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

4. 9 апреля 2026 г. в 22:23 UTCresolved

   This incident has been resolved.

1. 6 января 2026 г. в 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 января 2026 г. в 19:59 UTCresolved

   This incident has been resolved.

1. 12 ноября 2025 г. в 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 ноября 2025 г. в 22:46 UTCidentified

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

3. 12 ноября 2025 г. в 23:00 UTCresolved

   This incident has been resolved.

1. 4 ноября 2025 г. в 02:00 UTCidentified

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

2. 4 ноября 2025 г. в 02:41 UTCmonitoring

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

3. 4 ноября 2025 г. в 02:44 UTCresolved

   This incident has been resolved.

1. 29 сентября 2025 г. в 20:18 UTCinvestigating

   We are currently investigating this issue.

2. 29 сентября 2025 г. в 20:18 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 сентября 2025 г. в 21:55 UTCresolved

   This incident has been resolved.

1. 12 июня 2025 г. в 18:53 UTCinvestigating

   We are currently investigating this issue.

2. 12 июня 2025 г. в 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 июня 2025 г. в 19:21 UTCidentified

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

4. 12 июня 2025 г. в 19:51 UTCmonitoring

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

5. 12 июня 2025 г. в 20:18 UTCresolved

   This incident has been resolved.

1. 26 мая 2025 г. в 20:32 UTCinvestigating

   We are currently investigating this issue.

2. 26 мая 2025 г. в 20:34 UTCmonitoring

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

3. 26 мая 2025 г. в 20:36 UTCresolved

   This incident has been resolved.

1. 27 ноября 2024 г. в 17:37 UTCidentified

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

2. 27 ноября 2024 г. в 18:08 UTCmonitoring

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

3. 27 ноября 2024 г. в 18:23 UTCresolved

   This incident has been resolved.

1. 15 июля 2024 г. в 15:56 UTCinvestigating

   We are currently investigating this issue.

2. 15 июля 2024 г. в 16:02 UTCmonitoring

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

3. 15 июля 2024 г. в 16:13 UTCresolved

   This incident has been resolved.

1. 19 марта 2024 г. в 20:49 UTCinvestigating

   We are currently investigating this issue.

2. 19 марта 2024 г. в 20:49 UTCidentified

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

3. 19 марта 2024 г. в 21:32 UTCmonitoring

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

4. 19 марта 2024 г. в 21:33 UTCresolved

   This incident has been resolved.

1. 27 января 2024 г. в 06:31 UTCinvestigating

   We are currently investigating this issue.

2. 27 января 2024 г. в 06:33 UTCmonitoring

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

3. 27 января 2024 г. в 06:46 UTCresolved

   This incident has been resolved.

1. 2 ноября 2023 г. в 18:36 UTCidentified

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

2. 2 ноября 2023 г. в 19:09 UTCmonitoring

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

3. 2 ноября 2023 г. в 19:23 UTCresolved

   This incident has been resolved.

4. 2 ноября 2023 г. в 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 октября 2023 г. в 16:40 UTCinvestigating

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

2. 25 октября 2023 г. в 16:52 UTCidentified

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

3. 25 октября 2023 г. в 17:33 UTCmonitoring

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

4. 25 октября 2023 г. в 17:47 UTCresolved

   This incident has been resolved.

1. 28 августа 2023 г. в 19:44 UTCinvestigating

   We are currently investigating this issue.

2. 28 августа 2023 г. в 19:51 UTCidentified

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

3. 28 августа 2023 г. в 19:58 UTCmonitoring

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

4. 28 августа 2023 г. в 20:14 UTCresolved

   This incident has been resolved.

1. 8 декабря 2022 г. в 01:22 UTCinvestigating

   We are currently investigating this issue.

2. 8 декабря 2022 г. в 01:33 UTCidentified

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

3. 8 декабря 2022 г. в 01:52 UTCidentified

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

4. 8 декабря 2022 г. в 01:52 UTCresolved

   This incident has been resolved.

1. 24 мая 2022 г. в 17:02 UTCidentified

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

2. 24 мая 2022 г. в 18:05 UTCmonitoring

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

3. 24 мая 2022 г. в 18:06 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 24 мая 2022 г. в 18:15 UTCresolved

   This incident has been resolved.

5. 24 мая 2022 г. в 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 декабря 2021 г. в 22:59 UTCinvestigating

   Some customer are experiencing high load times.

2. 14 декабря 2021 г. в 23:11 UTCidentified

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

3. 14 декабря 2021 г. в 23:17 UTCmonitoring

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

4. 14 декабря 2021 г. в 23:44 UTCresolved

   This incident has been resolved.

1. 29 апреля 2021 г. в 15:32 UTCinvestigating

   We are currently investigating this issue.

2. 29 апреля 2021 г. в 15:34 UTCidentified

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

3. 29 апреля 2021 г. в 15:45 UTCmonitoring

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

4. 29 апреля 2021 г. в 15:56 UTCresolved

   This incident has been resolved.

1. 2 сентября 2020 г. в 16:19 UTCidentified

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

2. 2 сентября 2020 г. в 16:28 UTCmonitoring

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

3. 2 сентября 2020 г. в 16:41 UTCresolved

   This incident has been resolved.