RUSSIA (RU)

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 longcode and generic alphanumeric 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: Get opt-in consent from each end user before sending any communication to them, particular for marketing or other non-essential communications. Only communicate during an end user's daytime hours unless it is urgent. SMS campaigns should support HELP/STOP messages, and similar messages, in the end user's local language. Do not contact end users on do-not-call or do-not-disturb registries.

Phone Numbers & Sender ID

	Alphanumeric		Long Code		Short Code
	Pre-registration	Dynamic	Domestic	International
Operator network capability	Required	Not Supported	Not Supported	Not Supported	Not Supported
Twilio supported	Required	Not Supported	Not Supported	Supported	Not Supported
Sender ID preserved	Yes	---	---	No	---
Provisioning time	3 weeks	N/A	N/A	N/A	N/A
UCS-2 support	Supported	N/A	N/A	Supported	N/A
Use case restrictions	Content related to gambling may be blocked by operators. Some international and marketing traffic may also be blocked.	N/A	N/A	N/A	N/A
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.	N/A	N/A	N/A	N/A

	Alphanumeric - Pre-registration
Operator network capability	Required
Twilio supported	Required
Sender ID preserved	Yes
Provisioning time	3 weeks
UCS-2 support	Supported
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	---
Provisioning time	N/A
UCS-2 support	N/A
Use case restrictions	N/A
Best practices	N/A

	Long Code - Domestic
Operator network capability	Not Supported
Twilio supported	Not Supported
Sender ID preserved	---
Provisioning time	N/A
UCS-2 support	N/A
Use case restrictions	N/A
Best practices	N/A

	Long Code - International
Operator network capability	Not Supported
Twilio supported	Supported
Sender ID preserved	No
Provisioning time	N/A
UCS-2 support	Supported
Use case restrictions	N/A
Best practices	N/A

	Short Code
Operator network capability	Not Supported
Twilio supported	Not Supported
Sender ID preserved	---
Provisioning time	N/A
UCS-2 support	N/A
Use case restrictions	N/A
Best practices	N/A

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.