Vev incident

Custom Fonts / Google Fonts not rendering on Published Project

Major Resolved View vendor source →

Vev experienced a major incident on November 25, 2021 affecting Staging and Standard Hosting, lasting 6h 14m. The incident has been resolved; the full update timeline is below.

Started
Nov 25, 2021, 02:59 PM UTC
Resolved
Nov 25, 2021, 09:13 PM UTC
Duration
6h 14m
Detected by Pingoru
Nov 25, 2021, 02:59 PM UTC

Affected components

StagingStandard Hosting

Update timeline

  1. identified Nov 25, 2021, 02:59 PM UTC

    We've received reports and are currently working on resolving an issue where custom fonts are not being rendered on the published content after publishing. Please avoid publishing any LIVE projects, or publish to the STAGING domain first before publishing to the LIVE one before updating an article.

  2. identified Nov 25, 2021, 05:33 PM UTC

    The problem has been identified and a patch is being released. ETA 1 Hour. Projects that have been published while the incident was ongoing will need to be republished to get the correct font rendered on the Published Content.

  3. monitoring Nov 25, 2021, 08:30 PM UTC

    A fix has been implemented and all fonts should work as per normal. We are still MONITORING the situation to ensure that we everything is working.

  4. resolved Nov 25, 2021, 09:13 PM UTC

    RESOLVED After monitoring and internal + external testing we now regard this issue resolved. If you are still not seeing your fonts rendered, updating your project by moving something will trigger Vev to re-render any cached elements and your fonts will render as expected. If you still encounter any issues with Fonts, please reach out to Vev Support.