Jun <var data-var='date'>19</var>, <var data-var='time'>08:41</var> EDT Resolved - 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.

Multiparser Outage

Jun <var data-var='date'>17</var>, <var data-var='time'>04:29</var> EDT Resolved - 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.

Jun <var data-var='date'> 4</var>, <var data-var='time'>12:40</var> EDT Resolved - 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.

Incident - Loading and authorization issues

Jun <var data-var='date'> 2</var>, <var data-var='time'>01:45</var> EDT Resolved - 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, and you might have seen elevated API error rates on the "message/html" endpoint or with the onSave() callback. The root cause was a brief outage of our Multiparser, the service that translates Beefree JSON into HTML. 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.

Jun <var data-var='date'> 1</var>, <var data-var='time'>09:19</var> EDT Resolved - 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.

Content Service API Outage

May <var data-var='date'>16</var>, <var data-var='time'>02:02</var> EDT Completed - The maintenance restart has been completed successfully. Beefree SDK co-editing is fully operational, and any brief disconnections during the window should now be resolved. If you notice any unexpected behavior, please reach out to your CSM or contact support at sdksupport@beefree.io. May <var data-var='date'>16</var>, <var data-var='time'>02:00</var> EDT In progress - The scheduled maintenance restart of the co-editing infrastructure has started. Active Beefree SDK sessions with co-editing enabled may briefly disconnect for approximately 1 minute. Users can simply reconnect once the restart is complete. If your application has autosave enabled, no in-progress work should be lost. We'll post an update as soon as the maintenance is over. May <var data-var='date'>14</var>, <var data-var='time'>12:34</var> EDT Scheduled - We’ll perform a short maintenance restart of the infrastructure supporting Beefree SDK co-editing. During the restart, any active Beefree SDK session from applications with Co-Editing enabled will briefly disconnect for approximately 1 minute. Users can then reconnect. If your application has autosave enabled, no in-progress work should be lost. We’ve scheduled this window during a low-traffic period to minimize impact. No action is required on your side. If you have any questions, please reach out to your CSM or contact support at sdksupport@beefree.io.

Co-editing infrastructure restart

May <var data-var='date'>11</var>, <var data-var='time'>05:03</var> EDT Resolved - 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. May <var data-var='date'>11</var>, <var data-var='time'>04:37</var> EDT Update - 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. May <var data-var='date'>11</var>, <var data-var='time'>04:03</var> EDT Investigating - 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.

Sessions with co-editing enabled fail to start

Apr <var data-var='date'>30</var>, <var data-var='time'>05:14</var> EDT Resolved - Between 9:14 and 9:46 UTC, an internal update caused the builder to fail loading on new instances. Users who already had the builder open were not affected. We rolled back the change, and service was fully restored. Total duration: 32 minutes. Timeline: Identified (9:14 UTC): An internal update caused the builder to fail loading on new instances. Users who already had the builder open were not affected. Monitoring (9:40 UTC): We rolled back the change and started monitoring recovery. Resolved (9:46 UTC): Service fully restored.

Builder loading issue

Feb <var data-var='date'>10</var>, <var data-var='time'>16:30</var> EST Resolved - 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.

SDK Developer Portal Login Page Outage

