NYC Ryzen 9000 VPS FLASH SALE | 50% OFF | 2GB @ $3/mo | 4GB @ $6/mo | Unmetered BW

Fourplex · July 25

@timmmy said:

@zed said:

@Fourplex said:

@gbzret4d said:

@timmmy said:

@taizi said:
can anyone remind me what happen of this provider?

let @fourplex tell us...and lets see if he will tell the truth

@Fourplex what happened?

When we were starting out, we massively mishandled our offer threads. This led to basically unsustainable offers for both us and customers. In fact, our old offers were never profitable.

We got customers who only used service us for 3 or 4 months and then left. IPv4 and PayPal fees meant a $3.50/mo VPS customer plus "credit boosts" (often being your bill times four) would never break even. It should've been obvious it was ripe for abuse.

It was probably the biggest mistake we made. And I'll admit: the ban was the correct thing at the time. The time away also helped us restructure our business model and reach profitability.

We have since substantially revamped our policies and business, which is partially why we're profitable. Yes, we noticed a discrepancy back in December. But by the time we tried to fix it the tag was suspended.

Now, we offer sustainable, high-quality services without gimmicky offers. This means no more "scammy" giveaways and "credit boosts" or bumping, only brutally honest VPS hosting.

EDIT: Fix typo.

i thought you lost your tag for winning your own giveaways?

he admitted before and deleted it...but people already saw what he wrote...and no one should trust a provider with this behavior

I admitted this here in:

This means no more "scammy" giveaways and "credit boosts" or bumping

Basically learning from the past, so it's not gonna happen now.

zed · July 25

@Fourplex said:

@timmmy said:

@zed said:

@Fourplex said:

@gbzret4d said:

@timmmy said:

@taizi said:
can anyone remind me what happen of this provider?

let @fourplex tell us...and lets see if he will tell the truth

@Fourplex what happened?

When we were starting out, we massively mishandled our offer threads. This led to basically unsustainable offers for both us and customers. In fact, our old offers were never profitable.

We got customers who only used service us for 3 or 4 months and then left. IPv4 and PayPal fees meant a $3.50/mo VPS customer plus "credit boosts" (often being your bill times four) would never break even. It should've been obvious it was ripe for abuse.

It was probably the biggest mistake we made. And I'll admit: the ban was the correct thing at the time. The time away also helped us restructure our business model and reach profitability.

We have since substantially revamped our policies and business, which is partially why we're profitable. Yes, we noticed a discrepancy back in December. But by the time we tried to fix it the tag was suspended.

Now, we offer sustainable, high-quality services without gimmicky offers. This means no more "scammy" giveaways and "credit boosts" or bumping, only brutally honest VPS hosting.

EDIT: Fix typo.

i thought you lost your tag for winning your own giveaways?

he admitted before and deleted it...but people already saw what he wrote...and no one should trust a provider with this behavior

I admitted this here in:

This means no more "scammy" giveaways and "credit boosts" or bumping

Basically learning from the past, so it's not gonna happen now.

you're basically a pretzel with all the bending you're doing pretending to come clean without actually admitting shit. imagine reframing your cheating the community as "mishandling" offers and looking for sympathy because your business wasn't sustainable. didn't you even blame family for making you scam the giveaway? ah yea
https://lowendtalk.com/discussion/comment/4721724/#Comment_4721724

at no point have you actually taken responsibility or come clean.

listen most people aren't going to give a shit but unless you actually own it it's going to come back at you forever because it's entertaining to watch you squirm and wriggle.

just man up so you can shut it down when it's brought up next time.

Fourplex · July 25

@Fourplex said:
I have changed your IP address. It's just that being a small business, we operate on EST/EDT daytime hours.

UPDATE: @user0990's issue has been resolved. They said they can now access their service when I moved from a 147.X to a 23.X IPv4.

user0990 · July 25

@Fourplex said: I have changed your IP address. It's just that being a small business, we operate on EST/EDT daytime hours.

