Russia: Nebula Control Center access affected by Telegram ban

Nebula_BayardoNebula_Bayardo Moderator, Zyxel Official Agent Posts: 172  mod
edited November 28, 2018 2:06PM in Nebula Control Center

Dear Russian users,

As you may be aware, the Russian government has taken some actions to ban the use of Telegram messenger application. The effect is holistic, to such extent that a lot of famous sites including Amazon, Google, FIFA, Spotify … etc. are also impacted. Nebula and myZyxel which are hosted on AWS (Amazon Web Service) cloud are not the exceptions.

Nebula and myZyxel themselves are working just fine on the Internet, this problem is only affecting customer's accessibility through Russian ISP to Nebula/myZyxel due to Russian government’s act.  

The impact to Nebula product will be the whole range as a SaaS cloud networking & management platform. While the access to Nebula Control Center for devices and users is not available, the already configured Nebula devices will keep working with the latest settings applied. You can refer to our FAQ here for more details.

In the meantime, the Hybrid AP series working in standalone mode can be a quick solution in case you need to manage your wireless network. Please refer to these steps to switch your devices to standalone mode.

The effect is random and increasing for now, so it’s difficult to estimate when will it be recovered. We hope the situation will be positively solved soon.

News reference:

https://www.independent.co.uk/life-style/gadgets-and-tech/news/russia-telegram-ban-amazon-google-fifa-spotify-nintendo-twitch-down-latest-updates-a8313776.html

https://www.theverge.com/2018/4/17/17246150/telegram-russia-ban

Tagged:

Comments

  • DiGaDiGa Member Posts: 2  Freshman Member
    Hi, Nebula_Bayardo, if you check Roscomnadzor cite ( Russian Federal Supervision Agency for Information Technologies and Communications) of blocked adresses at http://blocklist.rkn.gov.ru, then you can find that 2 out of 3 adresses of Nebula Control Center servers (52.210.235.173 & 52.210.12.1) are blocked since 2015!
Sign In to comment.