> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/support-and-troubleshooting/common-issues-and-solutions/troubleshooting-performance-problems.md).

# 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:

<table><thead><tr><th width="366">Status</th><th>Typical Cause</th></tr></thead><tbody><tr><td>200</td><td>Request completed successfully</td></tr><tr><td>301 / 302</td><td>Redirect configured</td></tr><tr><td>304</td><td>Cached content reused</td></tr><tr><td>403</td><td>Access denied</td></tr><tr><td>404</td><td>Resource not found</td></tr><tr><td>429</td><td>Rate limiting</td></tr><tr><td>502</td><td>Invalid origin response</td></tr><tr><td>503</td><td>Origin unavailable</td></tr><tr><td>504</td><td>Origin timeout</td></tr></tbody></table>

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

**Related concepts**

* [HTTP Response Codes](/getting-started/concepts/http-response-codes.md)
* [Analytics](/products/performance-cdn/static-content-delivery/analytics.md)

### 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://clients.medianova.com/support-and-troubleshooting/common-issues-and-solutions/troubleshooting-performance-problems.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.