>
Thanks, appreciate you sorting it out. The new IP resolved the connectivity issue on my end — tunnel connects reliably now. All good, no further action needed. 🙏

forest · July 26

@zed said: at no point have you actually taken responsibility or come clean.

listen most people aren't going to give a shit but unless you actually own it it's going to come back at you forever because it's entertaining to watch you squirm and wriggle.

just man up so you can shut it down when it's brought up next time.

Honestly yeah, if the topic comes up it's best to just be brutally honest and admit you did something stupid, got caught, and had to pay the price of a ban. Hearing a real person say that they fucked up is a lot more relatable than hearing what sounds like a corporate passive voice "mistakes were made" answer. Owning it up is the best way to regain trust.

Just something like "We did a giveaway contest and realized we really shouldn't have done that but it was too late, and we made the stupid decision of winning our own giveaway to get out of it. It was a shitty thing for us to do and we really didn't think it through. It's not going to happen again." would be received much better than referring to it as a "scammy giveaway".

I do get that it's not something you'd really want to be brought up in a flash sale, but people won't ask forever. Evading it will only cause it to become bigger, but admitting to it without being defensive will work wonders. We're all humans and humans make mistakes, and people get that, but we also like drama. The best way to regain trust and avoid drama is to be upfront.

Fourplex · July 26

@forest said:

@zed said: at no point have you actually taken responsibility or come clean.

listen most people aren't going to give a shit but unless you actually own it it's going to come back at you forever because it's entertaining to watch you squirm and wriggle.

just man up so you can shut it down when it's brought up next time.

Honestly yeah, if the topic comes up it's best to just be brutally honest and admit you did something stupid, got caught, and had to pay the price of a ban. Hearing a real person say that they fucked up is a lot more relatable than hearing what sounds like a corporate passive voice "mistakes were made" answer. Owning it up is the best way to regain trust.

Just something like "We did a giveaway contest and realized we really shouldn't have done that but it was too late, and we made the stupid decision of winning our own giveaway to get out of it. It was a shitty thing for us to do and we really didn't think it through. It's not going to happen again." would be received much better than referring to it as a "scammy giveaway".

I do get that it's not something you'd really want to be brought up in a flash sale, but people won't ask forever. Evading it will only cause it to become bigger, but admitting to it without being defensive will work wonders. We're all humans and humans make mistakes, and people get that, but we also like drama. The best way to regain trust and avoid drama is to be upfront.

I agree with you. The "giveaways" were simply a stupid way to bump threads. That's it. They were always rigged.

And even then it didn't really work well, why is why "shilling" was used.

I only did a "flash sale" now because we're going to run out of IPv4, however, and getting new IPv4 takes about a week to provision. We do have enough for the sale.

rpqu · July 26

@Fourplex said:

@forest said:

@zed said: at no point have you actually taken responsibility or come clean.

listen most people aren't going to give a shit but unless you actually own it it's going to come back at you forever because it's entertaining to watch you squirm and wriggle.

just man up so you can shut it down when it's brought up next time.

Honestly yeah, if the topic comes up it's best to just be brutally honest and admit you did something stupid, got caught, and had to pay the price of a ban. Hearing a real person say that they fucked up is a lot more relatable than hearing what sounds like a corporate passive voice "mistakes were made" answer. Owning it up is the best way to regain trust.

Just something like "We did a giveaway contest and realized we really shouldn't have done that but it was too late, and we made the stupid decision of winning our own giveaway to get out of it. It was a shitty thing for us to do and we really didn't think it through. It's not going to happen again." would be received much better than referring to it as a "scammy giveaway".

I do get that it's not something you'd really want to be brought up in a flash sale, but people won't ask forever. Evading it will only cause it to become bigger, but admitting to it without being defensive will work wonders. We're all humans and humans make mistakes, and people get that, but we also like drama. The best way to regain trust and avoid drama is to be upfront.

