FRA-SSD-KVM-2048
€5.00/mo
Order Now
2 CPU Core (Equal Share)
2 GB Ram
50 GB Pure NVMe SSD Disk space 27000 GB Bandwidth @ 1 gbit (shared) <---- this (bold part)
1 x IPv4 address
1 x /64 IPv6
Sorry I am loaded with a category 10 man flu and I need new glasses, I cant see the typo?
It's okay
This plan have 18000 GB (17.58 TB) Bandwidth not 27000 GB
Nothing urgent to fix, just heads-up.
edit.
Ah, I see what it went wrong in plan description. Switched BW between two plans.
FRA-SSD-KVM-2048
2 CPU Core (Equal Share)
2 GB Ram
50 GB Pure NVMe SSD Disk space 27000 GB Bandwidth @ 1 gbit (shared) <- there should be 18000
1 x IPv4 address
1 x /64 IPv6
FRA-SSD-KVM-3072
2 CPU Core (Equal Share)
3 GB Ram
60 GB Pure NVMe SSD Disk space 18000 GB Bandwidth @ 1 gbit (shared) <- there should be 27000
1 x IPv4 address
1 x /64 IPv6
I did tracert on three location, which one should i choose? The one with least hop?
Pings are more or less the same across three locations.
Pheonix
Tracing route to 45.86.208.131 over a maximum of 30 hops
1 1 ms 1 ms 1 ms elisa.home [192.168.1.1]
2 44 ms 30 ms 43 ms 10.138.40.174
3 * * * Request timed out.
4 * * * Request timed out.
5 * 45 ms 46 ms 172.21.19.209
6 * * * Request timed out.
7 * * * Request timed out.
8 38 ms 51 ms 45 ms kul1pe3-digi.as15932.net [185.142.242.250]
9 * * * Request timed out.
10 * 52 ms 55 ms snge-b1-link.ip.twelve99.net [62.115.184.14]
11 127 ms 126 ms 125 ms tky-b3-link.ip.twelve99.net [62.115.126.245]
12 * * * Request timed out.
13 289 ms 296 ms 295 ms lax-b23-link.ip.twelve99.net [62.115.142.128]
14 233 ms 233 ms 225 ms lax-b22-link.ip.twelve99.net [62.115.143.39]
15 240 ms 232 ms 234 ms phx-b5-link.ip.twelve99.net [62.115.125.73]
16 242 ms 240 ms 233 ms phx-b6-link.ip.twelve99.net [62.115.125.53]
17 234 ms 277 ms 233 ms clouvider-svc079177-ic368910.c.telia.net [62.115.145.191]
18 253 ms 229 ms 236 ms 45.86.208.3
19 253 ms 233 ms 249 ms 45.86.208.4
20 242 ms 235 ms 239 ms 45.86.208.131
Trace complete.
Franfurt
Tracing route to 91.199.118.14 over a maximum of 30 hops
1 1 ms 1 ms 1 ms elisa.home [192.168.1.1]
2 49 ms 31 ms 38 ms 10.138.40.174
3 * * * Request timed out.
4 34 ms 39 ms 35 ms 10.132.48.6
5 44 ms 37 ms 47 ms 172.21.19.209
6 * * * Request timed out.
7 * 34 ms 37 ms 172.21.1.99
8 42 ms 46 ms 39 ms kul1pe3-digi.as15932.net [185.142.242.250]
9 * * * Request timed out.
10 49 ms 47 ms 39 ms 1.9.244.133
11 * * * Request timed out.
12 * * * Request timed out.
13 226 ms 220 ms 320 ms 91.238.82.11
14 258 ms 216 ms 215 ms 91.238.82.13
15 237 ms 244 ms 224 ms 91.238.82.43
16 226 ms 226 ms 214 ms 91.199.118.14
Trace complete.
London
Tracing route to 185.42.223.63 over a maximum of 30 hops
1 1 ms 1 ms 1 ms elisa.home [192.168.1.1]
2 50 ms 33 ms 46 ms 10.138.40.174
3 * * * Request timed out.
4 * * * Request timed out.
5 * 42 ms 42 ms 172.21.19.209
6 * * * Request timed out.
7 * * * Request timed out.
8 38 ms 53 ms 74 ms kul1pe3-digi.as15932.net [185.142.242.250]
9 * * * Request timed out.
10 38 ms 54 ms 56 ms 1.9.244.133
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 221 ms 216 ms 208 ms linx-lon1.thn2.peering.clouvider.net [195.66.227.14]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 216 ms 214 ms 208 ms h185-145-200-86.reverse.clouvider.net [185.145.200.86]
20 226 ms 224 ms 222 ms h185-145-200-87.reverse.clouvider.net [185.145.200.87]
21 * 205 ms 210 ms 185.145.200.36
22 225 ms 216 ms 218 ms h185-42-223-63.reverse.clouvider.net [185.42.223.63]
@forces said:
I did tracert on three location, which one should i choose? The one with least hop?
Pings are more or less the same across three locations.
Pheonix
Tracing route to 45.86.208.131 over a maximum of 30 hops
1 1 ms 1 ms 1 ms elisa.home [192.168.1.1]
2 44 ms 30 ms 43 ms 10.138.40.174
3 * * * Request timed out.
4 * * * Request timed out.
5 * 45 ms 46 ms 172.21.19.209
6 * * * Request timed out.
7 * * * Request timed out.
8 38 ms 51 ms 45 ms kul1pe3-digi.as15932.net [185.142.242.250]
9 * * * Request timed out.
10 * 52 ms 55 ms snge-b1-link.ip.twelve99.net [62.115.184.14]
11 127 ms 126 ms 125 ms tky-b3-link.ip.twelve99.net [62.115.126.245]
12 * * * Request timed out.
13 289 ms 296 ms 295 ms lax-b23-link.ip.twelve99.net [62.115.142.128]
14 233 ms 233 ms 225 ms lax-b22-link.ip.twelve99.net [62.115.143.39]
15 240 ms 232 ms 234 ms phx-b5-link.ip.twelve99.net [62.115.125.73]
16 242 ms 240 ms 233 ms phx-b6-link.ip.twelve99.net [62.115.125.53]
17 234 ms 277 ms 233 ms clouvider-svc079177-ic368910.c.telia.net [62.115.145.191]
18 253 ms 229 ms 236 ms 45.86.208.3
19 253 ms 233 ms 249 ms 45.86.208.4
20 242 ms 235 ms 239 ms 45.86.208.131
Trace complete.
Franfurt
Tracing route to 91.199.118.14 over a maximum of 30 hops
1 1 ms 1 ms 1 ms elisa.home [192.168.1.1]
2 49 ms 31 ms 38 ms 10.138.40.174
3 * * * Request timed out.
4 34 ms 39 ms 35 ms 10.132.48.6
5 44 ms 37 ms 47 ms 172.21.19.209
6 * * * Request timed out.
7 * 34 ms 37 ms 172.21.1.99
8 42 ms 46 ms 39 ms kul1pe3-digi.as15932.net [185.142.242.250]
9 * * * Request timed out.
10 49 ms 47 ms 39 ms 1.9.244.133
11 * * * Request timed out.
12 * * * Request timed out.
13 226 ms 220 ms 320 ms 91.238.82.11
14 258 ms 216 ms 215 ms 91.238.82.13
15 237 ms 244 ms 224 ms 91.238.82.43
16 226 ms 226 ms 214 ms 91.199.118.14
Trace complete.
London
Tracing route to 185.42.223.63 over a maximum of 30 hops
1 1 ms 1 ms 1 ms elisa.home [192.168.1.1]
2 50 ms 33 ms 46 ms 10.138.40.174
3 * * * Request timed out.
4 * * * Request timed out.
5 * 42 ms 42 ms 172.21.19.209
6 * * * Request timed out.
7 * * * Request timed out.
8 38 ms 53 ms 74 ms kul1pe3-digi.as15932.net [185.142.242.250]
9 * * * Request timed out.
10 38 ms 54 ms 56 ms 1.9.244.133
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 221 ms 216 ms 208 ms linx-lon1.thn2.peering.clouvider.net [195.66.227.14]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 216 ms 214 ms 208 ms h185-145-200-86.reverse.clouvider.net [185.145.200.86]
20 226 ms 224 ms 222 ms h185-145-200-87.reverse.clouvider.net [185.145.200.87]
21 * 205 ms 210 ms 185.145.200.36
22 225 ms 216 ms 218 ms h185-42-223-63.reverse.clouvider.net [185.42.223.63]
Trace complete.
London, since it is the only one you can spell properly
Does this include Chinaman who holds Canada student VISA and lives in Canada?
No, you are very welcome to order, to be fully transparent, we have hundreds of long term Chinese customers, this issue started around 6 - 7 years ago and we have tried to open up to China 3 times over the past 5 - 6 years and made a net loss as a result each time.
I understand it is a horrible blanket policy I hate it and I put it in place originally but the numbers speak for themselves and when we are talking at essentially €2 - €3 for an entire month worth of service there is not enough meat on the bone so to speak to fully manually audit every single order and write a huge amount of automation around it.
I do hope that at some point, we can start to accept the orders and simply complete further validation and start off accepting none reversible payment methods but that might be a while away yet.
Curiously, I got a 2nd VPS, kind of hoping it'd end up on a different node for redundancy, but it's the same one. Anyway, what's odd is the first one just has IPv4 and the second has IPv4 and IPv6. I'm not sure yet if I actually need IPv6 on both, but it seems strange to end up like that when they're both on KVMLDNN191.
Curiously, I got a 2nd VPS, kind of hoping it'd end up on a different node for redundancy, but it's the same one. Anyway, what's odd is the first one just has IPv4 and the second has IPv4 and IPv6. I'm not sure yet if I actually need IPv6 on both, but it seems strange to end up like that when they're both on KVMLDNN191.
we ran out of IPv6 /64's (only took 7 years) in London so some got provisioned without IPv6, I added more /64's and thought I had corrected them all, if I missed you pop a ticket in, I did that around 13:30 UK time today.
KVMLDNN191 is a new node, the provisioning automation will fill up the least populated nodes automatically until they are beyond a certain % full then start round robin again.
Curiously, I got a 2nd VPS, kind of hoping it'd end up on a different node for redundancy, but it's the same one. Anyway, what's odd is the first one just has IPv4 and the second has IPv4 and IPv6. I'm not sure yet if I actually need IPv6 on both, but it seems strange to end up like that when they're both on KVMLDNN191.
we ran out of IPv6 /64's (only took 7 years) in London so some got provisioned without IPv6, I added more /64's and thought I had corrected them all, if I missed you pop a ticket in, I did that around 13:30 UK time today.
Thanks for the quick reply! I just started raising a ticket and then noticed it had already appeared in the control panel, so I've copied that address into my /etc/network/interfaces and it all seems to work fine.
These little VPSs are really sweet - it's the first time I've had a VPS with a sub-10ms ping to my house, and amazingly it's only 5ms ping to my other hosts in Coventry, and 3ms to my Oracle cloud machines.
KVMLDNN191 is a new node, the provisioning automation will fill up the least populated nodes automatically until they are beyond a certain % full then start round robin again.
@ralf said: These little VPSs are really sweet - it's the first time I've had a VPS with a sub-10ms ping to my house, and amazingly it's only 5ms ping to my other hosts in Coventry, and 3ms to my Oracle cloud machines.
I have to give @Clouvider again the shout out for that It really is the best network.
Do you take orders from Iran? You have only mentioned China and Brazil in your website but I saw on OGF that you don't accept orders from Iran either. If you could provide me with your services I'd really appreciate it.
@awhite2020 said:
Do you take orders from Iran? You have only mentioned China and Brazil in your website but I saw on OGF that you don't accept orders from Iran either. If you could provide me with your services I'd really appreciate it.
Comments
Thanks all fixed.
https://inceptionhosting.com
Please do not use the PM system here for Inception Hosting support issues.
every year for the life of the service
https://inceptionhosting.com
Please do not use the PM system here for Inception Hosting support issues.
Well, you have to save something for Cyber Monday
https://inceptionhosting.com
Please do not use the PM system here for Inception Hosting support issues.
and the bandwith is monthly or yearly?
Monthly.
https://inceptionhosting.com
Please do not use the PM system here for Inception Hosting support issues.
Frankfurt. That's really some good stuff here.
These offers aren't good till cyber monday?
Just in time when i need a reliable reputable service to host my thesis research survey, awesome deal
Great, hope there will be some 1GB plans on Monday then. Fingers Crossed
welkambek Ant
Nice offers!
Chris on https://hostingforums.net/
Nice upgrade for my old server :-)
London. Great server as expected!
Legal Beagle?
Out of curiousity, are you putting the Phoenix orders on IOflood or Clouvider?
I think they're using Clouvider everywhere since they're a clouvider subsidiary.
Existing services in Phoenix are still at IOFlood and haven't been moved to Clouvider (at least yet).
Does this include Chinaman who holds Canada student VISA and lives in Canada?
Yo, join our premium masochist club
Very nice!
MichaelCee
Chinaman Left arm unorthodox Spin
VPS reviews and benchmarks |
I did tracert on three location, which one should i choose? The one with least hop?
Pings are more or less the same across three locations.
Pheonix
Tracing route to 45.86.208.131 over a maximum of 30 hops
1 1 ms 1 ms 1 ms elisa.home [192.168.1.1]
2 44 ms 30 ms 43 ms 10.138.40.174
3 * * * Request timed out.
4 * * * Request timed out.
5 * 45 ms 46 ms 172.21.19.209
6 * * * Request timed out.
7 * * * Request timed out.
8 38 ms 51 ms 45 ms kul1pe3-digi.as15932.net [185.142.242.250]
9 * * * Request timed out.
10 * 52 ms 55 ms snge-b1-link.ip.twelve99.net [62.115.184.14]
11 127 ms 126 ms 125 ms tky-b3-link.ip.twelve99.net [62.115.126.245]
12 * * * Request timed out.
13 289 ms 296 ms 295 ms lax-b23-link.ip.twelve99.net [62.115.142.128]
14 233 ms 233 ms 225 ms lax-b22-link.ip.twelve99.net [62.115.143.39]
15 240 ms 232 ms 234 ms phx-b5-link.ip.twelve99.net [62.115.125.73]
16 242 ms 240 ms 233 ms phx-b6-link.ip.twelve99.net [62.115.125.53]
17 234 ms 277 ms 233 ms clouvider-svc079177-ic368910.c.telia.net [62.115.145.191]
18 253 ms 229 ms 236 ms 45.86.208.3
19 253 ms 233 ms 249 ms 45.86.208.4
20 242 ms 235 ms 239 ms 45.86.208.131
Trace complete.
Franfurt
Tracing route to 91.199.118.14 over a maximum of 30 hops
1 1 ms 1 ms 1 ms elisa.home [192.168.1.1]
2 49 ms 31 ms 38 ms 10.138.40.174
3 * * * Request timed out.
4 34 ms 39 ms 35 ms 10.132.48.6
5 44 ms 37 ms 47 ms 172.21.19.209
6 * * * Request timed out.
7 * 34 ms 37 ms 172.21.1.99
8 42 ms 46 ms 39 ms kul1pe3-digi.as15932.net [185.142.242.250]
9 * * * Request timed out.
10 49 ms 47 ms 39 ms 1.9.244.133
11 * * * Request timed out.
12 * * * Request timed out.
13 226 ms 220 ms 320 ms 91.238.82.11
14 258 ms 216 ms 215 ms 91.238.82.13
15 237 ms 244 ms 224 ms 91.238.82.43
16 226 ms 226 ms 214 ms 91.199.118.14
Trace complete.
London
Tracing route to 185.42.223.63 over a maximum of 30 hops
1 1 ms 1 ms 1 ms elisa.home [192.168.1.1]
2 50 ms 33 ms 46 ms 10.138.40.174
3 * * * Request timed out.
4 * * * Request timed out.
5 * 42 ms 42 ms 172.21.19.209
6 * * * Request timed out.
7 * * * Request timed out.
8 38 ms 53 ms 74 ms kul1pe3-digi.as15932.net [185.142.242.250]
9 * * * Request timed out.
10 38 ms 54 ms 56 ms 1.9.244.133
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 221 ms 216 ms 208 ms linx-lon1.thn2.peering.clouvider.net [195.66.227.14]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 216 ms 214 ms 208 ms h185-145-200-86.reverse.clouvider.net [185.145.200.86]
20 226 ms 224 ms 222 ms h185-145-200-87.reverse.clouvider.net [185.145.200.87]
21 * 205 ms 210 ms 185.145.200.36
22 225 ms 216 ms 218 ms h185-42-223-63.reverse.clouvider.net [185.42.223.63]
Trace complete.
London, since it is the only one you can spell properly
London 2GB YABS: https://lowendspirit.com/discussion/comment/109052/#Comment_109052
Not guaranteed no, they are Black Friday offers, will have to see how it goes.
Clouvider.
No, you are very welcome to order, to be fully transparent, we have hundreds of long term Chinese customers, this issue started around 6 - 7 years ago and we have tried to open up to China 3 times over the past 5 - 6 years and made a net loss as a result each time.
I understand it is a horrible blanket policy I hate it and I put it in place originally but the numbers speak for themselves and when we are talking at essentially €2 - €3 for an entire month worth of service there is not enough meat on the bone so to speak to fully manually audit every single order and write a huge amount of automation around it.
I do hope that at some point, we can start to accept the orders and simply complete further validation and start off accepting none reversible payment methods but that might be a while away yet.
https://inceptionhosting.com
Please do not use the PM system here for Inception Hosting support issues.
Curiously, I got a 2nd VPS, kind of hoping it'd end up on a different node for redundancy, but it's the same one. Anyway, what's odd is the first one just has IPv4 and the second has IPv4 and IPv6. I'm not sure yet if I actually need IPv6 on both, but it seems strange to end up like that when they're both on KVMLDNN191.
we ran out of IPv6 /64's (only took 7 years) in London so some got provisioned without IPv6, I added more /64's and thought I had corrected them all, if I missed you pop a ticket in, I did that around 13:30 UK time today.
KVMLDNN191 is a new node, the provisioning automation will fill up the least populated nodes automatically until they are beyond a certain % full then start round robin again.
https://inceptionhosting.com
Please do not use the PM system here for Inception Hosting support issues.
Thanks for the quick reply! I just started raising a ticket and then noticed it had already appeared in the control panel, so I've copied that address into my /etc/network/interfaces and it all seems to work fine.
These little VPSs are really sweet - it's the first time I've had a VPS with a sub-10ms ping to my house, and amazingly it's only 5ms ping to my other hosts in Coventry, and 3ms to my Oracle cloud machines.
Ah, gotcha!
I have to give @Clouvider again the shout out for that It really is the best network.
https://inceptionhosting.com
Please do not use the PM system here for Inception Hosting support issues.
Do you take orders from Iran? You have only mentioned China and Brazil in your website but I saw on OGF that you don't accept orders from Iran either. If you could provide me with your services I'd really appreciate it.
Legally we cannot sorry.
https://inceptionhosting.com
Please do not use the PM system here for Inception Hosting support issues.