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 | ----- |
| 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 | Sender ID:
Russian carriers are filtering traffic with numeric, short code and unregistered sender IDs. Due to this filtering, sender IDs will be overwritten with all local carriers' generic sender IDs to ensure delivery to these operators. Gambling-related content is not permitted. Any content relating to gambling may be blocked by the operator. Some international and marketing traffic may also be blocked. You can pre-register sender IDs for high-volume traffic; however, the end operators will need to evaluate all requests first.
|
Phone Numbers & Sender ID
| Preregistered | Alphanumeric | Long Code | Short Code | |
|---|---|---|---|---|
| Operator network capability | --- | Supported | Not Supported | Not Supported |
| Twilio supported | --- | Supported | Supported | Not Supported |
| Sender ID preserved | --- | Yes | No | --- |
| Provisioning time | 1-2 weeks | -- | -- | -- |
| UCS-2 support | -- | -- | -- | -- |
| Use case restrictions | -- | Alphanumeric is only supported through pre-registration | Numeric sender IDs will be overwritten to generic alpha sender IDs to ensure 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. | -- |
| Preregistered | |
|---|---|
| Operator network capability | --- |
| Twilio supported | --- |
| Sender ID preserved | --- |
| Provisioning time | 1-2 weeks |
| UCS-2 support | -- |
| Use case restrictions | -- |
| Best practices | -- |
| Alphanumeric | |
|---|---|
| Operator network capability | Supported |
| Twilio supported | Supported |
| Sender ID preserved | Yes |
| Provisioning time | -- |
| UCS-2 support | -- |
| Use case restrictions | Alphanumeric is only supported through pre-registration |
| Best practices | -- |
| Long Code | |
|---|---|
| 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 to generic alpha sender IDs to ensure 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. |
| 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.