Riipen experienced a critical incident on October 1, 2019 affecting Platform, lasting 19m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 01, 2019, 10:38 PM UTC
We are currently experiencing an outage. We are investigating and will update with further details.
- identified Oct 01, 2019, 10:56 PM UTC
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.
- resolved Oct 01, 2019, 10:58 PM UTC
Stripe has resolved the issue on their end and the Riipen platform is back online.
- postmortem Oct 03, 2019, 04:54 AM UTC
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 `>`. 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.