New flespi region in Russia has been opened for users registrations.

This is the main task our team struggled for the last 8 months and now we are at the final line. The current flespi region has received code-name eu and the new region is coded as ru.

During authorization/registration at https://flespi.io it is possible to choose which region you want to authorize at by using region selector:

By default, https://flespi.io provides authorizations and registrations in eu region, while https://ru.flespi.io provides authorizations and registrations in ru region. Please be aware that it is possible to create new flespi accounts with the same e-mail or social network bindings in different data centers but they will be totally separated.

Both regions have totally dedicated infrastructure and interconnected only with shared tools like flespi billing system, flespi customer support system, protocols and devices availability and some internal checking tools. All other systems and databases are separated and the flespi support team provides migration possibility from one region to another for our users upon request.

Also we have separate NOC channels for both regions: flespi noc for eu region and flespi noc for ru region. Both infrastructures are automatically controlled by two separated bot networks. For eu region primary reporting bot is located in Amsterdam, Netherlands and for ru region our primary reporting bot is located in Moscow, but in a different data center.

The configuration of all flespi regions can be retrieved with REST API call: https://flespi.io/auth/regions
As you may notice there for connecting to ru region MQTT Broker or REST API endpoint you should use different hostnames - with ru- prefix, e.g.: ru-mqtt.flespi.io for MQTT and ru.flespi.io for REST.

Whenever you have any questions about regions you are welcome to post them here or in HelpBox.