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.
Comments
Here are results from 2 of the 3 that I got. I just cancelled the 3rd. The first one looks prime on disk speed but tell me what you think.
Both are fine (regarding network speeds).
Rolling the dice on another, hard to pass up for 9 Euros.
Edit: Got a good one.
The prices convinced me to get a KS-3C. Below my bench.sh output right after installing Debian 9, do you think it looks right?
Looks good to me, about what you should expect out of these. My results are almost exactly the same.
Glad to see were both getting good ones, maybe it's OVH making up for last time LoL.
I just replied to OVH with requested results. For "local" to BHS I used a linode in NJ. Same datacenter one of the speed tests are running to. MTR shows a weird spike near the BHS datacenter.
I've got one in the 192.99.0.0/16 block and it seems like it may have shit network too, be interested to know if anyone who has a good one is in the 192.99.0.0/16 block or if the good ones are all in other blocks.
Edit: Yeah pretty sure I got the shit network.
What's your speeds like?
I dont wanna be a dick but .. i prefer RBX ;-)
Setup fees aside, is this a better buy than a Dedibox SC 2016?
You know what to do ;-)
and yet here I am. Doing a verification bullshit. What a bummer.
Let us know if you get an i5
I surely will
Also: which URL did you use?
I decided to try for another order to see if I got better network, and I did. The IP is in the 142.4.192.0/19 block. Makes me think that the 192.99.0.0/16 block for Kimsufi is where the issue is, unless someone has a BHS KS in that range that is fine.
Hrmm. Bought one of the BHS KS-3C.. installed Debian and swizzin, it seemed ok. Now it doesn't respond to pings at all. Rebooted from the panel, got an email notification saying it is up and responding to pings, but I can't get anything. Reinstalling with Ubuntu just to see.
Does it install a firewall that blocks ICMP by default? Haven't used Swizzin, but had good experiences with QuickBox and Atomic Toolkit
@Setsura - got one in the 142.4.192./19 range (BHS-1, bay T01B36) which has sh*tty speeds, got another one in the same range (BHS-1, bay T01B76) which has perfect speeds... I would not jump to hasty conclusions.
My good one is in that range.
I'm only basing it off the others who had issues mentioning being in a 192.*.*.* block, and then I got one in such a block with issues. It could be related to the racks maybe.
My problematic one is in:
BHS2 - Rack: T02A36The one that is fine is in:
BHS1 - Rack: T01B77The one posted above. I just edited a few things.
Yea. My crappy one is on
and the good ones are on
Apparently I'm blind, I don't see a link from you. I only get the BHS option for the original code posted.
>
FYP
>
I guess we can safely assume
BHS2 - Rack: T02A36is crap at least.I believe that makes 4 known good servers in that range.
Yes you do. But as a small hint:
1. CTRL+U (Chrome)
2. CTRL+F bhs
3. s/bhs/default
Done. Profit.
... and one crappy one (142.4.214.xxx)
OTOH it might be an issue with faulty network hardware, cabling, whatever - which may have happened at any time during the initial setup of the DC, or much later whenever they alter some racks/bays. It could very well be there's no easy rule to predict which racks or servers are affected by the issue, which could in turn explain why OVH is so reluctant to actively fix things. They'd have to wait till us poor sods report each and every faulty server/rack/connection...