The "giveaways" were simply a stupid way to bump threads. That's it. They were always rigged.

I know it !

forest · July 26

@Fourplex Can you check if you can access 66.28.0.45 and 66.28.0.61 from within the VPS? Those are the Cogent upstream DNS resolvers, but I believe they only allow access from a Cogent address space.

Fourplex · July 26

@forest said:
@Fourplex Can you check if you can access 66.28.0.45 and 66.28.0.61 from within the VPS? Those are the Cogent upstream DNS resolvers, but I believe they only allow access from a Cogent address space.

These revolvers do work within our VPSes:

root@home:~# host google.com 66.28.0.45
Using domain server:
Name: 66.28.0.45
Address: 66.28.0.45#53
Aliases: 

google.com has address 142.250.113.102
google.com has address 142.250.113.139
google.com has address 142.250.113.100
google.com has address 142.250.113.101
google.com has address 142.250.113.138
google.com has address 142.250.113.113
google.com has IPv6 address 2607:f8b0:4023:1000::71
google.com has IPv6 address 2607:f8b0:4023:1000::66
google.com has IPv6 address 2607:f8b0:4023:1000::64
google.com has IPv6 address 2607:f8b0:4023:1000::8a
google.com mail is handled by 10 smtp.google.com.
root@home:~# host google.com 66.28.0.61
Using domain server:
Name: 66.28.0.61
Address: 66.28.0.61#53
Aliases: 

google.com has address 142.250.138.100
google.com has address 142.250.138.138
google.com has address 142.250.138.102
google.com has address 142.250.138.113
google.com has address 142.250.138.101
google.com has address 142.250.138.139
google.com has IPv6 address 2607:f8b0:4023:1006::71
google.com has IPv6 address 2607:f8b0:4023:1006::8b
google.com has IPv6 address 2607:f8b0:4023:1006::65
google.com has IPv6 address 2607:f8b0:4023:1006::8a
google.com mail is handled by 10 smtp.google.com.
root@home:~#

FYI our IPv4 space has moved from Cogent to Prefix Broker. This move was due to Cogent's high IP abuse fee. For Tor exit operators this allows relays with all ports but SMTP; the restrictive 53/80/443/8080 policy is gone.

forest · July 26

@Fourplex said:

@forest said:
@Fourplex Can you check if you can access 66.28.0.45 and 66.28.0.61 from within the VPS? Those are the Cogent upstream DNS resolvers, but I believe they only allow access from a Cogent address space.

These revolvers do work within our VPSes:

root@home:~# host google.com 66.28.0.45
Using domain server:
Name: 66.28.0.45
Address: 66.28.0.45#53
Aliases: 

google.com has address 142.250.113.102
google.com has address 142.250.113.139
google.com has address 142.250.113.100
google.com has address 142.250.113.101
google.com has address 142.250.113.138
google.com has address 142.250.113.113
google.com has IPv6 address 2607:f8b0:4023:1000::71
google.com has IPv6 address 2607:f8b0:4023:1000::66
google.com has IPv6 address 2607:f8b0:4023:1000::64
google.com has IPv6 address 2607:f8b0:4023:1000::8a
google.com mail is handled by 10 smtp.google.com.
root@home:~# host google.com 66.28.0.61
Using domain server:
Name: 66.28.0.61
Address: 66.28.0.61#53
Aliases: 

google.com has address 142.250.138.100
google.com has address 142.250.138.138
google.com has address 142.250.138.102
google.com has address 142.250.138.113
google.com has address 142.250.138.101
google.com has address 142.250.138.139
google.com has IPv6 address 2607:f8b0:4023:1006::71
google.com has IPv6 address 2607:f8b0:4023:1006::8b
google.com has IPv6 address 2607:f8b0:4023:1006::65
google.com has IPv6 address 2607:f8b0:4023:1006::8a
google.com mail is handled by 10 smtp.google.com.
root@home:~#

