> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/uof/error-handling/error-catalogue/connection-reset.md). # Connection reset **Error Description** Multiple instances of "SocketException: Connection reset" are appearing in the logs related to API calls, particularly when attempting to connect to ".[betradar.com](http://betradar.com)." "Related to API call" signifies that the first line above the stack trace, which corresponds to the associated exception, indicates a failed call to ".[betradar.com](http://betradar.com)." What It Means The "Connection reset" message indicates that the socket connection being utilized was forcibly closed, either by the remote server or by an intermediary device in the network path. This can occur due to various reasons, including: * The remote server crashing or restarting, leading to the termination of existing connections. * A network device (e.g., router or firewall) between the client and server terminating the connection due to a timeout or configuration rule. * Limitations on the number of concurrent connections at the remote server, resulting in the forced closure of connections. **Applies to** All integrations using Unified Odds Feed (including SDKs and direct integrations) **Symptoms** A relatively high volume of requests to the Sports API is resulting in "SocketException: Connection reset", with customer concerns arising when this occurrence rate reaches 0.1% to 0.5% of requests over several hours. When It Happens This exception can arise at different stages of network communication, such as during connection establishment, data transmission, or idle connection maintenance, depending on the underlying cause of the "connection reset." In any scenario, it is essential to handle SocketException and implement robust error recovery mechanisms to ensure reliability and performance, particularly in distributed environments susceptible to network-related issues. **Resolution** When investigating network-related issues, the recommended approach involves inspecting each router along the path from the client to the server to identify and resolve potential connectivity or configuration issues. --- # 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.sportradar.com/uof/error-handling/error-catalogue/connection-reset.md?ask=&goal= ``` `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.