Data centers

RC provides both domestic and international data centers to support businesses primarily located in China or abroad.

When creating a new application in the Console, you need to specify the data center for the application.

The client SDKs used for different data centers are consistent. However, apps using the international data center must modify the client SDK configuration during integration.
Different data centers must use the corresponding server API addresses based on the region.
Data migration between different data centers is not supported. Please choose your data center carefully.

Selecting a Data Center

You can choose from the following data centers:

China (Beijing) Data Center
Singapore Data Center

The following data centers are not available for self-selection by default. If you wish to select any of the following data centers, you can contact RC's business personnel. After receiving your request and completing the necessary review process, we will enable the corresponding data center option for you. Once enabled, you can select the following data centers in the Console.

North America Data Center
Singapore B Enterprise Cooperation Data Center
Saudi Arabia Data Center

tip

If you select the China (Beijing) Data Center, you must use the domestic API address when integrating RC's server API into your app's backend. By default, the client integration connects to the China (Beijing) Data Center.
If you select an international data center, such as Singapore, Singapore B, North America, or Saudi Arabia, you must use the corresponding international API address when integrating RC's server API into your app's backend. When integrating the client, you must pass in the corresponding area code or manually set the SDK's server connection address.

China (Beijing) Data Center

If your business is primarily in China and meets the following descriptions, it is recommended to select the China (Beijing) Data Center.

User and message data need to be stored in China.
The application is launched and operated in China.
The application's users are mainly in China with no frequent cross-border communication needs.

When using the China (Beijing) Data Center, please note the following:

When creating an application in the Console, you have already specified the Data Center as China (Beijing).
When integrating the client SDK, you do not need to worry about the internal data center address configuration. The RC client SDK connects to the China (Beijing) Data Center by default.
When integrating RC's Server API into your app's backend, you must use the dedicated API address for the China (Beijing) Data Center, as follows:
- api.rong-api.com
- api-b.rong-api.com

International Data Center

If your business is primarily abroad, and the application is directly launched overseas to serve local users, it is recommended to select an international data center (Singapore, Singapore B, North America, Saudi Arabia). To learn about RC's international data center access nodes, please refer to International Access Nodes.

tip

If your app's users are spread globally, with frequent cross-border user interactions, and your business is sensitive to latency and data security, you can access RC's global communication network service. This can reduce the latency for overseas users accessing domestic services from 2000ms to as low as 190ms. Learn more.

When using an international data center (Singapore, Singapore B, North America, Saudi Arabia), please note the following:

When creating an application in the Console, you have already specified the Data Center as Singapore, Singapore B, North America, or Saudi Arabia.
When integrating the client SDK, configure the SDK to connect to the corresponding international data center address.
- If you are using Android/iOS SDK version ≧ 5.4.2, you do not need to use the configuration method described in this document. Simply pass in the area code for the data center in the SDK's initialization configuration. Once configured, the SDK will enable the internal service address corresponding to the area code. For details, refer to the Initialization documentation in the client SDK.
- If you are using Android/iOS SDK version < 5.4.2, or using SDKs for other platforms, refer to the following section Configuring the SDK to Connect to an International Data Center.
When integrating RC's Server API into your app's backend, you must use the dedicated API address for the international data center (Singapore, North America).

Refer to the following section Using the Server API International Address.

Configuring the SDK to Connect to an International Data Center

If the application you created on the RC platform uses an international data center (not the China (Beijing) Data Center), you must modify the data center used by the SDK during integration.

tip

The data center of the App Key must match the data center in the client SDK.

Configuring via Area Code

In older versions of the SDK, if an international data center was used, you had to manually configure the navigation address, statistics service address, etc., for the corresponding data center in the client SDK. This often led to issues due to missing configurations.

To simplify the international data center configuration process, we have encapsulated the configurations for different data centers as area codes in the newer SDK versions. If your App Key uses an international data center, you only need to pass in a valid area code (AreaCode / RCAreaCode) during initialization to complete the configuration. Except for special scenarios, there is no longer a need to manually change a series of domain addresses.

If the SDK you are integrating meets the following requirements, you can directly configure the area code for the international data center:

