New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More
This discussion has been closed.
Comments
039 node always limit network speed to 30Mbps.
Then refund
vps stucks at 'booting from harddisk' after Os reinstallation. ticket #615174 .
Pls help @VirMach
First, install the AlmaLinux template from the client area panel.
Next, mount the netboot.xyz ISO from the SolusVM panel and install via VNC.
It is recommended to use a VNC client application such as UltraVNC, as VNC on a browser probably will not work.
This is the top service provided by Top Provider to MJJ, do you like it? This is so ironic
Please come out and explain, do not keep silent！Thanks.
This vir-jp machine on node 039, the test is much more perfect, I found it is the best, the upload speed is perfect, can eat ash very well。
Share test result:
· https://www.speedtest.net/result/c/a8170c32-2608-4cc0-91ea-cd79edd15494
· https://paste.ubuntu.com/p/mXd62pfRyc/
========================================
Superbench.sh -- https://www.oldking.net/350.html
Mode : Standard Version : 1.1.7
Usage : wget -qO- sb.oldking.net | bash
CPU Model : AMD Ryzen 9 5900X 12-Core Processor
CPU Cores : 1 Cores 3693.060 MHz x86_64
CPU Cache : 512 KB
OS : Debian GNU/Linux 10 (64 Bit) KVM
Kernel : 4.19.0-6-amd64
Total Space : 1.0 GB / 9.6 GB
Total RAM : 36 MB / 357 MB (234 MB Buff)
Total SWAP : 3 MB / 255 MB
Uptime : 0 days 0 hour 9 min
Load Average : 0.33, 0.24, 0.09
TCP CC : cubic
ASN & ISP : AS23959, Owl Limited
Organization : Virtual Machine Solutions LLC
Location : Tokyo, Japan / JP
Region : Tokyo
I/O Speed( 1.0GB ) : 115 MB/s
I/O Speed( 1.0GB ) : 243 MB/s
I/O Speed( 1.0GB ) : 1.3 GB/s
Average I/O Speed : 563.1 MB/s
Node Name Upload Speed Download Speed Latency
Speedtest.net 3.27 Mbit/s 87.32 Mbit/s (*)108.73 ms
Fast.com 0.00 Mbit/s 75.9 Mbit/s -
Nanjing 5G CT 12.04 Mbit/s 27.81 Mbit/s 38.99 ms
Hefei 5G CT 8.69 Mbit/s 77.77 Mbit/s 44.50 ms
Guangzhou 5G CT 24.17 Mbit/s 205.67 Mbit/s 52.86 ms
TianJin 5G CU 13.36 Mbit/s 109.33 Mbit/s 93.87 ms
Shanghai 5G CU 13.76 Mbit/s 20.21 Mbit/s 145.70 ms
Wuxi 5G CM 14.49 Mbit/s 87.28 Mbit/s 86.47 ms
Nanjing 5G CM 13.01 Mbit/s 72.38 Mbit/s 89.83 ms
Hefei 5G CM 25.63 Mbit/s 141.53 Mbit/s 87.91 ms
Finished in : 5 min 35 sec
Timestamp : 2022-04-09 11:15:00 GMT+8
Share result:
· https://www.speedtest.net/result/c/a8170c32-2608-4cc0-91ea-cd79edd15494
https://ping.pe/176.119.148.111
the network latency of 40 node.
@VirMach My first purchase of your product and I was disappointed. Hope to treat every customer sincerely in the future. For the first service, you can only get a refund within 7 days of purchase. Requesting a refund now. Please do not refund to the balance, thank you.
Ticket #762161
176.119.148.123 的 Ping 统计信息:
数据包: 已发送 = 5，已接收 = 5，丢失 = 0 (0% 丢失)，
往返行程的估计时间(以毫秒为单位):
最短 = 396ms，最长 = 908ms，平均 = 706ms
176.119.148.111 的 Ping 统计信息:
数据包: 已发送 = 8，已接收 = 8，丢失 = 0 (0% 丢失)，
往返行程的估计时间(以毫秒为单位):
最短 = 90ms，最长 = 95ms，平均 = 91ms
176.119.148.63 的 Ping 统计信息:
数据包: 已发送 = 7，已接收 = 6，丢失 = 1 (14% 丢失)，
往返行程的估计时间(以毫秒为单位):
最短 = 108ms，最长 = 155ms，平均 = 128ms
176.119.148.145 的 Ping 统计信息:
数据包: 已发送 = 6，已接收 = 6，丢失 = 0 (0% 丢失)，
往返行程的估计时间(以毫秒为单位):
最短 = 606ms，最长 = 725ms，平均 = 663ms
176.119.148.1 的 Ping 统计信息:
数据包: 已发送 = 8，已接收 = 8，丢失 = 0 (0% 丢失)，
往返行程的估计时间(以毫秒为单位):
最短 = 94ms，最长 = 99ms，平均 = 96ms
@VirMach How to explain these???Node40 ping is outrageous????? Special service for beta node?? Differentiated treatment of node40? lol
NTT is doing god's work.
Geo ISP Loss Sent Last Avg Best Worst StDev MTR Chart
Canada, BC, Vancouver Shaw 16.7% 6 348.97 466.76 242.44 761.95 228.77 ...
USA, CA, Fremont Hurricane FMT2 16.7% 6 402.43 443.49 204.22 732.39 219.26 ...
USA, CA, Fremont Linode 0% 6 580.8 695.11 435.92 949.78 216.63 ...
USA, CA, San Francisco Digital Ocean 0% 6 578.37 693.75 434.48 943.49 216.81 ...
USA, CA, Los Angeles QuadraNET 16.7% 6 398.77 455.09 198.75 742.71 209.62 ...
USA, CA, Los Angeles Vultr 16.7% 6 444.9 483.47 238.22 768.68 220.14 ...
USA, CA, Seattle Google 16.7% 6 365.28 424.09 188 715.51 222.41 ...
USA, CO, Denver Cogent 0% 5 348.91 469.49 252.88 803.87 230.16 ...
USA, TX, Dallas Softlayer 0% 6 571.72 732.13 474.43 997.46 228.87 ...
USA, IL, Chicago Cogent 0% 6 343.9 541.11 287.71 833.66 237.95 ...
USA, GA, Atlanta 55 Marietta/RamNode 0% 6 450.66 603.51 337.12 873.46 229.75 ...
USA, VA, Vint Hill OVH 0% 5 376.64 504.63 289.19 829.58 230.2 ...
USA, NY, New York Telehouse/RamNode 0% 6 433.48 621.51 359.61 905.67 239.74 ...
Canada, QC, Montreal OVH 0% 6 374.03 562.28 306.21 843.66 233.48 ...
UK, London Cogent 0% 5 683.84 793.76 588.08 1092.23 210.17 ...
France, Paris Online.net 0% 6 559.06 641.96 373.2 890.79 216.83 ...
Netherlands, Amsterdam Online.net 0% 6 565.94 642.23 371.01 879.2 215.1 ...
Netherlands, Nuland WeservIT/RamNode 0% 5 725.77 822.66 616.37 1113.96 207 show
Nigeria, Lagos Terrahost 0% 6 717.32 710.77 444.9 918.96 196.95 show
Norway, Sandefjord Terrahost 0% 6 604.26 666.07 401.08 910.14 210.79 show
Germany, Nuremberg Hetzner 0% 6 582.87 662.06 386.44 903.54 215.57 show
Italy, Milan Prometeus 0% 6 604.02 670.95 399.16 905.9 213.82 show
awesome latency
@VirMach How to explain these???Node40 ping is outrageous????? Special service for beta node?? Differentiated treatment of node40? lol
176.119.148.111 的 Ping 统计信息:
数据包: 已发送 = 4，已接收 = 4，丢失 = 0 (0% 丢失)，
往返行程的估计时间(以毫秒为单位):
最短 = 38ms，最长 = 73ms，平均 = 51ms
176.119.148.122 的 Ping 统计信息:
数据包: 已发送 = 4，已接收 = 4，丢失 = 0 (0% 丢失)，
往返行程的估计时间(以毫秒为单位):
最短 = 383ms，最长 = 503ms，平均 = 451ms
176.119.148.123 的 Ping 统计信息:
数据包: 已发送 = 4，已接收 = 4，丢失 = 0 (0% 丢失)，
往返行程的估计时间(以毫秒为单位):
最短 = 135ms，最长 = 175ms，平均 = 154ms
176.119.148.1 的 Ping 统计信息:
数据包: 已发送 = 4，已接收 = 4，丢失 = 0 (0% 丢失)，
往返行程的估计时间(以毫秒为单位):
最短 = 35ms，最长 = 42ms，平均 = 37ms
if 176.119.148.111's network changed?
人家都说了node 40是给着急想上线的人的，加上刚开机全都在测速加装系统当然会很糟糕。这价格你买得到更便宜的吗？没有就耐心等等或者别加这么多问号，搞得像自己花了几万块一样。
Translation: Virmach already explained the Node 40 is for those who's inpatient to get online, plus all of them are benmarking+installing os so it is bad. Can you buy anything lower on the market? If not then stop adding so many question marks like you spending thousands on this.
I never leave message to deploy my instance (The account was registered yesterday), why put my vps on node 40 that you mentioned for inpatient people?
And i monitor the latency for my vps all day, all the people doing benchmark all the day without sleeping? i don't think so.
I think must something wrong with node40, or may some bad buy occupied all the network resource to make network usable.
Don't say to refund, solve the problem is the right way, not to solve the people who raise the problem.
omg
virmach is missing
Is it so difficult to actually read what is being said by VirMach himself, instead of everybody repeating eachothers misunderstandings and assumptions? Node 40 is NOT the infamous "impatient" node, it's another one, but it's not told which one it is. The "40" comes not from the node number, but from the number of people that were put on it initially.
Yes, there is apparantly an issue with node 40, but that's not related to being the "MJJ node".
Also, everybody complaining about latency, speeds, etc: keep in mind that all the users are new on these nodes, and they are all installing, testing and benchmarking on it, so nodes are stressed to the limit and beyond. If you want a node that should be able to handle these kind of conditions, don't buy from LET, don't try to get the cheapest offer, but pay a premium+ price on a premium+ package and you MAY (yes, may) not experience this behaviour.
Both things above have been explained a number of times here already but still it won't get into the heads of people who either don't want to read or don't have the capability to understand. Just like don't understanding the concept (and risks) of a pre-order...
My order for March 12 is still waiting
别搞笑了好吧！前两天已经好好的了，网速io都已经稳定了。昨天突然开机，很多都加进去了，而且和ping有什么关系，没有40节点的测试，能让后面的可以好好使用？没有40的催着后面能更快上线？别跪舔了好吗？预售说的是两周，人们已经耐心等待了好吧，丢人咱回loc，没必要在这吵吵！白吃面了还闲面黑？没有前期测试后面的问题能改正？前人栽树后人乘凉！不找出问题，解决问题，就知道炮轰自己人，有意思？天天这么自己吵，他会解决问题？说出来是让他解决问题，你这么护着，就摆烂？
It doesn't like what you said at all.
Node 40 has network issue actually.
It has high latency to everywhere ,up to 300~400ms, even connect to the same network in JP.
Virmach need check the network and node completely instead of guess that customer keep benching this node all the day.
@VirMach
you wouldn't say that, if your server is deployed in 40 node.
@VirMach Hi, I applied to replace rDNS, but it has not been replaced after a day, Solusvm says.
I guess it's because the rDNS API hasn't been updated, I checked xtom's documentation, there is a way to modify rDNS.
curl -X POST "https://console.xtom.com/api/service/@id/rdns" \-H "Content-Type: application/json" \-d "{\"ipaddress\": {\"key\": \"value\"}}"https://console.xtom.com/userapi#reverse-dns-101
Hope it helps your work
EDIT:Forgive me for not knowing how to wrap lines in LET so I use this clumsy approach
Node40 not deploy for new users.We spend same money but own different service?
My Next Due Date 03/12/2023
Spend more money and time.
```orFirst of all, node40 is running stable and have a good experience. Yesterday it became very bad for no reason, but the other nodes were fine. Second, why can't we have the same experience for the same amount of money. Third, Virmach is one of mine vps, is it wrong to pursue better price/performance? Fourth, does the fact that we are post questions mean that
we self-imposed problems？Fifth, you have a problem but let others to take the medicine.thanks
臭煞币，使劲舔，衮泥马的舔勾