BEE Plugin Outage History

We implemented temporary contingencies to prevent the issue from happening again while we continue investigating the root cause. The service is now stable, and we are continuing to monitor.

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.

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.

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.

Following our investigation, we've confirmed that the SDK co-editing functionality was not impacted by the issue reported earlier. Co-editing can remain enabled in your SDK Configuration. We apologize for any confusion this may have caused.

At 21:26 UTC, the login page of the SDK Developer Portal was unavailable in select regions due to a brief Amazon CloudFront issue. The downtime varied by location, but the issue resolved itself within approximately 30 minutes. We are continuing to monitor the situation.

Cloudflare has released a fix to address the incident. Systems seem to be fully operational again, but we will keep monitoring.

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.

The issue affecting the Coediting functionality and causing templates not to load correctly in instances where Coediting was enabled has been fully resolved. After 30 minutes of monitoring, the service has remained stable, and all systems are now operating normally. Thank you for your patience while we worked to restore the service.

The issue has been resolved and our service has returned to normal. Our team is investigating the root cause and will provide additional details as they become available.

Our image hosting domain was recently listed on Spamhaus, which caused some end users to have trouble with images not loading correctly. We promptly requested a delisting, and by 10:00 a.m. Eastern Time on October 27th, our domain was no longer listed on Spamhaus. We are still monitoring the situation.

We traced the issue to a Lightstreamer deployment process. The service exited unexpectedly while checking a license. Service has returned to normal. To better understand the cause, our team will reproduce and debug the issue. Please reach out to [email protected] with any questions.

We would like to extend our sincere apologies for any inconvenience or concern caused by any incident you were notified of today. After a thorough review, we have identified that the issue was the result of a false alarm, which triggered our automated systems. Please be assured that our systems remain fully operational, and we are actively implementing updates and safeguards to prevent similar occurrences in the future. Our team is committed to maintaining the reliability and integrity of our services, and we deeply regret any disruption this may have caused. We appreciate your understanding and patience as we continue to improve our processes.

Between June 13th at 5:40 AM UTC and 7:20 AM UTC, some users experienced issues with the authorization services used by the Beefree SDK. 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.

The issue has been mitigated by rolling back the impacted component, and all services are now stable. While the immediate incident is resolved, we will be conducting further work to ensure a long-term fix and prevent recurrence.

The image editor experienced a brief outage and was unavailable for approximately 1 minute. The issue has been resolved, and full functionality has been restored.

We no longer see our CDN URL listed in popular ad blockers, and we confirmed that most customers no longer experience issues with images. There’s a small chance that some corporate filters or niche ad blockers may still temporarily block images until the fix propagates. In the unlikely case that you’re still experiencing issues, please reach out to our support team and we’ll investigate.

Our systems experienced degraded performance due to an unexpected surge in oversized JSON files. This caused temporary delays and occasional failures for a small percentage of users during specific timeframes: 8:12-8:24 AM PST 9:23-10:16 AM PST 11:21-11:47 AM PST To address the issue, we scaled our infrastructure, implemented safeguards to handle oversized requests, and deployed a fix on Monday, November 18, to prevent future parser hangs.

The co-edit worker services were redeployed, effectively recycling old connections and allowing new services to establish connections. The number of co-edit workers was also reduced to slow the rate of connection accumulation. An action plan and mitigation strategy were implemented to prevent reoccurrence.