We are currently investigating an issue causing websites hosted on our Website Builder platform to display a "Not Secure" message. Thank you for your patience.
Last update on
We are currently investigating an issue causing websites hosted on our Website Builder platform to display a "Not Secure" message. Thank you for your patience.
Last update on
The issue has been identified and our engineering team is actively working through final validation. Additional updates will be shared as more information becomes available.
Last update on
Investigating - Cloudflare is aware of and investigating an issue impacting a subset of KV API requests, resulting in increased latency and timeouts. Workers using Assets are also experiencing errors. This does not impact KV through the binding. Apr 13, 2026 - 20:15 UTC
Last update on
The root cause of the issue has been found. We believe that the issue will resolve itself as agents are allowed time to update. If you are still experiencing issues performing Remote Takeovers, please contact our support team for help resolving the issue. We will continue to monitor agent health and update here is the situation changes.
Last update on
Investigating - Cloudflare is aware of and investigating an issue impacting a subset of KV API requests, resulting in increased latency and timeouts. Workers using Assets are also experiencing errors. This does not impact KV through the binding. Apr 13, 2026 - 20:15 UTC
Last update on
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (Bahrain) Region (ME-SOUTH-1). We continue to make progress on recovery efforts across multiple workstreams. With the immediate phase of this event now better understood, we are moving to a more targeted communication model. Going forward, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center. We continue to strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.
Last update on
Monitors
Amazon Web Services
StatusGator