I believe that Fastly should provide guidelines for their WAF blocking rules. It should be public what the rules are that are blocking their contents. I believe Fastly should provide regional IP addresses instead of POP IPs. Fastly should provide features similar to Cloudflare regarding a block list. Additionally, a POP address should be there with a wide range of IP addresses provided, public static IP addresses, so customers can integrate egress IPs. Fastly should provide WebP image processing on the backend instead of on the fly. It would be a very useful feature to avoid unnecessary time for browser to browser and local cookies. I believe that Fastly service has a few gaps. We are not getting quick responses from Fastly technical support engineers. Sometimes they depend on their D3 developers. There should be transparency.