Android IMLib/Global IM UIKit: SDK ≧ 5.4.2

First, check the data center of the current App Key in the Console, and find the corresponding enumeration value in the API documentation AreaCode. The sample code configures the area code as AreaCode.SG (Singapore Data Center).
```
String appKey = "Singapore_dev_AppKey";
AreaCode areaCode = AreaCode.SG;

InitOption initOption = new InitOption.Builder()
    .setAreaCode(areaCode)
    .build();

RongCoreClient.init(context, appKey, initOption);
```
iOS IMLib/Global IM UIKit: SDK ≧ 5.4.2

First, check the data center of the current App Key in the Console, and find the corresponding enumeration value in the API documentation RCAreaCode. The sample code configures the area code RCAreaCodeSG (Singapore Data Center).
```
NSString *appKey = @"Your_AppKey"; // example: bos9p5rlcm2ba
RCInitOption *initOption = [[RCInitOption alloc] init];
initOption.areaCode = RCAreaCodeSG;

[[RCCoreClient sharedCoreClient] initWithAppKey:appKey option:initOption];
```
Web IMLib: SDK ≧ 5.7.9

First, check the data center of the current App Key in the Console, and find the corresponding enumeration value in the API documentation AreaCode. The sample code configures the area code as AreaCode.SG (Singapore Data Center).
```
// Application initialization, ensure this process is executed only once
RongIMLib.init({ appkey: '<Your-App-Key>', areaCode: AreaCode.SG});
```

Manually Configuring International Data Center Domains

If the SDK version and platform combination you are integrating meets the following descriptions, configuring an international data center via area code is not yet supported. Please follow the documentation below to manually configure the navigation server address and statistics server address.

Android IMLib/Global IM UIKit: SDK < 5.4.2
iOS IMLib/Global IM UIKit: SDK < 5.4.2
Web IMLib: SDK < 5.7.9
Flutter IMLib/Global IM UIKit: SDK < 5.2.4
React Native IMLib: SDK < 5.2.4

Android

tip

If the SDK version is < 5.4.2, please use the following configuration. If the SDK ≧ 5.4.2, please proceed to Configuring via Area Code.

Before initializing the SDK with init, first set the navigation server address and statistics server address for the international data center:

Use the setServerInfo method to set the navigation server address:

/**
* Set the navigation server and media server addresses for the international data center.
* This method must be used before {@link #init(Context, String)}.
*
* @param naviServer The navigation server address for the international data center.
* @param fileServer The file server address (only for private cloud use).
*/
public static void setServerInfo(final String naviServer, final String fileServer) {
    if (TextUtils.isEmpty(naviServer)) {
        RLog.e(TAG, "setServerInfo naviServer should not be null.");
        throw new IllegalArgumentException("naviServer should not be null.");
        }
        RongIMClient.setServerInfo(naviServer, fileServer);
}

Navigation server address (naviServer)
- Singapore: nav.sg-light-edge.com (primary), nav-b.sg-light-edge.com (backup)
- Singapore B: nav.sg-b-light-edge.com (primary), nav-b.sg-b-light-edge.com (backup)
- North America: nav.us-light-edge.com (primary), nav-b.us-light-edge.com (backup)
- Saudi Arabia: nav.sau-light-edge.com (primary), nav-b.sau-light-edge.com (backup)
File server address (fileServer): This is only applicable to private cloud customers. Public cloud customers can pass null to use the default file server address.

Use the setStatisticDomain method to set the statistics server address:
- Singapore: stats.sg-light-edge.com
- Singapore B: stats.sg-b-light-edge.com
- North America: stats.us-light-edge.com
- Saudi Arabia: stats.sau-light-edge.com

iOS

tip

If the SDK version is < 5.4.2, please use the following configuration. If the SDK ≧ 5.4.2, please proceed to Configuring via Area Code.

Before initializing the SDK with init, first set the navigation server address and statistics server address for the international data center:

Use the setServerInfo method to set the navigation server address:

