Monotype incident

Error rate increased on Enterprise

Critical Resolved View vendor source →

Monotype experienced a critical incident on April 13, 2026 affecting DashBoard and Browse and 1 more component, lasting 1h 39m. The incident has been resolved; the full update timeline is below.

Started
Apr 13, 2026, 09:22 AM UTC
Resolved
Apr 13, 2026, 11:02 AM UTC
Duration
1h 39m
Detected by Pingoru
Apr 13, 2026, 09:22 AM UTC

Affected components

DashBoardBrowseFoundriesFont-SyncMyLibraryWeb Font HostingWhatTheFontUsage And ReportsManage

Update timeline

  1. investigating Apr 13, 2026, 09:22 AM UTC

    We’re aware of an issue currently affecting Enterprise services and are actively investigating. Our engineering team is on it, and we’re working to get everything back to normal as quickly as possible. We’ll keep you updated right here.

  2. investigating Apr 13, 2026, 09:39 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Apr 13, 2026, 10:41 AM UTC

    We have identified the issue. The fix has been applied, and we’re starting to see services recover. We’re closely monitoring system performance to ensure everything remains stable. We’ll keep watching things and share any updates here.

  4. resolved Apr 13, 2026, 11:02 AM UTC

    The issue has been fully resolved, and all services are now functioning normally. We sincerely apologize for the disruption and appreciate your patience throughout the process.

  5. postmortem May 19, 2026, 10:06 AM UTC

    A root-cause analysis for this issue has been performed and is now available at: [https://monotyperca.s3.us-east-1.amazonaws.com/2026/04/13/Enterprise\_dashboard\_access\_disruption\_\+RCA\_13thApr26.pdf](https://monotyperca.s3.us-east-1.amazonaws.com/2026/04/13/Enterprise_dashboard_access_disruption_+RCA_13thApr26.pdf)