Bynet is back again
Belarusian data center is not available again. According to the information from the hosting provider, from which we buy a dedicated server - a problem with the channel of the Belarusian DC.
In the best traditions, we are waiting for an article tomorrow on Belarusian IT portals with the headlines “Again Beltelecom left Belarus without Bynet” and comments of Beltelecom in the spirit of “We know nothing - the goats themselves”.
And everything seems to be nothing if it were not for decree number 60 that was sensational last year, the core practically limits the hosting sites to the borders of the Republic of Belarus. And inside the borders of the Republic of Belarus, Beltelecom’s monopoly is known.
Here is what my traceroute 93.125.30.35 looks like now (to the server inside the B & B - Data Center)
traceroute to 93.125.30.35, 30 hops max, 60 byte packets
1 gw1.core.aichyna.com (213.184.232.193) 0.530 ms 0.564 ms 0.616 ms
2 * * *
3 * * *
...
Ps Even the sites of Beltelecom and the under-datacenter are not available.
UPD: 10 minutes after the publication of ALMOST ALL works
traceroute 93.125.30.35
traceroute to 93.125.30.35, 30 hops max, 60 byte packets
1 gw1.core.aichyna.com (213.184.232.193) 3.302 ms 3.371 ms 3.473 ms
2 195.137.180.252 (195.137.180.252) 3.499 ms 3.545 ms 3.602 ms
3 193.232.250.97 (193.232.250.97) 4.219 ms 4.616 ms 4.606 ms
4 gw1.datacenter.beltelecom.by (93.84.125.161) 4.615 ms 4.656 ms 4.757 ms
10.10.9.1 (10.10.9.1) 8.756 ms 9.493 ms 9.484 ms
6 appsrv.tld.tutby.com (93.125.30.35) 4.037 ms! X 1.076 ms! X 3.141 ms! X
(my server is available! Hooray!)
')
But the Beltelecomov segment of the data center seems not to be available yet.
traceroute beltelecom.by
traceroute to beltelecom.by (86.57.251.53), 30 hops max, 60 byte packets
1 gw1.core.aichyna.com (213.184.232.193) 4.215 ms 4.274 ms 4.294 ms
2 195.137.180.252 (195.137.180.252) 4.427 ms 4.415 ms 4.652 ms
3 93.84.125.49 (93.84.125.49) 4.683 ms 4.767 ms 4.804 ms
4 gw1.datacenter.beltelecom.by (93.84.125.161) 5.166 ms 5.267 ms 5.303 ms
10.10.10.2 (10.10.10.2) 4.917 ms 4.937 ms 5.058 ms
6 * * *
7 * * *
Who should bet on tomorrow's Beltelecom comments?
In the best traditions, we are waiting for an article tomorrow on Belarusian IT portals with the headlines “Again Beltelecom left Belarus without Bynet” and comments of Beltelecom in the spirit of “We know nothing - the goats themselves”.
And everything seems to be nothing if it were not for decree number 60 that was sensational last year, the core practically limits the hosting sites to the borders of the Republic of Belarus. And inside the borders of the Republic of Belarus, Beltelecom’s monopoly is known.
Here is what my traceroute 93.125.30.35 looks like now (to the server inside the B & B - Data Center)
traceroute to 93.125.30.35, 30 hops max, 60 byte packets
1 gw1.core.aichyna.com (213.184.232.193) 0.530 ms 0.564 ms 0.616 ms
2 * * *
3 * * *
...
Ps Even the sites of Beltelecom and the under-datacenter are not available.
UPD: 10 minutes after the publication of ALMOST ALL works
traceroute 93.125.30.35
traceroute to 93.125.30.35, 30 hops max, 60 byte packets
1 gw1.core.aichyna.com (213.184.232.193) 3.302 ms 3.371 ms 3.473 ms
2 195.137.180.252 (195.137.180.252) 3.499 ms 3.545 ms 3.602 ms
3 193.232.250.97 (193.232.250.97) 4.219 ms 4.616 ms 4.606 ms
4 gw1.datacenter.beltelecom.by (93.84.125.161) 4.615 ms 4.656 ms 4.757 ms
10.10.9.1 (10.10.9.1) 8.756 ms 9.493 ms 9.484 ms
6 appsrv.tld.tutby.com (93.125.30.35) 4.037 ms! X 1.076 ms! X 3.141 ms! X
(my server is available! Hooray!)
')
But the Beltelecomov segment of the data center seems not to be available yet.
traceroute beltelecom.by
traceroute to beltelecom.by (86.57.251.53), 30 hops max, 60 byte packets
1 gw1.core.aichyna.com (213.184.232.193) 4.215 ms 4.274 ms 4.294 ms
2 195.137.180.252 (195.137.180.252) 4.427 ms 4.415 ms 4.652 ms
3 93.84.125.49 (93.84.125.49) 4.683 ms 4.767 ms 4.804 ms
4 gw1.datacenter.beltelecom.by (93.84.125.161) 5.166 ms 5.267 ms 5.303 ms
10.10.10.2 (10.10.10.2) 4.917 ms 4.937 ms 5.058 ms
6 * * *
7 * * *
Who should bet on tomorrow's Beltelecom comments?
Source: https://habr.com/ru/post/133098/
All Articles