Jan <var data-var='date'>28</var>, <var data-var='time'>03:34</var> EST Completed - The scheduled maintenance has been completed. Jan <var data-var='date'>27</var>, <var data-var='time'>03:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan <var data-var='date'>22</var>, <var data-var='time'>04:44</var> EST Scheduled - As part of our transition to a more secure authentication system, we are phasing out the Beefree SDK’s legacy (v1) auth process. This includes a series of scheduled brownouts, ending with its permanent removal on January 27, 2026. On January 27, 2026, all auth traffic will be permanently rerouted to our /loginv2 endpoint. If you are still using the legacy endpoint (https://auth.getbee.io/apiauth), you may experience authentication failures. To avoid service interruptions, update your integration to use the new V2 authentication flow before the first brownout. 🔗 Learn more about the V2 Auth process and why we are making this change: https://devportal.beefree.io/hc/en-us/articles/20094954610450-Changes-to-the-Authorization-Process 🔗 You can find full Implementation details in our developer documentation: https://docs.beefree.io/beefree-sdk/getting-started/readme/installation/authorization-process-in-detail For any questions, please reach out to sdksupport@beefree.io

Legacy authentication endpoint final cut off

Jan <var data-var='date'>13</var>, <var data-var='time'>21:00</var> EST Update - The second and final brownout window for today has completed, marking the end of our scheduled maintenance. Jan <var data-var='date'>13</var>, <var data-var='time'>21:00</var> EST Completed - The scheduled maintenance has been completed. Jan <var data-var='date'>13</var>, <var data-var='time'>02:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Nov <var data-var='date'> 4</var>, <var data-var='time'>10:31</var> EST Scheduled - As part of our transition to a more secure authentication system, we are phasing out the Beefree SDK’s legacy (v1) auth process. This includes a series of scheduled brownouts, ending with its permanent removal on January 27, 2026. On January 13, 2026, all auth traffic will be temporarily rerouted to our /loginv2 endpoint during two brownout windows, lasting 6 hours each: - First window starts at 11:00 PM PST* / 2:00 AM EST / 7:00 AM UTC / 8:00 AM CET / 12:30 PM IST - Second window starts at 12:00 PM PST / 3:00 PM EST / 8:00 PM UTC / 9:00 PM CST / 1:30 AM IST *The brownout will start on January 12 at 11:00 PM on Pacific Standard Time. If you are still using the legacy endpoint (https://auth.getbee.io/apiauth), you may experience temporary authentication failures during these windows. This is a warning event to help identify lingering dependencies and help your team prepare for the full transition. To avoid service interruptions, update your integration to use the new V2 authentication flow before the first brownout. 🔗 Learn more about the V2 Auth process and why we are making this change: https://devportal.beefree.io/hc/en-us/articles/20094954610450-Changes-to-the-Authorization-Process 🔗 You can find full Implementation details in our developer documentation: https://docs.beefree.io/beefree-sdk/getting-started/readme/installation/authorization-process-in-detail 📅 Final cutover: - January 27, 2026 – Legacy auth permanently removed.

Last brownout for legacy auth deprecation

Dec <var data-var='date'> 5</var>, <var data-var='time'>04:15</var> EST Resolved - Cloudflare has released a fix to address the incident. Systems seem to be fully operational again, but we will keep monitoring. Dec <var data-var='date'> 5</var>, <var data-var='time'>04:09</var> EST Monitoring - 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

Website unreachable due to Cloudflare incident

Oct <var data-var='date'>31</var>, <var data-var='time'>16:38</var> EDT Resolved - 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. Oct <var data-var='date'>31</var>, <var data-var='time'>15:30</var> EDT Update - 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. Oct <var data-var='date'>31</var>, <var data-var='time'>14:02</var> EDT Monitoring - 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.

Update on Co-Editing Service Stability

Oct <var data-var='date'>31</var>, <var data-var='time'>13:10</var> EDT Resolved - 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. Oct <var data-var='date'>31</var>, <var data-var='time'>12:37</var> EDT Monitoring - 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. Oct <var data-var='date'>31</var>, <var data-var='time'>12:31</var> EDT Investigating - 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.

Coediting and Template Loading Issues

Oct <var data-var='date'>27</var>, <var data-var='time'>15:54</var> EDT Resolved - 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. Oct <var data-var='date'>27</var>, <var data-var='time'>15:29</var> EDT Investigating - 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.

Co-editing Issues

Oct <var data-var='date'>23</var>, <var data-var='time'>19:30</var> EDT Resolved - 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.

Spamhaus blocklist

Oct <var data-var='date'>21</var>, <var data-var='time'>17:09</var> EDT Resolved - This incident has been resolved. We continue to investigate the root cause and will add additional details as soon as possible. Oct <var data-var='date'>21</var>, <var data-var='time'>15:34</var> EDT Monitoring - A fix has been implemented and we are monitoring the results. Oct <var data-var='date'>21</var>, <var data-var='time'>15:33</var> EDT Investigating - At about 19:30 UTC we started to experience issues with our Coediting services, causing messages to not load. We restarted the systems for a prompt resolution, so your customers should no longer experience loading issues. We're monitoring the situation and are investigating the root cause.

Coediting issues

Oct <var data-var='date'>15</var>, <var data-var='time'>21:00</var> EDT Completed - The scheduled maintenance has been completed. Oct <var data-var='date'>15</var>, <var data-var='time'>19:01</var> EDT Update - The third brownout window for today has started. Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct <var data-var='date'>15</var>, <var data-var='time'>14:07</var> EDT Update - The second brownout window is completed. Please note that there will be a third brownout window today, October 15, at 4:00 PM PDT / 7:00 PM EDT / 12:00 AM UTC / 1:00 AM CEST / 4:30 AM IST. If you experienced service disruption during the brownout, or if you are still using the legacy authentication method and would like to be excluded from the next brownout window, please reach out to sdksupport@beefree.io. Oct <var data-var='date'>15</var>, <var data-var='time'>03:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep <var data-var='date'>25</var>, <var data-var='time'>05:11</var> EDT Scheduled - As part of our transition to a more secure authentication system, we are phasing out the Beefree SDK’s legacy (v1) auth process. This includes a series of scheduled brownouts, ending with its permanent removal in January 2026. On October 15, 2025, all auth traffic will be temporarily rerouted to our /loginv2 endpoint during three brownout windows, lasting 2 hours each: - First window starts at 12:00 AM PDT / 3:00 AM EDT / 7:00 AM UTC / 9:00 AM CEST / 12:30 PM IST - Second window starts at 9:00 AM PDT / 12:00 PM EDT / 4:00 PM UTC / 6:00 PM CEST / 9:30 PM IST - Third window starts. at 4:00 PM PDT / 7:00 PM EDT / 11:00 PM UTC / 1:00 AM CEST / 4:30 AM IST If you are still using the legacy endpoint (https://auth.getbee.io/apiauth), you may experience temporary authentication failures during these windows. This is a warning event to help identify lingering dependencies and help your team prepare for the full transition. To avoid service interruptions, update your integration to use the new V2 authentication flow before the first brownout. 🔗 Learn more about the V2 Auth process and why we are making this change: https://devportal.beefree.io/hc/en-us/articles/20094954610450-Changes-to-the-Authorization-Process 🔗 You can find full Implementation details in our developer documentation: https://docs.beefree.io/beefree-sdk/getting-started/readme/installation/authorization-process-in-detail 📅 Upcoming brownouts and final cutover: - January 13, 2026 – V2-only auth for 12 hours. - January 27, 2026 – Legacy auth permanently removed.

Second brownout for legacy auth deprecation

Sep <var data-var='date'>24</var>, <var data-var='time'>13:00</var> EDT Completed - The scheduled maintenance has been completed. Sep <var data-var='date'>24</var>, <var data-var='time'>12:07</var> EDT Update - Our second brownout window for today has started. Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep <var data-var='date'>24</var>, <var data-var='time'>05:12</var> EDT Update - The first brownout window was completed at 1:00 PM PDT / 4:00 AM EDT / 8:00 AM UTC / 10:00 AM CEST / 13:30 PM IST. Please note that there will be a second brownout window today, September 24 at 9:00 AM PDT / 12:00 PM EDT / 4:00 PM UTC / 6:00 PM CEST / 9:30 PM IST. If you experienced service disruption during the first brownout, or if you are still using the legacy authentication method and would like to be excluded from the next brownout window, please reach out to sdksupport@beefree.io. Sep <var data-var='date'>24</var>, <var data-var='time'>03:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>25</var>, <var data-var='time'>11:12</var> EDT Scheduled - As part of our transition to a more secure authentication system, we are phasing out the Beefree SDK’s legacy (v1) auth process. This includes a series of scheduled brownouts, ending with its permanent removal in January 2026. On September 24, 2025, all auth traffic will be temporarily rerouted to our /loginv2 endpoint during two brownout windows, lasting 1 hour each: - First window starts at 12:00 AM PDT / 3:00 AM EDT / 7:00 AM UTC / 9:00 AM CEST / 12:30 PM IST - Second window starts at 9:00 AM PDT / 12:00 PM EDT / 4:00 PM UTC / 6:00 PM CEST / 9:30 PM IST If you are still using the legacy endpoint (https://auth.getbee.io/apiauth), you may experience temporary authentication failures during these windows. This is a warning event to help identify lingering dependencies and help your team prepare for the full transition. To avoid service interruptions, update your integration to use the new V2 authentication flow before the first brownout. 🔗 Learn more about the V2 Auth process and why we are making this change: https://devportal.beefree.io/hc/en-us/articles/20094954610450-Changes-to-the-Authorization-Process 🔗 You can find full Implementation details in our developer documentation: https://docs.beefree.io/beefree-sdk/getting-started/readme/installation/authorization-process-in-detail 📅 Upcoming brownouts and final cutover: - October 15, 2025 – V2-only auth for 6 hours. - January 13, 2026 – V2-only auth for 12 hours. - January 27, 2026 – Legacy auth permanently removed.

First brownout for legacy auth deprecation

Sep <var data-var='date'>15</var>, <var data-var='time'>13:12</var> EDT Resolved - 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 sdksupport@beefree.io with any questions. Sep <var data-var='date'>15</var>, <var data-var='time'>12:04</var> EDT Update - We are continuing to investigate this issue. Sep <var data-var='date'>15</var>, <var data-var='time'>11:55</var> EDT Investigating - 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.

Partial Outage (co-editing)

Jun <var data-var='date'>20</var>, <var data-var='time'>11:28</var> EDT Resolved - 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.

INCIDENT - SDK API has been resolved

Jun <var data-var='date'>13</var>, <var data-var='time'>04:09</var> EDT Resolved - 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.

Authorization Service Disruption

Mar <var data-var='date'>25</var>, <var data-var='time'>13:00</var> EDT Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>25</var>, <var data-var='time'>11:03</var> EDT Update - Scheduled maintenance is still in progress. We will provide updates as necessary. Mar <var data-var='date'>25</var>, <var data-var='time'>11:00</var> EDT Update - We’re starting the scheduled brownout to prepare for our upcoming TLS changes (see full details below!) For the next hour (between 4pm and 5pm CET) our AUTH endpoint will no longer support insecure ciphers For the next 2 hours (between 4pm and 6pm CET) our CSAPI endpoints will no longer support insecure ciphers If you’re experiencing any issues during this brownout period, you’re likely still using older, low-strength ciphers to connect to the Beefree SDK. Please update your integration before the cutover on April 8. If you have any questions, please don't hesitate to reach out! Mar <var data-var='date'>25</var>, <var data-var='time'>11:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Dec <var data-var='date'>16</var>, <var data-var='time'>13:42</var> EST Scheduled - Keeping Beefree SDK safe and secure is our top priority, so we wanted to let you know about upcoming changes to our TLS configurations. These changes may affect your application’s ability to interact with the SDK, so please read this note carefully. What’s changing On March 25, 2025, we will start making changes to our TLS configuration to stop supporting ciphers that are no longer considered secure. If your application is using older, low-strength ciphers to connect to the SDK, you (and your end users) will experience issues when using the SDK. What do you need to do now? Please ensure your application can handle these changes before March 25, 2025. Here is everything you need to know to prepare: What ciphers are considered secure? TLS1.3 secure ciphers: TLS_CHACHA20_POLY1305_SHA256 TLS_AES_256_GCM_SHA384 TLS_AES_128_GCM_SHA256 TLS1.2 secure ciphers: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Ciphers not listed above are no longer considered secure—and the Beefree SDK will no longer support them. Which endpoints are impacted? While we’ll stop supporting insecure ciphers on all our API endpoints, we know that server-to-server connections are more likely to still rely on insecure ciphers. That’s why we encourage you to double-check your setup for the following crucial endpoints that are called in a server-to-server connection: Auth endpoint: auth.getbee.io/ Content Services API endpoint: api.getbee.io/ Test endpoints to help you validate your setup We’ve set up two temporary endpoints with the TLS changes already applied that you can use to test against. Auth endpoint: https://bee-auth-temp-secure.getbee.io Content Services API endpoint: https://bee-csapi-temp-secure.getbee.io If any of your tests with the temporary endpoints fail, you’ll need to update your application to support the new TLS settings. Please be aware that there is no expectation of uptime on these endpoints and that they will be shut down once we apply the TLS changes to our production endpoints. They should only be used for temporary testing of non-production traffic. Timeline To further reduce the risk of TLS changes impacting our clients’ integrations, we’re also performing a brownout test before updating our TLS configuration permanently: March 25, 2025, between 4pm-6pm CET Perform a “brownout” test, where we cut over to the new configuration for a short period of time in production: Auth endpoint: 1h brownout between 4pm and 5pm CET Content Services API endpoint: 2h brownout between 4pm and 6pm CET Any customers still using insecure ciphers will experience issues during this timeboxed test — a final warning to take action before the final cutover. We don’t want you and your customers to run into any issues, so please ensure you use secure ciphers before this date. April 8, 2025: Cut over production to new configuration permanently. We will also decommission temporary testing endpoints. If you have any questions, please reach out to us at pluginsupport@beefree.io.

Upcoming TLS changes: We’ll stop support for low-strength ciphers

Mar <var data-var='date'>11</var>, <var data-var='time'>14:59</var> EDT Resolved - 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. Mar <var data-var='date'>11</var>, <var data-var='time'>14:33</var> EDT Monitoring - The co-editing functionality is now working again. The service issue has been resolved. We are monitoring the service closely to ensure it continues functioning as expected. Mar <var data-var='date'>11</var>, <var data-var='time'>14:16</var> EDT Identified - We have identified the cause of the issue with the service powering the Co-editing functionality. Our team is actively working on a solution and will provide further updates shortly. Mar <var data-var='date'>11</var>, <var data-var='time'>13:35</var> EDT Investigating - We are currently investigating an issue with our service that powers our Co-editing functionality. As a result, customers using Co-editing are currently unable to launch the builder. Our team is already actively working to resolve the issue, and we will provide updates as soon as we have more information.

Co-editing functionality issue

Mar <var data-var='date'>10</var>, <var data-var='time'>12:36</var> EDT Resolved - The issue has been resolved, and all services are now operating normally. We will continue to monitor the situation closely over the next few days to ensure stability. Thank you for your patience. Mar <var data-var='date'>10</var>, <var data-var='time'>12:18</var> EDT Monitoring - We have identified the root cause of the issue and implemented a solution to address the intermittent issues affecting key services. Our team is closely monitoring the situation to ensure system stability. Mar <var data-var='date'>10</var>, <var data-var='time'>11:19</var> EDT Update - Update: We are currently identifying the root cause of the issue and are actively working on a solution. Our team is dedicated to resolving the problem as quickly as possible, and we will continue to provide updates on our progress. Mar <var data-var='date'>10</var>, <var data-var='time'>11:09</var> EDT Investigating - We are currently experiencing a partial outage that is affecting our login system. As a result, users may encounter 403 (Forbidden) and 504 (Gateway Timeout) errors when attempting to access our services via our login endpoint. Users may experience login failures, including 403 and 504 errors, and access to certain endpoints may be delayed or unavailable. Our team is actively investigating the issue and working towards a resolution.

Is Beefree SDK down?

Beefree SDK status is UP

Lastest published events

Multiparser Outage

Multiparser Outage

Incident - Loading and authorization issues

Beefree SDK Services, Components and Regions

Recent Beefree SDK events

Multiparser Outage

Multiparser Outage

Incident - Loading and authorization issues

Multiparser Outage

Content Service API Outage

Co-editing infrastructure restart

Get your FREE account now,
5 monitors included!

Is Beefree SDK down?

Beefree SDK status is UP

Lastest published events

Multiparser Outage

Multiparser Outage

Incident - Loading and authorization issues

Beefree SDK Services, Components and Regions

Recent Beefree SDK events

Multiparser Outage

Multiparser Outage

Incident - Loading and authorization issues

Multiparser Outage

Content Service API Outage

Co-editing infrastructure restart

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!