FYI our IPv4 space has moved from Cogent to Prefix Broker. This move was due to Cogent's high IP abuse fee. For Tor exit operators this allows relays with all ports but SMTP; the restrictive 53/80/443/8080 policy is gone.

Can you post a UDP traceroute to 66.28.0.45? I just want to make sure that, since you don't run your own resolver, there's a resolver just one or two hops away from the gateway. If it's right there (practically on the local network) then I'll definitely get a VPS. But if you moved away from Cogent on the node that Tor exits go to then it might not be.

Fourplex · July 27

@forest said:
Can you post a UDP traceroute to 66.28.0.45? I just want to make sure that, since you don't run your own resolver, there's a resolver just one or two hops away from the gateway. If it's right there (practically on the local network) then I'll definitely get a VPS. But if you moved away from Cogent on the node that Tor exits go to then it might not be.

Here's a UDP traceroute:

root@home:~# traceroute -U 66.28.0.45
traceroute to 66.28.0.45 (66.28.0.45), 30 hops max, 60 byte packets
 1  _gateway (147.90.234.1)  0.465 ms  0.423 ms  0.401 ms
 2  69.12.96.65 (69.12.96.65)  1.935 ms  2.337 ms  2.632 ms
 3  * * *
 4  * * *
 5  * * *
 6  be3202.ccr42.jfk02.atlas.cogentco.com (154.54.90.65)  1.436 ms be2997.ccr41.jfk02.atlas.cogentco.com (154.54.89.177)  1.494 ms be3202.ccr42.jfk02.atlas.cogentco.com (154.54.90.65)  1.449 ms
 7  be2896.rcr23.jfk01.atlas.cogentco.com (154.54.84.202)  2.913 ms be2897.rcr24.jfk01.atlas.cogentco.com (154.54.84.214)  2.024 ms be2896.rcr23.jfk01.atlas.cogentco.com (154.54.84.202)  2.067 ms
 8  be2803.rcr21.b001362-2.jfk01.atlas.cogentco.com (154.54.45.230)  1.996 ms  1.854 ms  2.210 ms
 9  res1.dns.cogentco.com (66.28.0.45)  1.444 ms  1.410 ms  1.417 ms
root@home:~#

forest · July 27

Ah damn. I guess I'll have to pass then, sorry.

If you do ever set up your own recursive resolver for people to use (e.g. listening on the gateway), please do ping me!

Fourplex · July 27

@forest said:
Ah damn. I guess I'll have to pass then, sorry.

If you do ever set up your own recursive resolver for people to use (e.g. listening on the gateway), please do ping me!

Ah, so sorry to hear that.

However, that's fine. We can't have two-hop connections to every destination. After all we are downstream of Metanet, which uses Megaport, which in turn uses Cogent and GTT.

If we ever set up a resolver we'll be sure to let you know.

rpqu · July 27

@Fourplex said:

@forest said:
Ah damn. I guess I'll have to pass then, sorry.

If you do ever set up your own recursive resolver for people to use (e.g. listening on the gateway), please do ping me!

Ah, so sorry to hear that.

However, that's fine. We can't have two-hop connections to every destination. After all we are downstream of Metanet, which uses Megaport, which in turn uses Cogent and GTT.

Metanet or megaport doesn't have resolver?

Fourplex · July 27

@rpqu said:
Metanet or megaport doesn't have resolver?

Unfortunately, Metanet doesn't. I'm not sure about Megaport.

I normally use Cloudflare as a resolver.

Howdy, Stranger!

Categories

In this Discussion

NYC Ryzen 9000 VPS FLASH SALE | 50% OFF | 2GB @ $3/mo | 4GB @ $6/mo | Unmetered BW

Comments

Howdy, Stranger!

Quick Links

Categories

In this Discussion

NYC Ryzen 9000 VPS FLASH SALE | 50% OFF | 2GB @ $3/mo | 4GB @ $6/mo | Unmetered BW

Comments