| We moved this page to our Documentation Portal. You can find the latest updates here. |
Question:
Why is my CDN Site still serving traffic after it has been deleted or suspended?
Environment:
OnApp CDN
Answer:
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' requests will still manage to hit to the CDN edge server A due to their ISP DNS cache. The time for DNS cache varies among different ISP DNS. In these circumstances, visitors (from the cached DNS network) will hit 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 is being updated, our system would not delete the CDN resource config at the CDN edge server immediately. The removal will be completed in 24 hours. This is related to the scenario of "DNS cache" as mentioned above.