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
@DeluxHost Possibly buy 2 and merge into 1? If no, would you mind making a deal of 4C 16G?
Waiting for the next nvme offer.. seems that those SSD drives struggle sometimes.
No sir
If you can please open a ticket and ask for Matteo
unfortunately not
We will see
Hello,
How long is this price valid for? Will it be more expensive in the second year?
we already out of stock?????
Same price
Thanks
Most of them yes
Are J-3 and J-4 packages out of stock?
yes
still getting ignored?
No one is ignoring you, unfortunately there is a high amount of work, but don't worry, your problem is high on the list, and I'm sure it will be resolved by today.
I've never asked for an immediate solution. Just maybe not leave a customer with like a 2-month old ticket ignored without a single update on the request?
You're right, and I'm sorry. We try our best to close tickets as quickly as possible. Unfortunately, in some cases, it's beyond our control, like in this case. We'll get back to you shortly with a solution. We haven't forgotten, and as we said, your problem has top priority.
top men are on it!
Enough! Of the NEITHERLAND DATA CENTER I purchased from your offers. Please offer another Germany even for just once again. I will like to grap pre order from GERMANY REGION
yesterday I bought one of J-2 plan. When will it be readey to use? iit isi still in pending.
Thanks.
PRE-ORDER ONLY, DELIVERY WITHIN 14 DAYS
i missing that
we'll see, maybe yes
When u guys will bring stock again?its out of stock?j4 and j3 both?
Just done a little restock.
Missed J3 once again
Is there still a chance for a restock?
J3 Please
@DeluxHost wondering if bgp has a recurring fee or just one time setup fee
I’ll leave my feedback here. I have two VPS servers from this provider, and everything was fine until the network upgrade. The provider promised improvements and assured that the upgrade wouldn’t affect server operation. After the upgrade, however, I suddenly received an email notifying me that my server had been frozen due to high CPU usage. It turned out that the warp-svc process had started consuming excessive CPU resources for no apparent reason.
Then more issues appeared. I found that I could no longer run scripts that download many files from GitHub. Why? Because I kept getting timeouts ranging from 3 to 15 minutes on different IPs. On top of that, an SFTP bug emerged — the connection would “die” after a short time, reconnection didn’t help, and only relogin restored access.
After several days of failed attempts to fix the situation myself, I opened a support ticket. Two or three days went by in a very slow and unproductive exchange. Eventually, support told me the problem was on Fastly’s side. That’s when I turned to ChatGPT. With its help, I ran diagnostics and submitted the results in the ticket. ChatGPT even drafted a plan of action for the support team to resolve the issue and recommended temporarily disabling neoprotect.
The provider gave me an IP without neoprotect, and some of the problems disappeared — I stopped getting random timeouts on all GitHub IPs, SFTP stopped disconnecting, and warp-svc no longer overloaded the CPU. However, one problem remained: a “dead” GitHub IP. It’s the only one that’s unreachable for me, but it’s almost always the first address resolved, so I can’t download anything from GitHub — timeouts reach up to 15 minutes per file.
I also tested other servers I own from different providers and regions, and I couldn’t reproduce this GitHub issue anywhere else.
So, what I needed from support was clear: properly configure neoprotect, which after the upgrade began seriously disrupting network performance; temporarily remove the “dead” GitHub IP so I could download necessary files without long delays; contact Fastly if the problem was on their side, or fix it if it was on the provider’s side.
Instead, I received the following response: “The problem with GitHub isn’t on our side. It may resolve itself over time. The server is fully operational. We can re-enable neoprotect if you want.”
My overall impression is that the support team simply doesn’t want to do their job. Declaring a server “fully operational” when it’s impossible to use the main software source feels like mockery. I’m not sure if I’ll renew my subscription if this continues — it’s been a week since I’ve been able to use my VPS, and it’s still unclear whether I’ll be able to at all.
We would like to clarify the situation regarding the feedback posted.
The customer reported slow or failed connections from his VPS to GitHub. After thorough verification, we confirmed that our infrastructure and NeoProtect DDoS protection system are fully operational, and that no internal fault or configuration change has occurred.
It is also important to note that the recent network upgrade did not modify NeoProtect in any way, its configuration, routing, and filtering policies remain exactly the same as before.
To assist the customer and rule out every possible factor, we temporarily assigned him a new IP address routed through a lighter protection profile, with less aggressive filtering, to test whether NeoProtect could have been involved. The behavior remained identical, which clearly confirmed that the protection system was not the cause of the issue.
The connectivity problem affects only one external Fastly/GitHub anycast node (185.199.108.//), which occasionally experiences routing or latency issues depending on Fastly’s global paths. All other GitHub IPs respond normally, and our network connectivity remains stable and consistent.
We explained this clearly to the customer, but he continued to insist that we “fix” an external routing issue that does not depend on us, often copying and pasting text generated by ChatGPT as if it were authoritative technical instruction. While we appreciate initiative, those AI-generated suggestions were not technically accurate or applicable in a real network environment.
Before publishing this feedback, the customer also mentioned that he would “post about this on LowEndTalk” as a form of pressure. Nevertheless, and despite that, we have opened tickets with our upstream providers to check whether a route optimization or alternative path can be arranged to help him, even though we cannot guarantee any result, since the problem lies outside our administrative domain.
In summary, our infrastructure and NeoProtect remain fully operational, the issue is external to our network, and we are still making every reasonable effort to assist.