/*!
Set the navigation server and file server information for the international data center.
@param naviServer    The navigation server address for the international data center. Refer to the following for specific formats.
@param fileServer    The file server address (only for private cloud use). Refer to the following for specific formats.
@return               Whether the setting was successful.
@warning Only for international data center use. Must be set before SDK init.
@discussion
naviServer must be a valid server address. If you want to use the default file server, pass nil for fileServer.
Format for naviServer and fileServer:
1. If using HTTPS, set it as https://cn.xxx.com:port or https://cn.xxx.com, where the domain part can also be an IP. If no port is specified, the default 443 port will be used.
2. If using HTTP, set it as cn.xxx.com:port or cn.xxx.com, where the domain part can also be an IP. If no port is specified, the default 80 port will be used. (iOS defaults to HTTPS. If you use HTTP, refer to the ATS settings in the iOS documentation.)
*/
-(BOOL)setServerInfo:(NSString *)naviServer fileServer:(NSString *)fileServer;

Navigation server address (naviServer)
- Singapore: nav.sg-light-edge.com (primary), nav-b.sg-light-edge.com (backup)
- Singapore B: nav.sg-b-light-edge.com (primary), nav-b.sg-b-light-edge.com (backup)
- North America: nav.us-light-edge.com (primary), nav-b.us-light-edge.com (backup)
- Saudi Arabia: nav.sau-light-edge.com (primary), nav-b.sau-light-edge.com (backup)
File server address (fileServer): This is only applicable to private cloud customers. Public cloud customers can pass nil to use the default file server address.

Use the setStatisticServer method to set the statistics server address:

/**
Set the statistics server information.

@param statisticServer The statistics server address. Refer to the following for specific formats.
@return Whether the setting was successful.

@warning Only for independent data center use. Must be set before SDK init and setDeviceToken.
@discussion
statisticServer must be a valid server address, otherwise push notifications and other services may not work properly.
Format:
1. If using HTTPS, set it as https://cn.xxx.com:port or https://cn.xxx.com, where the domain part can also be an IP. If no port is specified, the default 443 port will be used.
2. If using HTTP, set it as cn.xxx.com:port or cn.xxx.com, where the domain part can also be an IP. If no port is specified, the default 80 port will be used. (iOS defaults to HTTPS. If you use HTTP, refer to the ATS settings in the iOS documentation.)
*/
- (BOOL)setStatisticServer:(NSString *)statisticServer;

Singapore: stats.sg-light-edge.com
Singapore B: stats.sg-b-light-edge.com
North America: stats.us-light-edge.com
Saudi Arabia: stats.sau-light-edge.com

Web

tip

If the SDK version is < 5.7.9, please use the following configuration. If the SDK ≧ 5.7.9, please proceed to Configuring via Area Code.

Set the navigation server address for the international data center in the SDK's init method:

// IMLib v2
RongIMClient.init('<Your-AppKey>', null, { navi: 'https://nav.sg-light-edge.com' } );
// or IMLib v4
RongIMLib.init({ appkey: '<Your-AppKey>', navigators: ['https://nav.sg-light-edge.com'] });
// or IMLib v5
RongIMLib.init({ appkey: '<Your-AppKey>', navigators: ['https://nav.sg-light-edge.com'] });

Singapore: nav.sg-light-edge.com (primary), nav-b.sg-light-edge.com (backup)
Singapore B: nav.sg-b-light-edge.com (primary), nav-b.sg-b-light-edge.com (backup)
North America: nav.us-light-edge.com (primary), nav-b.us-light-edge.com (backup)
Saudi Arabia: nav.sau-light-edge.com (primary), nav-b.sau-light-edge.com (backup)

Mini Program

Not supported yet.

Flutter

tip

Only applicable to version 5.2.4 and later. Configuring the data center via area code is not yet supported.

In the SDK engine configuration, enter the navigation server address and statistics server address for the international data center:

RCIMIWEngineOptions options = RCIMIWEngineOptions.create();
options.naviServer = 'Configured navigation address';
options.statisticServer = 'Configured statistics server';
RCIMIWEngine engine = await RCIMIWEngine.create(appKey, options);

