Cloudflare has confirmed that all services have returned to normal. ConfigBee systems are also operating normally at this time, and we continue to monitor stability closely.
⏱ Incident Duration - Started: 11:30 AM UTC - Ended: 5:00 PM UTC
🟡 Impact on ConfigBee during the Incident - Our website and blog were unstable during the Cloudflare outage and experienced intermittent downtime. - ODN services experienced performance degradation, including increased latency due to global edge cache failures — but there were no actual errors and no downtime. - Configuration updates were delayed slightly
All mission-critical platform services (SDK reads, feature flags, dynamic configurations) remained fully operational.
🟢 Current Status All ConfigBee systems are functioning normally.
Cloudflare services have stabilized, and we are continuing to monitor both networks to ensure full recovery.
Posted Nov 18, 2025 - 18:06 UTC
Monitoring
Cloudflare is currently experiencing a global network service degradation, causing intermittent errors and elevated latencies across multiple regions.
How ConfigBee is affected - ConfigBee has observed increased latency due to widespread Cloudflare edge cache failures. However, there has been no downtime for any mission-critical services.
Thanks to our multi-cloud, hyper-available architecture powered by our proprietary ODN, all traffic automatically failed over to AWS within seconds. This ensured uninterrupted delivery of feature flags and dynamic configurations.
Current Status - Automatic multi-cloud failover is functioning as designed - No customer action is required - Expect slightly elevated latency until Cloudflare fully restores services - All non-essential services remain unaffected
We continue to monitor the situation closely
We will share further updates as Cloudflare progresses with remediation.
Posted Nov 18, 2025 - 11:30 UTC
This incident affected: ODN Services (Essential ODN service - Feature Flags & Configuration Delivery, Contextual Targeting & Real-time Streaming Service).