BEE Plugin Outage History

BEE Plugin is up right now

BEE Plugin had 12 outages in the last 2 years totaling 7h 38m of downtime — averaging 0.5 incidents per month.

There were 12 BEE Plugin outages since June 13, 2025 totaling 7h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.beefree.io

Critical May 11, 2026

Sessions with co-editing enabled fail to start

Detected by Pingoru
May 11, 2026, 08:03 AM UTC
Resolved
May 11, 2026, 09:03 AM UTC
Duration
59m
Affected: Co-editing
Timeline · 3 updates
  1. investigating May 11, 2026, 08:03 AM UTC

    We are currently experiencing an issue with the co-editing functionality. As a result, any editor session initialized with co-editing enabled will fail to start. While our team works on a resolution, editor access can be restored by disabling co-editing in the SDK configuration. We'll share further updates as soon as we have more information.

  2. investigating May 11, 2026, 08:37 AM UTC

    Our team is continuing to investigate the issue with the co-editing functionality. As a temporary measure, editor access can still be restored by disabling co-editing in the SDK configuration.

  3. resolved May 11, 2026, 09:03 AM UTC

    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.

Read the full incident report →

Notice February 10, 2026

SDK Developer Portal Login Page Outage

Detected by Pingoru
Feb 10, 2026, 10:21 PM UTC
Resolved
Feb 10, 2026, 09:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 10, 2026, 10:21 PM UTC

    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.

Read the full incident report →

Minor December 5, 2025

Website unreachable due to Cloudflare incident

Detected by Pingoru
Dec 05, 2025, 09:09 AM UTC
Resolved
Dec 05, 2025, 09:15 AM UTC
Duration
5m
Affected: Support site
Timeline · 2 updates
  1. monitoring Dec 05, 2025, 09:09 AM UTC

    An ongoing incident affecting the Cloudflare infrastructure is impacting our website, making developers.beefree.io and docs.beefree.io unreachable. It is still possible to log in directly to your SDK Console via this URL: developers.beefree.io/login

  2. resolved Dec 05, 2025, 09:15 AM UTC

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

Read the full incident report →

Notice October 31, 2025

Update on Co-Editing Service Stability

Detected by Pingoru
Oct 31, 2025, 06:02 PM UTC
Resolved
Oct 31, 2025, 08:38 PM UTC
Duration
2h 35m
Affected: Co-editing
Timeline · 3 updates
  1. monitoring Oct 31, 2025, 06:02 PM UTC

    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.

  2. monitoring Oct 31, 2025, 07:30 PM UTC

    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.

  3. resolved Oct 31, 2025, 08:38 PM UTC

    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.

Read the full incident report →

Critical October 31, 2025

Coediting and Template Loading Issues

Detected by Pingoru
Oct 31, 2025, 04:31 PM UTC
Resolved
Oct 31, 2025, 05:10 PM UTC
Duration
39m
Affected: Other services
Timeline · 3 updates
  1. investigating Oct 31, 2025, 04:39 PM UTC

    We are investigating a service disruption affecting the Coediting functionality. In instances where Coediting is enabled, users may experience issues with templates not loading correctly. Our team is actively working to identify the cause and restore full functionality as soon as possible. We will provide updates here as soon as more information becomes available. Thank you for your patience.

  2. monitoring Oct 31, 2025, 04:39 PM UTC

    We have identified and resolved the issue that was affecting the Coediting functionality and causing templates not to load correctly in instances where Coediting was enabled. The service is now fully operational, and we are currently monitoring to ensure stability.

  3. resolved Oct 31, 2025, 05:10 PM UTC

    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.

Read the full incident report →

Major October 27, 2025

Co-editing Issues

Detected by Pingoru
Oct 27, 2025, 07:29 PM UTC
Resolved
Oct 27, 2025, 07:54 PM UTC
Duration
25m
Affected: Other services
Timeline · 2 updates
  1. investigating Oct 27, 2025, 07:29 PM UTC

    We experienced a brief disruption with a real-time data streaming service. This may have impacted customers’ ability to use the builder and/or our co-editing service.

  2. resolved Oct 27, 2025, 07:54 PM UTC

    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.

Read the full incident report →

Notice October 23, 2025

Spamhaus blocklist

Detected by Pingoru
Oct 23, 2025, 11:30 PM UTC
Resolved
Oct 23, 2025, 11:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 27, 2025, 03:35 PM UTC

    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.

Read the full incident report →

Notice September 15, 2025

Partial Outage (co-editing)

Detected by Pingoru
Sep 15, 2025, 03:55 PM UTC
Resolved
Sep 15, 2025, 05:12 PM UTC
Duration
1h 16m
Affected: Authorization
Timeline · 3 updates
  1. investigating Sep 15, 2025, 03:55 PM UTC

    We experienced a disruption with a real-time data streaming service that lasted for approximately 25 minutes. This may have impacted customers' ability to use the builder and/or our co-editing service. The issue has since been resolved, and service has returned to normal. Our team is actively investigating the root cause and will provide additional details as they become available.

  2. investigating Sep 15, 2025, 04:04 PM UTC

    We are continuing to investigate this issue.

  3. resolved Sep 15, 2025, 05:12 PM UTC

    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.

Read the full incident report →

Notice June 20, 2025

INCIDENT - SDK API has been resolved

Detected by Pingoru
Jun 20, 2025, 03:28 PM UTC
Resolved
Jun 20, 2025, 03:28 PM UTC
Duration
—
Affected: API
Timeline · 1 update
  1. resolved Jun 20, 2025, 03:28 PM UTC

    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.

Read the full incident report →

Notice June 13, 2025

Authorization Service Disruption

Detected by Pingoru
Jun 13, 2025, 08:09 AM UTC
Resolved
Jun 13, 2025, 08:09 AM UTC
Duration
—
Affected: AuthorizationAPI
Timeline · 1 update
  1. resolved Jun 13, 2025, 08:09 AM UTC

    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.

Read the full incident report →