Navigation server address (naviServer)
- Singapore: nav.sg-light-edge.com (primary), nav-b.sg-light-edge.com (backup)
- Singapore B: nav.sg-b-light-edge.com (primary), nav-b.sg-b-light-edge.com (backup)
- North America: nav.us-light-edge.com (primary), nav-b.us-light-edge.com (backup)
- Saudi Arabia: nav.sau-light-edge.com (primary), nav-b.sau-light-edge.com (backup)
Statistics server address (statisticServer)
- Singapore: stats.sg-light-edge.com
- Singapore B: stats.sg-b-light-edge.com
- North America: stats.us-light-edge.com
- Saudi Arabia: stats.sau-light-edge.com

uni-app

tip

Only applicable to versions 5.2.4 and later. Configuring data centers via area codes is not supported yet.

In the SDK engine configuration, enter the navigation server address and statistic server address for overseas data centers:

let options = { naviServer: 'configured navigation address' }
let options = { statisticServer: 'configured statistic server' }
let engine = await RCIMIWEngine.create(appKey, options);

Navigation server address (naviServer)
- Singapore: nav.sg-light-edge.com (primary), nav-b.sg-light-edge.com (backup)
- Singapore B: nav.sg-b-light-edge.com (primary), nav-b.sg-b-light-edge.com (backup)
- North America: nav.us-light-edge.com (primary), nav-b.us-light-edge.com (backup)
- Saudi Arabia: nav.sau-light-edge.com (primary), nav-b.sau-light-edge.com (backup)
Statistic server address (statisticServer)
- Singapore: stats.sg-light-edge.com
- Singapore B: stats.sg-b-light-edge.com
- North America: stats.us-light-edge.com
- Saudi Arabia: stats.sau-light-edge.com

React Native

Important

Only applicable to versions 5.2.4 and later. Configuring data centers via area codes is not supported yet.

In the SDK engine configuration, enter the navigation server address and statistic server address for overseas data centers:

let options: RCIMIWEngineOptions = {};
let options: RCIMIWEngineOptions = {naviServer: 'configured navigation address'};
let options: RCIMIWEngineOptions = {statisticServer: 'configured statistic server'};
let engine: RCIMIWEngine = RCIMIWEngine.create(appkey, options);

Navigation server address (naviServer)
- Singapore: nav.sg-light-edge.com (primary), nav-b.sg-light-edge.com (backup)
- Singapore B: nav.sg-b-light-edge.com (primary), nav-b.sg-b-light-edge.com (backup)
- North America: nav.us-light-edge.com (primary), nav-b.us-light-edge.com (backup)
- Saudi Arabia: nav.sau-light-edge.com (primary), nav-b.sau-light-edge.com (backup)
Statistic server address (statisticServer)
- Singapore: stats.sg-light-edge.com
- Singapore B: stats.sg-b-light-edge.com
- North America: stats.us-light-edge.com
- Saudi Arabia: stats.sau-light-edge.com

Unity

tip

Only applicable to versions 5.2.4 and later. Configuring data centers via area codes is not supported yet.

In the SDK engine configuration, enter the navigation server address and statistic server address for overseas data centers:

RCIMEngineOptions options = new RCIMEngineOptions();
options.naviServer = \"configured navigation address\";
options.statisticServer = \"configured statistic server\";
RCIMEngine engine = RCIMEngine.create(appkey, options);

Navigation server address (naviServer)
- Singapore: nav.sg-light-edge.com (primary), nav-b.sg-light-edge.com (backup)
- Singapore B: nav.sg-b-light-edge.com (primary), nav-b.sg-b-light-edge.com (backup)
- North America: nav.us-light-edge.com (primary), nav-b.us-light-edge.com (backup)
- Saudi Arabia: nav.sau-light-edge.com (primary), nav-b.sau-light-edge.com (backup)
Statistic server address (statisticServer)
- Singapore: stats.sg-light-edge.com
- Singapore B: stats.sg-b-light-edge.com
- North America: stats.us-light-edge.com
- Saudi Arabia: stats.sau-light-edge.com

Using Overseas Server API Addresses

tip

The data center of the App Key must match the data center used by the Server API.

If your app uses an overseas data center, when calling the RC server API from your app server, connect to the RC overseas data center API address:

RC overseas data center domains:

