Is BEE Plugin down?

On June 19, between 12:21 and 12:24 am UTC, some users may have experienced issues accessing design previews in the editors or exporting HTML, and you might have seen elevated API error rates on the "message/html" endpoint or with the onSave() callback. The affected component was our Multiparser, the service that translates Beefree JSON into HTML. The root cause has been identified, and we have deployed a fix to address it. We aim to deploy it as soon as the testing is completed. The service is now stable, and we are continuing to monitor.

On June 17, between 06:37 and 06:55 am UTC, some users may have experienced issues accessing design previews in the editors or exporting HTML, and you might have seen elevated API error rates on the "message/html" endpoint or with the onSave() callback. The affected component was our Multiparser, the service that translates Beefree JSON into HTML. The root cause has been identified, and its fix is ready and undergoing QA. We aim to deploy it as soon as the testing is completed. The system has been rebooted, and we implemented temporary contingencies to prevent this from recurring while we complete testing for the definitive fix. The service is now stable, and we are continuing to monitor.

Today, June 4th, between 11:15 and 14:12 UTC, some customers may have experienced intermittent loading and authorization issues, causing the builders not to load. As a remediation strategy, we decided to roll back the involved component to the latest stable version while we investigate the root cause and determine the best path forward to prevent the issue from happening again. Although we don't expect any further disservice, we keep monitoring our systems.

On June 2, between 5:02 and 5:06 UTC, some users may have experienced issues accessing design previews in the editors and exporting HTML from JSON. The root cause was a brief outage of our multiparser service. The team performed a system reboot and has implemented contingencies to prevent this from recurring while the root cause investigation is ongoing. The service is now stable, and we are continuing to monitor.

Today, between 12:51 UTC and 13:03 UTC, we experienced an outage of our Content Service APIs, impacting all the related services. Our team worked to resolve the issue during this time, including performing a service reboot and retrieving the necessary logs and diagnostics to restore full functionality. All services are now fully operational, and we’re continuing to investigate the root cause to help prevent similar issues in the future. Thank you for your patience and understanding.