Skip to main content
This topic explains which domains the LaunchDarkly SDKs connect to by default. If you are restricting access, make sure your SDK can reach these domains. If you use the Relay Proxy, you must update your SDK’s configuration to connect to the Relay Proxy rather than using these defaults.
Configure your SDK: Relay Proxy configuration
If you use a federal instance of LaunchDarkly, and are not using the Relay Proxy, you must update your SDK’s configuration to connect to federal instance URLs.
Configure your SDK: Service endpoint configuration
If you use a firewall and would like to configure access based on IP addresses, read Public IP list.

​
Accessing LaunchDarkly by domain

The LaunchDarkly SDKs access various base uniform resource identifiers (URIs) for different services. The server-side, client-side, and mobile SDKs use the streaming service and polling service to request flag updates. They use the events service to send data back to LaunchDarkly for Experimentation analysis. The following table describes the default base URIs for each service for the server-side SDKs: The following table describes the default base URIs for each service for the client-side JavaScript SDKs: The following table describes the default base URIs for each service for the mobile SDKs: The edge SDKs do not use the streaming service or polling service to request flag updates. They get flag data from their provider-specific store. The edge SDKs send events data back to LaunchDarkly using the https://events.launchdarkly.com URI.