Compare the status, incidents stats and history between Fastly and Cloudflare
Every service has different practices when updating its status page, so compare these stats with a grain of salt. E.g., one service can be more aggressive when updating its status page than other so that they will have more incidents, but it doesn't mean it is worse than the other.
Traffic in Palermo (PMO) has been temporarily rerouted. All other locations and services are unaffected.
Customers with the Fastly WAF are unable to navigate to the WAF console for administration. Our engineering teams are currently investigating.
We are currently investigating performance issues affecting the VCL configuration and [email protected] module updates. CDN delivery, stats aggregation, and all other data plane services are unaffected.
Less than 1% of our customers are seeing sporadic 500 errors. We are rolling out a fix over the next few hours
Customers using Bot Management and Cloudflare Workers may no longer see JA3 Fingerprints when inspecting the Cloudflare object, or using Worker's JA3 field directly.
Cloudflare is investigating issues with DNS Analytics API. Customers that use DNS Analytics API may observe increased errors.
Try it out! How much time you'll save your team, by having the outages information close to them?