SecOpsNews / news

RSS items as GitHub Issues for the discerning engineering leader or security professional
MIT License
45 stars 0 forks source link

[CloudFlare] Dashboard and API Maintenance #15029

Closed github-actions[bot] closed 1 year ago

github-actions[bot] commented 1 year ago

THIS IS A SCHEDULED EVENT Jun 10, 15:00 - 15:45 UTC

May 15, 18:31 UTC

Scheduled - Over the past several months, Cloudflare has undertaken an overhaul of some of our critical configuration data systems to improve security and reliability. There are 3 remaining upgrades that need to take place. Each of these will result in a few minutes of intermittent availability for some of our APIs. None of these upgrades will impact the serving of traffic on the edge.

These APIs will have an elevated error rate during each of these upgrades. In all cases, we expect normal operations to resume after 3-5 minutes of intermittent errors, and any failed operations can be retried when service is restored.

Below is a list of the Impacted Cloudflare products. In each case you will find the API Impact described and confirmation of the parts of Cloudflare’s Edge that will continue to function as normal.

The creation/deletion of D1 databases - Already deployed D1 databases will continue to function as normal across Cloudflare’s network

The creation and deletion of Workers Pages Projects - Already deployed Pages sites/deployments will function as normal across Cloudflare’s network

API Shield and Page Shield configuration changes - Both API Shield and Page Shield will continue to function as normal across Cloudflare’s network

Bot Management and Bot Fight Mode configuration changes - Both Bot Management and Bot Fight Mode will continue to function as normal across Cloudflare’s network

Some Cache Configuration changes including Smart Tiered Cache, Max HTTP Version to origins, and Cache Reserve settings will not be able to be changed during the upgrade - These features will continue to work normally across Cloudflare’s network

Uploading new Images or modifying existing images or image variants - Images will continue to be served normally across Cloudflare’s network

Creating/deleting/changing Logpush jobs - Existing Logpush jobs will continue to run as normal

Enabling or disabling AMP Real URL - AMP URL will continue to work normally on enabled zones across Cloudflare’s network

Creating/deleting/changing Cloudflare Tunnels, new Tunnel registration, and new Warp Device registration - Existing Tunnels and Warp device connections will be uninterrupted unless network connectivity is dropped and a reconnect is attempted.

Cloudflare Radar may be intermittently available

Creation/modification of DDoS overrides - DDoS protection will be fully functional across Cloudflare’s network

Creation of new Zaraz configurations and/or modification of existing Zaraz configurations, including adding tools, fields, actions, triggers, variables and/or settings - Existing configuration will be fully functional across Cloudflare’s network

Creation and modification of any waiting room configuration settings - Existing configuration will be fully functional across Cloudflare’s network

Turnstile configuration changes - Existing configuration will be fully functional across Cloudflare’s network

Creation, modification and processing of live inputs, video uploads and new live streams - Existing streams will function as usual across Cloudflare’s network

For new accounts that signed up for R2 during this maintenance window, expect S3 API access to temporarily fail until the upgrade is complete - Existing accounts will function as usual across Cloudflare’s network

Pub/Sub: Creation of new namespaces, brokers, modification of existing brokers, and generation of new client keys - Existing brokers and message delivery. Publishing to a topic, subscribing to a topic and any on-publish Worker hooks will continue to work as usual across Cloudflare’s network

We will post more information about the 2nd and 3rd parts of the updates soon.

https://www.cloudflarestatus.com/incidents/l0ds1nj98js8

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 1 day with no activity. Remove stale label or comment or this will be closed in 1 day.

github-actions[bot] commented 1 year ago

This issue was closed because it has been stale with no activity.