Hopefully not because of this submission, some more updates started flowing on the Scaleway side [1], but nothing solving the issue.
The are some workarounds (from Marco@ [2])
moving workload out of scaleway to other datacenters and keeping all cloudflare CDN and features working perfectly (seems to be affecting exclusively scaleway/online.net)
disabling all cloudflare features (DNS only) (some people can’t do it as cloudflare could be integral part of webapps flow and servings)
But applying those can't be done in all cases (i.e. disables Cloudflare WAF, CDN, etc.).
Comments
Hopefully not because of this submission, some more updates started flowing on the Scaleway side [1], but nothing solving the issue.
The are some workarounds (from Marco@ [2])
But applying those can't be done in all cases (i.e. disables Cloudflare WAF, CDN, etc.).
[1] https://status.scaleway.com/incidents/y19hcz28rkwp
[2] https://scaleway-community.slack.com/archives/C7Z76CCUE/p167...