VirMach
VirMach
About
- Username
- VirMach
- Joined
- Visits
- 2,824
- Last Active
- Roles
- Member, Hosting Provider
- Thanked
- 9380
Comments
-
I had to force myself to sleep last night after the huge error I made, and it was very difficult to do even though I'm exhausted. Luckily I was able to probably sleep for another 4 hours after laying there for a few hours. So far so good, didn't mis…
-
(Quote) Yes, caused by me. I made a really stupid mistake, immediately realized it and contacted the datacenter/made network issue.
-
Okay slightly more detailed timeline/events, maybe. San Jose - I'm flying there tomorrow afternoon until Wednesday afternoon and hopefully I'll be able to do something, if not then whatever, at least a change of workplace, I'm already set up with m…
-
(Quote) It's on the network status update, we may refuse for any reason to process it but per comment here earlier, usually if rejected it means either not done correctly, which you've confirmed it was done correctly, or that you were marked as prev…
-
Summary SEA - Don't know but probably up this week. SJC - Confirmed Saturday latest (but it can technically get later-er or sooner.) PHX - Wednesday or sooner. DEN - Finishing loading from backups for failed migrations from weekend. Likely disconti…
-
Let's hope SolusVM got back to us on fixing the migration grievances, if not today is going to be hell with the the added transit outage as described above. Finally out of meetings, I got some sleep before the meetings maybe 4 hours but I've been u…
-
Yeah, so Atlanta is Flex + Lumen blend and fine. Dallas, Phoenix, and Denver were Unitas Global. (And Seattle, San Jose too.)
-
I'm assuming Unitas Global cut the transit as Denver, Dallas, Atlanta in the same boat now. Finished speaking with Flexential, they confirmed they didn't bring anything down on their end.
-
(Quote) Path.net was going to turn on new service Wednesday but one of transit providers that isn't them must have shut off Dedipath, so Path is helping us try to move it sooner before Wednesday as a result. This does likely mean old IP addresses w…
-
We've just confirmed setup day of Friday, September 15th, for Evocative San Jose. I've spoken with them and it's possible they may be able to allow us to rack it quicker if we can get someone else's help with that or if I can fly in any time sooner…
-
Seattle/San Jose migrations to LAX/NYC have been delayed. We have to wait for SolusVM to restore some level of functionality, it's pretty much otherwise impossible to efficiently do anything. I've been communicating with them today, we'll likely wor…
-
IPv4 change tickets will go out mostly likely tomorrow or Tuesday. These are the stages it'll be completed in. * By September 12th, new IPv4 provided for pre-planning, will not be ready until September 19th. This allows us time to coordinate all th…
-
Okay I figured it out, oh my god is it stupid.
-
What is the point of having a table for virtual servers with a Node ID, and having a script provided to change the Node ID that actually updates the database to change the Node ID, if that table is not utilized to represent the Node ID of a virtual …
-
I don't know what update caused this but trying to switch over a VM to a new location on SolusVM has been a huge headache. It just endlessly has a bunch of checks now that it didn't used to have before and times out trying to communicate to the serv…
-
(Quote) I don't know what you're talking about but just follow instructions in the network status update. I'm guessing you're quoting the AI suggestion. If you already made a request then either instructions weren't followed or you're not eligible,…
-
All new IPv4 for the changes have been purchased.
-
We're going to start splitting up brands soon, let me know if you guys have any questions. But for example BF specials will go into a BF flash deal brand, and so on. I had something nice and thorough written out to post but I lost it so this is all …
-
Keep in mind I'm personally rejecting every person's request if they already sent in tickets ignoring the network status page in the past. So if you get rejected either you entered it wrong or you didn't previously follow ticket etiquette during hig…
-
(Quote) Instructions added to network status page. Follow them exactly based on whether you want to move to LAX or not, we'll start processing these in batches every few hours. Additional note, anyone in the first few batches will move to 47.87.xx.x…
-
(Quote) Basically move to NYC if you need any serious protection. We're not advertising it as such but it's the only location with very good protection.
-
(Quote) Our Coinbase payment gateway broke and due to how it was coded it was breaking other parts of the website. We got rid of it for now, we're looking into developing another module ourselves and figuring out what's going on with it in developme…
-
Sabey called again, they sent someone in to check on everything and they did not power it off. There's a lot of moving parts on their end as well as they've been busy this week as a result of what happened, so they're going to get back to us on Mond…
-
Looks like I missed a call with Sabey yesterday but they reached out again and we're getting the ball rolling with that location as well. Their directory of leasing was very nice and he's also going to look into trying to get everything powered back…
-
General more detailed update on everything else, overdue from the other day. Flexential: Dallas still has two servers with routing issues, for whatever reason they're announced with Psychz now and perfectly timed to set off a false alarm. Otherwis…
-
(Quote) Temporarily. These are still included in the Dedipath migrations, but we were able to fix routing on it to allow more time to properly migrate them instead of loading in from backups. The backups are already also loaded in so we'll keep them…
-
Psychz strikes again. Routing issue for DALZ009 and DALZ006 appear to be caused by Psychz announcing these recently again for some reason, they've been sending us a ton of IP address change and of course invoices several times a month, I am guessin…
-
(Quote) Our monitoring system is going crazy because of all the other stuff, I noticed LAX have an outage at Hivelocity for at least one server and it's on my queue but my queue is endless. I'll try to at least get it added to network status page so…
-
@vgood said: (Quote) Generally if this occurs, you should not make a ticket and should check the network status page, but I've already reported this to our developer.
-
(Quote) We're aware. IP provider has to update it, we're waiting.
-
(Quote) Added something to the pop-up message for you.
-
(Quote) These can unironically describe the four stages of VirMach if you add in the other non-low end side of it. #1 we were starting out and rather than raising prices we just did #2 which was us making a lot of money on higher end market except …
-
(Quote) Hey now you know I was serious when I said you couldn't close it. The backstory, the fade always causes issue but it somehow always ends up in our developer's code. Even he knows it, he just replied and said "yea definitely remove the …
-
(Quote) We contacted them to get space, got the space, and then still got that spam email afterward from the same person that did our sales order. So definitely was just a send to everyone marketing email masked as pretend-concern.
-
As for our plans outside of NYC, I'll provide it in greater detail below, I'm still working on that update for you guys, but some of it needs to be changed as we wanted to use Hivelocity which we most definitely will not be doing after what happened…
-
(Quote) This is inaccurate, just making an important distinction: not every VM on every server will be done, those may still need to move around to get their new IP address. This is a very small number of services and we're aware ad working on it ac…
-
Huge ticket backlog did eventually build up. All custom created tickets will likely be auto closed, any created using the automatic creator where it assigns an appropriate title will be looked through still. Haven't decided yet. Keep in mind anyone…
-
Will provide a more detailed plan for other locations loading in from backups after NYC is closed out.
-
Oh also 3 others were waiting for the above 3 to be able to proceed in some ways so completing those too.
-
Connectivity restored to remaining 3 NYC, IP changes will proceed if not already completed.