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
Use the normal font size and don't use bold
Otherwise, there's a good reason to ignore you
I just registered. . . I didn't know the font would turn out like that.I even don't know how to delete that comment sorry。
order:1397158,Please help me change to San Jose or Seattle, I hope it's a 5950x machine. First time buying, if the experience is good, I will order the storage type again.
Does this mean that all vps in buffalo will be able to get migrated including BF-specials.
Thanks for the info! Can I know which category did you use when you submit the ticket? "General" or "Technical" or something else?
I guess if the VPS do not have any OS installed and the reinstall system does not work, it obviously does not boot... Now I just wonder why Rescue mode also won't work
I had some in Buffalo during previous BFs. Are they eligible for the migration too?
Technical Support https://billing.virmach.com/submitticket.php?step=2&deptid=4
Yes. There is no internal networking for now, so it will eat up both server's bandwidth quota
Tickets have not been processed, garbage merchants, not recommended to buy
MJJ? try use work order.
No congrats on your second post
Sorry I'm not sure what you mean but the 40Mbps figure I provided would be a ballpark average over all our nodes, in all locations, over essentially all time.
It just means it's pending deployment.
If Greencloud uses xTom in the same location, I would assume it would be the same network blend and would have the same problem, but if you order a service from us we'd push to get it fixed as long as you understand that network engineers at a datacenter and in general seem to want a lot of information and will drag it out for a long time.
As for the 40Mbps comment, that's per single node, over all our locations, networks, etc. In any given one second, all our servers will be using about 40Mbit or 5MB.
I can assure you that "only" 10Gbps is overkill and no, that doesn't mean anyone will be throttled.
No, sorry.
Please disregard my previous message.
I don't want to say it will include everything, but there's nothing else I can say that would be true really.
It will absolutely not be congested. We will essentially 100% run out of power before we run out of network the way we've set things up.
However, of course, if we run out, we have no option but to increase our commit. Otherwise, it will still continue even if we do not increase it, and we'll just be billed high overage fees instead.
I know this is difficult to believe as it is for me as well, but when I said 40 Mbps I specifically meant Megabits, as in 5MB (Megabytes) per second. For all the infinite bandwidth providers hand out, only about that much seemingly gets used per node and this is on our beefy 256GB RAM + dual Xeon servers.
Correct and we actually run on a port larger than the default commit so in general, we'd be under no situation where we'd have to really "upgrade" anything to maintain an acceptable service, it would just use up to the whole port speed and then we'd get billed overages.
Unless ColoCrossing realizes that we weren't bluffing and changes their mind and offers to pay us an exorbitant amount of money to keep services here, outside of E3 dedicated servers, we have no plans on keeping E5's in Buffalo at this time.
Epyc doesn't really work out for us. There are some situations where there will be minor improvements in pricing if we used Epyc over Ryzen, but that all just goes toward overselling/cramming people in.
I'm saying this very informally but any provider using Epyc either really loves "Enterprise" equipment that costs more or they really love overselling.
I've done the math many more times than I care to admit. Like an insane amount of time has been spent theorizing every possible build and every time I look at Epyc, I almost trick myself into thinking that it may be the way to go, until I run the numbers back and realize I've been correct for a dozen times and I only thought it'd be better because of hyper-inflated numbers in, for example, the RAM category.
Of course my statement may change at a later time, depending on how Epyc motherboards and Epyc processor pricing changes over time.
Congrats! I wonder how many of them are on VirMach threads.
Yes, there's no internal networking setup at the time.
View Ticket #355597
Tickets have not been dealt with what happens? Can anyone tell me?
I can't tell you that without looking at your ticket and I can't look at your ticket without encouraging this type of behavior, so I have no answer for you. The message board isn't here so you can copy/paste ticket IDs, sorry. If you want to describe it a little bit and I notice it's a case that can be resolved independently, then I'll have a look here.
Don't select San Jose or Seattle on Ryzen in the future, if you are provided the option, as those are not planned to have 5950X.
If you created a ticket to get migrated and you're not supposed to create one (I'm not saying you weren't, I haven't checked it) then you'll be moved to our secret special customer group and will be migrated last. I've actually been thinking if we should keep one server in Buffalo and migrate everyone in this group to that server.
(edit) Okay that's your order number, it'll be processed as normal.
I'll try to be as specific as possible without making any promises.
Buffalo will require about 2 to 3 cabinets to replace. We currently only have one cabinet in NYC Metro, and may have up to one cabinet in Chicago in the future. We'll also have one new cabinet in Tokyo, one new Cabinet in Amsterdam, and quarter cabinets in Denver and Phoenix.
That means you are more likely to be migrated than remain in Buffalo.
What's your ticket number?
Oh hey looks like you provided it. Let me have a look at why it wasn't processed. It still won't be processed just because you provided it here but I'll provide reasoning.
My bad. I was wondering if the communication between two VPSes, which are both from VirMach, located in Tokyo datacenter, would suffer from 40Mbps as well.
BTW, would appreciate it if you could have a look at Ticket #550087.
Thx.
I must have been missing a lot of discussions about migration, and just out of curiosity, are you going to eventually move out of all previous colocrossing locations or just certain location, eg Buffalo? @VirMach
coo colo co lo crossing coco
corona
cacao
have a
c'mon, still waiting for that drama to unfold!
Virmach is typing ...