Today, Amazon Web Services (AWS) experienced a significant disruption in its US-EAST-1 region, impacting many cloud-dependent platforms globally.
ConfigBee’s Essential Services remain fully operational and unaffected for nearly all customers, as our SDKs primarily connect through Cloudflare, ensuring continuous delivery of feature flags and configurations.
A very small, exceptional subset of customers with custom overrides pointing to AWS CloudFront as the primary endpoint may experience slight latency.
Non-Essential Services such as the Control Plane, real-time streaming, and REST API may experience increased error rates and latency, and some customers might observe intermittent availability issues. These affect management functions and real-time updates but do not impact core runtime delivery or your applications’ normal operation.
Our team is actively monitoring the situation raised by the AWS US-EAST-1 outage. Due to ConfigBee’s multi-cloud, hyper-available, and resilient architecture, the impact on our Essential Services has been minimal to none. The default SDK configuration prioritizes Cloudflare endpoints for initial configuration retrieval, ensuring continuous service delivery even during significant disruptions in any single cloud provider. This robust design allows ConfigBee to maintain uninterrupted feature flag delivery and runtime consistency, providing peace of mind to our customers and ourselves throughout this event.
For live updates on this and any ongoing incidents, please visit our status page at status.configbee.com or configbee.statuspage.io.
We encourage you to follow us on X (https://x.com/configbee) and Linkedin (https://www.linkedin.com/company/configbee/) to receive timely notifications, behind-the-scenes insights, and important service announcements. Your trust and staying informed are important to us—thank you for being part of the ConfigBee community.