# Connection Complaint Policy

We try our best to deliver the most performant network we can for our customers. Unfortunately, there are some things are are simply out of our control (congestion on ISPs, unstable mobile data signal, microwave ovens turned on, or similar).

Therefore, TCPShield requires the following before considering a connection degradation event:

* A minimum of 5 players in similar region experiencing similar issue(s)
* A traceroute from at least one player, to TCPShield\
  `tracert play.yourserver.com`
* Source IP or usernames from at least 3 players.

TCPShield will not impose fixes for one-off connection complains, and must see evidence of widespread issues. The internet is large and complex, and does not route ideally at times. As such, imposing fixes for one player may create unexpected issues for others.


---

# 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.tcpshield.com/troubleshooting/connection-complaint-policy.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.
