# Performance Scoring

## Overview

Performance scores measure how well a provider performs on a specific metric relative to other providers in the same location. View each provider’s metric performance scores in the **Summary View** and **Universal Application Summary** [destination views](https://docs.thousandeyes.com/product-documentation/internet-insights/provider-intelligence/view-results/destination-views).

## Performance Score Calculation and Example

Performance scores form the backbone of all overall scores. The process transforms the raw data received\* from tests into comparable normalized scores. Here’s how we do it.

1. **Data Collection**: We collect raw values for every metric every hour for all providers in the same city going to the same destination(s).\
   Example: For five providers, their latency values during one hour might be 10, 12, 15, 18, and 20 ms.
2. **Identify Min/Max:** Each hour, the scoring algorithm identifies the minimum and maximum values by any provider.\
   In our example: Min and max for the five providers is 10 ms and 20 ms for that hour.
3. **Deviation Analysis:** The algorithm then calculates how far from the max and min each provider’s value sits, resulting in a figure between 0 (the min) and 1 (the max), and inverted for most metrics to reflect that lower values equal better performance. This figure can then be translated into a 0-100 “performance score”.\
   In our example: Provider 3, whose latency is 15 ms, sits halfway between the min and max values, so scores 50 for that hour.
   * Notably, each hour can have a different min and max, since provider 3’s peers performance can vary, meaning the same raw value (like 15 ms) won’t always result in the same performance score.
4. **Aggregation of Deviations:** Daily performance scores are averaged from 24 hourly scores.\
   In our example: Despite remaining steady at 15 ms, provider 3’s hourly performance scores over one day could range from 33-100, but average out to 75.
5. **Final Scoring:** Longer-term performance scores are averaged from available daily scores over your selected time frame (1, 3, or 6 months).\
   In our example: Over 3 months, provider 3’s raw average might remain at 15 ms, but if its peers improved or worsened, that will affect provider 3’s performance score accordingly.

Each metric is scored independently for each [percentile](https://docs.thousandeyes.com/product-documentation/internet-insights/provider-intelligence/view-results/summary-statistics). Changing the percentile or time frame can affect relative scores.

\*For all metrics except response codes and outages, which always show counts, not scores.


---

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

```
GET https://docs.thousandeyes.com/product-documentation/internet-insights/provider-intelligence/scoring-methodologies/performance-scoring.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.