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
  • Remediation options
  • Bootstrap your SDK
  • Create a Relay Proxy
Infrastructure

LaunchDarkly in China and Pakistan

Was this page helpful?
Previous

LaunchDarkly in the European Union (EU)

Next
Built with

Overview

Some customers and end users in a limited list of countries have had difficulty maintaining a persistent connection to LaunchDarkly. The affected countries are China and Pakistan.

While LaunchDarkly is a product with global reach, inconsistencies between the internet services of different countries can make it difficult to predict where we might have outages. Customers in China and Pakistan have reported difficulty maintaining a connection to LaunchDarkly.

We offer these customers the following alternatives to a conventional LaunchDarkly process.

Remediation options

There are two options for improving performance if you’re using LaunchDarkly in China or Pakistan: bootstrapping your SDK, or creating a Relay Proxy.

Bootstrap your SDK

The pros and cons of bootstrapping include:

  • Pros: This is quick and easy to do, and will reduce startup time to near zero.
  • Cons: If you bootstrap from local storage, end users might initially receive outdated flag variations. New variation updates will still suffer from inconsistent performance.

Configure your SDK: Bootstrapping

Create a Relay Proxy

The pros and cons of using the Relay Proxy include:

  • Pros: This may be able to serve your clients much faster.
  • Cons: This is much more complicated to set up than bootstrapping.

To learn more, read The Relay Proxy.