Beefree SDK Status Page

Oct 14, 2026 · resolved Oct 14

# **Summary** On Oct 14, between 12:12 UTC and 12:26 UTC, a service disruption impacted the availability of the Editor component for end-users. The incident occurred during a planned configuration update aimed at decommissioning a legacy service. During execution via Terraform, an undetected state drift between the remote infrastructure and the defined configuration caused an unexpected destruction and recreation of the API Gateway, followed by a listener misconfiguration on the Application Load Balancer \(ALB\). Total service degradation lasted approximately 14 minutes. Full functionality was restored at 12:26 UTC following targeted manual remediation. # **Status** **Solved** # **Timeline \(UTC\)** Oct 14, 2026 * 12:10 UTC – A routine infrastructure update was initiated via Terraform to remove resources associated with a decommissioned service. * 12:12 UTC – Upon execution, Terraform identified an implicit dependency drift, triggering an unintended `destroy-and-recreate` cycle for the API Gateway instance. * 12:18 UTC – The API Gateway replacement was provisioned. However, traffic routing failed due to a mismatched configuration state on the Application Load Balancer \(ALB\) listener bindings. * 12:20 UTC – Engineering teams identified the routing anomaly on the ALB listener and initiated corrective configuration procedures. * 12:26 UTC – Listener configuration was fully restored and verified. Traffic flow to the EVC cluster normalized, resolving customer impact. **Incident window**: ~14m, all EVC services not reachable # **Customer impact** Duration: 14 minutes \(12:12 UTC – 12:26 UTC\) Affected Components: EVC Cluster underlying services, Editor interface. User Experience: End-users attempting to access or perform operations within the Editor experienced temporary service unavailability and request timeouts. No data loss or corruption occurred during this period. # **Root Cause** The root cause was an unexpected dynamic resource replacement triggered by Terraform execution, resulting from a latent configuration drift between the active cloud resources and the declarative state file. During the removal of legacy service declarations, an implicit resource attribute dependency within the Terraform provider schema evaluated the update as a breaking change requiring resource replacement rather than an in-place update. Because the environment had experienced minor manual or unindexed attribute shifts over time \(configuration drift\), the plan preview did not clearly highlight the cascading effect on the API Gateway's dependent ALB listener configuration. Consequently, when the gateway was recreated, the associated ALB listener bindings failed to map correctly to the target group, cutting off ingress traffic to the EVC cluster. # **Lessons Learned & Action Items** To prevent similar issues during future infrastructure changes, the following systemic improvements will be implemented: 1. Enhanced Pre-Apply Plan Inspection & Safety Gates: * Implement automated CI/CD checks to block Terraform execution if a plan contains destructive actions \(`destroy`\) on critical network infrastructure \(gateways, ALBs\) without explicit secondary authorization. 2. Drift Detection & Reconciliation Automation: * Introduce periodic scheduled drift-detection pipelines \(e.g., automated `terraform plan` audits\) to identify and reconcile discrepancies between real-world infrastructure and state files prior to active maintenance windows. 3. Decoupling Dependency Graphs: * Refactor infrastructure-as-code modules to isolate API Gateway definitions from underlying ALB target group lifecycle management, ensuring gateway updates cannot implicitly impact ingress routing listeners.

Sep 19, 2026 · resolved Sep 19

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.

Jun 19, 2026 · resolved Jun 19

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.

Jun 17, 2026 · resolved Jun 17

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 4, 2026 · resolved Jun 4

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.

Is Beefree SDK down right now?

No — Beefree SDK is up. All systems operational as of Oct 18, 2:15 AM UTC.

What is Beefree SDK's current status?

Beefree SDK: All Systems Operational. Alert24 checks Beefree SDK's status page continuously and can notify you the moment it changes.

How do I get alerted when Beefree SDK goes down?

Alert24 monitors Beefree SDK and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.