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
I'm talking specifically about the comms piece - I don't have any issue with the the pricing change, makes perfect sense in the current climate, it's the way stuff is communicated to customers that lets them down.
That said, I've just seen the full email and it's actually fine, perfectly clear and well explained, and the website reflects that, so fair play @Incero.
Maybe we would all do something different than what was done (I would, but I'm not them) but this is about changing policy to address the reality of the state of IPv4 addresses. Why you guys are all so obsessed with hoarding IPv4 addresses instead of fighting for IPv6 improvements is beyond me.
Some of you guys just look like you could seriously just use a beer. Seriously @GStanley, hit me up if you find yourself in East Texas. I'm buying
In before "you're biased so you can't talk about IPv4 shortages."
Beer on you?
Beers all around!
It is concerning that Wable change mind from time to time not even honoring existing customers.
Just checked with them whether this apply for existing customers who has already assigned the IPs ( as I have 2 Ips) and the answer below.
"This applies to all ADD-ON IPs in use from Nov 1st. You should remove IPs before then if you don't need them."
If they continue with more changes in the plan definitely will think about moving out.
Bears?!
What about location(s) or no requirement for multi location?
Thats from your VPS thats been suffering a network performance problem.
Was it, I thought I pulled that one from one of your example responses on how should be??? Actually if it is, then LOL ramnode getting smacked a little bit by a server with a bad nic.
@markturner mind posting one for me that isn't on a node that we are working on.
Another test from delimiter:
That should be around 60-80MB/s depending on how many people are hammering that machine for test.
The rest look about right
I just upgraded my Delimiter 5150 to E5420 here is the result just now
What @markturner determined after many attempts of us trying to figure out what the hell was going on is... coloat's test server is shit. For a few tests we can get 100+ and the next few we can barely get 10. It seems coloat is no longer a good bench to determine performance to the area.
Could use a few locations (West coast, East and EU if possible).
I wouldn't hold up Coloat's as being any worse than the others. Cachefly has the capacity to handle the traffic.
But Softlayer I was noticing traffic coming back from two different servers on two different paths within 10-15 seconds of running a test. And consistently following the same path depending on the server originating the traffic. That shows heavy variance depending on the server.
@markturner all the reason we need a new bench script.
I've been working on one that will properly test A->B and B->A (up/download) as well as limiting simultaneous tests.
Thanks for the feedback everyone :-)
I can predict more accounts being terminated just for making tickets like with the added backups.
lol
LeaseWeb network is WAY better than Incero.
wable in seattle
CPU model : Intel(R) Xeon(R) CPU E5-2643 v3 @ 3.40GHz Number of cores : 1 CPU frequency : 3400.019 MHz Total amount of ram : 512 MB Total amount of swap : 512 MB System uptime : 11:02, Download speed from CacheFly: 86.1MB/s Download speed from Coloat, Atlanta GA: 4.06MB/s Download speed from Softlayer, Dallas, TX: 50.1MB/s Download speed from Linode, Tokyo, JP: 15.8MB/s Download speed from i3d.net, Rotterdam, NL: 285KB/s Download speed from Leaseweb, Haarlem, NL: 31.1MB/s Download speed from Softlayer, Singapore: 6.12MB/s Download speed from Softlayer, Seattle, WA: 35.2MB/s Download speed from Softlayer, San Jose, CA: 77.1MB/s Download speed from Softlayer, Washington, DC: 15.2MB/s I/O speed : 153 MB/s
Joke's on you! I don't drink!
YOU CAN'T STOP ME FROM HATIN NOW
We have different mixes in our various locations. Do you have any data you could send me or ticket IDs I can check where our network hasn't been up to par for you?
I had some pretty bad network performance in Seattle and Atlanta . This was a bit ago and haven't looked into it more or created a ticket. At that time it seemed things were single homed.
RamNode Seattle location has been crappy for me as well, and for a long time. But I don't complain as it's only used as part of an IRC node:
Those colours.. Yuck, how do you read anything dark blue or purple..
Seattle was never single-homed, Atlanta was briefly 3 years ago... You made it sound like you were comparing our current network to others. We're happy to help if you see some issues with your service - just open a ticket and we'll take a look. We very rarely see network complaints unless a carrier is having trouble upstream or something.
@k0nsl - Happy to look more into it for you with a ticket. I bet we can figure out what's going on in short order. You might want to try this out in the meantime: https://clientarea.ramnode.com/knowledgebase.php?action=displayarticle&id=55
@nick_a not really . Was more giving options and warnings with my suggestions .