Singapore: api.sg-light-api.com (primary), api-b.sg-light-api.com (backup)
Singapore B: api.sg-b-light-api.com (primary), api-b.sg-b-light-api.com (backup)
North America: api.us-light-api.com (primary), api-b.us-light-api.com (backup)
Saudi Arabia: api.sau-light-api.com (primary), api-b.sau-light-api.com (backup)

Code example:

POST /user/getToken.json HTTP/1.1
Host: api.sg-light-api.com (primary),
api-b.sg-light-api.com (backup)
App-Key: uwd1c0sxdlx2
Nonce: 14314
Timestamp: 1408710653491
Signature: 45beb7cc7307889a8e711219a47b7cf6a5b000e8
Content-Type: application/x-www-form-urlencoded

userId=jlk456j5&name=Ironman&portraitUri=http%3A%2F%2Fabc.com%2Fmyportrait.jpg

Overseas Exclusive Features

For apps using overseas data centers, RC client SDK provides the following features to better serve overseas users:

Android supports FCM push
iOS supports VoIP push using iOS CallKit, meeting the call notification needs in audio and video scenarios.

Overseas Access Nodes

Applicable to IM and RTC signaling services.

Overseas access nodes are located in over 100 locations worldwide. The combination of access nodes in use may change without notice. Due to possible equipment maintenance, equipment failure, introduction of new access nodes, removal of old access nodes, and other events, the following list may not accurately reflect the access nodes currently in use.

Many cities have multiple access nodes to support service demands.

North America

Ashburn, Virginia; Atlanta, Georgia; Charleston, South Carolina; Chicago, Illinois; Council Bluffs, Iowa; Dallas/Fort Worth, Texas; Denver, Colorado; Las Vegas, Nevada; Lenoir, North Carolina; Los Angeles, California; Miami, Florida; Montreal, Quebec, Canada; New York City, New York; Querétaro, Mexico; Salt Lake City, Utah; San Francisco, California; Seattle, Washington; The Dalles, Oregon; Toronto, Ontario, Canada; Tulsa, Oklahoma
South America

Bogotá, Colombia; Buenos Aires, Argentina; Rio de Janeiro, Brazil; Santiago, Chile; São Paulo, Brazil
Europe

Amsterdam, Netherlands; Budapest, Hungary; Dublin, Ireland; Frankfurt, Germany; Groningen, Netherlands; Hamburg, Germany; Hamina, Finland; Helsinki, Finland; London, United Kingdom; Madrid, Spain; Marseille, France; Milan, Italy; Munich, Germany; Paris, France; Prague, Czech Republic; Sofia, Bulgaria; Saint-Ghislain, Belgium; Stockholm, Sweden; Warsaw, Poland; Zurich, Switzerland
Middle East

Fujairah, United Arab Emirates; Muscat, Oman
Asia Pacific

Changhua County, Taiwan, China; Chennai, India; Hong Kong Special Administrative Region, China; Jakarta, Indonesia; Kuala Lumpur, Malaysia; Mumbai, India; Delhi, India; Osaka, Japan; Seoul, South Korea; Singapore; Taipei, Taiwan, China; Tokyo, Japan
Oceania

Sydney, Australia; Melbourne, Australia
Africa

Johannesburg, South Africa; Lagos, Nigeria; Mombasa, Kenya

IMLib

Global Chat UIKit

push notification

IMLib

Global Chat UIKit

Chat Server

Chat Server SDK

Selecting a Data Center​

China (Beijing) Data Center​

International Data Center​

Configuring the SDK to Connect to an International Data Center​

Configuring via Area Code​

Manually Configuring International Data Center Domains​

Android​

iOS​

Web​

Mini Program​

Flutter​

uni-app​

React Native​

Unity​

Using Overseas Server API Addresses​

Overseas Exclusive Features​

Overseas Access Nodes​

Selecting a Data Center

China (Beijing) Data Center

International Data Center

Configuring the SDK to Connect to an International Data Center

Configuring via Area Code

Manually Configuring International Data Center Domains

Android

iOS

Web

Mini Program

Flutter

uni-app

React Native

Unity

Using Overseas Server API Addresses

Overseas Exclusive Features

Overseas Access Nodes