Country Summary
| Country name | Russia |
|---|---|
| ISO code | RU |
| Region | Europe |
| Mobile country code | 250 |
| Dialing code | +7 |
| Major carriers | MTS, Beeline, Tele2, Sotovaja Svjaz MOTIV, MegaFon |
Guidelines
| Two-way SMS supported | No |
|---|---|
| Number portability available | Yes |
| Twilio concatenated message support | Yes |
| Message length | 160 characters |
| Twilio MMS support | Converted to SMS with embedded URL |
| Sending SMS to landline numbers | You cannot send SMS to a landline destination number: the Twilio REST API will throw a 400 response with error code 21614, the message will not appear in the logs, and the account will not be charged. |
| Compliance considerations | Mobile operators in Russia are continuously improving their firewalls and routes that use Numeric, short code, and generic Alphanumweix Sender IDs may be blocked or filtered. To avoid this risk and to ensure optimal delivery, we recommend you opt for pre-registered Alphanumeric Sender IDs. Alphanumeric Sender ID registration comes with a recurring charge of US$230 per month. Please contact your account manager or Twilio customer support for more details. Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. The following are some general best practices:
|
Phone Numbers & Sender ID
| Alphanumeric | Long Code | Short Code | |||
|---|---|---|---|---|---|
| Pre-registration | Dynamic | Domestic | International | ||
| Operator network capability | Supported | Not Supported | Not Supported | --- | Not Supported |
| Twilio supported | Supported | Not Supported | Supported | --- | Not Supported |
| Sender ID preserved | Yes | No | No | --- | --- |
| Provisioning time | 3 weeks | --- | --- | --- | --- |
| UCS-2 support | --- | --- | --- | --- | --- |
| Use case restrictions | Content related to gambling may be blocked by operators. Some international and marketing traffic may also be blocked. | Alphanumeric Sender ID is only supported through pre-registration. Content related to gambling may be blocked by operators. Some international and marketing traffic may also be blocked. | Numeric Sender IDs will be overwritten with generic Alphanumeric Sender IDs with a best effort delivery. | --- | --- |
| Best practices | On receiving your registration request, the Sender ID team will ask you to upload your business registration certificate. This is a legal document issued by the government or a government-related body that legitimizes the formation of a company or corporation. | To maximize message delivery rates and preserve Sender IDs, we recommend you pre-register Sender IDs. | You may use a global SMS-capable number to reach mobile phones in Russia; however the Sender ID will not be preserved. | --- | --- |
| Alphanumeric - Pre-registration | |
|---|---|
| Operator network capability | Supported |
| Twilio supported | Supported |
| Sender ID preserved | Yes |
| Provisioning time | 3 weeks |
| UCS-2 support | --- |
| Use case restrictions | Content related to gambling may be blocked by operators. Some international and marketing traffic may also be blocked. |
| Best practices | On receiving your registration request, the Sender ID team will ask you to upload your business registration certificate. This is a legal document issued by the government or a government-related body that legitimizes the formation of a company or corporation. |
| Alphanumeric - Dynamic | |
|---|---|
| Operator network capability | Not Supported |
| Twilio supported | Not Supported |
| Sender ID preserved | No |
| Provisioning time | --- |
| UCS-2 support | --- |
| Use case restrictions | Alphanumeric Sender ID is only supported through pre-registration. Content related to gambling may be blocked by operators. Some international and marketing traffic may also be blocked. |
| Best practices | To maximize message delivery rates and preserve Sender IDs, we recommend you pre-register Sender IDs. |
| Long Code - Domestic | |
|---|---|
| Operator network capability | Not Supported |
| Twilio supported | Supported |
| Sender ID preserved | No |
| Provisioning time | --- |
| UCS-2 support | --- |
| Use case restrictions | Numeric Sender IDs will be overwritten with generic Alphanumeric Sender IDs with a best effort delivery. |
| Best practices | You may use a global SMS-capable number to reach mobile phones in Russia; however the Sender ID will not be preserved. |
| Long Code - International | |
|---|---|
| Operator network capability | --- |
| Twilio supported | --- |
| Sender ID preserved | --- |
| Provisioning time | --- |
| UCS-2 support | --- |
| Use case restrictions | --- |
| Best practices | --- |
| Short Code | |
|---|---|
| Operator network capability | Not Supported |
| Twilio supported | Not Supported |
| Sender ID preserved | --- |
| Provisioning time | --- |
| UCS-2 support | --- |
| Use case restrictions | --- |
| Best practices | --- |
For the benefit of all our customers, these guidelines are provided to help you comply with applicable requirements and to help ensure Twilio's platform remains compliant with global telecommunications ecosystem requirements. These guidelines represent our current understanding of common compliance requirements generally applicable to Twilio and its customers, and do not constitute legal advice. By posting these guidelines, Twilio makes no assurances regarding the legal compliance of your application built using our APIs. You are expected to understand and abide by all compliance obligations applicable to your specific application. You should check these pages regularly for updates as telecommunications ecosystem requirements continue to evolve and change, and the information below may be updated or changed without notice.