--- title: Run Mobile App tests from Restricted Networks description: Run Mobile App tests from restricted networks breadcrumbs: >- Docs > Synthetic Testing and Monitoring > Mobile Application Testing and Monitoring > Run Mobile App tests from Restricted Networks --- # Run Mobile App tests from Restricted Networks {% callout %} # Important note for users on the following Datadog sites: app.ddog-gov.com {% alert level="danger" %} This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site.md). (). {% /alert %} {% /callout %} ## Overview{% #overview %} Some of your applications might not be available to the public internet because they are accessing development or local environments, or they are internal applications intended for users within your corporate network (for example, your corporate intranet or VPN). {% image source="https://docs.dd-static.net/images/mobile_app_testing/mobile_app_restricted_networks.f4c99444d4232c0b3682d9aa8c34673c.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/mobile_app_testing/mobile_app_restricted_networks.f4c99444d4232c0b3682d9aa8c34673c.png?auto=format&fit=max&w=850&dpr=2 2x" alt="Diagram showing testing of mobile apps behind a firewall or restricted networks" /%} To test these applications, add the following IP address ranges to your company's allowlist. This ensures that requests from your applications in Datadog Mobile App Testing succeed. The following is the list of IP ranges associated with the real devices used for Datadog Mobile App Testing: `54.244.50.32/27``99.78.197.0/29``15.248.40.40/29``54.239.50.200/29``34.125.90.96/27``34.125.246.157/32``44.225.33.89/32``66.85.48.0/21``162.222.72.0/21``66.85.48.0/21``162.222.72.0/21``34.145.254.128/27``34.107.82.96/27``34.141.28.96/32``162.222.79.0/27``185.94.24.0/22``103.231.42.40/29``103.231.79.40/29``209.58.137.40/29``217.112.145.88/29``149.6.5.8/29``3.221.56.233``3.72.174.80``3.73.105.110/32``3.72.144.221/32``18.235.85.58/32``44.207.198.148/32``3.109.252.59``43.205.182.101``18.138.79.89``54.254.173.86``52.72.255.172``13.126.232.213``34.246.27.205``3.222.169.4``43.204.134.9``54.228.155.35``54.225.186.4``52.71.149.142``44.238.12.62``3.111.139.20``54.255.17.88``3.64.247.89` ### HTTP steps{% #http-steps %} Below is the list of IP ranges required for executing HTTP steps within Synthetic Mobile Application Tests. You may disregard these ranges if your tests do not use HTTP steps. `52.13.151.244/32``54.201.250.26/32``44.236.137.143/32``52.35.189.191/32``52.88.130.174/32``44.236.20.182/32``35.85.123.4/32``34.210.15.72/32``54.244.50.32/27``99.78.197.0/29``15.248.40.40/29``54.239.50.200/29``34.208.32.189/32``52.35.61.232/32``52.89.221.151/32``3.120.223.25/32``3.121.24.234/32``18.195.155.52/32` ## Troubleshooting{% #troubleshooting %} If you experience issues with Mobile App Testing on restricted networks, use the following troubleshooting guidelines. If you need further assistance, contact [Datadog support](https://docs.datadoghq.com/help). ### Unable to launch recorder{% #unable-to-launch-recorder %} To launch the Mobile Application Testing (MAT) Recorder, Datadog needs to establish UDP/TCP TURN connections to enable WebRTC connections. If the user is behind a restrictive network (such as a strict firewall or VPN), these connections may fail, leading to a "Device unexpectedly disconnected" error: {% image source="https://docs.dd-static.net/images/mobile_app_testing/restricted_networks/device_disconnected_error.9d222293ae02203c9f1144a81389def6.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/mobile_app_testing/restricted_networks/device_disconnected_error.9d222293ae02203c9f1144a81389def6.png?auto=format&fit=max&w=850&dpr=2 2x" alt="Screenshot of launching a mobile device, displaying the disconnected error." /%} To check for successful UDP/TCP TURN connections, run a network test using a [Twilio Network Test](https://networktest.twilio.com/). The result of the test confirms whether connectivity to TURN servers is successful or not. If the connection is successful, you will see a message like "Successfully established a UDP connection to Twilio": {% image source="https://docs.dd-static.net/images/mobile_app_testing/restricted_networks/twilio_test.11b40bff06dd8023ab4ab2e7eacafdaa.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/mobile_app_testing/restricted_networks/twilio_test.11b40bff06dd8023ab4ab2e7eacafdaa.png?auto=format&fit=max&w=850&dpr=2 2x" alt="Screenshot of a successful test using a Twilio Network Test." /%} If the test fails, Twilio generates a log output indicating errors due to an inability to establish a connection. For example: ``` [3:09:13 PM] Test "TURN UDP Connectivity" started... [3:09:20 PM] Error: Error: Could not establish a UDP connection to Twilio within 5 seconds [3:09:20 PM] Test "TURN TCP Connectivity" started... [3:09:25 PM] Error: Error: Could not establish a TCP connection to Twilio within 5 seconds [3:09:25 PM] Test "TURN TLS Connectivity" started... [3:09:30 PM] Error: Error: Could not establish a TLS connection to Twilio within 5 seconds [3:09:30 PM] Test "Bandwidth" started... [3:09:35 PM] Error: Error: Could not establish a connection to Twilio within 5 seconds ``` ## Further reading{% #further-reading %} - [Best practices for creating end-to-end tests](https://www.datadoghq.com/blog/test-creation-best-practices/) - [Learn how to create Synthetic mobile app tests](https://docs.datadoghq.com/synthetics/mobile_app_testing.md) - [Learn how to upload your iOS or Android mobile applications](https://docs.datadoghq.com/synthetics/mobile_app_testing/settings.md)