On June 8th at 12:22 UTC our engineers identified an issue with CSS assets for Recordings not being cached due to an internal upgrade. This was resolved by 15:12 UTC.

What happened?

When processing recordings, we store a copy of the website CSS and load the saved file on recording playback. If we fail to store the CSS file, we fall back to the "public" URL.

This was caused by an internal update that made the fetching fail for certain users.

The result will be that for a number of Recordings we will try to load the "public" CSS asset, which might have changed or been removed since, but for most recordings no degradation will occur.

Why did this issue occur?

Our engineers carried out an internal update to our underlying software to a newer version. This caused an incompatibility issue with certain stylesheets.

What will we do to prevent this from happening in the future?

An internal postmortem will be held to identify further checks for these kind of issues.