For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Access LaunchDarkly through a public IP range for general or European Union (EU) instances
  • Updates
  • Additional resources
Infrastructure

Public IP list

Was this page helpful?
Previous

Projects

Next
Built with

Overview

This topic explains how to access LaunchDarkly through one of our public IPs. If you’re using a firewall, add a LaunchDarkly IP range to your firewall settings.

If you want to configure access by domain instead, read the Domain list.

Access LaunchDarkly through a public IP range for general or European Union (EU) instances

To help you access LaunchDarkly services through your firewall, we provide a list of LaunchDarkly’s public IP ranges.

Access the list of public IP ranges from this URL:

Access public IP ranges
$ https://app.launchdarkly.com/api/v2/public-ip-list

The LaunchDarkly European Union (EU) instance has its own public IP list. This list is available at the following URL:

Access EU instance public IP ranges
$ https://app.eu.launchdarkly.com/api/v2/public-ip-list

The public IP endpoint returns a JSON object with two attributes:

  • addresses: This element contains the IP addresses LaunchDarkly uses. These IP addresses receive HTTPS connections your SDKs initiate through port 443. Configure your firewalls and proxies to allow persistent outbound connections so your SDKs can subscribe to updates.
  • outboundAddresses: This element contains the IP addresses LaunchDarkly uses for outbound webhook-based notifications and integrations. LaunchDarkly uses these addresses when making calls to your network. Add each outbound address to your allow list individually.

Updates

We update this list from time to time. You can automate calls to this API to detect when the IP ranges change.

We also post upcoming changes to this list in advance on our status page. Normally we post the update two weeks in advance of the change taking effect. However, in certain exceptional circumstances the notification window may be shorter.

You can also use the REST API: Get the public IP list

Additional resources

To learn how to obtain the IP list for just the required domains associated with a specific SDK, read How to get IPs LaunchDarkly uses.

If you want to manage an IP allowlist to restrict access to your LaunchDarkly account, read IP allowlist.