No components marked as affected
Resolved
Today, between 9:20 and 10:30 UTC, we saw elevated levels of "Content initialization failed" errors during the start of workspaces. The errors were caused by a malfunctioning VM. The VM has been removed and operations run smoothly again.