>`. \n\nUnfortunately Stripe does not provide any sort of versioned history of this file. The maintain a single “live” version which we must pull in on page load. In this particular outage, Stripe made a change to this package’s script which conflicted with any web platform built with `webpack` using its code splitting features. In particular, Stripe overwrote the `window.webpackJsonp` variable to be non compatible with webpack.\n\nAs Riipen’s automated platform infrastructure was not affected by this outage, but rather customers visiting the website experienced a local issue, Riipen was unable to automatically detect this event. However, Riipen’s error detection system for client side errors experienced a larger volume of errors which led our team to investigate the production site and thus discovered the issue.\n\nOur status page was promptly updated while we waited for Stripe to fix the issue on their end.","startDate":"2019-10-02T21:59:42.155-07:00","endDate":"2019-10-01T15:58:15.061-07:00","status":"investigating"}]]}}
Riipen

Is Riipen Down Right Now? Check if there is a current outage ongoing.

Riipen is currently Operational

Last checked from Riipen's official status page

Historical record of incidents for Riipen

Report: "Partial outage from vendor"

Last update
investigating

We are currently investigating this issue.

Report: "Incident"

Last update
resolved

This incident has been resolved.

monitoring

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

investigating

We are currently investigating this issue.

Report: "Incident"

Last update
Resolved

This incident has been resolved.

Monitoring

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

Investigating

We are currently investigating this issue.

Report: "LMS integration with LTI"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

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

Report: "Platform outage"

Last update
resolved

This incident has been resolved.

monitoring

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

investigating

We are currently investigating this issue.

Report: "Match teams page unable to load for some matches"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

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

investigating

We are currently investigating this issue.

Report: "Platform outage"

Last update
resolved

This incident has been resolved.

monitoring

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

investigating

We are currently investigating this issue.

Report: "Partial Outage"

Last update
postmortem

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

resolved

This incident has been resolved.

monitoring

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

identified

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

Report: "Partial outage for specific time zones"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

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

investigating

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

Report: "Platform Outage"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

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

investigating

We are currently investigating this issue.

Report: "Platform Outage"

Last update
resolved

This incident has been resolved.

identified

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

identified

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

identified

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

identified

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

investigating

We are currently investigating this issue.

Report: "Major Service Outage"

Last update
postmortem

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.

resolved

This incident has been resolved.

monitoring

We are continuing to monitor for any further issues.

monitoring

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

identified

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

Report: "Partial Outage"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

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

investigating

Some customer are experiencing high load times.

Report: "Core services partial outage"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

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

investigating

We are currently investigating this issue.

Report: "Email links partially not working"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

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

Report: "Riipen Partial Outage"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

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

investigating

We are currently investigating this issue.

Report: "Partial Outage"

Last update
resolved

This incident has been resolved.

monitoring

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

investigating

We are currently investigating this issue.

Report: "Outage"

Last update
resolved

This incident has been resolved.

monitoring

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

investigating

We are currently investigating this.

Report: "API Maintenance"

Last update
resolved

The maintenance has completed.

monitoring

Maintenance complete. Monitoring stability.

identified

The maintenance is being completed within the next 15 mins.

investigating

We are currently performing maintenance on the API

Report: "Outage"

Last update
resolved

This incident has been resolved.

monitoring

We are continuing to monitor for any further issues.

monitoring

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

identified

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

identified

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

investigating

Riipen is currently experiencing an outage. We are aware of the situation and are investigating.

Report: "Platform outage"

Last update
postmortem

This outage was caused by Riipen’s reliance on the Stripe.js v3 CDN. This package is dynamically pulled into Riipen at system run-time via `<script src="https://js.stripe.com/v3/"</script>>`. Unfortunately Stripe does not provide any sort of versioned history of this file. The maintain a single “live” version which we must pull in on page load. In this particular outage, Stripe made a change to this package’s script which conflicted with any web platform built with `webpack` using its code splitting features. In particular, Stripe overwrote the `window.webpackJsonp` variable to be non compatible with webpack. As Riipen’s automated platform infrastructure was not affected by this outage, but rather customers visiting the website experienced a local issue, Riipen was unable to automatically detect this event. However, Riipen’s error detection system for client side errors experienced a larger volume of errors which led our team to investigate the production site and thus discovered the issue. Our status page was promptly updated while we waited for Stripe to fix the issue on their end.

resolved

Stripe has resolved the issue on their end and the Riipen platform is back online.

identified

The issue has been identified as an issue with Riipen'a payment processor Stripe. We are in contact with them and will continue to update as needed.

investigating

We are currently experiencing an outage. We are investigating and will update with further details.