I don't expect fastly to name and shame a customer who made a valid change, nor do I expect fastly to give us a detailed explanation of what the bug is. I'm st

I don't expect fastly to name and shame a customer who made a valid change, nor do I expect fastly to give us a detailed explanation of what the bug is. I'm still a little annoyed at their status page [0]. It says: > We're currently investigating potential impact to performance with our CDN services. yet in the blog post we're talking about here it says: > Early June 8, a customer pushed a valid configuration change that included the specific circumstances that triggered the bug, which caused 85% of our network to return errors. 85% of your network returning errors is _not_ a potential performance impact. [0] https://status.fastly.com/incidents/vpk0ssybt3bj https://status.fastly.com/incidents/vpk0ssybt3bj