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
As soon as the datacenter is able to complete a task that would (currently, they're not done yet so who knows how much worse it'll get) have taken Tokyo 15 times less time to do.
Funny part is I asked them to do this with great priority and even said I'd pay emergency hands rate for it, and specifically asked them not to take two weeks like with the others... well it's like day 13.5 so they technically have a few hours left to make it in under 2 weeks.
Miami will be one of those locations where we had 0 people in the past, so all the seats are open. There's a good chance you can do that.
I should've been more careful. Now I feel like it won't happen.
No idea but they have MainCubes near Schiphol airport listed as the only one. I'm still also speaking with QuadraNet and it seems like they can do it in 5 days. I'll see how quick xTom can do it in once they reply.
We'll see if we can open up rounds of letting everyone move wherever they want. I honestly don't care, as long as we have the space and it's done in a way where it balances out as much as possible.
Seeing as Tokyo will probably be the most popular and the most expensive, we probably wouldn't be against letting people move from Tokyo to pretty much anywhere else.
We stopped offering Voxility filtering a while ago. It just wasn't that popular. We had 500 of these IP addresses available with plans on expanding it to 1,000 but I think at its peak we had something like only 300 sold? And that's at our extremely low price for it.
Then, Voxility did some things that had us concerned so we just ended it.
Psychz Los Angeles was going to have protection with it. QuadraNet will have protection as well, just a lower amount. It's hard to tell how much each company's filtering is actually equivalent to because it's easy to say "40Gbps protection" but it's also very easy for there to be too many factors to accurately represent what you actually end up getting. Voxility was awful for gameservers and it had a lot of false positives and random small outages where they were overwhelmed. CC pretty much never worked properly and was useless, and caused a lot of problems as well, plus they would always just nullroute anyway and not provide any justification in those cases. It'd pretty much always leak through.
I don't think we're going to try advertising DDoS protection that much but pretty much all locations will have some kind of automatic protection, at least to the point where one attack shouldn't ruin it for everyone.
We're in Tokyo, not Osaka. IMO the blend in Tokyo is better but who knows. It seems like Osaka used to be their main location and that's also where they have an office but they're pushing Tokyo more now because Osaka ran out of space or something to that effect.
We would like to know more about the Frankfurt DC (and AMS), which lg link should be representative?
I've been purposefully very quiet about the entire CC saga. That's going to make up the first 200 pages.
Yeah I'd love to hear more as well. When we first heard about them it was for IP space, and I honestly had no idea how it would go, but they ended up being a pleasant surprise. It was difficult finding out much about them though and most of what I learned were from questions I asked them directly.
I'm guessing this would be the closest to an accurate representation.
https://fra.lg.v.ps/
anybody here still with pending 2.5GB TYO?
hope i'm not alone to be left abandoned 😜
Don't worry, I'm with you.
In addition to this, now that V.PS has added their presence in Tokyo a few weeks ago, there's this Looking Glass to check the blend out, which should be similar to what VirMach Tokyo has: https://nrt.lg.v.ps
I look forward to TYOC038 recovering as soon as possible
you cant be serious.
I can't believe Elon Musk himself registered on LowEndTalk to complain about his service with VirMach Tokyo not working as it should.
Hey @ElonMusk, how's the Twitter purchase going? ActivityPub support when?
Buy Virmach then.
It will be fixed by 3000. Definitely.
Why? Because it's easy money, or you have to hide something you really screwed up.
I've had experience with a number of dutch datacenters directly (ones like (then) Telecity, Equinix, Evo, etc) and with all we had a number of cabinets, and ofcourse not all were filled. A number of them really work on committed power; so if you don't use a cabinet (i.e. don't power), you'd still be charged for it. However, that's usually all within the scope of your contract, so not by cabinet, and you'd take into consideration how much your cabinets are filled, etc.
So I can understand a bit that either the DC itself or the party that actually have the contract with them makes some money when you don't use any power in a empty cabinet.
But I never ever experienced that a cabinet that has been "sold" to a customer (by a DC themselves) suddenly isn't available during contracting period. And we've had a number of empty cabinets in my days (because convenient for future expansion and being able to make intercabinet connections by ourselves).
Changing the terms I only experience these days when we are confronted with massive rise of energy costs. DCs usually have prices that can change by a short period of time (some even by minute), and they are getting pretty nervous by the rise they've seen lately. And most of them have some small section in their contracts they can use or they just make a calculation that keeping a happy customer is way to expensive, it's a crowded market, so lets try it, and when they do it, we're lucky. I guess something similar may be a factor here, and if you try again and again and get yourself deeper into your web of tries and lies, you are less likely to open up to your customer...
Add some Doge coin news on Twitter! I have longed 100X.
node is TYOC036, only 5days after service finally got online ,the service has been offline ever since,tickt unanswered,so could u help me a little bit。@VirMach
Nah, I'd just print out this thread. Enough pages to make it through a rainy weekend.
+1
Is node 29 a little abnormal? The delay is a little scary.
The most interesting part about this is that Psychz was notified of the temporary price increase in December 2021, and they didn't let us know about it until April, right when we sent in hardware. And if they didn't want to renew contract with us, then our one year was up in February.
Even if they only care about money, it's just a bad business decision, given the situation.
We never said we wouldn't pay the extra costs, I just asked for a better explanation and assurance that if the power costs went down, we could re-evaluate. When we also have Los Angeles, Dallas, and Chicago with them, and we're going to basically keep these for years or at least the first year, and we've indicated numerous times that we want more, they should try to keep us as a customer just for our money. In fact, we're such a good customer that for the first 14 months in Amsterdam we used literally nothing and we're not even planning on filling these locations to the brim. Even if we did, they'd have a nice profit over the year that would exceed whatever they'd refund on Amsterdam if they decided to do the right thing.
On Amsterdam, though, they didn't even seem interested in selling us a cabinet. Let's pretend that we didn't even buy a cabinet, and just sent in any inquiry. The only thing I really got back is that they're sold out.
Meanwhile, right after they say this to us, they post colocation deals on WHT and include Amsterdam in there. So therefore, I'm going to go with:
I see high I/O bursts. Some ping spikes. High PPS. Download speed is fine on it though. I'll change something around right now, let me know if it gets better.
I/O abuser suspended. I just hope it isn't you, a lot of times whoever smelt it dealt it. Not saying it is but it's happened so many times before.
He was bursting 30-50% of the total disk IOPS for an hour at a time every hour or so all day.
Holy shit it's the real Elon
It has now recovered Ping value and broadband are very considerable.
Just curious do you plan to setup monitoring on these nodes for abusers and what is the course of action?
Has the TYOC038 node been repaired?
Emergency maintenance on 038 started about four hours ago, my server reappeared (with a new IP, on node 039) about 20-30 minutes ago. Seems to be working fine but I'm trying to get CPU passthrough working so haven't done any benches or anything.
edit: Installing AlmaLinux template got passthrough working, then installing Debian 11 kept it. Nice. Time to restore services.
The scripts have to be tuned. We want to allow people to burst so we set them really high and we'll tune it down to lower levels as we figure out what ends up being more acceptable for these NVMe drives versus SATA.
So this guy was causing the node to overload but it was technically allowed by the anti-abuse script since he would cool off every hour and then burst. So that means we need to add in some other constraints.
AI Mining is running on his machine?
Could it be something like fluxnode?
Sorry, haven't been following the thread and comments but any idea where things are with the NL deployment?
Free extension orders
The following have been selected randomly, but keep in mind that after posting these, I'll go through them and if they have tickets as I mentioned on their account, they're disqualified. These are going based off service IDs, not invoice IDs.
I took the next 50 to activate, and selected 10. We'll do this 4 more times for a total of 50. This starts from ID 652571 and ends with 654189, using random number generator. So 652571 is #1 out of 50 and 654189 is #50 out of 50.
The drawn positions are:
39
49
10
32
18
5
36
22
28
42
These translate to service IDs:
653017 Winner +1 Year
653607 Winner +1 Year
653753 Winner +1 Year
653964 Winner +1 Year
654034 Winner +2 Years
654061 Winner +2 Years
654092 Winner +1 Year
654117 Winner +2 Years
654125 Winner +2 Years
654183 Disqualified for creating a ticket asking when it's available. Lost +2 Years.