All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Kuroit | Pre-Order | KVM VPS | Ryzen 9 3900X in Tokyo, JP | IPv4 & IPv6
Hello Everyone!
We're back with our second Pre-Order offer!
Tokyo, JP location is almost ready and we've decided to offer pre-order plans until we're ready to launch the location. With this offer, you can buy our Premium VPS in Tokyo at discounted pricing of Regular VPS only!
AVA-1 | 15GB Disk - 1vCore - 1GB RAM
1 vCore (Ryzen 9 3900X)
1GB RAM
15GB SSD/NVMe Disk Space
1TB Bandwidth
1Gbps Network Uplink
Price: £4.00 £3.00 GBP Monthly
AVA-2 | 25GB Disk - 1vCore - 2GB RAM
1 vCore (Ryzen 9 3900X)
2GB RAM
25GB SSD/NVMe Disk Space
2TB Bandwidth
1Gbps Network Uplink
Price: £6.00 £5.00 GBP Monthly
Higher spec plans available on our website!
Expected Delivery: Next Week (14th to 18th Aug) - IP announcement pending only!
Pre-Order here: https://my.kuroit.com/store/tokyo-jp-vps-servers
Upstream: Host Universal Pty Ltd
Test IP: 180.149.230.1 - LG Coming soon!
Payment Methods - Debit/Credit Card, Paypal, AliPay, Bitcoin & other crypto currencies.
GeekBench 6:
Single Core | 1844
Multi Core | 10671
Full Test | https://browser.geekbench.com/v6/cpu/2211645
Network Speed Result : https://cdn1.frocdn.ch/4rSp8XFIolLO2oO.txt
Comments
PING 180.149.230.1 (180.149.230.1) 56(84) bytes of data.
64 bytes from 180.149.230.1: icmp_seq=1 ttl=243 time=285 ms
64 bytes from 180.149.230.1: icmp_seq=2 ttl=243 time=228 ms
64 bytes from 180.149.230.1: icmp_seq=3 ttl=243 time=228 ms
64 bytes from 180.149.230.1: icmp_seq=4 ttl=243 time=188 ms
64 bytes from 180.149.230.1: icmp_seq=5 ttl=243 time=273 ms
My local network is CMCC-5G(asn:AS56040)，from china guangdong
My network is AS200690, from USA Kansas City.
We are a pure IPv6 network.
It's pretty good latency, but slightly higher than expected.
[C:\~]$ ping 180.149.230.1 Pinging 180.149.230.1 with 32 bytes of data: Reply from 180.149.230.1: bytes=32 time=124ms TTL=247 Reply from 180.149.230.1: bytes=32 time=122ms TTL=247 Reply from 180.149.230.1: bytes=32 time=123ms TTL=247 Reply from 180.149.230.1: bytes=32 time=120ms TTL=247 Ping statistics for 180.149.230.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 120ms, Maximum = 124ms, Average = 122ms.
..
...
For my ISP (Indonesia) the normal latency to Tokyo (JP) should be less than 100ms.
[C:\~]$ ping 103.121.210.3 Pinging 103.121.210.3 with 32 bytes of data: Reply from 103.121.210.3: bytes=32 time=95ms TTL=53 Reply from 103.121.210.3: bytes=32 time=95ms TTL=53 Reply from 103.121.210.3: bytes=32 time=95ms TTL=53 Reply from 103.121.210.3: bytes=32 time=97ms TTL=53 Ping statistics for 103.121.210.3: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 95ms, Maximum = 97ms, Average = 95msPING 180.149.230.1 (180.149.230.1) 56(84) bytes of data.
64 bytes from 180.149.230.1: icmp_seq=1 ttl=251 time=2.72 ms
64 bytes from 180.149.230.1: icmp_seq=2 ttl=251 time=2.51 ms
64 bytes from 180.149.230.1: icmp_seq=3 ttl=251 time=3.69 ms
64 bytes from 180.149.230.1: icmp_seq=4 ttl=251 time=3.35 ms
64 bytes from 180.149.230.1: icmp_seq=5 ttl=251 time=2.81 ms
64 bytes from 180.149.230.1: icmp_seq=6 ttl=251 time=4.07 ms
64 bytes from 180.149.230.1: icmp_seq=7 ttl=251 time=2.72 ms
64 bytes from 180.149.230.1: icmp_seq=8 ttl=251 time=3.99 ms
64 bytes from 180.149.230.1: icmp_seq=9 ttl=251 time=2.19 ms
64 bytes from 180.149.230.1: icmp_seq=10 ttl=251 time=3.71 ms
64 bytes from 180.149.230.1: icmp_seq=11 ttl=251 time=2.10 ms
64 bytes from 180.149.230.1: icmp_seq=12 ttl=251 time=2.11 ms
64 bytes from 180.149.230.1: icmp_seq=13 ttl=251 time=3.03 ms
64 bytes from 180.149.230.1: icmp_seq=14 ttl=251 time=1.63 ms
64 bytes from 180.149.230.1: icmp_seq=15 ttl=251 time=2.06 ms
64 bytes from 180.149.230.1: icmp_seq=16 ttl=251 time=1.51 ms
very nice from JP too 😉
are you also in Singapore?
i'm like as @febryanvaldo , Sir 😁 +62
btw
thanks for askingi just want to marry you and not the others.
LOL 🤣
i'm LaughingIPV6 support in tokyo?
Yes, IPv6 will be supported in Tokyo, and each VPS will get IPv6 /64 subnet.
Just waiting on IP announcement to be done.
Can you leave a message with your order number in Tokyo, Japan to obtain double traffic?
What about BGP?
C:\Users\Administrator>ping 180.149.230.1
Pinging 180.149.230.1 with 32 bytes of data:
Reply from 180.149.230.1: bytes=32 time=131ms TTL=243
Reply from 180.149.230.1: bytes=32 time=131ms TTL=243
Reply from 180.149.230.1: bytes=32 time=131ms TTL=243
Reply from 180.149.230.1: bytes=32 time=130ms TTL=243
正在 Ping 180.149.230.1 具有 32 字节的数据:
来自 180.149.230.1 的回复: 字节=32 时间=80ms TTL=241
来自 180.149.230.1 的回复: 字节=32 时间=98ms TTL=241
来自 180.149.230.1 的回复: 字节=32 时间=96ms TTL=241
来自 180.149.230.1 的回复: 字节=32 时间=74ms TTL=241
来自 180.149.230.1 的回复: 字节=32 时间=84ms TTL=241
来自 180.149.230.1 的回复: 字节=32 时间=81ms TTL=241
It was a very quick response from Tokyo OCI. (it is natural)
From Equinix TY8
No double traffic since bandwidth is expensive
No BGP sessions
IPv4 is ready, and we're expecting IPv6 announcement to be ready by next week!
Should we deploy servers now or wait till IPv6 is ready?
I say just wait and deliver a complete service, with a working IPv4 and IPv6
https://paste.spiritlhl.net/code/oYgQRu.txt
No China Mainland optimized.
Original post: https://hostloc.com/thread-1196116-1-1.html
@kuroit
I tried setting up a tokyo server, and I found that its ipv4 network seems to have packet loss? Moreover, the server in the Netherlands I bought before had an ipv6 no-routing problem in the past two days, can you help me check it out? Ticket #345063
Hey IPv6 issue has been resolved
I am looking for getting the dedicated server. Can we have a chat?
Sure, you can join our live chat on our website or our Discord server: https://discord.gg/t6rpBmgf6z.