> For the complete documentation index, see [llms.txt](https://docs.proxyshard.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proxyshard.com/eng/technologies-and-capabilities/about-udp/field-test-results.md).

# Results of our field tests

Initially, we added <mark style="color:purple;">**UDP**</mark> support to all our <mark style="color:purple;">Datacenter</mark> proxy locations and tested it through ClashX. We got the following results:

* Google - 15 accounts created in a row with no errors and no phone numbers.
* Discord - registration and server login, including servers with enhanced bot checks, were successful! Even on servers that usually block ISP proxies.
* Twitter - a 10-image captcha was accepted with errors, and re-verification passed without issues.
* Facebook/Instagram/FB ADS... - registration without problems or captcha.

For comparison, the same actions through ISP proxies without **UDP** ended in errors or required SMS verification.

And all of this on Datacenter proxies!

**Support is now available on all our products** :tada:


---

# 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://docs.proxyshard.com/eng/technologies-and-capabilities/about-udp/field-test-results.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.