Why is my CDN Site still serving traffic after it has been deleted or suspended?
This is possibly caused by the combination of DNS cache + CDN Resource Config Delete Delay.
DNS Cache- Once you suspend/remove a cdn resource or updating edge group (change from location A to B), our DNS redirector will stop redirecting all new user request to the CDN edge server A. However, there are some visitors request will still manage to hit to the CDN edge server A due to their ISP DNS cache. The time for DNS cache is varies among different ISP DNS. In this circumstances, visitors (from the cached dns network) will hit to the CDN edge A directly without going through CDN redirector.
CDN Resource Config Delete Delay - Once a CDN resource is suspended/removed or edge group being updated, our system would not delete the cdn resource resource config at the CDN edge servers immediately but only do that 24 hours later. This is to cater for the scenario of "DNS cache" as mentioned above.