Troubleshooting Performance Problems

Performance issues can originate from the client, the CDN, the origin server, or the network between them. Identifying where latency or failures occur is the first step in resolving delivery problems.

Medianova provides monitoring tools, analytics, and diagnostic information to help investigate performance-related issues.

Check Response Status Codes

HTTP response status codes provide a quick indication of where a request failed.

Common examples include:

Status	Typical Cause
200	Request completed successfully
301 / 302	Redirect configured
304	Cached content reused
403	Access denied
404	Resource not found
429	Rate limiting
502	Invalid origin response
503	Origin unavailable
504	Origin timeout

A sudden increase in 4xx or 5xx responses may indicate configuration issues, origin failures, or security policies blocking requests.

Related concepts

• HTTP Response Codes

• Analytics

Verify Origin Health

If cached content cannot be served, the CDN forwards the request to the origin.

Verify that:

• The origin server is reachable.

• DNS resolution is correct.

• The origin responds within the configured timeout.

• SSL/TLS configuration is valid.

• Firewall rules allow CDN IP addresses.

Origin connectivity problems commonly result in 502, 503, or 504 responses.

Review Cache Behavior

Unexpected cache behavior can increase origin traffic and response times.

Check the following:

• Cache expiration settings

• Browser cache policies

• Cache-Control headers

• Query string caching

• Purge operations

Confirm that frequently requested content is cacheable whenever appropriate.

Analyze Traffic Patterns

Review available analytics to identify abnormal traffic patterns.

Useful indicators include:

• Request volume

• Bandwidth usage

• Cache hit ratio

• Geographic traffic distribution

• Response status code trends

Traffic spikes or sudden changes may indicate origin issues, configuration changes, or malicious traffic.

Review Security Policies

Security features may intentionally block requests.

Review configured:

• WAF rules

• Rate Limiting policies

• IP Access Rules

• Geo restrictions

Blocked requests commonly generate 403 Forbidden or 429 Too Many Requests responses.

Contact Support

If the issue cannot be identified after reviewing the available diagnostics, collect relevant information before contacting support.

Include:

• Resource hostname

• Affected URLs

• Timestamp of the issue

• HTTP status codes

• Error messages

• Steps to reproduce the problem

Providing this information helps reduce investigation time.