CDN Status Codes Report

To view a status codes report:

  1. Go to your Control Panel > Metrics > Status Codes menu.
  2. You can filter the statistics by:

    Frequency - select the frequency type (one minute, one hour, or one day)
    CDN resource - choose the CDN resource for which you want to view the statistics
    Time period - select the period start and end dates

  3. Click the Apply button. You will get the statistics chart and two tables:
    • The chart shows the number of requests with different error codes for the selected period.
    • You can view the list of error codes together with their amount of requests in the Status Codes table.
    • The HTTP Error Report (4XX & 5XX) table shows the list of CDN resources together with their amount of error requests.

OnApp applies the global setting for HTTP error code caching as follows:

  • proxy_cache_valid 404 1m
  • proxy_cache_valid 200 301 1d

To sort information by column in ascending or descending order, hover over the particular column header and click a triangle icon.

To export the statistics in csv format, click the Export to CSV button.

CDN hostname may return the following status codes:

  • 2XX (200, 201, 202, etc.) means that the HTTP request is successful.
  • 3XX (301, 302, etc.) means that there is a redirection layer being set up on the origin or webserver. To avoid any redirection conflict when using CDN, you can use an IP origin instead of a hostname origin. For example, instead of using www.mywebsite.com as an origin, use the IP address of www.mywebsite.com as a CDN resource origin.

  • 4XX (401, 402, etc.) means that the CDN PoP (edge servers) has an issue.

    Check the following:

    • The status of your CDN resource is Active. If it is Preparing, this status code is correct because the configuration of the CDN resource has not been populated to the CDN edge server.
    • If you set any country access in the Access Policy field when creating or editing for your CDN resource, this status code is correct provided that you are from the prohibited countries.
    • With the Content Compare Tool, check which edge server is throwing a 4XX error. If it happened only on a few CDN edge servers but not all, contact OnApp Support and remove these locations from our CDN edge group temporarily to keep users from receiving a 4XX error.

  • 5XX (501, 502, etc.) means that CDN edge servers have an issue with fetching content from the CDN resource origin. When the CDN resource origin is offline, cached files are still available. If the file requested from a visitor is not currently cached on the edge server when the origin is offline, end users get a 500 error.

    Check the following:

    • The Origin HTTP is accessible.
    • The firewall has not blocked the edge server.
    • DNS for the origin hostname is working.