Update on Co-Editing Service Stability

Summary

Update on Co-Editing Service Stability

Although the incident is now marked as Resolved, we remain in a monitoring phase to confirm that the issue does not recur. Our co-editing service will continue to operate on the old version, which is fully stable and functioning as expected. We're leaving no stone unturned and are dedicating substantial resources to strengthening our co-editing infrastructure.

• Started

  Oct 31, 2025 · 2:02 PM

• Resolved

  Oct 31, 2025 · 4:38 PM

• Duration

  2h 35m

• Severity

  None

• ◉

  Monitoring

  Oct 31 · 2:02 PM BEE Plugin

  Due to recent issues with the latest version of our co-editing service, we’re temporarily routing traffic to a previous version. This older version offers lower performance but higher stability, which helps us minimize the risk of a total service outage while we address the underlying problems. Known Issues in the Older Version Intermittent “Connecting…” messages: Some users on specific network types may see this message, accompanied by corresponding entries in the onError callback logs. Duplicate user icons: In some implementations, refreshing the browser can cause duplicate user avatars to appear. What This Means We understand these issues may look like a regression in behavior, and we recognize the potential discomfort for users. Our priority is to maintain continuous availability of the co-editing experience while we work on a stable fix for the new version.

• ◉

  Monitoring

  Oct 31 · 3:30 PM BEE Plugin

  After careful evaluation, we have decided to continue utilizing the previous version of our co-editing service for at least the next several days. This approach will provide us with additional time to ensure system stability, thoroughly investigate and resolve any potential issues, and implement measures to minimize disruptions. Our goal is to reduce—and ideally eliminate—instances where the editor crashes due to a co-editing service failure.

• ✓

  Resolved

  Oct 31 · 4:38 PM BEE Plugin

  Although the incident is now marked as Resolved, we remain in a monitoring phase to confirm that the issue does not recur. Our co-editing service will continue to operate on the old version, which is fully stable and functioning as expected. We're leaving no stone unturned and are dedicating substantial resources to strengthening our co-editing infrastructure.